Hey @playzare,
The plugin converts images to WebP automatically. You can check in Firefox or Chrome dev tools.

Normally gzip compression should also be done automatically. But there seems to be an issue with o2switch. I’ll create an account with o2switch and test this myself, and hopefully find a solution.
–Albert
Hi @playzare,
It turns out that o2switch does compress responses with the MIME type application/json, which is used by PhastPress.
I’ve released version 1.97 which changes this MIME type to text/plain. This should cause o2switch to automatically apply brotli or gzip compression.
Could you update to version 1.97 and let me know whether this solves the issue?
–Albert
Hi @kiboit yeah it’s perfect now !!! Thank you very much!
I saw that oxygen builder doesn’t like phastpress in edit mode, do you plan to add an option to disable it for administrators ? I see there is already the opposite.
Thanks again for this perfect plugin, way better than autoptimize !
Best regards,
-
This reply was modified 5 years, 7 months ago by
Playzare.
Hi @playzare,
Oxygen Builder was not yet supported. I’ve just released version 1.98 with a fix for Oxygen Builder. No need to change any settings.
Let me know if this resolves the problem.
–Albert
Hi @kiboit perfect it’s fully compatible now !!
Thank you very much for this very quick support and this plugin.
Is it possible to make a donation to you?
Best regards
Hi @playzare,
Great. 🙂
If you’d like, you can donate via PayPal to info@kiboit.com.
–Albert
Hey @playzare,
Thanks for your donation!
This latest issue should only happen on the first load, because a CSS stylesheet has not been cached yet. After the page is optimized a second time, it should be fixed.
But when using caching it is possible that a partially optimized version is shown. In this case, clearing your full page cache (WP Fastest Cache in your case) should help.
Could you try clearing your WP Fastest Cache, and seeing if this fixes the issue?
–Albert
Hi @kiboit i tried to clear everything and to preload manually on a New private tab but pagespeed displays the same notice!
Do you think it’s an issue with wpfc ? Do you recommend another cache plugin fully compatible with phastpress to remove this notice ?
Thanks for your Time
Best regards
Hi @playzare,
It’s very strange. The same notice doesn’t show when you add ?1 or another query string to the URL to get a fresh version, and neither does it show when I test it with Lighthouse in a local Chrome. So I don’t know where it comes from. I would ignore it for now and see if it persists when you go into production.
I think WP Fastest Cache should work fine. I always use WP Super Cache, it is simpler and developed by Automattic.
There’s one weird thing about your site: the first time you open it, if you don’t have cookies set, it loads, and then reloads. You can test this by opening it in a private browser window (incognito mode).
It’s because of this script on your site:
/wp-content/plugins/borlabs-cookie/javascript/borlabs-cookie.min.js
This plugin “Borlabs Cookie” seems to have a “Reload after consent” setting that causes a reload on the first visit even if I don’t click anything. That should probably be fixed by disabling this setting or using another plugin.
–Albert
Thanks for your time !! Seems better when i disable Borlabs so i think you are right !! Very good news!
Sorry for the time spent on your side 🙁
Best regards !