Albert Peschar

This FAQ entry should answer your question:

https://www.ads-software.com/plugins/phastpress/#can%20i%20optimize%20images%20without%20changing%20their%20urls%3F

I’m afraid not. It has not been a consideration in implementing this image optimization feature.

> Status: Not connected even when Redis available and the plugin is enabled

You need a Redis server installed and available on your hosting to use Redis Object Cache.

> CDN

PhastPress does not provide CDN integration. I would recommend Cloudflare instead of a separate CDN.

> 1. Add Missing Sizes?

Not sure what this means exactly, but PhastPress probably does not do it.

> 2. Image WebP Replacement ?

PhastPress does this.

> 3. Optimize Original Images

Not sure what this means. PhastPress can optimize images on the original URL. See the FAQ for instructions.

> will it be ok to use along side docketcache ?

PhastPress does not do any object caching, so there should be no conflict. But for object caching I would suggest Redis Object Cache.

https://www.ads-software.com/plugins/redis-cache/

> Small side wphive say the plugin has some issues

I think it’s just a problem with their testing. None of those issues have come up in real life. In any case they do not provide sufficient detail to look into their reports.

Hi @snipsnip,

I see. So this is delaying the rendering of those elements.

https://css-tricks.com/almanac/properties/c/content-visibility/

It’s an interesting feature but I don’t currently have any plans to add this to PhastPress.

–Albert

Any optimizations (HTML/CSS/JS/images) should be disabled. See the FAQ.

Hi @snipsnip,

Do you move some content to AJAX requests, or do I misunderstand?

–Albert

Hi @akgt,

Should work fine. You don’t have to change any of PhastPress’ settings, the defaults should work.

–Albert

Hi @reelism,

There should be no need for additional configuration. It should just work.

–Albert

Hi @kw11,

Thanks for your testing.

I have released version 2.10 which reverts back to using application/json as the MIME type on bundler responses, and removes the X-Robots-Tag header.

Hopefully this will prevent the issue in future.

–Albert

Hi @markdenis,

There’s no setting. It should happen automatically when image optimization is enabled.

It only converts JPEG, not PNG.

–Albert

Hi @kw11,

I’m actually not sure what will happen.

On the one hand, it doesn’t stop Google from indexing the content of your page.

On the other hand, it prevents Google from using the Phast bundler, and I’m not sure what that will do to Google’s impression of your site’s performance.

I edited the plugin so the Content-Type to application/json; charset=utf-8. I’ll let you know what Googlebot thinks in a few days. On our server, it’s automatically Brotli compressed.

Thanks for this. I’m looking forward to hearing the results of this experiment. If it makes a big difference I may add a setting to the plugin.

–Albert

• This reply was modified 2 years, 4 months ago by Albert Peschar.

Hi @mukaaartz,

In this case the filter should be written like this:

add_filter('wp_enqueue_scripts', function () {
  wp_scripts()->add_data('burst', 'phast_no_defer', true);
  wp_scripts()->add_data('burst-timeme', 'phast_no_defer', true);
});

In any case, I’ve just released PhastPress 2.8 which includes this filter so that Burst Statistics scripts are automatically not delayed by PhastPress.

–Albert

Hi @alx359,

Generally, it’s not necessary to use persistent object cache, if your server is fast enough.

When I do use a persistent object cache, I go for Redis Object Cache.

–Albert

Hi @kw11,

We cannot prevent the initial request to phast.php from happening by changing the headers on that response. Because the headers are retrieved only after actually making the request.

So I suggest adding phast.php to your robots.txt. There’s nothing there that should be crawled by Google.

–Albert