Post by account_disabled on Feb 27, 2024 11:00:32 GMT
The you have an excuse not to do these things theyre all bestpractice and they all help. But they dont represent the whole site speed picture. With that in mind heres a skeptical reading of each of the PageSpeed Insights rules. Tests focusing on reducing bandwidth use Rule Skeptical reading Optimize images Unless you have huge images this might not be a big deal. This is only measuring whether images could be further compressed not whether youre loading too many. Enable compression Compression is easy. You should use it. It also may not make much of a difference unless you have for instance huge JavaScript files loading. Minify HTML Will likely reduce overhead only by tens of KB.
Latency will have a bigger impact than response size. Minify CSS Will likely Kazakhstan Phone Number reduce overhead only by tens of KB. Latency will have a bigger impact than response size. Minify JS Probably not as important as consolidating JS into a single file to reduce the number of requests that have to be made. Tests focusing on reducing latency Rule Skeptical reading Leverage browser caching Definitely lets cache our own files. Lots of the files that could benefit from caching are probably hosted on rdparty servers. Youd have to host them yourself to change cache times.
Reduce server response time Threshold on PSI is too high. of the serverinstead looking only at how long it takes the server to respond once it receives a request. Avoid landing page redirects Yes. Eliminate renderblocking JavaScript and CSS in abovethefold content A valid concern but can be frustratingly difficult. Having zero requests on top of the initial page load to render abovethefold content isnt necessary to meet most performance goals. Prioritize visible content Actually kind of important. Dont treat these as the final word on site performance Independent of these tests here are some things to think about. Some arent covered at all by PageSpeed Insights and some are only covered halfway Caching content you control. Reducing the amount of content youre loading from rdparty domains. Reducing server.
Latency will have a bigger impact than response size. Minify CSS Will likely Kazakhstan Phone Number reduce overhead only by tens of KB. Latency will have a bigger impact than response size. Minify JS Probably not as important as consolidating JS into a single file to reduce the number of requests that have to be made. Tests focusing on reducing latency Rule Skeptical reading Leverage browser caching Definitely lets cache our own files. Lots of the files that could benefit from caching are probably hosted on rdparty servers. Youd have to host them yourself to change cache times.
Reduce server response time Threshold on PSI is too high. of the serverinstead looking only at how long it takes the server to respond once it receives a request. Avoid landing page redirects Yes. Eliminate renderblocking JavaScript and CSS in abovethefold content A valid concern but can be frustratingly difficult. Having zero requests on top of the initial page load to render abovethefold content isnt necessary to meet most performance goals. Prioritize visible content Actually kind of important. Dont treat these as the final word on site performance Independent of these tests here are some things to think about. Some arent covered at all by PageSpeed Insights and some are only covered halfway Caching content you control. Reducing the amount of content youre loading from rdparty domains. Reducing server.