Page speed moves three things at once: rankings (through Core Web Vitals), user experience, and conversion. This walkthrough takes you through diagnosing and fixing it layer by layer, in the order that returns the most for the least effort.

Step 1: Benchmark your key pages

Start with data, not guesses. Run your most important pages through PageSpeed Insights to capture both lab diagnostics and real-user field data, and record a baseline for LCP, INP, and CLS. Note the two upstream metrics that reveal causes — Time to First Byte (a slow server) and First Contentful Paint (how soon anything appears).

Step 2: Optimize media first

Media is usually the single biggest win. Compress images and video without visible quality loss, convert to modern formats like WebP or AVIF, and lazy-load offscreen media with native loading="lazy". Size images to their actual display slot rather than shipping oversized files, and serve responsive images via srcset so each device gets an appropriate file.

Step 3: Speed up the server

Reduce Time to First Byte at the source. Put a CDN in front of your assets to cut latency, enable server-side and browser caching so unchanged files aren’t regenerated or re-downloaded, and move off under-provisioned shared hosting when load demands it. Keep server, CMS, and plugins current, and enable HTTP/3 where connections are lossy or high-latency.

Step 4: Unblock rendering with CSS

CSS can block the first paint if it isn’t managed. Minify your stylesheets, remove unused CSS, and inline the critical CSS needed for above-the-fold content so the first view paints immediately. Load the remaining CSS asynchronously so it doesn’t hold up the initial render.

Step 5: Tame JavaScript

JavaScript is what most often hurts responsiveness (INP). Minify and compress bundles, add defer or async to <script> tags so JS doesn’t block HTML parsing (defer is usually the safer default), and cut execution time by splitting long tasks and removing unused code. Give third-party scripts — analytics, ads, widgets, fonts — their own audit and drop whatever isn’t essential.

Step 6: Verify and keep monitoring

Confirm each change actually helped. Change one thing at a time so you can attribute the gain, re-test in Lighthouse or WebPageTest, then confirm the improvement in Search Console’s Core Web Vitals field data over the following weeks. Revisit periodically — new features and third-party scripts erode speed over time.

Full guide → Page Speed Optimization: A Practical Guide