Class, gather round the patient. Our WordPress site is sluggish: pages crawl, images plod, and visitors are drumming their fingers. Today we perform a speed makeover. We’ll measure first, fix the biggest problems, and measure again. No guesswork, no magic potions.
Step 1: Measure Before You Change Anything
You can’t improve what you don’t measure. Run your homepage and one typical post through:
- PageSpeed Insights (pagespeed.web.dev) — shows lab data and, when enough visitors exist, real-world field data from Chrome users.
- Google Search Console — its Core Web Vitals report groups pages by status across your whole site.
Write down your results. Test a few times, since scores naturally vary between runs.
Meet the Core Web Vitals
- LCP (Largest Contentful Paint): how quickly the main content, often a hero image or headline, appears.
- INP (Interaction to Next Paint): how quickly the page responds when someone clicks, taps or types.
- CLS (Cumulative Layout Shift): how much the layout jumps around while loading.
Professor’s note: Don’t chase a perfect 100 score. The goal is a site that feels fast to real visitors. A score is a helpful thermometer, not the patient.
Step 2: Fix Your Images (the Biggest Quick Win)
Large images are frequently the heaviest part of a page. To slim them down:
- Resize before uploading: a photo straight from a phone is often far larger than any screen needs.
- Compress and convert: WordPress supports modern formats like WebP and AVIF. A plugin such as ShortPixel can compress and convert automatically.
- Let lazy loading work: WordPress adds loading=”lazy” to images by default, so off-screen images load only when needed.
- Don’t lazy-load your hero image: the main above-the-fold image should load immediately. WordPress tries to detect this automatically and can add fetchpriority=”high”.
Here’s what a well-optimised image tag looks like:
<img src="hero.webp" width="1200" height="600"
alt="Professor Press at the whiteboard"
fetchpriority="high">
Including width and height lets the browser reserve space, which helps prevent layout shift (CLS).
Step 3: Turn On Caching
Without caching, WordPress builds each page from scratch with PHP and database queries for every visitor. Page caching serves a ready-made copy instead.
- Check your host first — many managed hosts provide server-level caching. Enable it in your hosting dashboard.
- Otherwise, add a caching plugin — options include WP Rocket or LiteSpeed Cache (see our plugins page). Use only one.
- Consider a CDN — a content delivery network serves files from locations closer to your visitors. Many hosts include one or make it easy to connect.
- Clear cache after changes — and test while logged out, since logged-in users often bypass the cache.
Warning: Settings like “combine” or “delay JavaScript” can break sliders, menus or forms. Change one setting at a time and test your site after each change.
Step 4: Trim the Fat
Audit plugins
Every active plugin can add code. Remove plugins you don’t use, and replace heavy plugins with lighter alternatives or built-in blocks where possible. The Query Monitor plugin can help developers identify slow queries and heavy plugins.
Choose a lightweight theme
Themes that load lots of scripts, fonts and sliders on every page can drag performance down. Block themes tend to load only the styles for blocks actually used on a page. See our themes page for lean options.
Go easy on fonts and third-party scripts
Each web font file, chat widget, embedded video and tracking script adds weight. Use one or two font families, and ask whether every third-party script earns its place.
Tidy the database
WordPress stores post revisions, which are useful but can pile up. You can limit how many are kept by adding this line to wp-config.php, above the line that says “That’s all, stop editing!”:
define( 'WP_POST_REVISIONS', 10 );
Always back up before editing wp-config.php.
Step 5: Check Your Hosting and PHP Version
No amount of optimisation fully fixes an overloaded server. Visit Tools → Site Health to see your PHP version and other recommendations. Newer supported PHP versions are generally faster and more secure; most hosts let you switch in their dashboard. Test your site afterwards, as very old plugins may not be compatible.
Tip: If your site is still slow after images, caching and plugin clean-up, it may be time to upgrade your hosting plan or move to managed WordPress hosting.
Step 6: Measure Again and Celebrate
Re-run the same tests on the same pages and compare with your notes. Field data in Search Console updates more slowly, since it’s based on real visitor data collected over time, so give it a few weeks.
Want a deeper, structured approach? Our course has a full performance module, and our tools page lists handy testing utilities.
Homework
Run PageSpeed Insights on your homepage and write down your LCP, INP and CLS. Then make just one change: compress and convert your largest image. Re-test and record the difference. Small, measured improvements add up to a snappy site.