pyrexae.com website review

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

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

68 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

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

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

About 498 KiB of JavaScript is downloaded but never used on this page.

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

Optanon costs a phone 215 ms of main-thread work and 426 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.

Google Tag Manager costs a phone 225 ms of main-thread work and 313 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.

Shopify costs a phone 101 ms of main-thread work and 517 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 files are served with short cache lifetimes, so returning visitors download them again (177 KiB).

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

Polyfills for old browsers add 17 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.

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 25.3 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 30.1 s. Good is under 3.8 s.

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

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

Real visitors wait 403 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 227 ms to 296 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

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

Your homepage downloads 22.6 MB in 616 requests on a phone: images 19.5 MB (296), scripts 1.3 MB (104) and other files 979 KiB (151). Under 2 MB keeps phones on slow connections fast.

banner_airfryer_EU.svg weighs 3.6 MB. On a phone connection a single image that size takes seconds.

banner_airfryer_EU.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (61 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 13 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 17 characters: “Pyrex® Webshop EU”. 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.

9 links have no real href, so search engines can't follow them.

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 545 pages on pyrexae.com and 0 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://www.pyrex.eu/$%7Bproduct.url%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and https://www.pyrex.eu/a/wishlist all use the title “Pyrex® Webshop EU”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pyrex.eu/collections/nouveautes, https://www.pyrex.eu/pages/la-marque, https://www.pyrex.eu/blogs/blogs, https://www.pyrex.eu/a/wishlist, https://www.pyrex.eu/collections/promos and https://www.pyrex.eu/collections/cuisson and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.pyrex.eu/pages/la-marque, whose canonical is https://www.pyrex.eu/pages/histoire. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.pyrex.eu/collections/nouveautes, https://www.pyrex.eu/collections/promos, https://www.pyrex.eu/collections/cuisson and https://www.pyrex.eu/collections/plat-en-verre have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.pyrex.eu/a/wishlist and https://www.pyrex.eu/collections/promos took over 3 s to send their HTML from our server.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

3 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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,309 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager 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 8 cookies (measured from a US location before any click).

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