Website review, no card needed
myoddballs.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 95 checks
This review found 46 issues worth fixing on myoddballs.co.uk, 16 of them high impact, across 95 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71C- #101,196 of 125,711 reviewed websitesbeats 17%
- #61,518 of 70,247 online storesbeats 10%
- #57,027 of 63,812 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 237 ms |
| May 23, 2026 | 234 ms |
| May 30, 2026 | 237 ms |
| Jun 6, 2026 | 244 ms |
| Jun 13, 2026 | 249 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 263 ms |
| Jul 11, 2026 | 269 ms |
| Jul 18, 2026 | 270 ms |
| Jul 25, 2026 | 265 ms |
| Aug 1, 2026 | 267 ms |
| Aug 8, 2026 | 270 ms |
| Aug 15, 2026 | 273 ms |
| Aug 22, 2026 | 274 ms |
| Aug 29, 2026 | 272 ms |
| Sep 5, 2026 | 269 ms |
| Sep 12, 2026 | 269 ms |
| Sep 19, 2026 | 276 ms |
| Sep 26, 2026 | 286 ms |
| Oct 3, 2026 | 294 ms |
| Oct 10, 2026 | 296 ms |
| Oct 17, 2026 | 300 ms |
| Oct 24, 2026 | 303 ms |
| Oct 31, 2026 | 306 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.4 s
4.5 s
5.6 s
6.7 s
7.8 s
9.0 s
Speed
Reduce unused JavaScript
1.9 s · 491 KiBAbout 491 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.
Use efficient cache lifetimes
1.6 s · 345 KiB24 files are served with short cache lifetimes, so returning visitors download them again (345 KiB).
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9,265 HTML elements
The page has 9,265 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 8.1 s
A phone's processor spends 8.1 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, stape.io and Snapchat and others), adding 3.3 MB and 866 ms of main-thread time.
Improve image delivery
300 ms · 418 KiB17 images could be 418 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 633 ms. During a long task the page ignores taps.
Render-blocking requests
350 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Reduce unused CSS
300 ms · 49 KiBAbout 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 adds 78 ms
78 msShopify costs a phone 78 ms of main-thread work and 2.0 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 adds 247 ms
247 msKlaviyo costs a phone 247 ms of main-thread work and 350 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 adds 102 ms
102 msLoyaltyLion costs a phone 102 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.
Legacy JavaScript
200 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Duplicated JavaScript
150 ms · 42 KiB42 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 32.9 s
32.9 sYour largest element takes 32.9 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% …”.
Time to Interactive: 34.0 s
34.0 sThe page becomes fully interactive after 34.0 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 892 ms
892 msScripts block taps and scrolling for 892 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 261 ms
261 msReal visitors wait 261 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 29% slower for real visitors
+29%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).
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%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).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 379 ms
379 msReal visitors wait 379 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 8.2 MB in 438 requests
8.2 MBYour homepage downloads 8.2 MB in 438 requests on a phone: images 4.7 MB (121), scripts 1.8 MB (148) and other files 1.0 MB (138). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
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 below the first screen load straight away
3 images further down the page (173 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.31 g of CO₂e: 277.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (144 elements)
All page content should be contained by landmarks: 144 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
24 links without text
24 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 (19 elements)
Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h4 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
29 links with vague text
29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Structured data has 2 problems
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…”.
336 internal links, 90 external
The homepage links to 336 pages on myoddballs.co.uk and 90 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Discover underwear, men’s boxer shorts & socks in bold designs. Comfortable, colourful & built for everyday. Free deliv…”.
Title: 49 characters
Your title is a healthy 49 characters: “OddBalls - The Underwear Everyone's Talking About”.
Canonical URL set
The canonical URL is https://www.myoddballs.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.myoddballs.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (4,319 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.myoddballs.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a title
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.
3 pages without a meta description
https://www.myoddballs.com/collections/the-flintstones, https://www.myoddballs.com/collections/elf and https://www.myoddballs.com/pages/subscription-selector have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
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.
2 links to non-canonical URLs
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.
13 pages without an H1
https://www.myoddballs.com/collections/mr-men-little-miss, https://www.myoddballs.com/collections/the-flintstones, https://www.myoddballs.com/pages/christmas-underwear-pyjamas-socks, https://www.myoddballs.com/collections/christmas-matching-pyjamas, https://www.myoddballs.com/collections/matching-pyjamas and https://www.myoddballs.com/collections/mens-christmas-pyjamas and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.myoddballs.com/pages/christmas-underwear-pyjamas-socks, https://www.myoddballs.com/collections/christmas-matching-pyjamas/department-kids, 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 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 142 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image 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
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
90 of 107 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 2,647 words of copy
The homepage carries about 2,647 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP CHRISTMAS”.
24 calls to action
The homepage has 24 calls to action, for example “Shop The Flintstones 🦴”, “Shop Elf 🍭” and “JOIN THE PANTS PARTY NOW”.
8 short forms
8 short forms (6 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 27 customer or partner logos, a star rating and 85 trust badges.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
13 trackers load before any consent
13Before 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.
37 cookies set on arrival
37Opening the homepage sets 37 cookies (measured from a US location before any click).
No consent tool detected
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.
67 other companies contacted
Loading the homepage contacts 67 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at myoddballs.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Tapcart Mobile App · Zigpoll Customer Surveys · Triplewhale · Loyalty Rewards And Referrals · Elevate Ab Testing · Nosto · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Customerjourney Intelligence · snapchat.com · 9gtb.com · cloudfront.net · amazonaws.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on myoddballs.co.uk, including 21 speed issues, 3 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.