keringeyewear.com website review

122 files are served with short cache lifetimes, so returning visitors download them again (35.1 MB).

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).

Your mobile performance score is 59 (desktop: 54). Pages that score under 90 lose visitors before the first paint.

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

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

About 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

3 third-party services load with your homepage (Optanon, Google Tag Manager and Adobe TypeKit), adding 328 KiB and 147 ms of main-thread time.

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

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

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.

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

Your largest element takes 324.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “In addition to the cookies that are strictly necessary for …”.

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

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

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

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

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-17, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 175.6 MB in 146 requests on a phone: images 142.7 MB (102), media 32.4 MB (17) and scripts 363 KiB (13). Under 2 MB keeps phones on slow connections fast.

40 images weigh 94.2 MB together. On a phone connection a single image that size takes seconds.

40 images (94.2 MB) 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 49.77 g of CO₂e: 5972.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

2 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 25 characters: “Homepage | Kering Eyewear”. 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.

There are 15 <h1> headlines (“LINDBERG”, “Maui Jim” and “Gucci”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing 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 127 pages on keringeyewear.com and 9 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.

There is no https://www.keringeyewear.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/, https://www.keringeyewear.com/it, https://www.keringeyewear.com/fr and https://www.keringeyewear.com/zh all use the title “Homepage | Kering Eyewear”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.keringeyewear.com/it, https://www.keringeyewear.com/fr, https://www.keringeyewear.com/zh, https://www.keringeyewear.com/brands, https://www.keringeyewear.com/about and https://www.keringeyewear.com/join-us and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.keringeyewear.com/it, whose canonical is https://www.keringeyewear.com/it/homepage. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.keringeyewear.com/brands, https://www.keringeyewear.com/brands/lindberg, https://www.keringeyewear.com/brands/mauijim, https://www.keringeyewear.com/brands/gucci, https://www.keringeyewear.com/brands/cartier and https://www.keringeyewear.com/brands/saint-laurent and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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