Website review, no card needed
admiralsports.com website review
Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 83 checks
This review found 30 issues worth fixing on admiralsports.com, 10 of them high impact, across 83 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
84B- #22,341 of 125,423 reviewed websitesbeats 77%
- #14,306 of 70,179 online storesbeats 74%
- #13,871 of 63,765 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 977 ms |
| Jun 6, 2026 | 956 ms |
| Jun 13, 2026 | 923 ms |
| Jun 20, 2026 | 929 ms |
| Jun 27, 2026 | 957 ms |
| Jul 4, 2026 | 986 ms |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 996 ms |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 80 ms |
| May 23, 2026 | 81 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 76 ms |
| Jun 20, 2026 | 75 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 77 ms |
| Jul 11, 2026 | 80 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 92 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 90 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 91 ms |
| Sep 19, 2026 | 90 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 96 ms |
| Oct 31, 2026 | 102 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.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.5 s
Speed
Reduce unused JavaScript
2.0 s · 323 KiBAbout 323 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Improve image delivery
1.1 s · 617 KiB8 images could be 617 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.2 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Klaviyo and others), adding 1.5 MB and 1.0 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 100 KiB21 files are served with short cache lifetimes, so returning visitors download them again (100 KiB).
Google Tag Manager adds 473 ms
473 msGoogle Tag Manager costs a phone 473 ms of main-thread work and 511 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 163 ms
163 msKlaviyo costs a phone 163 ms of main-thread work and 501 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.
1,622 HTML elements
The page has 1,622 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.0 s
18.0 sYour largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SALE: Black November”.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 80 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 386 ms
386 msScripts block taps and scrolling for 386 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
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 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 116 ms
116 msReal visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 500 ms
500 msReal visitors wait 500 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: 3.9 MB in 260 requests
3.9 MBYour homepage downloads 3.9 MB in 260 requests on a phone: scripts 1.5 MB (116), images 1.4 MB (34) and other files 630 KiB (71). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (368 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.
2 images below the first screen load straight away
2 images further down the page (51 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 131.8 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<svg> elements with an img or image role must have alternative text (5 elements)
<svg> elements with an img or image role must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“SALE: Black November”, “New In Training” and “Journal”). One clear main headline is easier for people and search engines.
152 internal links, 7 external
The homepage links to 152 pages on admiralsports.com and 7 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “The official Admiral Sports site. Explore teamwear for your football club plus retro and performance styles from Britai…”.
Title: 49 characters
Your title is a healthy 49 characters: “Admiral Sports | Teamwear and Sportswear Clothing”.
Canonical URL set
The canonical URL is https://admiralsports.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://admiralsports.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,309 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://admiralsports.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://admiralsports.com/pages/contact has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://admiralsports.com/pages/kitbuilder has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 103 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
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 750 words of copy
The homepage carries about 750 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: “SALE: Black November SHOP NOW” and “SHOP NOW”.
17 calls to action
The homepage has 17 calls to action, for example “Contact”, “Admiral Book” and “Shop now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 admiralsports.com, 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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pify Size Charts · Klaviyo Email Marketing Sms · Free Contact Form · perfectapps.io · trustpilot.com · goaffpro.com · Qikify
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 1914
- Headquarters
- Manchester
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on admiralsports.com, including 16 speed issues, 1 SEO issue 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.