pyrex.co.uk website review

76 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

The page has 13,799 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

Optanon costs a phone 1.3 s of main-thread work and 402 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 8.9 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Optanon, Google Tag Manager and Shopify and others), adding 1.4 MB and 1.9 s of main-thread time.

About 627 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

17 files are served with short cache lifetimes, so returning visitors download them again (164 KiB).

Google Tag Manager costs a phone 440 ms of main-thread work and 466 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

19 long tasks block the main thread while loading, the longest for 304 ms. During a long task the page ignores taps.

Shopify costs a phone 87 ms of main-thread work and 472 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 22 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 27.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 31.9 s. Good is under 3.8 s.

Visually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 968 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 287 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 139 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

5 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 19.1 MB in 495 requests on a phone: images 16.1 MB (224), scripts 1.4 MB (95) and other files 883 KiB (119). Under 2 MB keeps phones on slow connections fast.

22 images are downloaded at several times the size a phone draws them, for example AF22SR6_-_2.jpg at 389 px wide, shown at 60 px. Resized copies would save about 2.2 MB.

2 images (189 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 5.43 g of CO₂e: 651.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

2 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

<marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

70 visible links have no text or label, so screen readers cannot say where they go.

ARIA role should be appropriate for the element: 59 elements on the page fail this check, rated minor by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 17 characters: “Pyrex® Webshop UK”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 608 pages on pyrex.co.uk and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://pyrex.co.uk/$%7Bproduct.url%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

https://pyrex.co.uk/blogs/recipe/spinach-radish-parmesan-dressing-salad has no meta description, so Google writes the search snippet from whatever text it finds.

https://pyrex.co.uk/collections/comfort-food, https://pyrex.co.uk/collections/air-fryer-dishes, https://pyrex.co.uk/collections/food-storage-containers, https://pyrex.co.uk/collections/cake-tins and https://pyrex.co.uk/collections/all-products have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 155 found) and read each the way a search engine does.

79 of 200 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Swiper is not defined https://pyrex.co.uk/cdn/shop/t/160/assets/section-featured-single-collection.js?v=167431828028081…”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,243 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 15 cookies (measured from a US location before any click).

Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.