theodderside.com website review

About 399 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

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

8 third-party services load with your homepage (FontAwesome CDN, Shopify and Yotpo and others), adding 16.5 MB and 1.5 s of main-thread time.

Shopify costs a phone 295 ms of main-thread work and 15.6 MB 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.

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

FontAwesome CDN costs a phone 624 ms of main-thread work and 36 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.

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

44 KiB could be saved by minifying JavaScript.

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

5 images could be 84 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

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

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

Your homepage downloads 19.5 MB in 332 requests on a phone: media 15.1 MB (5), images 1.9 MB (53) and scripts 1.4 MB (139). Under 2 MB keeps phones on slow connections fast.

9 images (848 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.

5 images further down the page (131 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

13 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 14 characters: “The Odder Side”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

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 165 pages on theodderside.com and 26 external pages.

https://theodderside.com/en/collections/all-products and https://theodderside.com/collections/wszystkie-produkty all use the title “Ubrania TheOdderSide – polskie produkty”. Search engines can't tell which page to show for a search, so each competes with the others.

https://theodderside.com/en/collections/new-in, https://theodderside.com/en/collections/aw-26, https://theodderside.com/en/collections/essence-aw26, https://theodderside.com/en/collections/justynas-picks and https://theodderside.com/en/collections/ss-26 have no meta description, so Google writes the search snippet from whatever text it finds.

https://theodderside.com/en/collections/all-products and https://theodderside.com/collections/wszystkie-produkty 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://theodderside.com/collections/wszystkie-produkty, whose canonical is https://theodderside.com/en/collections/all-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://theodderside.com/collections/wszystkie-produkty took over 3 s to send its HTML from our server.

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

30 of 75 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 “Failed to load resource: net::ERR_FAILED”.

Requests the geolocation permission on page load.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 31 cookies, 2 of them by other companies (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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.