Appliance Website Performance: Core Web Vitals Guide

Appliance shoppers compare. They open a washing machine, go back to the list, open the next one, tick two models to compare, check a delivery date against their postcode and come back the following day to do it again. Appliance product pages, meanwhile, tend to carry manufacturer feature content, energy label pop-ups, cashback banners, finance offers and installation options. A site that is slow at any step of that loop is slow many times per visit.

This page explains how Google measures speed and where appliance sites typically lose it.

What Google measures

Google’s Core Web Vitals are drawn from real Chrome users and judged at the 75th percentile, with mobile and desktop scored apart.

LCP, loading: the largest image, text block or video in view should render within 2.5 seconds. Beyond 4 seconds is poor.
INP, responsiveness: after a click, tap or key press, the next frame should appear within 200 ms. Beyond 500 ms is poor. The score is usually the visit’s slowest interaction.
CLS, stability: unexpected layout movement should score 0.1 or less. Above 0.25 is poor.

Field figures appear in Search Console and at the top of PageSpeed Insights. Lighthouse produces lab figures for diagnosis but cannot measure INP.

What I measured on UK appliance product pages (October 2026)

I tested five UK appliance product pages in PageSpeed Insights on 23 October 2026, in mobile mode, which emulates a mid-range phone on slow 4G, with one run per page.

Page	Performance score	Lab LCP	Total Blocking Time	Lab CLS
Retailer A	31	15.9 s	1,180 ms	0.083
Retailer B	38	17.5 s	810 ms	0
Retailer C	8	24.9 s	5,090 ms	0.338
Retailer D	31	21.0 s	550 ms	0.25

This was one of the slowest groups I tested: a median score of 31, a median lab LCP of about 19 seconds and median blocking time just under a second. Lighthouse flagged images without set dimensions, the discovery of the LCP image and forced reflow on all four pages, and three had layout shift culprits, which fits the late promotions and syndicated content described below. Retailer C scored 8, with over five seconds of blocking time and a lab CLS of 0.338.

Keep these limits in mind:

A throttled lab phone exaggerates load times compared with most real visits, and lab LCP is not Google’s measure.
Only Retailer A’s URL had its own field data in the Chrome UX Report, and it failed Core Web Vitals. Of the other three, judged on whole-site data, one passed.
Four pages make a small sample, so treat this as a snapshot rather than a ranking.
The fifth page returned a 410, meaning the product URL had been removed, so it was left out.

Make the back button instant

Because appliance buyers tend to move back and forth between listings and product pages, I think the back/forward cache matters more here than on many sites. It lets the browser restore a page from memory when someone presses back, instead of loading it again. Google’s CLS documentation also notes that a page restored this way starts again with a CLS of zero.

The 2024 Web Almanac performance chapter, covering all websites in mid-2024, found that 21% of pages sent Cache-Control: no-store and around 15 to 16% used unload handlers. Both can stop a page being kept in the back/forward cache.

Check listing and product pages in Chrome DevTools under Application, then Back/forward cache. It reports why a page was not eligible.
Reserve no-store for pages that genuinely need it, such as the basket or account area. Listing and product pages rarely do.
Replace unload handlers in analytics or chat scripts with pagehide, or ask the vendor to.

Syndicated manufacturer content

Some retailers receive manufacturer feature content, such as feature tiles, videos and comparison panels, through a syndication script that injects it after the page loads. The content helps sell, but the way it arrives can hurt all three measures.

INP. If the script runs on the main thread just as the page becomes usable, a buyer who taps a colour or the add-to-basket button at that moment can be left waiting behind it.
CLS. Google’s CLS guidance lists content inserted above existing content and asynchronously loaded content among the causes of shift. A feature block that appears above the specification or reviews pushes them down.
LCP. Feature images served from another host need an extra connection, and you may have no control over their size or format.

The fixes: load the script after the page is usable, place its container below the first screen, and give that container a reserved minimum height. Where the manufacturer allows it, host the assets yourself as static images and HTML.

The product photo, the price and server response (LCP)

On an appliance page, the LCP element is often the main product photo. On narrow screens it can instead be the product title or price block. Google’s LCP optimisation guide covers both cases.

Render price and stock on the server. If they come from a client-side request, the text block may be drawn late, and Google advises against hiding the LCP element until JavaScript has loaded.
Put the main photo in the HTML with src and srcset, give it fetchpriority="high", and do not lazy-load it.
Watch server response time. In the 2024 Web Almanac data, only 42% of mobile sites had a good time to first byte. Visitors from comparison sites, affiliates and voucher sites can arrive with unique tracking parameters, which Google’s guide notes can stop a CDN serving its cached copy. Set the CDN to ignore parameters that do not change the page.

Compare tools and filters (INP)

The 2024 Web Almanac found INP was good on 74% of mobile sites and 97% of desktop sites, so in 2024 responsiveness problems showed up mainly on phones. Appliance sites ask for a lot of taps.

Compare ticks. Each tick on a “compare” box is an interaction. Update the tick and the compare tray at once, and build the full comparison table only on the compare page.
Filter taps. Width, capacity, energy class and integrated or freestanding are typical filters. Show a loading state at once, then update the grid. Paginate rather than drawing every model.
Tile spec lists. Product tiles that list five or six specifications each add a lot of page structure. Keep the markup simple, since a large DOM can slow every update.

Postcode checkers, delivery slots and installation options

Typing a postcode is several key presses, and INP counts every one. A checker that sends a request on each key press, or redraws a delivery calendar as the buyer types, can feel sluggish.

Validate the postcode format in the browser, and send one lookup when the buyer submits or pauses.
Show the result in space that already exists on the page, so the add-to-basket button does not move.
Load the delivery calendar only after a valid postcode, and give it a fixed size.
Installation and recycling options that expand on tap are fine for CLS, since shifts within 500 ms of a tap are excluded.

Promotions, finance and energy labels (CLS)

Appliance pages often display cashback offers, price promises, countdown timers and finance calculators, often added by scripts after load.

Reserve space for every promotional slot, including when the slot is empty for some products.
Use a fixed overlay, not an inserted bar, for site-wide offers.
Load the full energy label image when the buyer opens it, not on page load, and show the class badge as a small sized image or text. Check that any change to how the label is displayed still meets the energy labelling rules for online sales.
Give every image width and height.

An appliance site speed check

In Search Console’s Core Web Vitals report, see whether product or listing URLs fail, and on which device.
Run a popular model page through PageSpeed Insights. Note whether the LCP element is the photo or the price.
Press back from a product page to a listing in Chrome and check the back/forward cache panel for blocking reasons.
Load a product page and watch where the manufacturer content appears. Does anything move?
Tick three compare boxes quickly on a mid-range Android phone.
Type a postcode into the delivery checker and watch the network panel for requests per key press.
Request a product URL with and without a tracking parameter, and compare the CDN cache headers.

Most of these changes are invisible to buyers except in how quickly pages respond. For help, see Core Web Vitals, Shopify speed optimisation or WooCommerce speed, caching and scripts. The other pages in this series are appliance ecommerce SEO and selling appliances online, and examples are collected in the appliance configurator demos.

Sources

web.dev, checked October 2026: Web Vitals, LCP, Optimise LCP (price blocks and CDN caching), INP (compare ticks and postcode entry), and CLS (syndicated content and back/forward cache restores).
HTTP Archive, Web Almanac 2024: Performance, November 2024. Mid-2024 figures across all websites, not appliance retailers; mobile and desktop are labelled where given.
My own tests: PageSpeed Insights, 5 UK product pages per industry, 23 October 2026, for the appliance results table above.