myoddballs.com website review

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

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

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Klaviyo, stape.io and Shopify and others), adding 3.4 MB and 797 ms of main-thread time.

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

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

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

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

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

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

LoyaltyLion costs a phone 64 ms of main-thread work and 365 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.

Polyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

42 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

2 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 33.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Win Up To 10% Off Your First Order 🎁 5% Off Not Today 10% …”.

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

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

Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

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

39 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' largest content (lcp) went from 2.4 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.2 MB in 439 requests on a phone: images 4.7 MB (120), scripts 1.8 MB (148) and other files 1.1 MB (140). Under 2 MB keeps phones on slow connections fast.

3 images (175 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.

3 images further down the page (153 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 2.34 g of CO₂e: 280.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

6 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Structured data found (BreadcrumbList and Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.myoddballs.com/cdn/shop/files/OddBalls_Logo_Black…”.

The homepage links to 362 pages on myoddballs.com and 95 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://www.myoddballs.com/collections/matching-pyjamas, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.myoddballs.com/collections/christmas-matching-pyjamas, https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-ladies and https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-kids all use the title “Christmas Pyjamas | Matching & Family Sets | OddBalls”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.myoddballs.com/collections/garfield, https://www.myoddballs.com/pages/subscription-selector, https://www.myoddballs.com/collections/alpine and https://www.myoddballs.com/collections/stormtrooper have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.myoddballs.com/collections/christmas-matching-pyjamas, https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-ladies and https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-kids use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-ladies, whose canonical is https://www.myoddballs.com/collections/christmas-matching-pyjamas. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.myoddballs.com/collections/stormtrooper, https://www.myoddballs.com/collections/christmas-matching-pyjamas, https://www.myoddballs.com/collections/christmas-underwear, https://www.myoddballs.com/collections/christmas-boxers, https://www.myoddballs.com/collections/penguins and https://www.myoddballs.com/collections/christmas-tartan and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example url:'//www.myoddballs.com/cdn/shop/files/TOPGUNM.BRIEFFRONT_medium.png?v=1726978164.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 8 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 35 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 69 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.