A page that loads in under a second feels instant, keeps people from bouncing, and quietly helps you rank. Here is the exact order we tune sites in — the changes that move the needle first, in plain English, no fluff.

Before you start

  • Access — Login to your hosting or site dashboard, plus the ability to add a plugin or edit a setting or two.
  • A baseline — One PageSpeed Insights run saved before you start, so you can prove the improvement afterward.
  • An hour — Images and caching are quick wins; the script and font cleanup is where the real time goes.

1. Measure first, with real data

Run your slowest pages through PageSpeed Insights and look at the field data (real visitors), not just the lab score. Note your Largest Contentful Paint — that is the number you are chasing under 2.5 seconds, then under one.

2. Compress and resize your images

Images are almost always the heaviest thing on the page. Export them at the size they actually display, convert to WebP or AVIF, and add width and height so the layout does not jump. This alone often halves load time.

3. Lazy-load everything below the fold

Add loading="lazy" to images and embeds that are not visible when the page opens. The browser then waits to fetch them until someone scrolls, so the first screen paints far faster.

4. Cut the JavaScript and third-party junk

Audit your scripts. Chat widgets, heavy sliders, extra fonts, and old tracking tags are usually the biggest offenders. Remove what you do not use, defer the rest, and never load a 200KB library to do a 10-line job.

5. Turn on real caching and a CDN

Full-page caching serves a ready-made HTML file instead of rebuilding the page every visit. Put a CDN like Cloudflare in front so your site loads from a server near the visitor, not across the country.

6. Fix render-blocking CSS and fonts

Inline the critical CSS for the top of the page, defer the rest, and self-host fonts with font-display: swap so text shows instantly instead of waiting on a download.

7. Re-measure and protect the win

Run PageSpeed Insights again and confirm the LCP dropped. Then set a budget — if a new plugin or image pushes you back over a second, you will know before your customers do.