Albert Peschar

Hi Sam,

Thanks for letting us know about that issue. I haven’t tested with Divi pagebuilder recently, so I’ll make a not of that and fix it in an upcoming release.

–Albert

PS: Please open a new topic next time, instead of posting in an existing one.

Hi there,

Thanks for trying out PhastPress.

The issue you describe is usually due to some script on the page that animates the load, or changes content (like A/B testing scripts such as Google Optimizer). Unfortunately, it’s hard to say without manual testing what the exact cause is.

I would first try disabling all other optimization plugins, and any animations/lazy loading in the theme, and seeing if that fixes the issue.

–Albert

Hi Giorgos,

Yeah, I see, that’s annoying. Unfortunately, I cannot think of a quick way to change the URL to the file that serves resources in Phast.

For now, you could disable image optimization in PhastPress. That will save most of the bandwidth.

I’ll be on a holiday soon until the end of the month, but I’m going to have a look if I can add this functionality to Phast in July. I’ll keep you posted.

–Albert

Barold,

I’m happy to hear that.

I have one additional tip for you: if I turn off JavaScript, the content of the page doesn’t render. See: https://peschar.net/s/uIZwNqp108wl02EhPgDe/

That might be due to some animations in the theme, or some kind of lazy loading plug-in. In any case, if you change this so that the page can render without JavaScript, it will improve the perceptual load speed of the page enormously.

–Albert

P.S.: I would recommend turning off other optimization software (except caching), such as WP Rocket and Cloudflare Rocket Loader, since those can conflict with PhastPress, and don’t offer important added functionality.

• This reply was modified 5 years, 9 months ago by Albert Peschar.

Hi Barold,

I’ve testing your GTM script on a local install of PhastPress, and I’m not seeing the same problem, unfortunately.

There is in fact a way to exclude scripts, but it requires editing the source code:

Would you be able to adjust the <script> tag to contain a data-phast-no-defer attribute? For example: <script data-phast-no-defer> (GTM code here) </script>. That should disable Phast for that particular script.

–Albert

Amibe,

No, unfortunately not. You will have to make the path in wp-content accessible in order for PhastPress to work.

Please create a new topic if you have further questions. (So that the original topic owner doesn’t get notifications.)

–Albert

Hi Barold,

Thank you for trying out PhastPress.

Unfortunately, it’s not yet possible to exclude scripts from optimization. On the other hand, Google Tag Manager should work nevertheless, even with PhastPress enabled.

If you share the URL to your site, I could take a look and perhaps find out why it doesn’t work with script optimization enabled.

–Albert

Phast uses at least one execution per image, plus 2 executions per page (one for all JS, one for all CSS). So that is probably the reason for the high execution count.

Your hosting provider limits the executions you use to maximize the amount of sites per server, and PhastPress requires some additional executions in order to optimize images.

It seems you are using SiteGround. In that case, please check that you have the static cache enabled.

Otherwise I can only suggest that you upgrade your hosting package or move your site to a VPS (UpCloud is very fast) to get rid of resource limitations.

Normally, when this problem occurs, you should be able to see it in the developer tools console on your site. In this case, that doesn’t seem to be happening. That means it only occurs sometimes.

Maybe something weird is happening to PhastPress’s cache– it is perhaps being emptied at different times. Or there is something else going on that I’m not aware of.

Exactly how many of these errors do you see in a 24-hour period, and how does this compare to the amount of visits you have? Are you able to send me the error log perhaps?

–Albert

Well, there are two legitimate reasons that PhastPress might cause more PHP scripts to run (I think this is what your host means with executions):

• Firstly, PhastPress loads images via a PHP script, so that they can be optimized. The optimized image is cached though, and this shouldn’t cause much load on the server. (But it might contribute to the count of ‘executions’.)
• Secondly, PhastPress also loads all CSS files through a single request per visit, and all JS files in the same way. Similarly as with the images, optimized versions are cached, so this shouldn’t cause trouble.

It is possible that something isn’t working right on your site, causing more load than usual. In that case, warnings should be visible in the developer console. You can also share your site URL with me, and I’ll have a look.

Your configuration should be correct: Use WP Rocket only for caching, disable all other optimizations. They are superfluous when you use PhastPress, and some of them conflict. (Especially everything that has to do with JavaScript loading.)

Hi Giorgos,

This can happen when the Phast cache is cleared, but the full-page cache has not been cleared. In that case, a secret token that Phast stores in its cache is reset, but the cached pages still use the old token.

Although you might not have any caching plugins installed, your hosting provider is nevertheless caching your site’s pages for a maximum time of 28 days. You can verify this by checking your site’s response headers in developer tools:

< HTTP/2 200 
< server: nginx
< date: Sun, 19 May 2019 13:49:39 GMT
< content-type: text/html; charset=UTF-8
< content-length: 528015
< expires: Thu, 19 Nov 1981 08:52:00 GMT
< pragma: no-cache
< last-modified: Sat, 13 Apr 2019 15:52:44 GMT
< wpe-backend: apache
< vary: Accept-Encoding,Cookie
< x-cacheable: YES:2419200.000
< cache-control: max-age=2419200, must-revalidate
< x-cache: HIT: 5
< x-pass-why: 
< x-cache-group: normal
< accept-ranges: bytes
< x-type: default

Usually you should be able to fix the issue by clearing the cache manually using any interface that your hosting provider provides for this.

–Albert

Hi Giorgos,

The plugin currently does not support CDNs. We hope to fix that in an upcoming release.

A CDN is most useful when you have users from multiple continents. In that case I would recommend that you use Cloudflare. It offers a CDN for your entire site, and works automatically with PhastPress.

–Albert

Hi unalgu,

Can you confirm that you deleted only the W3 Total Cache files? Because it seems that it’s still a full-page caching issue. Are you clearing the cache via the W3 Total Cache settings, or otherwise?

For example, I see the issue on this URL:

https://www.society19.com/

But not when I add a random parameter to avoid the cache:

https://www.society19.com/?2019

If you did indeed only clear the W3 Total Cache again, and the issue persists, could you install the Health Check plugin and post the debug information and paste it here? (See instructions.)

–Albert

Hey unalgu,

Sorry, I think my message was unclear. I understand you deleted this:

• W3 Total Cache full-page cache
• PhastPress cache folder

When PhastPress is used, it generates a token (a kind of password) that is used to sign the URLs for images, CSS, JS, etc., to avoid changing the URLs (allowing users to overload the server by resizing images, etc.).

You should not empty the PhastPress because it resets the token. If someone loads a page before you do the reset, that page will have the old token in the full-page cache, then you empty the PhastPress cache, and the token is reset. Those pages in the full-page cache with the old token no longer work.

So could you try again to empty only the W3 Total Cache? Please let me know how it goes– if you still have the issue I’ll make sure it gets fixed.

–Albert

• This reply was modified 5 years, 12 months ago by Albert Peschar. Reason: Formatting