Adlago

Achieving good results does not happen by changing just one parameter. Your site probably has other reasons for delays. If you want, send me a PM with a link to your site so I can do some tests.

Even in older versions 4.x I found that when the time cache block expires there is a sharp increase in the first byte (i.e. the first visitor to a site gets it) - that's why this parameter was always set to 1 hour for me. Now it's the same on 4.7.19. I had it set like that back in the first beta 5.0. Now in beta 8 - I noticed that only the cache block expiration time test has excellent results. Or simply put, with 1 hour cache a site is doomed to poor results for 1 hour. Now with 5 minutes - there are many more excellent test results. My suspicion is that after caching blocks, the first visitor to a site has an excellent experience (after which probably for some reason all blocks are non cached until the expiration time set in ACP - advanced, and then cached again until the first next visit) - i.e. please test this hypothesis. Keep in mind that PSI test uses additional network latency for mobile (slow 4G). I used "fast 3G" in my tests - and what I noticed was a very slow loading of "fa-solid-900.woff2" - about 6 seconds. Then I activated one of my hooks with which I eliminate "preload font" and this loading time for the font dropped to 2 seconds. Then I noticed a high result of the network indicators-PSI test, at a time of already cached blocks - and the next test was again 30 points worse. After lowering the cache block time to 5 minutes - excellent results are much more and more regular. I.e. in my opinion there is some issue with the management of cache blocks.

This issue is related to cache blocks. I reduced the cache time to 10 minutes and after a few tests: Then again bad tests, but after 10 minutes again very good. Now I left it at 5 minutes - and again often very good test results. @Matt Please review the "Cache sidebar, header and footer blocks" management.

I don't like Cloudflare - and in general any configuration related to cache prioritization. In my hosting plan I have the option (and I used it for two years) to configure an Apache main server and an Nginx cache server. Due to the fact that cache management from Nginx and cache managed by the IPS platform cannot be synchronized to be maximally effective, and I have seen all sorts of antilogical states in the thousands of tests I do (this is my hobby - not a commitment) - I gave up using the Nginx server and now I work only with Apache - and this completely satisfies me.

In beta 7, the images were the same, and as can be seen from the test linked in my first post on this topic, it is comparable in performance to that of 4.7.19 - unlike the lowered performance for beta 8.

Why do I think beta 8 has a degradation? Here are two tests - 4.7.19 and 5.0. beta 8 - on the same server, same admin (ha ha), same test platform - with a difference of a few minutes...

@Gary Your LCP is a text block that actually has a large render delay

This

The only difference I see in the test is what I wrote above - too much delay of FCP and LCP. And that is provided that the first byte is under 200 milliseconds and TBT is 20 ms. It is inexplicable to me because I have not changed anything regarding images in blocks and anything else between beta 7 and beta 8. See test now

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.

Maybe this will be useful - All activity was loaded in my browser (FF latest version). I haven't been in front of my laptop for more than an hour. When I was there again and opened a browser, I reloaded the page and what is in the picture appeared - even so many repetitions after scrolling.

The home page of my test site is built only with Pages/blocks. Earlier this month, the PSI corrected the "CPU throttling factor" 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. Shortly after that, you activated beta 7 - I shared in the corresponding article about beta 7 - the sharp improvement in all network indicators. Now, after updating to beta 8 - mobile performance is already severely reduced, (65-75 points) without me having made any changes to my page.

@Matt What is noticeable in beta 8 (excluding bugs) is a sharp decrease in mobile performance - by more than 20 points compared to beta 7.