Website review, no card needed
dailymail.co.uk website review
Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 90 checks
This review found 41 issues worth fixing on dailymail.co.uk, 15 of them high impact, across 90 checks. The most urgent: main-thread work: 11.1 s. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 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.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 297 ms |
| Jun 6, 2026 | 297 ms |
| Jun 13, 2026 | 297 ms |
| Jun 20, 2026 | 299 ms |
| Jun 27, 2026 | 303 ms |
| Jul 4, 2026 | 305 ms |
| Jul 11, 2026 | 307 ms |
| Jul 18, 2026 | 308 ms |
| Jul 25, 2026 | 309 ms |
| Aug 1, 2026 | 311 ms |
| Aug 8, 2026 | 315 ms |
| Aug 15, 2026 | 321 ms |
| Aug 22, 2026 | 325 ms |
| Aug 29, 2026 | 329 ms |
| Sep 5, 2026 | 328 ms |
| Sep 12, 2026 | 328 ms |
| Sep 19, 2026 | 327 ms |
| Sep 26, 2026 | 327 ms |
| Oct 3, 2026 | 329 ms |
| Oct 10, 2026 | 330 ms |
| Oct 17, 2026 | 334 ms |
| Oct 24, 2026 | 337 ms |
| Oct 31, 2026 | 330 ms |
| Nov 7, 2026 | 319 ms |
| Nov 14, 2026 | 302 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.5 s
1.0 s
1.5 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Main-thread work: 11.1 s
A phone's processor spends 11.1 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,684 HTML elements
The page has 3,684 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
300 ms · 3.4 MB85 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Reduce unused JavaScript
230 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 230 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 1.8 MB and 1.4 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.
Reduce unused CSS
446 KiBAbout 446 KiB of CSS is downloaded but never applied on this page.
Google/Doubleclick Ads adds 296 ms
296 msGoogle/Doubleclick Ads costs a phone 296 ms of main-thread work and 540 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.
Google Tag Manager adds 226 ms
226 msGoogle Tag Manager costs a phone 226 ms of main-thread work and 340 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.
permutive.app adds 119 ms
119 mspermutive.app costs a phone 119 ms of main-thread work and 392 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.
Improve image delivery
113 KiB11 images could be 113 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
95 KiBPolyfills for old browsers add 95 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
Minify CSS
13 KiB13 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: 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: 50.7 s
50.7 sThe page becomes fully interactive after 50.7 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 241 ms
241 msReal visitors wait 241 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 297 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 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.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 10.3 MB in 880 requests
10.3 MBYour homepage downloads 10.3 MB in 880 requests on a phone: scripts 3.8 MB (86), images 2.6 MB (256) and media 2.3 MB (3). Under 2 MB keeps phones on slow connections fast.
About 2.9 g of CO₂ per visit
2.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.92 g of CO₂e: 349.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
57 buttons without a name
57 buttons have no accessible name, so screen readers announce just “button”.
19 images without alt text
19 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
2 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 6 WCAG 2.2 A/AA and best-practice rules on the phone render: 2 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (27 characters)
Your title is only 27 characters: “US Home | Daily Mail Online”. Between 30 and 65 characters leaves room to say what you do and for whom.
10 links with vague text
10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
855 internal links, 20 external
The homepage links to 855 pages on dailymail.co.uk and 20 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Daily Mail - get the latest breaking news, celebrity photos, viral videos, science & tech news, and top stories from Da…”.
One H1 headline
Your main headline reads: “US Home”.
Canonical URL set
The canonical URL is https://www.dailymail.com/ushome/index.html.
Structured data in place
Structured data found: CollectionPage 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://www.dailymail.com/google-news-sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). 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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, 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
llms.txt published
The site publishes https://www.dailymail.com/llms.txt (39 KiB, 169 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.dailymail.com/tvshowbiz/article-16298179/heidi-gardner-boyfriend-died-ray-tintori-snl.html has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.dailymail.com/crime-desk/us/index.html and https://www.dailymail.com/home/index.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.
6 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.
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
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
54 third-party cookies
54 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 3 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 11,531 words of copy
The homepage carries about 11,531 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Subscribe Daily Mail”, “Get in Touch” and “Contact us”.
1 short form
A short form (3 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 14 customer or partner logos.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 dailymail.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
- React
- Hosting
- Akamai
Company
- Founded
- 1896
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on dailymail.co.uk, including 19 speed issues, 3 SEO issues and 2 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.