Website review, no card needed
mirror.co.uk website review
Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 81 checks
This review found 33 issues worth fixing on mirror.co.uk, 14 of them high impact, across 81 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
68DClosest 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.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 530 ms |
| May 16, 2026 | 502 ms |
| May 23, 2026 | 469 ms |
| May 30, 2026 | 451 ms |
| Jun 6, 2026 | 427 ms |
| Jun 13, 2026 | 415 ms |
| Jun 20, 2026 | 413 ms |
| Jun 27, 2026 | 402 ms |
| Jul 4, 2026 | 399 ms |
| Jul 11, 2026 | 392 ms |
| Jul 18, 2026 | 385 ms |
| Jul 25, 2026 | 383 ms |
| Aug 1, 2026 | 383 ms |
| Aug 8, 2026 | 391 ms |
| Aug 15, 2026 | 398 ms |
| Aug 22, 2026 | 403 ms |
| Aug 29, 2026 | 411 ms |
| Sep 5, 2026 | 415 ms |
| Sep 12, 2026 | 406 ms |
| Sep 19, 2026 | 364 ms |
| Sep 26, 2026 | 327 ms |
| Oct 3, 2026 | 294 ms |
| Oct 10, 2026 | 269 ms |
| Oct 17, 2026 | 271 ms |
| Oct 24, 2026 | 272 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
2.0 s
3.9 s
5.9 s
7.9 s
9.8 s
11.8 s
13.8 s
15.8 s
Speed
Reduce unused JavaScript
3.3 s · 2.7 MBAbout 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Main-thread work: 22.0 s
A phone's processor spends 22.0 s on main-thread work while loading, 12.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 5
5/100Your mobile performance score is 5. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Avoid multiple page redirects
754 msThe page goes through 1 redirect before it starts loading, costing about 754 ms. Link and advertise the final URL directly.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 685 ms. During a long task the page ignores taps.
awswaf.com adds 91 ms
91 msawswaf.com costs a phone 91 ms of main-thread work and 305 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 third-party service on the page
1 third-party service load with your homepage (awswaf.com), adding 305 KiB and 91 ms of main-thread time.
Minify JavaScript
22 KiB22 KiB could be saved by minifying JavaScript.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 99 ms
99 msYour server sent the HTML in 99 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.
First Contentful Paint: 11.0 s
11.0 sThe first text or image appears after 11.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.3 s
23.3 sYour largest element takes 23.3 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 28.3 s
28.3 sVisually, the page fills in at 28.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 4.7 s
4.7 sScripts block taps and scrolling for 4.7 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 84.6 s
84.6 sThe page becomes fully interactive after 84.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.446
0.446The layout shifts by 0.446 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 365 ms
365 msReal visitors wait 365 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
7 images without width and height
7 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-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 342 ms
342 msReal visitors wait 342 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 47% faster for real visitors
-47%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 530 ms to 272 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.4 MB in 1,242 requests
9.4 MBYour homepage downloads 9.4 MB in 1,242 requests on a phone: scripts 6.3 MB (144), other files 1.2 MB (582) and images 943 KiB (337). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
0_MAIN-HEALEY1.jpg 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 2.7 g of CO₂ per visit
2.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.68 g of CO₂e: 321.2 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
Links must have discernible text (3 elements)
Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
250 internal links, 56 external
The homepage links to 250 pages on mirror.co.uk and 56 external pages.
8 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Get the latest news, sport, celebrity gossip, TV, politics and lifestyle from The Mirror. Big stories with a big heart,…”.
One H1 headline
Your main headline reads: “The Mirror: The Heart of Britain”.
Title: 32 characters
Your title is a healthy 32 characters: “The Mirror: The Heart of Britain”.
Canonical URL set
The canonical URL is https://www.mirror.co.uk/.
Structured data in place
Structured data found: CollectionPage.
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.mirror.co.uk/map_news.xml.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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.
No llms.txt
There is no https://www.mirror.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.
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,285 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.mirror.co.uk/all-about/crime has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://www.mirror.co.uk/news, https://www.mirror.co.uk/3am, https://www.mirror.co.uk/sport/football, https://www.mirror.co.uk/lifestyle, https://www.mirror.co.uk/news/uk-news and https://www.mirror.co.uk/news/politics and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.mirror.co.uk/lifestyle and https://www.mirror.co.uk/opinion have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://www.mirror.co.uk/opinion and https://www.mirror.co.uk/news/weird-news took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 140 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
1 broken image
1 image failed to load on a phone, for example https://www.facebook.com/tr?id=331470507705028&ev=PageView&noscript=1.
86 small tap targets
86 of 110 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
36 third-party cookies
36 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 1,110 words of copy
The homepage carries about 1,110 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe to premium membership” and “SHOP”.
8 calls to action
The homepage has 8 calls to action, for example “Shop”, “Newsletter Signup” and “Yimbly Shop”.
Privacy and tracking
13 trackers load before any consent
13Before a visitor clicks anything, the page loads Amazon Ads, Amplitude, Comscore, Criteo and Google Ads 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
125 other companies contacted
Loading the homepage contacts 125 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 mirror.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
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on mirror.co.uk, including 15 speed issues and 3 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.