oneill.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and web.app and others), adding 1.4 MB and 690 ms of main-thread time.

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

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

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

Klaviyo costs a phone 135 ms of main-thread work and 358 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.

web.app costs a phone 110 ms of main-thread work and 315 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 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

45 KiB could be saved by minifying JavaScript.

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

Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WOMEN SNOW MEN SNOW KIDS SNOW”.

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

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

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

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

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

The layout shifts by 0.168 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 180 ms to 179 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 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.2 MB in 449 requests on a phone: media 9.1 MB (2), images 2.5 MB (44) and scripts 1.9 MB (93). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 9 elements on the page fail 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.

2 form fields have 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.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

There are 2 <h1> headlines (“O'Neill” and “Follow us @oneilleurope”). One clear main headline is easier for people and search engines.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 280 pages on oneill.com and 22 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://eu.oneill.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://eu.oneill.com/collections/snow-collection-2026 has no meta description, so Google writes the search snippet from whatever text it finds.

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

6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'let'”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The page uses urgency cues (a countdown or limited-time wording).

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

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

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