oodie.eu website review

11 images could be 994 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

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

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

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

Shopify costs a phone 270 ms of main-thread work and 397 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.

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

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

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

About 39 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.

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

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

Your largest element takes 8.9 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 14.7 s. Good is under 3.8 s.

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

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

3 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 146 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 300 requests on a phone: images 1.9 MB (43), scripts 1.1 MB (120) and other files 798 KiB (105). Under 2 MB keeps phones on slow connections fast.

2 images (408 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.

1 image further down the page (21 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 1.20 g of CO₂e: 144.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Your <h1> is empty.

The homepage links to 219 pages on oodie.eu and 9 external pages.

https://oodie.eu/collections/oodie%E2%84%A2-original-classic, https://oodie.eu/collections/original-oodies, https://oodie.eu/collections/50-off-black-friday-sale, https://oodie.eu/collections/40-off-black-friday-sale-copy, https://oodie.eu/collections/30-off-black-friday-sale and https://oodie.eu/collections/10-off-black-friday-sale and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://oodie.eu/collections/oodie%E2%84%A2-original-classic, whose canonical is https://oodie.eu/collections/oodie%e2%84%a2-original-classic. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://oodie.eu/collections/products, https://oodie.eu/collections/oodie%E2%84%A2-original-classic, https://oodie.eu/collections/original-oodies, https://oodie.eu/collections/50-off-black-friday-sale, https://oodie.eu/collections/40-off-black-friday-sale-copy and https://oodie.eu/collections/30-off-black-friday-sale and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://oodie.eu/.

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

3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'replaceAll')”.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 504 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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