Albert Peschar

Hi Mukesh,

I’m happy to help, but cannot do so without an example of the problem where I can diagnose the cause. So if you’d still like my assistance, please set up a copy of the site with PhastPress enabled, so I can debug the issue.

–Albert

Hi Mukesh,

I see you’ve sent this in a separate message, thank you. I’ll check it out.

–Albert

Hi Mukesh,

Please share the URL of your website, so I can have a look.

–Albert

Yes, they are dynamic, and they will change. So all URLs containing (or beginning with) wp-content/plugins/phastpress/phast.php should be whitelisted.

Hi there,

Thanks for trying out PhastPress.

The problem you’re seeing is due to mod_security, a security plugin that your web hoster is using. Mod_security is making URLs like these inaccessible:

…/wp-content/plugins/phastpress/phast.php?service=scripts&src=https%3A%2F%2Fwww.google-analytics.com%2Fanalytics.js&cacheMarker=218127

Because I’ve seen similar issues before, I’ll see if I can fix this in PhastPress somehow, by changing the URLs so they don’t trigger mod_security. I’ll have a look at it coming weekend and get back to you.

Alternatively, you can ask your web hosting provider to exclude URLs starting with …/wp-content/plugins/phastpress/phast.php from mod_security.

–Albert

Hi rvdpteg,

I’m sorry. WordPress forum policies do not allow me to accept login details through these forums.

https://www.ads-software.com/support/guidelines/#the-bad-stuff

You can use the Health Check plugin to save some debugging information about configuration and plugins and post on Pastebin. Perhaps we’ll be able to see what’s going on that way.

https://make.www.ads-software.com/support/handbook/appendix/troubleshooting-using-the-health-check/

–Albert

Hi rvdpteg,

Are you sure that PhastPress is enabled? It looks like it’s not. When opening the developer console there should be a message saying “Optimized with PhastPress”.

Maybe there’s another optimization plugin that’s conflicting with it… Try disabling those one by one to see if it makes a difference.

You can also tell from the GTmetrix report that PhastPress isn’t working, because the request count should be much lower, and image URLs should refer to phast.php. https://gtmetrix.com/reports/atlastoilets.com/rKiUcaEa

–Albert

Hi rvdpteg,

Thanks for trying out PhastPress.

I can have a look at your site, if you enable the plugin and post a screenshot of the GTmetrix report and the rule that you are having trouble with (after PhastPress is activated).

–Albert

Beste Arnout,

De rich snippet tekst is helaas alleen in het Nederlands beschikbaar.

Wel is er sinds kort de mogelijkheid om de rich snippet via de WebwinkelKeur sidebar te plaatsen. Er staat dan geen tekst meer op de pagina, maar de informatie over de reviews wordt met verborgen metadata aan Google getoond.

Meer info hier: https://www.webwinkelkeur.nl/faq/hoe-activeer-ik-rich-snippet-sterren/

–Albert

Thank you Giorgos! I haven’t forgotten, but I haven’t gotten around to it yet, either. I’ll let you know personally as soon as this feature has been added.

Hey cck23,

Thanks for your review!

Are you using some kind of lazy loading plugin that uses data-src. It’s true that PhastPress doesn’t process this attribute on img tags. But perhaps you can disable the lazy loading plugin or functionality in your theme? (Lazy loading doesn’t really help in reality.)

–Albert

Hi Barold,

Thanks for the report, and your detailed analysis.

Rendering shouldn’t be dependent on JavaScript (at least most of it), otherwise you’ll get this problem.

It would be possible to add the feature you describe (excluding scripts based on name or path). However, this goes against the zero configuration approach PhastPress attempts to take. Furthermore, when you exclude certain scripts, you are likely to run into problems regarding dependencies. For instance, WP Bakery might require jQuery, and it’s not possible to keep track of this automatically.

For now, it’s not something I’m planning to implement.

–Albert

Hi,

Thanks for using PhastPress!

I’ve fixed these warnings in the latest version that was just uploaded, 1.20.

If you like PhastPress, I would really appreciate a review here: https://www.ads-software.com/support/plugin/phastpress/reviews/#new-post

–Albert

Hi all,

Interestingly, Phast should already add font-display: swap to all webfonts in order to fix this issue. It seems that for some reason it didn’t/doesn’t work in your case.

I’m going to mark this as resolved for now, should you run into the same issue in future, please let me know and I’ll find out why it isn’t working.

–Albert

Hi there,

Looks like you’re no longer using PhastPress at the moment, so I’m not able to see the issues anymore.

In any case, you are now using W3 Total Cache, of which not all features are compatible with PhastPress. That might have caused some of the issues you were seeing.

If you’d like me to have another look, please re-enable PhastPress.

–Albert