At the moment I doing some tests with webp and I try to understand this topic.
I do not know how well 'native' webp support of Thirtybees (and moreover a compatible theme like Panda that officially supports webp - whatever that means) goes with apache mod: pagespeed_mod.
The later is supported via my host Hetzner. I can activate it via host's console and some addings to my htaccess. I hope to benefit from pagespeed_mod in terms of pagespeed (and ranking). I hope that it may work better that Prets/Thirtybees CCC option in backoffice performance. Noteworthy is here that I am on a shared host. So ressources matter and I do not know how excactly pagespeed_mod works but I believe that on my host's server a caching folder exists next to my Thirtybees install where optimized css, js, htmk and webp images are stored for access. If this is fast that CCC in Thirtybees I do not know. So, when I use pagespeed_mod I deactivate all CCC in Thirtybees.
I also do not know if pagespeed_mod detects in the case we use Thirtybees wepb option that the product image already exists physically in webp format and there wont try to recompress/reprocess since this would cost time.
In a nutshell I would be very happy if some one could be so kind to explain these thing here to me. My aim is ofcourse to speed up my shop and loading time.
On top of my htaccess I added:
<IfModule pagespeed_module>
# exclusion configuration (mandatory for some JS editors and frameworks) testen ob aktuell noch betroffen! 2020.10
# Lossy image recompression quality (0 to 100, -1 just strips metadata):
# !! This option sets the quality for JPEG and WebP formats. It can be overridden by any format-specific or application-specific quality. The default is 85.
#ModPagespeedImageRecompressionQuality 85
# Jpeg recompression quality (0 to 100, -1 uses ImageRecompressionQuality): This option sets the quality for JPEG images. It overrides ImageRecompressionQuality, unless it is set to -1. The default value is 85.
Question
Pedalman
At the moment I doing some tests with webp and I try to understand this topic.
I do not know how well 'native' webp support of Thirtybees (and moreover a compatible theme like Panda that officially supports webp - whatever that means) goes with apache mod: pagespeed_mod.
The later is supported via my host Hetzner. I can activate it via host's console and some addings to my htaccess. I hope to benefit from pagespeed_mod in terms of pagespeed (and ranking). I hope that it may work better that Prets/Thirtybees CCC option in backoffice performance. Noteworthy is here that I am on a shared host. So ressources matter and I do not know how excactly pagespeed_mod works but I believe that on my host's server a caching folder exists next to my Thirtybees install where optimized css, js, htmk and webp images are stored for access. If this is fast that CCC in Thirtybees I do not know. So, when I use pagespeed_mod I deactivate all CCC in Thirtybees.
I also do not know if pagespeed_mod detects in the case we use Thirtybees wepb option that the product image already exists physically in webp format and there wont try to recompress/reprocess since this would cost time.
In a nutshell I would be very happy if some one could be so kind to explain these thing here to me. My aim is ofcourse to speed up my shop and loading time.
On top of my htaccess I added:
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now