Skip to content
https://tate.org.uk

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

27

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

Performance issues directly impact user engagement and conversion rates.

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.

RequestCache TTLTransfer Size
/aztate-prd-ew-dg-wgtail-st1-ctr-data/original_images/Tat...86400.0 s839.2 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawksbill_Ba...86400.0 s337.0 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawksbill_Ba...86400.0 s240.4 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/visitor_draw...86400.0 s226.9 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/original_images/Lea...86400.0 s215.8 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
/signals/config/283050022064437?v=2.9.303&r=stable&domain...1200.0 s46.2 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Nigerian_Mod...86400.0 s72.7 KiB
/da530001-e05b-49ef-be2a-5006a8b39f81/loader.js?target_ty...7200.0 s33.7 KiB
cdn.scarabresearch.com/js/15F8C397B23FCB36/scarab-v2.js3600.0 s22.7 KiB
/signals/config/2359278220789639?v=2.9.303&r=stable&domai...1200.0 s16.1 KiB
/signals/config/2875408016060796?v=2.9.303&r=stable&domai...1200.0 s16.0 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_shop.wi...86400.0 s33.3 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Tate_Etc_202...86400.0 s28.8 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Tate_Liverpo...86400.0 s24.5 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_britain...86400.0 s20.3 KiB
tags.srv.stackadapt.com/events.js5.0 s7.7 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_st_ives...86400.0 s18.2 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Tate_Liverpo...86400.0 s18.1 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/hockney_book...86400.0 s16.8 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_modern_...86400.0 s15.9 KiB
static.hotjar.com/c/hotjar-1586264.js?sv=760.0 s6.3 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/eminmybed.ma...86400.0 s15.5 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_britain...86400.0 s15.0 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_prints_...86400.0 s14.4 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/the_art_of_g...86400.0 s14.0 KiB
consentag.eu/public/3.1.1/consenTag.js3600.0 s6.9 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_st_ives...86400.0 s13.8 KiB
static.queue-it.net/script/queueconfigloader.min.js7200.0 s6.5 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/eminmybed.wi...86400.0 s11.7 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Nocturn_Whis...86400.0 s10.8 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/13_a._Aleksa...86400.0 s10.7 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tate_modern_...86400.0 s9.4 KiB
acdn.adnxs.com/dmp/up/pixie.js86402.0 s9.2 KiB
static.queue-it.net/script/queueclient.min.js7200.0 s4.7 KiB
try.abtasty.com/03d869a33f572dd77e62594449ebd8cb.js30.0 s3.1 KiB
rules.quantcount.com/rules-p-yJp-XzbYwjHtL.js3600.0 s3.7 KiB
ct.pinterest.com/static/ct/token_create.js7200.0 s3.9 KiB
s.pinimg.com/ct/lib/main.10d2511a.js1209600.0 s27.4 KiB
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/tmexpandedci...86400.0 s4.8 KiB
s.pinimg.com/ct/core.js7200.0 s2.1 KiB
/tate/integrationconfig/javascript/queueclientConfig.js?v...300.0 s1.2 KiB
tags.pw.adn.cloud/BFWG9R/activation.js14400.0 s396 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=283050022064437&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/tr/?id=2359278220789639&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms16 B
/tr/?id=2875408016060796&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms16 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.219963] map[node:map[boundingRect:map[bottom:39 height:14 left:359 right:404 top:25 width:45] lhId:page-10-DIV nodeLabel:search path:1,HTML,1,BODY,7,DIV,0,HEADER,1,DIV,0,DIV,3,DIV,0,DIV selector:div.container > div.container__inner > div.header-nav > div.header-nav__item snippet:<div class="header-nav__item header-nav__search"> type:node] score:0.183421 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:935 height:203 left:66 right:346 top:732 width:280] lhId:page-1-IMG nodeLabel:div.card-media > div.card-media__inner > picture > img path:1,HTML,1,BODY,7,DIV,2,MAIN,0,ARTICLE,2,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,PICTURE,1,IMG selector:div.card-media > div.card-media__inner > picture > img snippet:<img alt="" src="https://media.tate.org.uk/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawk…" loading="eager" width="420" height="305" data-current-size="0-0" data-visible=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:39 height:14 left:251 right:412 top:25 width:161] lhId:page-6-DIV nodeLabel:search path:1,HTML,1,BODY,7,DIV,0,HEADER,1,DIV,0,DIV,3,DIV selector:header#header > div.container > div.container__inner > div.header-nav snippet:<div class="header-nav"> type:node] score:0.036542]]
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.000249] map[node:map[boundingRect:map[bottom:784 height:18 left:96 right:325 top:766 width:230] lhId:page-11-SPAN nodeLabel:Do not Share or Sell my Personal Information path:1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,BUTTON,0,SPAN selector:div.didomi-notice__interior-border > div#buttons > button#didomi-notice-learn-more-button > span snippet:<span> type:node] score:0.000249]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:44.129 source:map[column:27323 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.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:106.645 source:map[type:text value:[unattributed]]] map[reflowTime:40.607 source:map[column:49615 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js urlProvider:network]] map[reflowTime:3.522 source:map[column:49637 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js urlProvider:network]] map[reflowTime:28.794 source:map[column:104234 line:1 type:source-location url:https://sdk.privacy-center.org/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-web-en-web.22ecd6bfac93de604efec0b75b2c796ee1675f92.js urlProvider:network]] map[reflowTime:4.351 source:map[column:84992 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.card-media__inner > div > picture > img div.card-media__inner > div > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawksbill_Ba...336.6 KiB314.9 KiB
div.card-media > div.card-media__inner > picture > img div.card-media > div.card-media__inner > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawksbill_Ba...240.1 KiB219.3 KiB
A visitor sitting and drawing in a gallery div.card-media > div.card-media__inner > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/visitor_draw...226.6 KiB191.0 KiB
div.card-media > div.card-media__inner > picture > img div.card-media > div.card-media__inner > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Tate_Etc_202...28.7 KiB7.2 KiB

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-4-IMG
nodeLabel: div.banner > div.banner__image > picture > img
path: 1,HTML,1,BODY,7,DIV,2,MAIN,0,ARTICLE,0,DIV,0,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.banner > div.banner__image > picture > img
snippet: <img alt="" src="https://media.tate.org.uk/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Nige…" loading="lazy" width="420" height="299" style="object-position: 45% 5%;">

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

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.

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

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.

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: 753 ms
URLTime Spent
tate.org.uk/753 ms
www.tate.org.uk/0.0 ms

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.

ElementLayout shift score
search div.container > div.container__inner > div.header-nav > div.header-nav__item
0.183
search header#header > div.container > div.container__inner > div.header-nav
0.037
Do not Share or Sell my Personal Information div.didomi-notice__interior-border > div#buttons > button#didomi-notice-learn-more-button > span
0.000

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: 600 ms 101.8 KiB
URLTransfer SizeEst Savings
www.tate.org.uk/static/css/styles.3f47c07a720e.css92.6 KiB87.8 KiB
#didomi-host .didomi-components-button{background-color:#eee;border:1px solid rgba(34,34,34,.2); … } …17.0 KiB14.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable1.2 s139 ms0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js1.1 s936 ms123 ms
try.abtasty.com/03d869a33f572dd77e62594449ebd8cb/main.4f8fe8525f40523c4a4c.js1.1 s928 ms26 ms
www.tate.org.uk/1.0 s18 ms9.0 ms
www.googletagmanager.com/gtm.js?id=GTM-WQPJ9H918 ms766 ms85 ms
www.googletagmanager.com/gtag/js?id=G-Q4CTQC82D1&cx=c&gtm=4e64h1454 ms348 ms100 ms
www.googletagmanager.com/gtag/js?id=G-4GZRWXM2P8&cx=c&gtm=4e64h1443 ms344 ms54 ms
ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js435 ms227 ms9.8 ms
www.tate.org.uk/static/js/TateUI.c2ca8065327f.js415 ms255 ms67 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js348 ms284 ms58 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/ui-w...341 ms154 ms61 ms
connect.facebook.net/en_US/fbevents.js329 ms171 ms98 ms
/sdk/22ecd6bfac93de604efec0b75b2c796ee1675f92/modern/sdk....308 ms232 ms40 ms
/signals/config/2875408016060796?v=2.9.303&r=stable&domai...295 ms232 ms11 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js234 ms201 ms21 ms
www.googletagmanager.com/gtag/js?id=AW-16456287227&cx=c&gtm=4e64h1209 ms168 ms40 ms
www.googletagmanager.com/gtag/js?id=AW-1012661956&cx=c&gtm=4e64h1208 ms167 ms40 ms
static.ads-twitter.com/uwt.js187 ms173 ms12 ms
www.googletagmanager.com/gtag/js?id=DC-13274131&cx=c&gtm=4e64h1153 ms119 ms33 ms
s.pinimg.com/ct/lib/main.10d2511a.js129 ms100 ms22 ms
/signals/config/283050022064437?v=2.9.303&r=stable&domain...127 ms82 ms43 ms
/signals/config/2359278220789639?v=2.9.303&r=stable&domai...94 ms77 ms13 ms
tags.srv.stackadapt.com/events.js92 ms75 ms2.4 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js74 ms50 ms24 ms
static.queue-it.net/script/queueconfigloader.min.js73 ms8.8 ms63 ms
static.hotjar.com/c/hotjar-1586264.js?sv=755 ms52 ms2.3 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.

CategoryTime Spent
Script Evaluation6.7 s
Other1.6 s
Script Parsing & Compilation1.1 s
Style & Layout912 ms
Garbage Collection258 ms
Parse HTML & CSS217 ms
Rendering88 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.3 KiB
URLTransfer SizeEst Savings
cdn.scarabresearch.com/js/15F8C397B23FCB36/scarab-v2.js22.2 KiB5.3 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.card-media__inner > div > picture > img div.card-media__inner > div > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/Hawksbill_Ba...
div.card-media__inner > div > picture > img div.card-media__inner > div > picture > img
/aztate-prd-ew-dg-wgtail-st1-ctr-data/images/eminmybed.ma...
Tate Logo div.header-branding > div.site-logo > a#tate-logo > img
www.tate.org.uk/static/images/tate-logo.21bf83bab79c.svg

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

●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 25 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 5 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 70 ms
●Server Backend Latencies 410 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
○INP breakdown
100

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EXHIBITION Hurvin Anderson Experience the intensely colourful work of British … div.slick-slide > div > div.card > a
Tate Britain Free admission Open today 10.00–18.00 div > div.card-list > div.card > a
Tate Modern Free admission Open today 10.00–18.00 div > div.card-list > div.card > a
Tate Liverpool + RIBA North Free admission Open today 10.00–17.50 div > div.card-list > div.card > a
Tate St Ives Ticket or membership card required Open today 10.00–17.20 div > div.card-list > div.card > a
Buy books, prints and more Shopping with Tate helps supports our galleries div > div.card-list > div.card > a
Donate to Tate Your donation could provide art materials for young people or h… div > div.card-list > div.card > a
Stories Watch videos, listen to audio and read articles about art and artists div.slick-slide > div > div.card > a
Books Discover our titles on art history, artists, and our award-winning child… div > div.card-list > div.card > a
Gifts Shop art-inspired gifts for all ages and tastes div > div.card-list > div.card > a
Prints Browse from over 1,000 artworks from Tate's collection, to enjoy your f… div > div.card-list > div.card > 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]` 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.
●ARIA attributes are used as specified for the element's role
●`[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
●`<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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○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 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.
○`<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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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.

●Uses HTTPS
●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
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
100

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.

○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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback