New version is out! Should fix your problems.
and another issue thanks
LCP breakdown
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.LCPUnscored
We use cookies to enhance your browsing experience, serve personalised ads or c…
Another issue on pagespeed.
It seems google does not like your default colour either.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Accept cookies
<button type=”button” class=”faz-placeholder-btn” data-faz-accept=”marketing” data-faz-accept-service=”youtube”>
I managed to fix most of the issues but this one still exists.
Can it be fixed ?
Render-blocking requests Est savings of 150 ms
https://shoppingonline.global/wp-content/uploads/faz-cookie-manager/assets/banner-1799edcfe9c8b36beeb2ded3eb600069.css
Hi Scott,
Yes, I have checked the remaining banner stylesheet request and the fix will be included in the next release. Your public page is currently serving the 1.34.3 assets with the banner CSS loaded as a normal screen stylesheet, which explains why PageSpeed still lists it as render-blocking.
The update loads the banner stylesheet without blocking the page’s first paint, keeps the small styles needed for blocked-content placeholders inline, and applies the full stylesheet before revealing the banner. The JavaScript configuration and runtime remain deferred while the early consent protections stay active. The placeholder-button contrast correction is also already present in the upcoming code.
After updating, please purge the page/optimisation cache and any CDN cache, then run PageSpeed again against a fresh page. The update targets the remaining CSS render-blocking request; the banner can still be identified as the largest visible element in the separate LCP breakdown.
Fabio
Great stuff thanks ! Looking forward to the next release.
New release fixed it thanks a million