Ever since Google Pagespeed, there has been a misconception that Google doesn't really want to create despite sufficient criticism. But before I demonize Google, I want to first praise Google. Praise for the fact that Google has been the only authority for almost 20 years now, which is committed to the loading time of a website. However, not without benefiting from it. Since Google has been considering the loading time as a ranking factor for some time now, everyone, without exception, is trying to do the maximum possible for it.
However, the loading time has a crucial catch. Google, or Google Pagespeed, does not measure loading time at all and cannot do so at all. There are two reasons behind this negation.
In order to be able to measure the loading time fairly and under the same conditions, the same conditions should always be used when accessing any website. In particular, this always includes the same distance between the origin host and Google. However, this cannot be guaranteed, especially since this distance plays a decisive role in the transmission and connection speed. It is therefore wrong that Google Pagespeed can measure the loading time fairly and fairly. Otherwise, those hosts that are closer to a Google node would be favored and everyone else would be disadvantaged.
It is also wrong that Google measures "load time" itself. For the reasons given above, a measurement result would always be wrong and unfair. Google does not measure the loading time, but Google Chrome measures the loading time, or the user of a page who uses the Chrome browser. The Chrome browser has the least known user API, which calls "home" every time a website is accessed. From this and only from this data, Google determines a ranking factor. If you test your website at https://pagespeed.web.dev/, the result of the test has little to do with the test results that sometimes transmit 1000 users or more to Google.
It is also wrong that Google Pagespeed measures the loading time. Pagespeed measures the "Display Time". What is the difference in loading time? The display time measures how long it takes for everything to be displayed in the browser "after" all the data has been loaded from the server. The actual loading of the sources plays (almost) no role here.
What does that mean now?
This means that you can have a ridiculously slow server but your website is optimized to the maximum, but you get a high score for it. However, this also means that you can have a lightning-fast server but your website is not optimized and you get a bad score for it, even though your website "felt" loads faster.
Is that fair? Answer this question yourself.
The only thing that matters is that you optimize your website for the user and not for Google. This means that you need LiteSpeed LScache on the one hand, but also an optimization, because only both contribute to a maximum user experience. Just to remind you, it's not optimization that makes a website fast. It's LScache!
You too can benefit from our experience and knowledge. We have been specializing in optimizing the loading time of websites for 20 years now. Since 2012, i.e. for more than 10 years, we have also specialized in LiteSpeed and are therefore rightly the only authorized LiteSpeed Support Partner. Soon also solution partner. https://www.cachecrawler.com
However, the loading time has a crucial catch. Google, or Google Pagespeed, does not measure loading time at all and cannot do so at all. There are two reasons behind this negation.
In order to be able to measure the loading time fairly and under the same conditions, the same conditions should always be used when accessing any website. In particular, this always includes the same distance between the origin host and Google. However, this cannot be guaranteed, especially since this distance plays a decisive role in the transmission and connection speed. It is therefore wrong that Google Pagespeed can measure the loading time fairly and fairly. Otherwise, those hosts that are closer to a Google node would be favored and everyone else would be disadvantaged.
It is also wrong that Google measures "load time" itself. For the reasons given above, a measurement result would always be wrong and unfair. Google does not measure the loading time, but Google Chrome measures the loading time, or the user of a page who uses the Chrome browser. The Chrome browser has the least known user API, which calls "home" every time a website is accessed. From this and only from this data, Google determines a ranking factor. If you test your website at https://pagespeed.web.dev/, the result of the test has little to do with the test results that sometimes transmit 1000 users or more to Google.
It is also wrong that Google Pagespeed measures the loading time. Pagespeed measures the "Display Time". What is the difference in loading time? The display time measures how long it takes for everything to be displayed in the browser "after" all the data has been loaded from the server. The actual loading of the sources plays (almost) no role here.
What does that mean now?
This means that you can have a ridiculously slow server but your website is optimized to the maximum, but you get a high score for it. However, this also means that you can have a lightning-fast server but your website is not optimized and you get a bad score for it, even though your website "felt" loads faster.
Is that fair? Answer this question yourself.
The only thing that matters is that you optimize your website for the user and not for Google. This means that you need LiteSpeed LScache on the one hand, but also an optimization, because only both contribute to a maximum user experience. Just to remind you, it's not optimization that makes a website fast. It's LScache!
You too can benefit from our experience and knowledge. We have been specializing in optimizing the loading time of websites for 20 years now. Since 2012, i.e. for more than 10 years, we have also specialized in LiteSpeed and are therefore rightly the only authorized LiteSpeed Support Partner. Soon also solution partner. https://www.cachecrawler.com
Attachments
Last edited: