Adlago Posted Monday at 11:40 AM Posted Monday at 11:40 AM 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. sobrenome and konon 2
Management Matt Posted Monday at 11:59 AM Management Posted Monday at 11:59 AM I've reviewed the commits and there's nothing that would change it from our end. There are no structural CSS changes, or changes on how JS/resources are loaded. sobrenome 1
Management Matt Posted Monday at 12:06 PM Management Posted Monday at 12:06 PM What does the report say the delay is caused by? sobrenome 1
Adlago Posted Monday at 01:13 PM Author Posted Monday at 01:13 PM (edited) 1 hour ago, Matt said: What does the report say the delay is caused by? 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 Edited Monday at 01:18 PM by Adlago sobrenome 1
Management Matt Posted Monday at 01:57 PM Management Posted Monday at 01:57 PM If you scroll down, you can check what is causing the delay to FCP/LCP. G17 Media and sobrenome 2
Adlago Posted Monday at 03:56 PM Author Posted Monday at 03:56 PM 1 hour ago, Matt said: If you scroll down, you can check what is causing the delay to FCP/LCP. sobrenome 1
Marco Junior Posted Monday at 04:05 PM Posted Monday at 04:05 PM What website do you use to do these tests? Could you tell me? sobrenome 1
Adlago Posted Monday at 04:07 PM Author Posted Monday at 04:07 PM 2 minutes ago, Marco Junior said: What website do you use to do these tests? Could you tell me? This sobrenome 1
Gary Posted Monday at 10:37 PM Posted Monday at 10:37 PM (edited) I'm getting a better mobile scoring on my vanilla installation of v5 Beta 8, with higher scoring on desktop. I have no plugins or add ons. Edited Monday at 10:38 PM by Gary sobrenome 1
Adlago Posted Monday at 11:12 PM Author Posted Monday at 11:12 PM @Gary Your LCP is a text block that actually has a large render delay sobrenome and konon 2
Gary Posted yesterday at 12:14 AM Posted yesterday at 12:14 AM (edited) Which doesn't really bother me or my members. It has never taken that long for any part of my site to load, whether it be on a mobile or a desktop. Especially considering my target audience are those in Australia and New Zealand. I much prefer focusing on content rather than squeezing every millisecond for a score. Edited yesterday at 12:22 AM by Gary PanSevence, onlyME, dmaidon1 and 1 other 1 3
EliasM Posted yesterday at 11:48 AM Posted yesterday at 11:48 AM For me beta 8 gives a very good performance
Management Matt Posted yesterday at 03:11 PM Management Posted yesterday at 03:11 PM Yeah, I'm not sure why it's flagging an image load as blocking. I'm not sure what we can do about that.
Randy Calvert Posted yesterday at 04:16 PM Posted yesterday at 04:16 PM The one thing I’ve learned over the years is that Google is not always right and many times breaks or does not even follow its own guidance. Marc and Gary 2
Marc Posted yesterday at 04:35 PM Posted yesterday at 04:35 PM 18 minutes ago, Randy Calvert said: The one thing I’ve learned over the years is that Google is not always right and many times breaks or does not even follow its own guidance. This is actually a very good point. Just one random example
Adlago Posted 23 hours ago Author Posted 23 hours ago 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... konon 1
KT Walrus Posted 23 hours ago Posted 23 hours ago (edited) Why more images visible in second screenshot? Maybe this has something to do with lazy image loading in the first test results versus the second. Maybe hitting a case of their browser not wanting to download as many images in parallel for the v5 case. Just my initial thoughts on what might be going on… Or is there only one image for both? Edited 23 hours ago by KT Walrus
Adlago Posted 23 hours ago Author Posted 23 hours ago 4 minutes ago, KT Walrus said: Why more images visible in second screenshot? Maybe this has something to do with lazy image loading in the first test results versus the second. Maybe hitting a case of their browser not wanting to download as many images in parallel for the v5 case. Just my initial thoughts on what might be going on… 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.
KT Walrus Posted 22 hours ago Posted 22 hours ago 36 minutes ago, Adlago said: 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. Have you looked in your browser’s dev tools to see the timeline of where the delay is coming from? Seems to me it would be related to the number of HTTPS requests and whether the browser is doing most requests in parallel. I always use Cloudflare in front of my servers to optimize page loading. Make sure you are using HTTP3 for your site. https://http3check.net/?host=preview.invisionalpha5.com
Adlago Posted 20 hours ago Author Posted 20 hours ago 2 hours ago, KT Walrus said: Make sure you are using HTTP3 for your site. 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.
KT Walrus Posted 19 hours ago Posted 19 hours ago 1 hour ago, Adlago said: 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. I was thinking about Cloudflare not as CDN but as an HTTPS server that really knows how to serve websites most efficiently. HTTP3 connections is only one example. Cloudflare is free to put in front of your site and doesn’t take much setup out of the box. Just flip a DNS switch and Cloudflare just works. If it doesn’t help, just turn it off and use Cloudflare’s DNS. But you can also optimize your site by using some of the many services Cloudflare includes in your account.
Randy Calvert Posted 18 hours ago Posted 18 hours ago If you're going to compare versions, you are better off having multiple installations. Remember... Google frequenly changes how it measures stuff. Sometimes even daily. Saying "nothing changed" ignores the fact that Google can and does change. SeNioR- 1
Adlago Posted 18 hours ago Author Posted 18 hours ago 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. konon 1
EliasM Posted 16 hours ago Posted 16 hours ago 2 hours ago, Adlago said: This issue is related to cache blocks. I reduced the cache time to 10 minutes Is there an option for that in ACP or is it from the server?
Adlago Posted 7 hours ago Author Posted 7 hours ago 8 hours ago, EliasM said: Is there an option for that in ACP or is it from the server? konon 1
Recommended Posts