Salon furniture is sold on looks, so salon supplier websites lean hard on photography. Home pages open with a full-screen slider of finished salons. Project pages hold dozens of fit-out photos. Product pages show a styling chair in twelve upholstery colours, sometimes with a 3D view, and some sites embed a social media feed of recent installs. Trade suppliers add a login check that reveals prices and buttons only to account holders.

Each of these choices makes sense for a design-led trade. Together they can make pages slow to show their main image, jumpy while they load and sluggish when a buyer taps a colour. This guide explains how Google measures that and how to fix it without losing the photography.

How Google scores a page

Google defines three Core Web Vitals, each measured on real Chrome visits at the 75th percentile, with phone and desktop visits kept apart.

  • Loading, through LCP. The largest image, video or text block in view should render within 2.5 seconds. Beyond 4 seconds is rated poor.
  • Responsiveness, through INP. After a click, tap or key press, the next frame should appear within 200 milliseconds. Over 500 milliseconds is poor.
  • Stability, through CLS. Unexpected shifts should score 0.1 or less. Above 0.25 is poor.

For context, the 2024 Web Almanac performance chapter found that 43% of sites passed all three on mobile and 54% on desktop. Those are web-wide figures from 2024, not salon-specific ones, but they show that passing is far from automatic.

What I measured on UK salon furniture product pages (October 2026)

I ran five UK salon and barbering supplier product pages through PageSpeed Insights on 23 October 2026, a single mobile run each, emulating a mid-range phone on slow 4G.

PagePerformance scoreLab LCPTotal Blocking TimeLab CLS
Retailer A4715.3 s400 ms0.00
Retailer B4214.5 s360 ms0.24
Retailer C3612.8 s1,350 ms0.00
Retailer D3326.9 s2,560 ms0.01
Retailer E495.1 s720 ms0.00

The median score was 42 and the median lab LCP 14.5 seconds. One salon page took 26.9 seconds to draw its largest element and also logged 2,560 ms of blocking time. Images without explicit width and height were flagged on three pages, the same category-grid and thumbnail habit covered in the CLS section below. Only one page went above 0.1 for lab CLS, at 0.24, so slow loading of the main photograph mattered more here than movement.

The field picture was kinder. None of these URLs had their own Chrome UX Report data, but four of the five supplier sites passed Core Web Vitals on whole-site (origin) data. That gap is a reminder that a throttled lab phone is much slower than most salon owners’ real visits, and that Google does not rank on lab LCP. Five supplier pages make a small sample, not a ranking.

Full-screen sliders and fit-out galleries (LCP)

A full-width slider of finished salons is a common way to open a supplier’s site. It is also a common LCP problem, for reasons that are easy to miss.

  • Chromium ignores some elements when choosing the LCP. web.dev’s LCP article notes that elements covering the full viewport, elements with zero opacity and low-detail placeholder images are left out. A slider that fades its first slide in from zero opacity may not register until the slide becomes visible, and an element that fills the whole screen may not count at all, leaving the browser to pick another element later.
  • Background images are LCP candidates but load late. A slide set as a CSS background-image can still become the LCP element. The browser only finds it after the stylesheet is applied, though, which delays the download.
  • Only the first slide matters at load. Put that slide in the HTML as an <img> with fetchpriority="high" and no lazy loading. Mark the hidden slides fetchpriority="low", as Google’s LCP optimisation guide suggests for offscreen carousel images.

Project galleries follow the same pattern. The first image deserves priority, and every other photo can lazy-load as the buyer scrolls. Serve sizes that match the layout in AVIF or WebP, because fit-out photography exported for print is far larger than a phone screen needs.

Prices that appear late and images without sizes (CLS)

Trade-only pricing creates a layout problem specific to suppliers like these. The page loads, a script checks whether the visitor is logged in, and then the price, the add-to-basket button and a trade discount line appear. Everything below them moves.

The fix is to reserve the space. Render a placeholder of the same height as the price block, then fill it in. Better still, render the logged-in state on the server so the page arrives complete.

Unsized images are the other common cause. In 2024, 66% of mobile pages across the web had at least one image without set dimensions, with a median of two per page. On a salon site, category grids of chairs and project thumbnails are the usual places to check. Give each image width and height attributes, or a CSS aspect-ratio, so the browser can hold its space before the file arrives.

The same Web Almanac data shows CLS as the measure most often passed on mobile in 2024, with 79% of sites rated good. Desktop was lower, at 72%. So if a supplier’s product pages fail on CLS, it is worth tracing exactly which elements move and when.

Upholstery pickers and 3D chairs (INP)

Every tap on an upholstery swatch is an interaction that INP measures, and INP generally reports the slowest of the visit. A picker that swaps a large chair photograph, recalculates the price and updates a summary in one go can take longer than 200 milliseconds on a mid-range phone.

  • Swatch thumbnails should be tiny. A small square of vinyl or leather texture needs only a few kilobytes.
  • Fetch a colour’s chair image when the buyer shows interest, for example on hover or keyboard focus, and keep the current photo visible until the next is ready. Hovering is not an INP interaction in itself, so the fetch is not timed as one.
  • Do the cheap work first. Highlight the chosen swatch and update the colour name straight away, then swap the image.
  • Load 3D on request. A 3D chair viewer or salon layout planner should start with a still image and load the model only when the buyer asks for it. I explain the 3D side in how a 3D product configurator is built.

Social feeds, booking calendars and chat

Salon buyers respond to finished work, so some suppliers embed a feed of recent installs from social media. Those embeds load their own scripts, fonts and images, and they often resize once their content arrives. web.dev lists third-party widgets that resize among the causes of layout shift.

My advice is to replace live feeds with a static gallery you update yourself, or to load the feed only when the visitor scrolls near it, inside a container with a fixed height. The same thinking applies to consultation booking calendars, quote forms and live chat. Load each one after the main content is usable, and remove any that nobody can justify.

A speed review for a salon supplier

  1. In Search Console’s Core Web Vitals report, see whether failing URLs cluster around product pages, projects or the home page.
  2. Run the home page through PageSpeed Insights and note which element it reports as LCP. If it is not the first slide, find out why.
  3. Log in as a trade account on a phone and watch whether prices push content down as they appear.
  4. Check chair category grids and project thumbnails for missing image dimensions.
  5. On a mid-range phone, tap through five upholstery colours quickly and note any lag.
  6. List the third-party embeds on the home page and on one product page, with an owner for each.

If you would like this done for your site, see Core Web Vitals, or for WooCommerce, speed, caching and scripts. The rest of the series covers salon ecommerce SEO and selling salon and barbering equipment online, and the salon and barbering demos are there to try.

Sources