WordPress speed optimization: fixes that move the score

3 min readSpeedBy Code Genie Studio

Most slow WordPress sites are slow for the same handful of reasons, and most speed advice online is a list of forty tweaks in no particular order. This guide works the other way round: measure, find the biggest cause, fix it, measure again. The order matters more than any single plugin.

Measure before you touch anything

Run Google PageSpeed Insights on your home page and on one important inner page, on mobile. Run each test three times and keep the middle result, because the score moves between runs. Write down Largest Contentful Paint, Total Blocking Time and Cumulative Layout Shift, not only the overall score. If those names are new, read what your PageSpeed score actually measures first.

Then read the diagnostics under the score. They name the files responsible: the oversized hero image, the slider script, the chat widget. That list is your work plan.

1. Images

Oversized images are the most common reason the main content appears late. Fix them in this order:

  • Resize each image to the largest size the layout actually shows. A 4,000-pixel photo in a 1,200-pixel slot wastes most of its weight.
  • Serve modern formats such as WebP or AVIF. Recent WordPress versions accept both, and image plugins can convert what is already in your media library.
  • Let the main image load first: never lazy-load the hero image, and lazy-load the images further down.
  • Give images a width and height so the page does not jump while they load.

2. Hosting and caching

If the server takes a long time to send the first byte, nothing else helps much. The signs are a slow server response in the diagnostics and a sluggish admin area. Page caching serves a ready-made copy of each page instead of building it on every visit; many hosts include it, and a caching plugin can do the job where they do not. A content delivery network then serves files from a location close to the visitor.

Budget shared hosting can be fine for a small site with caching. It stops being fine once the site carries heavy plugins, a shop or real traffic.

3. Page builders and plugins

Page builders and all-in-one themes load their code on every page, whether that page uses those features or not. On mobile this is often the main source of Total Blocking Time. Go through your plugins and ask three questions of each: is it used, is there a lighter way to do the same job, and does it load scripts on pages that do not need them? Removing one heavy slider or pop-up plugin can do more than any optimization plugin.

Optimization plugins that combine, minify and defer files do help, but test after every setting. Aggressive settings can break menus, forms and checkout without an obvious error message.

4. Fonts

  • Use fewer font files: one or two families, and only the weights you actually use.
  • Host the fonts on your own site instead of loading them from a third party.
  • Use font-display: swap, so text appears straight away in a fallback font.
  • Preload the one font used in the main heading.

5. Third-party scripts

Chat widgets, heatmaps, several analytics tools, ad pixels, embedded maps and video players all load code from someone else’s server. Together they are often why a page looks loaded but does not respond to a tap. Remove the ones nobody looks at, load the rest after the page has become interactive, and replace embedded maps and videos with a still image that loads the real thing on click.

What is not worth the effort

  • Chasing a perfect 100. Moving from red to green on mobile matters; the last few points rarely do.
  • Testing only the home page. Visitors from search often land on inner pages.
  • Stacking several optimization plugins that do the same job.
  • Polishing the desktop score while mobile stays red.

When to rebuild instead

Sometimes the theme or page builder is the problem, and no amount of tuning makes the mobile pages fast. If you have fixed the images, the hosting and the plugins and the mobile score still sits in the red, a rebuild on a lean theme, or a setup where WordPress only manages the content and a separate front end serves the pages, can cost less than another year of patches. Measure first, so the decision rests on numbers rather than opinions.

Our free site check runs Google’s PageSpeed test on the mobile version of your site and shows the score with the four numbers that matter most. If you would rather have the work done for you, see our website speed optimization service.

Is your site losing people right now?

Type your address. We run Google's own PageSpeed test on the mobile version of your site and show you the score in about twenty seconds. No sign-up.

Google tests your site on a mid-range phone over a mobile connection, the way most of your customers see it.

Tell us about it.

A few lines is enough. A person reads every message and replies by email.

What do you need?
or write to business@codegeniestudio.com