Camera shops sell a product whose whole purpose is images, and their pages show it. A body’s product page may carry a dozen angles, a sample gallery straight from the sensor, a video review, a lens compatibility finder and a trade-in calculator. A used stock page can list hundreds of individual units, each with its own photos.

Photographers notice image quality, so cutting it is not the answer. The answer is to load the right image at the right size at the right moment. This page sets out how Google measures speed and where camera pages tend to lose it.

How Google scores a camera page

Google’s Core Web Vitals are measured on real visits by Chrome users, and the score for each is the value that 75% of visits meet or beat. Phones and desktops get separate results.

MeasureQuestion it answersGoodPoor
LCPWhen does the main image or text appear2.5 s or underabove 4 s
INPHow quickly does a click, tap or key press get a visible response200 ms or underabove 500 ms
CLSHow far does the layout jump unexpectedly0.1 or underabove 0.25

Since 2024, INP has been the responsiveness metric, replacing First Input Delay. Field data comes from the Chrome UX Report and appears in PageSpeed Insights and Search Console. Lighthouse runs a single lab test, which is useful for finding causes but cannot report INP.

For a sense of scale, the 2024 Web Almanac performance chapter found that 43% of all sites passed every Core Web Vital on mobile, and 54% on desktop, using mid-2024 data. Those are figures for the whole web, not for camera retailers.

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

I ran five UK camera product pages through PageSpeed Insights on 23 October 2026, once each, using its mobile setting of an emulated mid-range phone on slow 4G.

PagePerformance scoreLab LCPTotal Blocking TimeLab CLS
Retailer A348.6 s8,310 ms0
Retailer B3915.6 s600 ms0.08
Retailer C2213.2 s3,160 ms0.118
Retailer D3620.4 s2,090 ms0.002

Blocking time stood out: the median was 2,625 ms, the highest of any industry I tested, and Retailer A blocked the main thread for over eight seconds. Lighthouse flagged forced reflow and layout shift culprits on all four pages, and three were flagged both for images without set dimensions and for how the LCP image was discovered, which matches the gallery and product shot problems below. The median score was 35 and the median lab LCP 14.4 seconds.

Points to bear in mind:

  • Lab runs on a throttled phone are far slower than typical visits, and Google does not use lab LCP.
  • Two of the four URLs had their own Chrome UX Report field data, and both passed Core Web Vitals. The other two had only whole-site data, and both of those sites failed.
  • Four camera pages are a small sample, not a ranking.
  • The fifth page refused the test with a 403 and was left out.

Sample galleries without the weight

Sample images are the camera-specific problem. Buyers want to judge sharpness, noise and colour, and a resized thumbnail cannot show that. Some shops respond by putting full-resolution files straight into the page.

In the 2024 Web Almanac, across all websites, 8% of mobile pages had an LCP image over 1,000 KB. A camera’s out-of-camera JPEG can be many times that. If the gallery’s first image is the largest thing on screen, it becomes the LCP element and the page waits for it.

  • Show resized versions in the page, sized to the layout with srcset, in WebP or AVIF.
  • Link to the original file for buyers who want to inspect it at full size. That download then happens only on request.
  • Lazy-load sample images below the fold. They are rarely the first thing a buyer sees.
  • Keep sample galleries off the critical path. A separate tab or section that loads on demand is fine for most visitors.

The main product shot

On a camera product page, the first product photo is typically the LCP element. The Web Almanac found an image was the LCP element on 73.3% of mobile pages and 83.3% of desktop pages in 2024, across all sites.

Two figures in that data point to easy gains. 16% of mobile pages whose LCP is an image lazy-loaded it, which delays it. And only 15% of mobile pages used fetchpriority="high" on the LCP image. Google’s LCP optimisation guide recommends the opposite on both counts:

  • Never set loading="lazy" on the first product image, including through a gallery plugin’s default settings.
  • Add fetchpriority="high" to that image alone. The guide says the benefit falls away if it is used on more than one or two images.
  • Keep it in the initial HTML as an <img> with src and srcset, not injected by a gallery script.
  • Serve it from the page’s own origin, ideally through a CDN in front of that origin.

A camera body shot on white compresses well. A dark body on a dark background, or a lens shot with fine texture on the grip, needs more care with quality settings to avoid visible banding.

Video reviews and demo reels

Video sells cameras, especially for hybrid shooters. An embedded review player on the product page can bring a large script bundle with it, often from another domain.

The LCP guide says a <video> element counts as an LCP candidate, timed from its poster image or first frame, whichever arrives first. A large self-hosted video near the top of the page can therefore become the element Google times.

  • Use a still image with a play button in place of the player, and load the real player when the buyer clicks.
  • Size that placeholder to the player’s final dimensions so nothing moves when it swaps.
  • Place video below the main gallery unless the product is sold mainly on its video features.

Lens finders and kit builders

Many camera shops offer tools such as “lenses for your camera”, a kit builder or a compare view for three bodies side by side. Each choice is an interaction, and INP counts clicks, taps and key presses for the whole visit, usually reporting the slowest. Scrolling and zooming do not count.

web.dev lists long tasks, heavy script evaluation, large layouts and a large DOM among the causes of slow responses. A lens finder that filters a full catalogue in the browser on every tap can trip all of those.

  • Filter on the server or in a web worker for large catalogues, and show a loading state at once.
  • Limit comparison tables to the rows that differ by default, with an option to show all specs.
  • Update the kit price and summary first when a lens is added, then refresh stock and delivery estimates.

The camera configurator page covers how a kit builder can work, and the camera demos let you try one.

Used stock listings

A used camera listing page is unusual: every item is unique, so every thumbnail is different, and new stock arrives daily. Condition badges, shutter counts and “just in” labels may load from a separate stock system.

CLS counts unexpected movement over the life of the page. Its causes include images with no set dimensions, content inserted above what is on screen, and asynchronously loaded content.

  • Give every thumbnail width and height, or a fixed aspect-ratio, so the grid holds its shape as images arrive.
  • Reserve space for condition badges and prices in each card.
  • Load more items below the existing ones, never above.
  • Lazy-load thumbnails below the first screen, but not the first row.

Trade-in calculators and finance offers on new body pages need the same treatment: a fixed space, filled when ready.

Testing a camera page step by step

  1. Open the Core Web Vitals report in Search Console and note which URL groups fail on mobile and on desktop.
  2. Run a new body page, a lens page and the used stock listing through PageSpeed Insights. Start with the field data.
  3. Find the LCP element on the body page. Check its file size, format and whether it is lazy-loaded.
  4. Check how large the sample images are as delivered to a phone.
  5. Click through the lens finder on a mid-range Android phone and note any choice that lags.
  6. Scroll the used listing on a phone over mobile data and watch for cards that move.

Faster image delivery rarely changes how a camera shop looks. If you would like help, see Core Web Vitals or, for WooCommerce shops, speed, caching and scripts. The rest of this series covers camera ecommerce SEO and selling cameras online.

Sources