Website review, no card needed
jdsports.co.uk website review
Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 82 checks
This review found 40 issues worth fixing on jdsports.co.uk, 17 of them high impact, across 82 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 410 ms |
| May 16, 2026 | 411 ms |
| May 23, 2026 | 416 ms |
| May 30, 2026 | 410 ms |
| Jun 6, 2026 | 410 ms |
| Jun 13, 2026 | 408 ms |
| Jun 20, 2026 | 408 ms |
| Jun 27, 2026 | 410 ms |
| Jul 4, 2026 | 415 ms |
| Jul 11, 2026 | 413 ms |
| Jul 18, 2026 | 411 ms |
| Jul 25, 2026 | 378 ms |
| Aug 1, 2026 | 386 ms |
| Aug 8, 2026 | 396 ms |
| Aug 15, 2026 | 410 ms |
| Aug 22, 2026 | 426 ms |
| Aug 29, 2026 | 445 ms |
| Sep 5, 2026 | 453 ms |
| Sep 12, 2026 | 445 ms |
| Sep 19, 2026 | 433 ms |
| Sep 26, 2026 | 419 ms |
| Oct 3, 2026 | 408 ms |
| Oct 10, 2026 | 405 ms |
| Oct 17, 2026 | 420 ms |
| Oct 24, 2026 | 438 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
0.4 s
0.8 s
1.2 s
1.7 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Reduce unused JavaScript
9.0 s · 2.6 MBAbout 2.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.0 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 4.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,993 HTML elements
The page has 6,993 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 4.8 MB67 files are served with short cache lifetimes, so returning visitors download them again (4.8 MB).
Improve image delivery
1.5 MB22 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
850 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Optanon and csidetm.com and others), adding 5.5 MB and 201 ms of main-thread time.
Amplience adds 0 ms
0 msAmplience costs a phone 0 ms of main-thread work and 5.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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 452 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 64 KiBAbout 64 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.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 33 ms
33 msYour server sent the HTML in 33 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.
Real-user INP: 654 ms
654 msReal visitors wait 654 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.35
0.35For real visitors the layout shifts by 0.35 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 26.4 s
26.4 sYour largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “offer”.
Time to Interactive: 42.3 s
42.3 sThe page becomes fully interactive after 42.3 s. Good is under 3.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 410 ms to 438 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 602 ms
602 msReal visitors wait 602 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.0 MB in 226 requests
11.0 MBYour homepage downloads 11.0 MB in 226 requests on a phone: scripts 4.7 MB (82), media 2.9 MB (2) and images 2.1 MB (61). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
1.2 MB6 images are downloaded at several times the size a phone draws them, for example DESK-DISCOVER_SPOT-840x760 at 1,680 px wide, shown at 90 px. Resized copies would save about 1.2 MB.
7 images in older formats
7 images (1.3 MB) 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.
An image on the first screen is lazy-loaded
MOBILE-TOP-BANNER-750x1000_1 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.1 g of CO₂ per visit
3.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.11 g of CO₂e: 373.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 2 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.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.
No XML sitemap
No XML sitemap at https://www.jdsports.co.uk/sitemaps/index-sitemap.xml, so Google discovers your pages only by following links.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
684 internal links, 54 external
The homepage links to 684 pages on jdsports.co.uk and 54 external pages.
5 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Shop the biggest brands online now at JD Sports ✓Free Standard Delivery ✓10% Student Discount ✓ Top Picks 20% Off”.
Title: 30 characters
Your title is a healthy 30 characters: “JD Sports UK - Forever Forward”.
Canonical URL set
The canonical URL is https://www.jdsports.co.uk/.
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.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, 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.
No llms.txt
There is no https://www.jdsports.co.uk/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.
2 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 (1,531 words), so crawlers that don't run JavaScript still read it.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.jdsports.co.uk/page/football, whose canonical is https://www.jdsports.co.uk/sport/football. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.jdsports.co.uk/page/football and https://www.jdsports.co.uk/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.jdsports.co.uk/men, https://www.jdsports.co.uk/men/mens-footwear and https://www.jdsports.co.uk/men/mens-clothing took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 193 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 7 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
117 of 120 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 457 words of copy
The homepage carries about 457 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “Shop at JD - United Kingdom”.
15 calls to action
The homepage has 15 calls to action, for example “Shop Now”, “Shop The Molly Mae Collection” and “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 jdsports.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- AWS
Hiring
- Hiring
- 224 open roles
- Teams
- Retail Sales Assistants & Supervisors (99), Retail Sales Advisor (69), Retail Store Management (15), Retail (10)
- Job board
- greenhouse
Company
- Founded
- 1981
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on jdsports.co.uk, including 20 speed issues, 5 SEO issues and 4 conversion gaps. 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.