A static Next.js rebuild that took page speed from 60 to 100

The challenge

What we did

1. 1

   Rebuilt the site as a static Next.js application

   Replaced the hand-written HTML, CSS and JavaScript with a statically generated Next.js build, so every page ships as pre-rendered markup rather than assembling itself in the browser.

2. 2

   Modernised the UI to the client's brief

   Redesigned the interface and page layouts against the client's own requirements, with full responsiveness so the experience holds from a phone to a desktop.

3. 3

   Took page speed from 60 to 100

   Static rendering, right-sized assets and a disciplined JavaScript budget moved the client's reported page-speed score from 60 to 100.

4. 4

   Improved accessibility across the site

   Contrast, focus states, semantics and keyboard navigation handled in the components, so the improvements carry across every page rather than sitting on a few.

5. 5

   Ran advanced SEO on the new build

   Crawlability, indexation, metadata and content structure addressed on the rebuilt site, so the technical foundation and the content worked towards the same queries.

6. 6

   Tracked impressions through to leads

   Monitored the path from search impressions to clicks to enquiries, adjusting the content plan against what the data showed rather than what was assumed.

Results

60 → 100Page speed score

The client's reported page-speed score after the static Next.js rebuild, up from 60 on the previous hand-written site.

StrongImpression growth

Search impressions grew as the rebuilt site became easier to crawl, index and surface on Google.

StrongImpressions converting to leads

A rising share of those impressions turned into clicks and then enquiries, rather than visibility that stopped at the results page.