Website review, no card needed
polydor.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 82 checks
This review found 35 issues worth fixing on polydor.co.uk, 8 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
75C- #77,669 of 117,972 reviewed websitesbeats 30%
- #49,679 of 67,058 online storesbeats 22%
- #46,958 of 61,142 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 140 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 134 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 128 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 131 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 153 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
Speed
8,043 HTML elements
The page has 8,043 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, transcend-cdn.com and digitalgenius.com and others), adding 1.2 MB and 678 ms of main-thread time.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
300 ms · 292 KiB15 images could be 292 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.
Google Tag Manager adds 502 ms
502 msGoogle Tag Manager costs a phone 502 ms of main-thread work and 808 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.
Reduce unused JavaScript
509 KiBAbout 509 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 255 KiB13 files are served with short cache lifetimes, so returning visitors download them again (255 KiB).
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 24 KiBAbout 24 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
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: 32 ms
32 msYour server sent the HTML in 32 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.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 255 ms
255 msReal visitors wait 255 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 881 ms
881 msReal visitors wait 881 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 501 ms
501 msScripts block taps and scrolling for 501 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 140 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 230 requests
4.0 MBYour homepage downloads 4.0 MB in 230 requests on a phone: images 1.7 MB (69), scripts 1.4 MB (57) and other files 782 KiB (94). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
2hollis_Mobile_1.png 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 1.1 g of CO₂ per visit
1.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.15 g of CO₂e: 137.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “Polydor Store UK - Official Store - Shop Exclusive Vinyl, CDs, Merch & More”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Official Store - Shop Exclusive Vinyl, CDs, Merch…” and “Official Store - Shop Exclusive Vinyl, CDs, Merch…”). One clear main headline is easier for people and search engines.
455 internal links, 8 external
The homepage links to 455 pages on polydor.co.uk and 8 external pages.
5 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “The official Polydor Label Group online store. Shop exclusive vinyl, CDs, cassettes, merchandise and more from Polydor,…”.
Canonical URL set
The canonical URL is https://polydor.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.
XML sitemap found
Your XML sitemap is reachable at https://polydor.co.uk/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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 (2,473 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://polydor.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages share a meta description
https://polydor.co.uk/pages/artists, https://polydor.co.uk/collections/pre-order, https://polydor.co.uk/collections/pop, https://polydor.co.uk/collections/rock, https://polydor.co.uk/collections/kpop and https://polydor.co.uk/collections/alternative and 9 others use the same meta description. A description written for each page earns more clicks.
10 pages slow to respond
https://polydor.co.uk/collections/kpop, https://polydor.co.uk/collections/alternative, https://polydor.co.uk/collections/hip-hop-r-b, https://polydor.co.uk/collections/indie, https://polydor.co.uk/collections/soundtracks and https://polydor.co.uk/collections/cd and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 160 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'window'”.
2 checks passed
Tap targets are thumb-sized
251 of 260 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 2,031 words of copy
The homepage carries about 2,031 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “PRE-ORDER”.
7 calls to action
The homepage has 7 calls to action, for example “PRE-ORDER”, “Pre-Order” and “Shop All”.
111 short forms
111 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
11 other companies contacted
Loading the homepage contacts 11 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 polydor.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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 Tag Manager
- Hosting
- Shopify
Company
- Employees
- 120
- Founded
- 1913
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on polydor.co.uk, including 18 speed issues, 3 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.