Speed optimisation for slow websites

Speed optimisation for businesses across Halifax and West Yorkshire. We find what is slowing your site down, fix it, and measure it again. No guesswork and no screenshot of a desktop score.

How we speed up your site

Google and SOASTA's research put mobile abandonment at 53% once a page passes three seconds. Most of the sites that come here are well past it.

Full performance audit

Your site goes through PageSpeed Insights, Lighthouse and WebPageTest to find every bottleneck. You get a clear list of what is wrong and what will be fixed, not a screenshot of a score and a vague set of suggestions.

Images and assets

Oversized images are the most common single cause of a slow page. Converting to modern formats, serving the right size for the device, and loading offscreen images only when needed usually accounts for most of the gain.

Code and third-party scripts

Unused CSS, render-blocking JavaScript and the accumulated pile of tracking tags all get addressed. Third-party scripts are often the worst offenders and the ones nobody thinks to question.

Core Web Vitals

Google measures LCP, INP and CLS on real visits rather than on a lab test, which is why a good Lighthouse score and bad field data can happen at once. The target is green on all three where the traffic is.

How the work runs

Every fix is measured before and after. The last stage is the one that separates this from a report.

  1. Measure the real thing first

    Lab tools and field data both, because they disagree more often than people expect. Chrome's field data reflects what your visitors experience on their phones and connections, which is the number Google uses.

  2. Rank the fixes by what they buy

    A performance report will list forty items. Usually three of them are worth doing and the rest are noise. You get told which is which, along with what each one is realistically worth in seconds.

  3. Fix, then measure again

    Changes get made and re-tested rather than assumed. Anything that does not move the number gets reverted rather than left in as clutter, because complexity that buys nothing is its own cost later.

  4. Tell you what is left

    Sometimes the honest answer is that the platform is the ceiling and no amount of optimisation gets a bloated build under two seconds. If that is the case, you will be told rather than sold a second round.

What the work covers

Priced per site after the audit, because a five page brochure site and a bloated store are not the same job. You get the numbers before and after, not a claim.

  • Lab and field performance audit
  • Image format and sizing overhaul
  • Render-blocking resource removal
  • Third-party script review
  • Core Web Vitals: LCP, INP and CLS
  • Caching and compression checks
  • Before and after measurements
  • A written list of what changed

Questions we get asked

The second one is the question worth asking before you spend anything.

How much faster will my site get?
It depends entirely on what is wrong with it, which is why the audit comes first and why nobody honest quotes a number before looking. A site slowed by unoptimised images can improve dramatically for very little. A site slowed by its own platform has a ceiling, and you will be told where that ceiling is.
Is it worth optimising, or should I rebuild?
If the design still works and the site is just slow, optimisation is far cheaper and gets you most of the way. If it is slow because it is a decade-old build carrying fifteen plugins, you are paying to make a poor foundation slightly less poor, and a rebuild is usually the better spend. You will get a straight answer on which yours is.
Does site speed really affect Google rankings?
Yes, though less dramatically than the industry likes to claim. Core Web Vitals are a confirmed ranking signal, but they are one of many and they will not lift a page that does not deserve to rank. The larger effect is on people: a slow page loses visitors before they have read anything, and that costs you enquiries whatever Google does.
Do new Webvise sites need this?
No. Builds here target 95 or above on mobile PageSpeed as a matter of course, because the way they are built pre-renders pages rather than assembling them on request. This service exists for sites built elsewhere.