Hi,
Google PageSpeed insights actually has some good insights. Minify CSS, optimize images, leverage browser caching, etc.
But then Google says I need to reduce server response time. And their guidance here is less than helpful:
Gather and inspect existing performance and data. If none is available, evaluate using an automated web application monitoring solution (there are hosted and open source versions available for most platforms), or add custom instrumentation.
Identify and fix top performance bottlenecks. If you are using a popular web framework, or content management platform, consult the documentation for performance optimization best practices.
Monitor and alert for any future performance regressions!
Right, very actionable advice there.
So what exactly should I be inspecting? Where do I find bottlenecks? The dev team is fixing all the other issues, but I don't know what determined server response time (as opposed to page load times).
Google PageSpeed insights actually has some good insights. Minify CSS, optimize images, leverage browser caching, etc.
But then Google says I need to reduce server response time. And their guidance here is less than helpful:
Gather and inspect existing performance and data. If none is available, evaluate using an automated web application monitoring solution (there are hosted and open source versions available for most platforms), or add custom instrumentation.
Identify and fix top performance bottlenecks. If you are using a popular web framework, or content management platform, consult the documentation for performance optimization best practices.
Monitor and alert for any future performance regressions!
Right, very actionable advice there.
So what exactly should I be inspecting? Where do I find bottlenecks? The dev team is fixing all the other issues, but I don't know what determined server response time (as opposed to page load times).