C — https://telegraph.co.uk | BeaverCheck Audit

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

Room to improve — your 4.9s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 sites average 72

At average

Better than 14% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Apple sites average 73

At average

Better than 12% of Apple sites See full Apple benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Page weighs 17.5 MB (9.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ftelegraph.co.uk)](https://beavercheck.com/results/0707b0c7-8515-484e-a81a-ac30ef086712)

HTML

<a href="https://beavercheck.com/results/0707b0c7-8515-484e-a81a-ac30ef086712"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftelegraph.co.uk" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Ftelegraph.co.uk

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

Your LCP is 4.9s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Return on Investment

£375 investment → £2,901/month returns + GBP 18,050,000 risk avoided

Payback period: < 1 month First-year ROI: +9183%

Investment

£375

5h · 5 findings

Monthly returns

£2,901 /mo

~£34,810 / year

Conversions recovered £2,899
Bandwidth savings £1.86

Regulatory risk avoided

GBP 18,050,000

if kept compliant

UK GDPR GBP 17,500,000
PECR GBP 500,000
Equality Act 2010 GBP 50,000

Payback period

0 12mo 24mo

£113 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

£375

5.0 developer hours at £75/hr

Based on United Kingdom rates (£75/hr)

Quick wins

£113 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

£1,504,169 / month at risk

~£18,050,022 / year if left unfixed

Compliance Risk

£18,050,000

UK GDPRPECREquality Act 2010

No privacy policy link detected
UK GDPR: GBP 10,000 – GBP 17,500,000
Trackers detected but no cookie policy found
UK GDPR: GBP 10,000 – GBP 17,500,000
Trackers detected but no cookie policy found
PECR: GBP 1,000 – GBP 500,000

+5 more

Bandwidth Waste

£1.86 /mo

29504.3 MB/mo × 0.063 GBP/GB

Optimize transfer: save ~3.0 MB per page load
Saves £1.86/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.98 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.93 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.96 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.729

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.20 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

35.30 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cdn.viafoura.net/vf-v2.js	300.0 s	188.7 KiB
/content/dam/travel/2025/12/29/TELEMMGLPICT000454685762_1...	43200.0 s	294.2 KiB
/71dcbb11123ce6b2e1ce4d47fd79a130aad3fc95/satelliteLib-17...	3600.0 s	158.9 KiB
/content/dam/global-health/2026/04/14/TELEMMGLPICT0004202...	43200.0 s	244.7 KiB
/content/dam/PortalPictures/april-2026/478647047_AP_Luis ...	43200.0 s	238.9 KiB
/content/dam/news/2026/04/14/TELEMMGLPICT000478466726_177...	43200.0 s	206.5 KiB
/brVdvbqDHWmIn/6s0074rRHavgQ/w/QJarDDYu7fu7/Y3kmDQE/I1hmE...	21600.0 s	153.1 KiB
/content/dam/news/2026/04/15/TELEMMGLPICT000478574257_177...	43200.0 s	189.7 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	261.0 s	94.8 KiB
cdn.tinypass.com/api/tinypass.min.js	14400.0 s	132.2 KiB
/content/dam/PortalPictures/april-2026/l478612547_Getty-I...	43200.0 s	172.0 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.2 KiB
/content/dam/briefs/2026/04/15/TELEMMGLPICT000478596240_1...	43200.0 s	119.5 KiB
/content/dam/news/2026/04/15/TELEMMGLPICT000478617273_177...	43200.0 s	118.1 KiB
static.telegraph.co.uk/telegraph-advertising/tmg-gpt.min.js	300.0 s	57.1 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	151.0 s	54.2 KiB
/content/dam/news/2026/04/15/TELEMMGLPICT000478629266_177...	43200.0 s	98.9 KiB
www.telegraph.co.uk/martech/js/core.min.js	186.0 s	39.8 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	38.4 KiB
/embeds/00__25-viafoura-conversation-modal/_astro/index.C...	3600.0 s	42.8 KiB
/content/dam/football/2026/04/15/TELEMMGLPICT000478647152...	43200.0 s	68.5 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	26.7 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	21.4 KiB
/content/dam/tv/2026/04/13/TELEMMGLPICT000476538785_17761...	43200.0 s	39.6 KiB
cdn.viafoura.net/entry/index.js	600.0 s	16.6 KiB
/content/dam/politics/2026/04/15/TELEMMGLPICT000478608055...	43200.0 s	28.8 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	130.0 s	13.5 KiB
/content/dam/en-us/news/2026/04/15/TELEMMGLPICT0004786452...	43200.0 s	20.3 KiB
/content/dam/Author photos/James Kirkup Dec 2021.png?impo...	0.0 ms	10.0 KiB
static.chartbeat.com/js/chartbeat_video.js	86400.0 s	24.8 KiB
/content/dam/PortalPictures/april-2026/l478609852__.jpg?i...	43200.0 s	19.3 KiB
/content/dam/en-us/news/2026/04/15/TELEMMGLPICT0004786136...	43200.0 s	16.8 KiB
static.telegraph.co.uk/telegraph-advertising/tmg-cmp.min.js	300.0 s	8.7 KiB
/embeds/00__25-viafoura-conversation-modal/_astro/Viafour...	3600.0 s	9.3 KiB
www.telegraph.co.uk/martech/js/TGT-1205--piano-library/index.js	37.0 s	6.8 KiB
cf.eip.telegraph.co.uk/podcasts/posters/658300edbbd71a00174fea51.jpeg	21600.0 s	9.3 KiB
cdn.cxense.com/cx.cce.js	3600.0 s	6.8 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
static.telegraph.co.uk/telegraph-advertising/tmg-cmpLinks.min.js	300.0 s	4.9 KiB
cf.eip.telegraph.co.uk/podcasts/posters/6583019ebbd71a00175001c8.jpeg	21600.0 s	6.7 KiB
/content/dam/Author photos/Annabel_Denham_new.png?impolic...	43200.0 s	8.4 KiB
static.chartbeat.com/js/chartbeat_mab.js	86400.0 s	10.1 KiB
/content/dam/utility-bar/Cam-Tim-Utility-Bar.png?impolicy...	43200.0 s	8.1 KiB
/content/dam/Author photos/032 Guy.png?impolicy=byline-au...	43200.0 s	7.9 KiB
/content/dam/Author photos/439202599_patrick-kidd.png?imp...	43200.0 s	7.6 KiB
www.telegraph.co.uk/martech/js/TGT-4026--hash-email-store/index.js	284.0 s	3.6 KiB
/content/dam/utility-bar/Travel-writing_competition_SQ.jp...	43200.0 s	5.0 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	165.0 s	1.9 KiB
www.telegraph.co.uk/content/dam/George%20Chesterton.png?impolicy=byline-author	43200.0 s	3.7 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.3 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	1.8 KiB
www.telegraph.co.uk/martech/js/TGT-1002--paywall-meters-profile/index.js	37.0 s	1.7 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC10bd4d63b1fe4f2...	3600.0 s	1.9 KiB
experience.tinypass.com/xbuilder/experience/load?aid=NJu5KnOFpu	1800.0 s	1.7 KiB
cdn.jsdelivr.net/npm/recombee-js-api-client/dist/recombee-api-client.min.js	604800.0 s	13.9 KiB
cdn.jsdelivr.net/gh/recombee/js-api-client/dist/recombee-api-client.min.js	604800.0 s	13.6 KiB
/content/dam/utility-bar/Iran_ Utility Bar.jpg?impolicy=u...	43200.0 s	2.6 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RCb9995f44e99c43d...	3600.0 s	1.5 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC00cee9bc4ada429...	3600.0 s	1.3 KiB
cf.eip.telegraph.co.uk/assets/_css/fontsv08.css	3600.0 s	1.2 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC196522a11d1a4e6...	3600.0 s	1.2 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	973 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC5e02d88a96114aa...	3600.0 s	1.1 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC0392241e4a1a46c...	3600.0 s	1.1 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RCc14ca73cd707423...	3600.0 s	1.1 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC5e2dbb35c68847d...	3600.0 s	1.1 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RCeb3f3be5867947f...	3600.0 s	1.0 KiB
applets.ebxcdn.com/ebx.js	7200.0 s	1.0 KiB
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC5b23bcae5fb9431...	3600.0 s	957 B
/embeds/00__25-viafoura-conversation-modal/_astro/client....	3600.0 s	878 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RCf678a9b3b302440...	3600.0 s	831 B
secure.s.telegraph.co.uk/tmgads/adtech/2024/prebid/9.0.ab/prebid.js	0.0 ms	643 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC130d8c2bfb5d4ac...	3600.0 s	748 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC575f15ce13af493...	3600.0 s	693 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RCd54e9c42e0624ea...	3600.0 s	521 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC2b5b0c599b1c462...	3600.0 s	515 B
/Repo/rep.gif?ver=3.3.0&typ=pgv&rnd=mo0nzxbcff28i18l&sid=...	0.0 ms	412 B
/bb77750356fd/42bfe6bcc850/ceaacb276cdd/RC63265de272154d8...	3600.0 s	469 B
cf.eip.telegraph.co.uk/assets/_css/doricv01.css	86400.0 s	643 B
cf.eip.telegraph.co.uk/assets/_css/fontsv09.css	86400.0 s	617 B
/v3/polyfill.min.js?flags=gated&features=default,fetch,In...	604800.0 s	407 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	300.0 s	0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.729034] map[node:map[boundingRect:map[bottom:541 height:258 left:0 right:412 top:283 width:412] lhId:page-0-IMG nodeLabel:a > figure.package__figure > div.u-image-placeholder-container > img.responsive path:1,HTML,1,BODY,2,MAIN,1,DIV,1,DIV,3,SECTION,0,DIV,1,DIV,0,A,0,FIGURE,0,DIV,0,IMG selector:a > figure.package__figure > div.u-image-placeholder-container > img.responsive snippet:<img class="responsive package__image-src" src="https://www.telegraph.co.uk/content/dam/politics/2026/04/15/TELEMMGLPICT00…" srcset="/content/dam/politics/2026/04/15/TELEMMGLPICT000478608055_17762637972510.j…" alt="" sizes="(min-width: 768px) 320px, 33.333vw" pinger-seen="true"> type:node] score:0.72871 subItems:map[items:[map[cause:Unsized image element]] type:subitems]] map[node:map[boundingRect:map[bottom:1091 height:258 left:0 right:412 top:834 width:412] lhId:page-3-IMG nodeLabel:a > figure.package__figure > div.u-image-placeholder-container > img.responsive path:1,HTML,1,BODY,2,MAIN,1,DIV,1,DIV,4,SECTION,0,DIV,1,DIV,0,A,0,FIGURE,0,DIV,0,IMG selector:a > figure.package__figure > div.u-image-placeholder-container > img.responsive snippet:<img class="responsive package__image-src" src="https://www.telegraph.co.uk/content/dam/PortalPictures/april-2026/l4786125…" srcset="/content/dam/PortalPictures/april-2026/l478612547_Getty-Images-Europe_Isra…" alt="" sizes="(min-width: 768px) 640px, 100vw" pinger-seen="true"> type:node] score:0.000324 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://cf.eip.telegraph.co.uk/assets/_fonts/Austin%20News%20Deck%20Web-Semibold.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:183 height:23 left:348 right:388 top:161 width:40] lhId:page-0-P nodeLabel:27:07 path:1,HTML,1,BODY,0,MAIN,0,SECTION,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,1,DIV,2,P selector:div.media__inner > div.audioPlayer > div.audioPlayer__timeline > p.audioPlayer__timeDisplay snippet:<p class="audioPlayer__timeDisplay" data-js-totaltime=""> type:node] score:0 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.telegraph.co.uk/etc.clientlibs/settings/wcm/designs/telegraph/core/clientlibs/ui/dist/static/resources/fonts/doric-news-uprights-vf-basic-web.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:213 height:23 left:344 right:388 top:191 width:44] lhId:page-0-P nodeLabel:40:26 path:1,HTML,1,BODY,0,MAIN,0,SECTION,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,1,DIV,2,P selector:div.media__inner > div.audioPlayer > div.audioPlayer__timeline > p.audioPlayer__timeDisplay snippet:<p class="audioPlayer__timeDisplay" data-js-totaltime=""> type:node] score:0 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://www.telegraph.co.uk/etc.clientlibs/settings/wcm/designs/telegraph/core/clientlibs/ui/dist/static/resources/fonts/doric-news-uprights-vf-basic-web.woff2]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
cf.eip.telegraph.co.uk/assets/_fonts/Austin%20News%20Deck%20Web-Semibold.woff2	45 ms
cf.eip.telegraph.co.uk/assets/_fonts/Austin%20News%20Text%20Web-Roman.woff2	30 ms

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: a > figure.package__figure > div.u-image-placeholder-container > img.responsive

path: 1,HTML,1,BODY,2,MAIN,1,DIV,1,DIV,3,SECTION,0,DIV,1,DIV,0,A,0,FIGURE,0,DIV,0,IMG

selector: a > figure.package__figure > div.u-image-placeholder-container > img.responsive

snippet: <img class="responsive package__image-src" src="https://www.telegraph.co.uk/content/dam/politics/2026/04/15/TELEMMGLPICT00…" srcset="/content/dam/politics/2026/04/15/TELEMMGLPICT000478608055_17762637972510.j…" alt="" sizes="(min-width: 768px) 320px, 33.333vw" pinger-seen="true">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
static.telegraph.co.uk/telegraph-advertising/tmg-cmp.min.js	8.7 KiB	801 ms
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	94.8 KiB	902 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 800 ms

URL	Time Spent
telegraph.co.uk/	800 ms
www.telegraph.co.uk/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 959 ms

URL	Time Spent
www.telegraph.co.uk/	1.1 s

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
a > figure.package__figure > div.u-image-placeholder-container > img.responsive `a > figure.package__figure > div.u-image-placeholder-container > img.responsive`	0.729
a > figure.package__figure > div.u-image-placeholder-container > img.responsive `a > figure.package__figure > div.u-image-placeholder-container > img.responsive`	0.000
27:07 `div.media__inner > div.audioPlayer > div.audioPlayer__timeline > p.audioPlayer__timeDisplay`	0.000
40:26 `div.media__inner > div.audioPlayer > div.audioPlayer__timeline > p.audioPlayer__timeDisplay`	0.000

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 450 ms 90.7 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	94.5 KiB	90.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	1.4 s	269 ms	0.0 ms
www.telegraph.co.uk/	983 ms	78 ms	9.6 ms
/71dcbb11123ce6b2e1ce4d47fd79a130aad3fc95/satelliteLib-17...	801 ms	613 ms	97 ms
/brVdvbqDHWmIn/6s0074rRHavgQ/w/QJarDDYu7fu7/Y3kmDQE/I1hmE...	692 ms	639 ms	41 ms
/visuals-cms/particles/animated-carousel/public-assets/js...	341 ms	292 ms	42 ms
cdn.tinypass.com/api/tinypass.min.js	271 ms	225 ms	31 ms
cdn.viafoura.net/vf-v2.js	264 ms	204 ms	49 ms
www.googletagmanager.com/gtag/js?id=AW-362151000&l=gDataLayer&cx=c&gtm=4e64e1	257 ms	201 ms	54 ms
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	253 ms	187 ms	51 ms
www.googletagmanager.com/gtag/js?id=AW-11084402548&l=gDataLayer	245 ms	202 ms	38 ms
cf.eip.telegraph.co.uk/particle-embed/js/particle.js	241 ms	216 ms	15 ms
www.googletagmanager.com/gtag/js?id=AW-808307600&l=gDataLayer&cx=c&gtm=4e64e1	225 ms	186 ms	37 ms
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	191 ms	152 ms	17 ms
www.googletagmanager.com/gtag/js?id=DC-10936650&l=gDataLayer&cx=c&gtm=4e64e1	161 ms	134 ms	25 ms
www.telegraph.co.uk/martech/js/core.min.js	160 ms	136 ms	12 ms
www.googletagmanager.com/gtag/js?id=DC-11213712&l=gDataLayer&cx=c&gtm=4e64e1	144 ms	117 ms	27 ms
cdn.privacy-mgmt.com/unified/4.40.1/ccpa-gpp.d3f006f99fb3b63e8837.bundle.js	116 ms	79 ms	37 ms
static.chartbeat.com/js/chartbeat_video.js	116 ms	106 ms	5.4 ms
static.telegraph.co.uk/telegraph-advertising/tmg-cmp.min.js	114 ms	98 ms	2.2 ms
cdn.cxense.com/cx.js	79 ms	60 ms	8.9 ms
static.chartbeat.com/js/chartbeat_mab.js	74 ms	52 ms	2.1 ms
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	69 ms	52 ms	13 ms
static.telegraph.co.uk/telegraph-advertising/tmg-gpt.min.js	69 ms	38 ms	26 ms
/7a8c956f-996d-4cc3-a2a6-588c841638d5.home-page.html?dire...	66 ms	0.2 ms	0.3 ms
cdn.privacy-mgmt.com/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js	53 ms	39 ms	14 ms
cdn.viafoura.net/chunks/141.e7f9da4928a448cc2565.js	52 ms	48 ms	1.5 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	4.7 s
Other	1.3 s
Script Parsing & Compilation	699 ms
Style & Layout	629 ms
Parse HTML & CSS	274 ms
Rendering	161 ms
Garbage Collection	103 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 879.2 KiB

URL	Transfer Size	Est Savings
cdn.viafoura.net/vf-v2.js	187.7 KiB	125.1 KiB
cdn.tinypass.com/api/tinypass.min.js	131.7 KiB	82.5 KiB
www.googletagmanager.com/gtag/js?id=AW-362151000&l=gDataLayer&cx=c&gtm=4e64e1	133.9 KiB	63.3 KiB
www.googletagmanager.com/gtag/js?id=AW-808307600&l=gDataLayer&cx=c&gtm=4e64e1	145.5 KiB	62.7 KiB
www.googletagmanager.com/gtag/js?id=DC-10936650&l=gDataLayer&cx=c&gtm=4e64e1	129.2 KiB	59.3 KiB
www.googletagmanager.com/gtag/js?id=DC-11213712&l=gDataLayer&cx=c&gtm=4e64e1	129.2 KiB	59.2 KiB
www.googletagmanager.com/gtag/js?id=AW-11084402548&l=gDataLayer	136.4 KiB	59.1 KiB
/visuals-cms/particles/animated-carousel/public-assets/js...	137.0 KiB	58.7 KiB
/etc.clientlibs/settings/wcm/designs/telegraph/core/clien...	53.8 KiB	44.3 KiB
static.telegraph.co.uk/telegraph-advertising/tmg-gpt.min.js	56.9 KiB	40.5 KiB
/71dcbb11123ce6b2e1ce4d47fd79a130aad3fc95/satelliteLib-17...	158.6 KiB	29.7 KiB
/brVdvbqDHWmIn/6s0074rRHavgQ/w/QJarDDYu7fu7/Y3kmDQE/I1hmE...	152.8 KiB	28.4 KiB
cdn.cxense.com/cx.js	37.5 KiB	21.7 KiB
/embeds/00__25-viafoura-conversation-modal/_astro/index.C...	42.8 KiB	21.5 KiB
cdn.privacy-mgmt.com/unified/4.40.1/ccpa-gpp.d3f006f99fb3b63e8837.bundle.js	41.3 KiB	21.1 KiB
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	37.1 KiB	20.4 KiB
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	37.1 KiB	20.4 KiB
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	37.1 KiB	20.4 KiB
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	37.1 KiB	20.4 KiB
cf.eip.telegraph.co.uk/visuals-cms/particles/helpers.js	37.1 KiB	20.4 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/uploads/file-uploader/fcc2b5af-704e-458d-b0f0-bb8791d1c3...	2.1 MiB
/uploads/file-uploader/ffd82fa5-0f20-4a7f-af89-3a45e46717...	1.8 MiB
/responsive-image/content/15eae00a-ee2d-45bb-874d-262345f...	340.0 KiB
/content/dam/travel/2025/12/29/TELEMMGLPICT000454685762_1...	294.2 KiB
/content/dam/global-health/2026/04/14/TELEMMGLPICT0004202...	244.7 KiB
/content/dam/PortalPictures/april-2026/478647047_AP_Luis ...	238.9 KiB
/content/dam/news/2026/04/14/TELEMMGLPICT000478466726_177...	206.5 KiB
/content/dam/news/2026/04/15/TELEMMGLPICT000478574257_177...	189.7 KiB
cdn.viafoura.net/vf-v2.js	188.7 KiB
/content/dam/PortalPictures/april-2026/l478612547_Getty-I...	172.0 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 36 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.site-header__container > div.site-header__masthead > div.site-header__logo > a.e-site-logo `div.site-header__container > div.site-header__masthead > div.site-header__logo > a.e-site-logo`
section.package > div.package__grid > div.grid-col > a `section.package > div.package__grid > div.grid-col > a`
section.package > div.package__grid > div.grid-col > a `section.package > div.package__grid > div.grid-col > a`
section.package > div.package__grid > div.grid-col > a `section.package > div.package__grid > div.grid-col > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
David Blair `span.e-byline > span > span.e-byline__details-multiAuthors > a.e-byline__link`
Shevaun Haviland `span.e-byline > span > span.e-byline__details-multiAuthors > a.e-byline__link`
Tom Stevenson `span.e-byline > span > span.e-byline__details-multiAuthors > a.e-byline__link`
Gary Rycroft `span.e-byline > span > span.e-byline__details-multiAuthors > a.e-byline__link`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
/visuals-cms/particles/animated-carousel/public-assets/js...
cdn.viafoura.net/vf-v2.js	cdn.viafoura.net/vf-v2.js.map
cdn.viafoura.net/chunks/255.0a14e6cf041b1c00f4ae.js	cdn.viafoura.net/chunks/255.0a14e6cf041b1c00f4ae.js.map
cdn.cxense.com/cx.cce.js	cdn.cxense.com/cx.cce.js.map
cdn.viafoura.net/entry/index.js	cdn.viafoura.net/entry/index.js.map
cdn.jsdelivr.net/npm/recombee-js-api-client/dist/recombee-api-client.min.js	cdn.jsdelivr.net/npm/recombee-js-api-client/dist/recombee-api-client.min.js.map
cdn.jsdelivr.net/gh/recombee/js-api-client/dist/recombee-api-client.min.js	cdn.jsdelivr.net/gh/recombee/js-api-client/dist/recombee-api-client.min.js.map

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.telegraph.co.uk/contact-us/editorial-complaints/	here
www.telegraph.co.uk/news/0/telegraph-corrections-and-clarifications/	here

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
`li#travel > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`
`li#recommended > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`
`li#recommended > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`
`li#recommended > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`
`li#lifestyle > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`
`li#culture > ul.all-sections__secondary-list > li.all-sections__secondary-item > a.all-sections__link`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

463 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

500 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

499 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

500 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 243 ms

URL	Time Spent
telegraph.co.uk/	243 ms
www.telegraph.co.uk/	0.0 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.5 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 4 KiB

●Minimizes main-thread work 0.0 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 350 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○JavaScript execution time

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Names and labels

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Background and foreground colors have a sufficient contrast ratio

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

Content Best Practices

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Results for https://telegraph.co.uk

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Accessibility

Names and labels

Internationalization and localization

Best practices

Best Practices

Browser Compatibility

SEO

Content Best Practices

Keyboard Shortcuts