Skip to content
Audit Complete

Results for https://www.theguardian.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 4, 2026 15:52 UTC
Share card preview
Share on X Share on LinkedIn Share via Email Download share image
Download JSON

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C78

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

1

'unsafe-eval' found in script source

Security › Content Security Policy
2

'unsafe-inline' found in script source

Security › Content Security Policy
3

Cookie 'gu_client_ab_tests' is missing the Secure flag

Security › Cookie Security
4

Cookie 'gu_v2_mvt_id' is missing the Secure flag

Security › Cookie Security
5

No H1 heading found

Accessibility › Heading Hierarchy
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theguardian.com)](https://beavercheck.com/results/c0a56ac5-386c-46ed-aab8-fa8b28a3ccf1)
<a href="https://beavercheck.com/results/c0a56ac5-386c-46ed-aab8-fa8b28a3ccf1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theguardian.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theguardian.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

46
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
77
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

4.82 s

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

7.70 s

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

692 ms

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

0.005

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

4.82 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.

9.05 s

Detailed Report

Audit breakdown by category with detailed findings.

46

Performance

Insights

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

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

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

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:37.303 source:map[column:122659 line:1 type:source-location url:https://assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:67.199 source:map[type:text value:[unattributed]]] map[reflowTime:0.679 source:map[column:40493 line:0 type:source-location url:https://sourcepoint.theguardian.com/unified/wrapperMessagingWithoutDetection.js urlProvider:network]] map[reflowTime:0.449 source:map[column:7861 line:0 type:source-location url:https://assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js urlProvider:network]] map[reflowTime:37.303 source:map[column:122689 line:0 type:source-location url:https://assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js urlProvider:network]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Golestan Palace, Tehran, a Unesco world heritage site li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/42a87959721423d78d72379c3f03d67893269f28/747_0...67.3 KiB30.7 KiB
Heavy damage at a laboratory in Shahid Beheshti University, Tehran, Iran li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/ac994e5bae89ab034cb6ca8b0fc22355cff9a4bf/914_0...60.4 KiB27.6 KiB
The aftermath of an Israeli strike in Tyre, Lebanon li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/3648d482d7ce8fa714cd974e6cee4b49f2226e60/760_0...53.9 KiB24.6 KiB
Images published by Iranian state media purporting to show the fighter jet wrec… li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/482982697628386efabd0a787d9590da0690e8a1/0_0_5...52.0 KiB23.7 KiB
The Earth seen from space div.dcr-1ummryo > div.dcr-1iak74q > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/0f90c4547316152cac838b2f5fbf06d714f443ce/659_0...36.3 KiB16.6 KiB
Trainee operators test out an unmanned ground robot in the snow div.dcr-1ummryo > div.dcr-1iak74q > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/a4d06fabd2a74d9c7fdd7bd06b14232abaaf4638/441_0...34.0 KiB15.5 KiB

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.

Estimated savings: 786 ms
URLTime Spent
www.theguardian.com/786 ms
www.theguardian.com/international0.0 ms

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.

TTI

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.

Diagnostics

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

Estimated savings: 640 ms 149.1 KiB
URLTransfer SizeEst Savings
sourcepoint.theguardian.com/Notice.8f529.js90.8 KiB61.4 KiB
assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js167.2 KiB53.7 KiB
assets.guim.co.uk/commercial/4209b0b7fab4ca3f32ab/graun.standalone.commercial.js55.9 KiB34.0 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.theguardian.com/international1.8 s55 ms13 ms
Unattributable994 ms67 ms0.0 ms
sourcepoint.theguardian.com/Notice.8f529.js894 ms579 ms50 ms
assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js640 ms439 ms1.0 ms
sourcepoint.theguardian.com/unified/wrapperMessagingWithoutDetection.js274 ms200 ms19 ms
assets.guim.co.uk/assets/Metrics-island.client.web.89d0611e576844a15b71.js211 ms207 ms1.5 ms
assets.guim.co.uk/assets/0.client.web.9123216163237343ed91.js156 ms141 ms15 ms
assets.guim.co.uk/assets/Titlepiece-island.client.web.ff2455b029191d3f4985.js146 ms137 ms8.5 ms
assets.guim.co.uk/assets/frameworks.client.web.8844a1b3ccdb9ca9be92.js108 ms58 ms0.6 ms
/assets/StickyBottomBanner-island.client.web.cec82945865a...108 ms105 ms2.5 ms
/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js81 ms59 ms22 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

CategoryTime Spent
Script Evaluation2.4 s
Style & Layout1.4 s
Other1.2 s
Parse HTML & CSS469 ms
Script Parsing & Compilation209 ms
Rendering181 ms
Garbage Collection74 ms

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,279 KiB
●User Timing marks and measures 142 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 140 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
90

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Failing Elements
News Opinion Sport Culture Lifestyle Search input google-search Search Support … div#header-expanded-menu > div.dcr-1srap2j > div.dcr-1ndqjmr > ul.dcr-6sl420

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Failing Elements
Bally Bagayoko Newly elected French mayor on tackling the far right Simon Tisda… div.dcr-1ykr3rf > gu-island > div.dcr-1beghel > ul.dcr-1tj3ydw
Images published by Iranian state media purporting to show the fighter jet wrec… gu-island > div.dcr-dz92n5 > a > ul.dcr-x0nc1o

These are opportunities to improve the experience of reading tabular or list data using 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.

Failing Elements
Barney RonayKane is finally getting the love he deserves ul.sublinks > li.dcr-b5asvx > div.dcr-b5c991 > a.dcr-1ij2qgb

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Images published by Iranian state media purporting to show the fighter jet wrec… div.dcr-19y4zys > gu-island > div.dcr-dz92n5 > a
○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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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

●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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
77

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.

Link destinationLink Text
www.theguardian.com/info/2024/feb/28/what-is-the-deeply-read-listLearn more

Canonical links suggest which URL to show in search results. Learn more about canonical links.

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Line #ContentError
101License: https://theguardian.com/license.xmlUnknown directive

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
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
94
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
77
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

698 ms

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

827 ms

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

20 ms

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

0.001

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

1.11 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.

881 ms

Detailed Report

Audit breakdown by category with detailed findings.

98

Performance

Insights

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

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

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

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:59.753 source:map[type:text value:[unattributed]]]]

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

lhId: page-0-IMG
nodeLabel: Images published by Iranian state media purporting to show the fighter jet wrec…
path: 1,HTML,1,BODY,13,MAIN,1,SECTION,3,DIV,0,UL,0,LI,0,DIV,0,DIV,2,DIV,0,DIV,0,GU-ISLAND,0,DIV,0,A,0,UL,0,LI,0,FIGURE,0,PICTURE,8,IMG
selector: li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
snippet: <img alt="Images published by Iranian state media purporting to show the fighter jet…" src="https://i.guim.co.uk/img/media/482982697628386efabd0a787d9590da0690e8a1/0_…" loading="eager" data-chromatic="ignore" class="dcr-l300o4">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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
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

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Golestan Palace, Tehran, a Unesco world heritage site li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/42a87959721423d78d72379c3f03d67893269f28/747_0...73.3 KiB23.2 KiB
Donald Trump says 'Cuba's next' but what what does it mean? div.dcr-pwlslf > button.dcr-rvfwnd > picture > img.dcr-1qi2at0
/img/media/c93875fbb4f6e5c593d8b37c73f83f1a10bc0b57/47_0_...37.7 KiB17.7 KiB
Heavy damage at a laboratory in Shahid Beheshti University, Tehran, Iran li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/ac994e5bae89ab034cb6ca8b0fc22355cff9a4bf/914_0...67.7 KiB17.6 KiB
The aftermath of an Israeli strike in Tyre, Lebanon li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/3648d482d7ce8fa714cd974e6cee4b49f2226e60/760_0...57.6 KiB7.6 KiB
Images published by Iranian state media purporting to show the fighter jet wrec… li.dcr-11wtom7 > figure > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/482982697628386efabd0a787d9590da0690e8a1/0_0_5...57.0 KiB7.0 KiB
Aerial view of the Pentagon building. div.dcr-9z444h > div.dcr-17jliau > picture.dcr-1ydxyte > img.dcr-l300o4
/img/media/934755303f5380d328b0d1d9140a6be39d349d04/317_0...13.0 KiB6.7 KiB
Mock-up image of Charles as a circus master and Trump as a lion on a podium div.dcr-8ierls > div.dcr-kkt25y > picture.dcr-19yn8oe > img.dcr-l300o4
/img/media/ab78c5043708ff7ab60eb0838476927897628ee2/65_19...92.5 KiB6.2 KiB

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

Diagnostics

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

Estimated savings: 70 ms 149.1 KiB
URLTransfer SizeEst Savings
sourcepoint.theguardian.com/Notice.8f529.js90.8 KiB61.4 KiB
assets.guim.co.uk/assets/index.client.web.18dee422f56822d692d5.js167.2 KiB53.7 KiB
assets.guim.co.uk/commercial/4209b0b7fab4ca3f32ab/graun.standalone.commercial.js55.9 KiB34.0 KiB

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

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

Estimated savings: 235 ms
URLTime Spent
www.theguardian.com/235 ms
www.theguardian.com/international0.0 ms
●Max Potential First Input Delay 70 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Time to Interactive 0.9 s
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,297 KiB
●User Timing marks and measures 142 user timings
●JavaScript execution time 0.4 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 180 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
94

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Failing Elements
Bally Bagayoko Newly elected French mayor on tackling the far right Simon Tisda… div.dcr-1ykr3rf > gu-island > div.dcr-1beghel > ul.dcr-1tj3ydw
Images published by Iranian state media purporting to show the fighter jet wrec… gu-island > div.dcr-dz92n5 > a > ul.dcr-x0nc1o

These are opportunities to improve the experience of reading tabular or list data using 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.

Failing Elements
Video'You look beautiful': Artemis II crew makes contact from space ul.sublinks > li.dcr-tkgy > div.dcr-1e8pf3e > a.dcr-1ij2qgb
In picturesArtemis II lifts off from the Kennedy Space Center ul.sublinks > li.dcr-tkgy > div.dcr-1e8pf3e > a.dcr-1ij2qgb
ItalyGattuso exits as manager after World Cup qualifying failure ul.sublinks > li.dcr-b5asvx > div.dcr-ak74t3 > a.dcr-1ij2qgb

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Images published by Iranian state media purporting to show the fighter jet wrec… div.dcr-19y4zys > gu-island > div.dcr-dz92n5 > a
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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

●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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
77

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.

Link destinationLink Text
www.theguardian.com/info/2024/feb/28/what-is-the-deeply-read-listLearn more

Canonical links suggest which URL to show in search results. Learn more about canonical links.

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Line #ContentError
101License: https://theguardian.com/license.xmlUnknown directive

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
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`

Send Feedback