After updating to beta 8, there is a decrease in performance. What I mean is:
- on December 5, PSI made a useful adjustment to its test platform, which eliminated the large TBT times.

Dec 5, 2024
The CPU throttling factor for PageSpeed Insights has been adjusted to account for the low CPU performance benchmarks typical in PageSpeed Insights production environments. In general, this should result in increased lab data TBT scores for sites on mobile. Field data and desktop scores should not be affected. 

On December 7th, after updating to beta 7, PSI tests showed perfect performance, which I wrote about:

 

Now, after updating to beta 8 - mobile performance is already severely reduced, (65-75 points) without me having made any changes to my page.

What does this decrease mean:
- First Contentful Paint - delayed by over 3 seconds
- Largest Contentful Paint - delayed by over 5 seconds
This happened with beta 8.

@Adlago, you appear to be misunderstanding how the caching works. It's not a local cache on a users machine, it's caching the html for the block server side, so the backend isn't generating it each visit. If you cache it for 1 hour, it'll retrieve the html from that cache for 1 hour, and then check again for an update the first load after that. Once it's done that, it'll cache it again for an hour. 

So, setting it for one hour will make it faster across the hour than setting it for 5 minutes. 

 

Blocks are cached when a user views it for the duration set. There is no background tasks updating data based on that timeframe.

Thanks for the confirmation. Can it be modified, so that it's event based?

If event driven is not possible, schedule would help as well i.e. every 5 mins run 1 query, update block, static block (5 mins)  -> all users get it if it's configured as don't check for permissions. 

 

 

What is the reason you found

This template is loaded after open html tag, before the head tag.

{template="htmlDataAttributes" app="core" group="global" location="front" params=""}

Its content requires too many root css rules. These rules are loaded with a framework css, and it loads slowly...Ie. for these rules needed after the html tag before the head tag there should be a small and pre-loaded css after open head tag.
Checked, created and works correctly (although double loaded) - there is no other option