Did you know? Optimizing a website does not improve loading time!
Are you one of the many millions of users who believe that optimizing a website could improve the loading time?
Unfortunately, this is a misconception and who is to blame? It's Google, or Google PageSpeed, because PageSpeed can't measure the loading time and doesn't want to and can't.
Google PageSpeed wants you to optimize your website, but for Google, optimization means that the data needed for display should be processed quickly. However, processing quickly does not mean that the data being loaded can also be loaded quickly. The loaded data must first be processed by the browser, which is why the motto applies: "The less data there is to load, the faster the loading time and the faster the display time and the better the PageSpeed Score."
For your information:
Processing Cascading StyleSheets (CSS) causes the highest CPU load on the client side. This means that the speed of the display depends on the performance of the device used by the client. The consequence of this is that a visually appealing theme with a lot of CSS inevitably means that it is harder to optimize and therefore receives a worse PageSpeed Score.
However, this objective only applies to a limited extent. Static sources, especially CSS, are largely responsible for the display in the browser. CSS is responsible for the formatted display in the browser. Without CSS there is also output in the browser, but unformatted. If there is a time delay between the loaded HTML code and the CSS formatting, this time delay leads to an unsightly display. Anyone who uses the UCSS code function or the guest mode of the cache plugin should be aware of this phenomenon.
CSS is a static source like any other static source such as Javascript or images. Static sources are defined in the main document. This means that a static source cannot be loaded until the main document has been loaded. The loading of the main document is significantly influenced by how quickly the PHP interpreter can query the data from the database. This means that the data required for the display (CSS, Javascript, images), ... can only be loaded from the server when the main document can provide the required data. If this provision takes longer, then loading the static sources and thus displaying the static sources also takes longer.
Now what is the consequence?
The consequence is actually easy to understand. If you aim to optimize your website, then this optimization only makes sense if you take measures to make the main document load faster, because as we now know, everything depends on it. Pagespeed rewards you with a well-optimized website. But your website remains as slow as before because the main document also loads as slowly as before.
What is the solution to this significant problem?
The solution to this problem consists of a holistic solution. Holistic means that you first have to create the prerequisites for the main document to load faster. You can achieve this through a server-side HTTP cache, or through LiteSpeed LScache or any LScache PLugin. Only then is it possible to deal with the actual optimization, the scope and possibilities of which depend on the CMS and the theme used or the plugins installed.
If you would like to learn more about why Google PageSpeed cannot measure loading time, visit: Google PageSpeed Secrets
************************************************************************************************************************************************************************************************
Join https://www.cachecrawler.com - Lightning fast Cache Warmup Crawler for Wordpress, OpenCart, PrestaShop, W3 Total Cache, WP Rocket, Shopware and Magento.
************************************************************************************************************************************************************************************************
Are you one of the many millions of users who believe that optimizing a website could improve the loading time?
Unfortunately, this is a misconception and who is to blame? It's Google, or Google PageSpeed, because PageSpeed can't measure the loading time and doesn't want to and can't.
Google PageSpeed wants you to optimize your website, but for Google, optimization means that the data needed for display should be processed quickly. However, processing quickly does not mean that the data being loaded can also be loaded quickly. The loaded data must first be processed by the browser, which is why the motto applies: "The less data there is to load, the faster the loading time and the faster the display time and the better the PageSpeed Score."
For your information:
Processing Cascading StyleSheets (CSS) causes the highest CPU load on the client side. This means that the speed of the display depends on the performance of the device used by the client. The consequence of this is that a visually appealing theme with a lot of CSS inevitably means that it is harder to optimize and therefore receives a worse PageSpeed Score.
However, this objective only applies to a limited extent. Static sources, especially CSS, are largely responsible for the display in the browser. CSS is responsible for the formatted display in the browser. Without CSS there is also output in the browser, but unformatted. If there is a time delay between the loaded HTML code and the CSS formatting, this time delay leads to an unsightly display. Anyone who uses the UCSS code function or the guest mode of the cache plugin should be aware of this phenomenon.
CSS is a static source like any other static source such as Javascript or images. Static sources are defined in the main document. This means that a static source cannot be loaded until the main document has been loaded. The loading of the main document is significantly influenced by how quickly the PHP interpreter can query the data from the database. This means that the data required for the display (CSS, Javascript, images), ... can only be loaded from the server when the main document can provide the required data. If this provision takes longer, then loading the static sources and thus displaying the static sources also takes longer.
Now what is the consequence?
The consequence is actually easy to understand. If you aim to optimize your website, then this optimization only makes sense if you take measures to make the main document load faster, because as we now know, everything depends on it. Pagespeed rewards you with a well-optimized website. But your website remains as slow as before because the main document also loads as slowly as before.
What is the solution to this significant problem?
The solution to this problem consists of a holistic solution. Holistic means that you first have to create the prerequisites for the main document to load faster. You can achieve this through a server-side HTTP cache, or through LiteSpeed LScache or any LScache PLugin. Only then is it possible to deal with the actual optimization, the scope and possibilities of which depend on the CMS and the theme used or the plugins installed.
If you would like to learn more about why Google PageSpeed cannot measure loading time, visit: Google PageSpeed Secrets
************************************************************************************************************************************************************************************************
Join https://www.cachecrawler.com - Lightning fast Cache Warmup Crawler for Wordpress, OpenCart, PrestaShop, W3 Total Cache, WP Rocket, Shopware and Magento.
Last edited: