Fixing the Three Numbers Without a Developer

What is actually within reach

Performance advice is written for developers, which leaves the person who runs a small site assuming none of it applies to them.

A useful amount of it is settings and files rather than code.

Across ordinary business sites, most of what fails Google's three measurements comes down to oversized images, a loading order nobody chose, and space that was not reserved. All three are addressable without touching a template.

What follows assumes a site on a common platform with a performance plugin available, which is where most small businesses are.

Loading: make the biggest visible thing smaller

The measurement watches how long the largest element in the visible area takes to appear, and on almost every business site that element is one image.

Two changes fix most failures.

Resize the file. A banner displayed at eight hundred pixels wide does not need to be four thousand, and reducing it to around two thousand at moderate compression typically removes eighty percent of its weight with no visible difference.

Then stop deferring it. Plugins that lazy-load every image apply that to the banner as well, which deliberately delays the one image the measurement is watching. Every such plugin has a setting to skip the first image or two, and it should be used.

Those two together move more sites into the acceptable range than anything else on this page.

Stability: reserve the space

This measurement records how much the page moves while loading, and the causes on a small site are short.

• Images without width and height set on them.
• A cookie notice inserted at the top after loading.
• Embedded maps or videos in a box with no fixed height.
• A web font that reflows text when it arrives.

The first is usually a setting in the theme or a plugin that adds dimensions automatically, and it resolves the majority of cases on its own.

The cookie notice is a configuration choice: overlay it rather than pushing the page down, which most consent tools support.

Responsiveness: usually already fine

The third measurement records how quickly the page reacts the first time somebody taps.

Most small business sites pass it comfortably, because they run very little code and there is nothing keeping the browser busy.

Where a site does fail, the cause is almost always a quantity of scripts: a page builder, several plugins each adding their own, and third-party widgets.

The fix is reduction rather than optimisation, which means removing plugins you do not use and deferring the ones you do.

If this is your failing measurement, it is worth checking how many plugins are actually active, since the number is frequently higher than anybody remembers.

The plugin settings that do the work

On a typical setup, a handful of options account for most of the available improvement.

Lazy loading, on, with the first image or two excluded.

Deferred JavaScript, on, then check the site for anything that broke.

Image dimensions added automatically, on.

Font display set so text appears in a fallback immediately rather than staying invisible.

Caching, on, which does not affect these measurements directly and helps everything else.

Change one at a time and reload the site after each, because the failure mode here is enabling six options at once and discovering something is broken without knowing which caused it.

A worked example

A clinic's site was reported as poor on mobile and they had been quoted for development work.

The homepage banner was a photograph exported at full camera resolution, weighing over four megabytes, and it was being lazy-loaded along with everything else.

Their cookie notice pushed the page down about a second after it loaded.

The practice manager resized the banner, excluded the first image from lazy loading, turned on automatic image dimensions, and switched the cookie notice to an overlay.

Total time was about ninety minutes, with no code written and nothing bought.

Lab testing showed the improvement immediately, and the field report moved into the acceptable range about five weeks later, which is the normal reporting delay rather than a slow fix.

Where a developer is genuinely needed

Worth stating so the boundary is clear.

A theme that loads everything on every page, where the fix is splitting stylesheets by page type.

Anything requiring changes to templates, such as restructuring the header so the banner is referenced in the page rather than in a stylesheet.

Server-side problems, where the page is slow to start arriving at all regardless of what it contains.

And any site where the content is assembled by scripts, which is a structural decision rather than a settings question.

If you have done everything above and the numbers have not moved, that is the point to get help, and you will be able to say precisely what you have already tried.

Do not chase the score

The measurements have thresholds, and the sensible target is to clear them on mobile for the pages that matter.

Beyond that, effort produces diminishing returns and starts to compete with things that matter more, such as what the page actually says.

Google has been clear that relevance and usefulness remain the dominant factors, and that these measurements act as a differentiator between comparable pages rather than as a substitute for being the better answer.

Reaching acceptable and stopping is the correct outcome. A perfect score on a page nobody wants to read is worth nothing.

The counter-case

There is a version of this that causes damage, and it is worth naming before somebody enables everything at once.

Aggressive deferral and combination settings break sites regularly. A slider stops working, a form fails silently, a menu opens in the wrong place, and because the settings were applied together nobody knows which one did it.

The consequences of a broken contact form are far larger than the benefit of a slightly better measurement.

Take a backup, change one setting, reload the site, and test the form. Every time. It is slower and it is the difference between an afternoon of improvement and a week of diagnosis.

The order to work in

1. Take a backup before changing anything.
2. Resize the homepage banner and any large images.
3. Exclude the first image from lazy loading.
4. Turn on automatic image dimensions.
5. Overlay the cookie notice instead of inserting it.
6. Defer scripts, one setting at a time, testing the form after each.
7. Stop at acceptable rather than chasing perfect.

Steps two and three alone resolve the most common failure, and neither requires anything beyond a photo editor.

Where the numbers come from is covered in measuring speed the way Google does.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.