Skip to content
Get Ranked On TopIllustrative case studySignal plan

A fictional business. The figures are a modelled scenario, not a client result.

Ivelstone Garden Rooms · Garden office & garden room builder, 25 staff · Exeter

How a garden-room builder kept its 3D configurator and still got its pages level on a phone

Level on all three Core Web Vitals, then +64% organic enquiries

8 months · UK & Ireland · Signal plan · Core Web Vitals · Lazy-loaded 3D configurator · Image pipeline · Layout-shift fixes

LCP
2.1 s
before 5.2 s
INP
140 ms
before 410 ms
CLS
0.04
before 0.31
Field data · mobile p75 · month 8Dead level

01The challenge

A handsome site that would not sit level.

A heavy 3D configurator and huge photos gave five-second mobile loads and jumping layouts, and organic enquiries from search were sliding away.

Ivelstone designs and builds insulated garden offices and garden rooms across Devon, Cornwall and Somerset, and most buyers start their research on a phone, in the evening, from the sofa. The site had been rebuilt around a showpiece 3D configurator and full-resolution photography. On the studio iMac it looked superb. On a phone in a Dartmoor village it took more than five seconds to show anything useful, and then the page jumped as the gallery arrived.

Organic enquiries had fallen by a fifth in a year while rankings slipped only a few places. The question was never whether the configurator should stay. It was how to keep it without making every visitor wait for it.

Mobile LCP at p75
5.2 s
of organic visits came from phones
71%
fewer organic enquiries than a year earlier
19%
What a phone saw, before: late content shoves the quote button down just as the thumb arrives.

02Diagnosis

Where the audit found the site out of true.

3D configurator

3.9 MB

of JavaScript before first paint

The three.js configurator, its default room model and textures loaded on every page, blog posts included, before anything else could render. On a mid-range phone the main thread was blocked for almost three seconds.

Finding 1 of 4

Images

9.6 MB

of images on a typical product page

The photographer's full-size JPEGs went straight into the gallery and were served whole to a phone screen a few hundred pixels wide. No AVIF or WebP, no srcset, and the hero image was not preloaded.

Finding 2 of 4

Layout shift

0.31

CLS at p75 on mobile

The configurator canvas, the gallery and the reviews widget arrived with no reserved height, a cookie banner pushed the page down and the web font swapped late. People tapped “Get a quote” and hit a photo instead.

Finding 3 of 4

Field data

3%

of mobile URLs passing

In the Chrome UX Report almost no mobile URLs passed Core Web Vitals, yet seven in ten organic visits came from phones. Lab scores on the office broadband had hidden the problem for a year.

Finding 4 of 4

03The plan

Keep the showpiece. Take it off the critical path.

Built on our Signal plan: technical SEO judged on real-user data from phones, not on lab scores from a fast laptop.

  1. Core Web Vitals in the field

    Real-user monitoring on every template next to CrUX, a performance budget for each page type and a check in the deploy pipeline that fails any build that breaks it.

  2. Configurator on demand

    A still render with a “Design your room” button takes the configurator's place. three.js and the models load only when someone taps it, and never on guides or blog posts.

  3. Image pipeline

    Every photo is resized on upload into AVIF and WebP at six widths and served with srcset and sizes. The hero image is preloaded with high fetch priority; everything below the fold loads lazily.

  4. Reserved space

    Width and height on every image, aspect-ratio boxes for the gallery, configurator and reviews, the cookie notice turned into an overlay, and fallback font metrics matched so the text stops jumping.

04Try it

Put the page on the level.

Switch the three fixes on and off in any order and watch the bubble. It only settles between the lines when all three Core Web Vitals are in the green.

Bubble 12 mm off centre

Mobile page weight14.8 MB0 of 3 Core Web Vitals pass

Bubble 12 mm off centre. 0 of 3 Core Web Vitals pass. LCP 5.2 s, INP 410 ms, CLS 0.31.

LCP only settles once both the images and the configurator are dealt with; CLS only once the space is reserved.

LCPLargest Contentful Paintgood ≤ 2.5 s
5.2 sPoor
INPInteraction to Next Paintgood ≤ 200 ms
410 msNeeds work
CLSCumulative Layout Shiftgood ≤ 0.10
0.31Poor

Modelled mobile p75 values for the product pages. Each fix's effect is its modelled share of the improvement measured in the field.

05The work

Eight months, one reading a month.

The bubble each month, from field LCP, INP and CLS together
  1. Month 1

    LCP 5.2 sCLS 0.31 · INP 410 ms

  2. Month 2

    LCP 5.1 sCLS 0.30 · INP 400 ms

  3. Month 3

    LCP 4.2 sCLS 0.29 · INP 390 ms

  4. Month 4

    LCP 3.4 sCLS 0.28 · INP 240 ms

  5. Month 5

    LCP 2.7 sCLS 0.09 · INP 170 ms

  6. Month 6

    LCP 2.4 sCLS 0.06 · INP 155 ms

  7. Month 7

    LCP 2.2 sCLS 0.05 · INP 145 ms

  8. Month 8

    LCP 2.1 sCLS 0.04 · INP 140 ms

  1. Month 1

    Level the base

    Field data from CrUX and real-user monitoring, a template inventory and a ranked list of what cost the most time on a phone.

  2. Months 2–3

    Image pipeline

    Resizing on upload, AVIF and WebP, srcset and sizes, a preloaded hero. LCP falls by more than a second.

  3. Months 3–4

    Configurator on demand

    The still render and the tap-to-load button go live; the JavaScript on first load drops by almost four megabytes and INP passes.

  4. Month 5

    Reserve the space

    Aspect-ratio boxes, the cookie overlay and matched font metrics. CLS falls from 0.28 to 0.09 in a month.

  5. Months 6–8

    Hold it level

    The 28-day field window catches up, the budget guards every release, and enquiries keep climbing.

06Results

Level on a phone, and the enquiries came back.

Organic enquiries a month

+64%

78 → 128 a month, month 1 to month 8

Mobile LCP (p75)

5.2 s → 2.1 s

Field data, mobile, 75th percentile

Layout shift (CLS)

0.31 → 0.04

Good is 0.1 or less

Mobile URLs passing Core Web Vitals

3% → 94%

Share of mobile URLs in the Chrome UX Report

Modelled scenario for a fictional business — not a client result. Rankings, traffic and enquiries are never guaranteed; see our Terms.

Field LCP, month by month
0246good ≤ 2.5 s5.2M15.1M24.2M33.4M42.7M52.4M62.2M72.1M8
Organic enquiries a monthIvelstone Garden RoomsModelled trend without the fixes
05010078M175M281M388M499M5110M6121M7128M8

Mobile positions for the money queries

Query (as searched)Month 1Month 8
garden office exeter#9#3
garden rooms devon#12#5
garden office planning permission uk#15#7
insulated garden office#18#9
garden room with bathroom#23#11
garden room prices#27#14

Modelled monthly average positions on mobile. Core Web Vitals are a light ranking signal: most of the gain came from visitors staying long enough to price a room and send the form.

Is your site level on a phone?

Our Signal plan finds what slows and shifts your pages in real-user data, fixes it in order of impact and keeps it fixed.

All case studies