Skip to content
Audit Complete

Results for https://bp.com

Visit site
Brazil Brazil · Sao Paulo Completed: Apr 21, 2026 22:12 UTC
Download Markdown Report

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

Decent speed, but optimizing further could improve engagement.

Strong security — your users are well protected.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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

WordPress · 413 peers
You 78
·
Avg 74
At average
0 50 100
Better than 83% of WordPress sites See full WordPress benchmark →
Amazon Route 53 · 669 peers
You 78
·
Avg 72
+6 above average
0 50 100
Better than 91% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

1

'unsafe-eval' found in script source

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

Security › Content Security Policy
2

No <main> landmark found

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

Accessibility › Landmark Structure
3

No favicon or icon links detected

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

Accessibility › Favicon & Branding
4

30 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbp.com)](https://beavercheck.com/results/1ce5df89-84c6-4137-a281-b1e7c696da33)
<a href="https://beavercheck.com/results/1ce5df89-84c6-4137-a281-b1e7c696da33"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbp.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fbp.com

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

2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 8.0s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 6 warning

9 barrier(s) likely increasing bounce by ~38%.

Speed (1)

Page takes 8.0s to load

+12% bounce

Users abandon at ~3s — you're 5.5s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

£450 investment → £4,488/month returns + GBP 18,050,000 risk avoided

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

Investment

£450

6h · 5 findings

Monthly returns

£4,488 /mo

~£53,859 / year

  • Conversions recovered £4,488
  • Bandwidth savings £0.18

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

£75 — 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

£450

6.0 developer hours at £75/hr

Based on United Kingdom rates (£75/hr)

Quick wins
£75 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

£1,504,167 / month at risk

~£18,050,002 / 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

£0.18 /mo

2863.0 MB/mo × 0.063 GBP/GB

  • Optimize transfer: save ~286 KB per page load
    Saves £0.18/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

37
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
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.
92
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.

5.09 s

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

8.03 s

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

167 ms

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

0.674

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

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

8.13 s

Detailed Report

Audit breakdown by category with detailed findings.

37

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.

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.674034] map[node:map[boundingRect:map[bottom:4930 height:4930 left:0 right:412 top:0 width:412] lhId:page-5-DIV nodeLabel:Site traffic information and cookies We use cookies to collect and analyse inf… path:1,HTML,1,BODY,3,DIV selector:body.nr-navigation--presence > div.aem-Grid snippet:<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 "> type:node] score:0.389923] map[node:map[boundingRect:map[bottom:1224 height:213 left:0 right:412 top:1011 width:412] lhId:page-2-DIV nodeLabel:Key documents Country websites Frequent searches path:1,HTML,1,BODY,3,DIV,9,DIV selector:body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component snippet:<div data-component-name="layout" data-component-container="true" class="nr-layout-component nr-component aem-GridColumn aem-GridColumn--default--12"> type:node] score:0.146493] map[node:map[boundingRect:map[bottom:1224 height:213 left:0 right:412 top:1011 width:412] lhId:page-2-DIV nodeLabel:Key documents Country websites Frequent searches path:1,HTML,1,BODY,3,DIV,9,DIV selector:body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component snippet:<div data-component-name="layout" data-component-container="true" class="nr-layout-component nr-component aem-GridColumn aem-GridColumn--default--12"> type:node] score:0.073257] map[node:map[boundingRect:map[bottom:1224 height:213 left:0 right:412 top:1011 width:412] lhId:page-2-DIV nodeLabel:Key documents Country websites Frequent searches path:1,HTML,1,BODY,3,DIV,9,DIV selector:body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component snippet:<div data-component-name="layout" data-component-container="true" class="nr-layout-component nr-component aem-GridColumn aem-GridColumn--default--12"> type:node] score:0.061016] map[node:map[boundingRect:map[bottom:568 height:52 left:0 right:412 top:516 width:412] lhId:page-10-DIV nodeLabel:GBp 563.6 (+6.7) USD 45.91 (+0.79)* path:1,HTML,1,BODY,3,DIV,7,DIV,2,ASIDE,0,DIV,1,DIV selector:div.nr-navigation-component > aside.nr-navigation > div.nr-navigation__inner > div.nr-navigation__shareprice snippet:<div class="nr-navigation__shareprice nr-navigation__shareprice--mobile-type nr-naviga…" data-format="ticker" data-feed-timeout="60000" data-feed-url="https://apps.bp.com/SharePriceFeed" data-x-api-key="8tmAkp0htLAW4cq1zSPk8YGgKpG4dU62gl80C6Cj"> type:node] score:0.003345 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:797 height:231 left:0 right:412 top:566 width:412] lhId:page-0-IMG nodeLabel:Inspection of seismic imagery path:1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG selector:div.slick-slide > div > div.nr-feature-carousel__item > img.nr-feature-carousel__media snippet:<img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" alt="Inspection of seismic imagery" src="https://www.bp.com/content/dam/bp/business-sites/en/global/corporate/image…" width="500" height="100%" class="nr-feature-carousel__media nr-lazy-size lazyloaded" srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…"> type:node]]] 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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:20.593 source:map[column:66658 line:42 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.179 source:map[column:66744 line:42 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.309 source:map[column:670731 line:62 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.392 source:map[column:65030 line:61 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:1.862 source:map[column:49902 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.431 source:map[column:49960 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.399 source:map[column:50024 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:9.698 source:map[column:49184 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.549 source:map[column:50937 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.287 source:map[column:49206 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]]]

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: Inspection of seismic imagery
path: 1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.slick-slide > div > div.nr-feature-carousel__item > img.nr-feature-carousel__media
snippet: <img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" alt="Inspection of seismic imagery" src="https://www.bp.com/content/dam/bp/business-sites/en/global/corporate/image…" width="500" height="100%" class="nr-feature-carousel__media nr-lazy-size lazyloaded" srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…">

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

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
Inspection of seismic imagery div.slick-slide > div > div.nr-feature-carousel__item > img.nr-feature-carousel__media
/content/dam/bp/business-sites/en/global/corporate/images...64.8 KiB17.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
bp.com/1.3 s
www.bp.com/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
Site traffic information and cookies We use cookies to collect and analyse inf… body.nr-navigation--presence > div.aem-Grid
0.390
Key documents Country websites Frequent searches body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component
0.146
Key documents Country websites Frequent searches body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component
0.073
Key documents Country websites Frequent searches body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component
0.061
GBp 563.6 (+6.7) USD 45.91 (+0.79)* div.nr-navigation-component > aside.nr-navigation > div.nr-navigation__inner > div.nr-navigation__shareprice
0.003

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.

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

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: 270 ms 43.4 KiB
URLTransfer SizeEst Savings
www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.css48.6 KiB43.4 KiB

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: 1.4 s 250.8 KiB
URLTransfer SizeEst Savings
www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js327.9 KiB250.8 KiB

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 22.3 KiB
URLTransfer SizeEst Savings
inline: var navDataArr = [ { …59.8 KiB22.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
icon ul.nr-navigation__list > li.nr-navigation__list-item > a.nr-navigation__quick-link > img.nr-navigation__icon
/content/dam/bp/business-sites/en/global/corporate/images...
icon ul.nr-navigation__list > li.nr-navigation__list-item > a.nr-navigation__quick-link > img.nr-navigation__icon
/content/dam/bp/business-sites/en/global/corporate/images...

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

Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 932 KiB
JavaScript execution time 0.6 s
Minimizes main-thread work 1.6 s
Avoid long main-thread tasks 3 long tasks found
Avoid non-composited animations 2 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 200 ms
Server Backend Latencies 210 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
User Timing marks and measures
96

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Disclaimer div.nr-footer__content > div.nr-row > div.nr-footer__disclaimer > a.nr-footer__disclaimer-title

These are opportunities to improve the legibility of your content.

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

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

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.

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
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`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

71
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
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.
92
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.

1.22 s

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

2.06 s

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

23 ms

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

0.276

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

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

2.06 s

Detailed Report

Audit breakdown by category with detailed findings.

71

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.

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.27597200000000005] map[node:map[boundingRect:map[bottom:702 height:450 left:253 right:1350 top:252 width:1097] lhId:page-7-::after nodeLabel:body.nr-navigation--presence > ::after path:1,HTML,1,BODY,0,::after selector:body.nr-navigation--presence > ::after snippet:<::after> type:node] score:0.113188] map[node:map[boundingRect:map[bottom:868 height:616 left:253 right:1350 top:252 width:1097] lhId:page-8-SECTION nodeLabel:Hidden depths: Finding energy for tomorrow, today Helping to supply the world… path:1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION selector:body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel snippet:<section class="nr-feature-carousel nr-feature-carousel--dark" data-prev="Previous" data-next="next"> type:node] score:0.035244 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2144 height:75 left:548 right:681 top:2069 width:133] lhId:page-14-IMG nodeLabel:First quarter 2026 trading statement path:1,HTML,1,BODY,3,DIV,14,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,UL,0,LI,0,A,0,IMG selector:ul.nr-list__item-wrap > li.nr-list__item > a.nr-list__thumbnail > img.lazyload snippet:<img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" alt="First quarter 2026 trading statement " src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" width="175" height="100%" class="lazyload nr-lazy-size nr-list__thumbnail-image"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:868 height:616 left:253 right:1350 top:252 width:1097] lhId:page-8-SECTION nodeLabel:Hidden depths: Finding energy for tomorrow, today Helping to supply the world… path:1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION selector:body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel snippet:<section class="nr-feature-carousel nr-feature-carousel--dark" data-prev="Previous" data-next="next"> type:node] score:0.020915 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2144 height:75 left:548 right:681 top:2069 width:133] lhId:page-14-IMG nodeLabel:First quarter 2026 trading statement path:1,HTML,1,BODY,3,DIV,14,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,UL,0,LI,0,A,0,IMG selector:ul.nr-list__item-wrap > li.nr-list__item > a.nr-list__thumbnail > img.lazyload snippet:<img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" alt="First quarter 2026 trading statement " src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" width="175" height="100%" class="lazyload nr-lazy-size nr-list__thumbnail-image"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:868 height:616 left:253 right:1350 top:252 width:1097] lhId:page-8-SECTION nodeLabel:Hidden depths: Finding energy for tomorrow, today Helping to supply the world… path:1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION selector:body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel snippet:<section class="nr-feature-carousel nr-feature-carousel--dark" data-prev="Previous" data-next="next"> type:node] score:0.018054 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2144 height:75 left:548 right:681 top:2069 width:133] lhId:page-14-IMG nodeLabel:First quarter 2026 trading statement path:1,HTML,1,BODY,3,DIV,14,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,UL,0,LI,0,A,0,IMG selector:ul.nr-list__item-wrap > li.nr-list__item > a.nr-list__thumbnail > img.lazyload snippet:<img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" alt="First quarter 2026 trading statement " src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" width="175" height="100%" class="lazyload nr-lazy-size nr-list__thumbnail-image"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:868 height:616 left:253 right:1350 top:252 width:1097] lhId:page-8-SECTION nodeLabel:Hidden depths: Finding energy for tomorrow, today Helping to supply the world… path:1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION selector:body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel snippet:<section class="nr-feature-carousel nr-feature-carousel--dark" data-prev="Previous" data-next="next"> type:node] score:0.016974 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2144 height:75 left:548 right:681 top:2069 width:133] lhId:page-14-IMG nodeLabel:First quarter 2026 trading statement path:1,HTML,1,BODY,3,DIV,14,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,UL,0,LI,0,A,0,IMG selector:ul.nr-list__item-wrap > li.nr-list__item > a.nr-list__thumbnail > img.lazyload snippet:<img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" alt="First quarter 2026 trading statement " src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/graphics…" width="175" height="100%" class="lazyload nr-lazy-size nr-list__thumbnail-image"> type:node]]] 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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:23.681 source:map[type:text value:[unattributed]]] map[reflowTime:0.532 source:map[column:66658 line:42 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.186 source:map[column:66744 line:42 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:2.089 source:map[column:49902 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.385 source:map[column:49960 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.363 source:map[column:50024 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:6.685 source:map[column:49184 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.61 source:map[column:50937 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:0.114 source:map[column:49206 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]] map[reflowTime:2.756 source:map[column:84963 line:10 type:source-location url:https://www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js urlProvider:network]]]

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: Inspection of seismic imagery
path: 1,HTML,1,BODY,3,DIV,8,DIV,0,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.slick-slide > div > div.nr-feature-carousel__item > img.nr-feature-carousel__media
snippet: <img data-src="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" data-srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…" alt="Inspection of seismic imagery" src="https://www.bp.com/content/dam/bp/business-sites/en/global/corporate/image…" width="1175" height="100%" class="nr-feature-carousel__media nr-lazy-size lazyloaded" srcset="/content/dam/bp/business-sites/en/global/corporate/images-jpg-png/news-and…">

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

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
Inspection of seismic imagery div.slick-slide > div > div.nr-feature-carousel__item > img.nr-feature-carousel__media
/content/dam/bp/business-sites/en/global/corporate/images...110.4 KiB14.2 KiB

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

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: 40 ms 43.1 KiB
URLTransfer SizeEst Savings
www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.css48.7 KiB43.1 KiB

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: 200 ms 250.8 KiB
URLTransfer SizeEst Savings
www.bp.com/apps/settings/wcm/designs/refresh/bp/assets.js327.9 KiB250.8 KiB

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 22.3 KiB
URLTransfer SizeEst Savings
inline: var navDataArr = [ { …59.8 KiB22.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 795 ms
URLTime Spent
bp.com/795 ms
www.bp.com/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
body.nr-navigation--presence > ::after body.nr-navigation--presence > ::after
0.113
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.035
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.021
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.018
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.017
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.013
Key documents Country websites Frequent searches body.nr-navigation--presence > div.aem-Grid > div.nr-layout-component
0.010
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.010
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.009
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.007
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.006
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.005
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.003
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.002
Hidden depths: Finding energy for tomorrow, today Helping to supply the world… body.nr-navigation--presence > div.aem-Grid > div#featureCarousel > section.nr-feature-carousel
0.002
Time to Interactive 2.1 s
Max Potential First Input Delay 70 ms
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 1,061 KiB
JavaScript execution time 0.2 s
Minimizes main-thread work 0.5 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 2 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 200 ms
Server Backend Latencies 220 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
User Timing marks and measures
96

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Disclaimer div.nr-footer__content > div.nr-row > div.nr-footer__disclaimer > a.nr-footer__disclaimer-title

These are opportunities to improve the legibility of your content.

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

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

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.

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
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`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback