Skip to content
Audit Complete

Results for https://androidpolice.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 15, 2026 23:24 UTC
Download JSON 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)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

Facebook sites average 72
At average
Better than 75% of Facebook sites See full Facebook benchmark →
Google Search Console sites average 73
At average
Better than 64% of Google Search Console sites See full Google Search Console 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

'unsafe-inline' found in script source

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

Security › Content Security Policy
3

Wildcard '*' found in script source

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

Security › Content Security Policy
4

18 link(s) with no accessible text

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

Accessibility › Link & Button Quality
5

2 control(s) without accessible label

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

Accessibility › Form Accessibility
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Fandroidpolice.com)](https://beavercheck.com/results/5bea0d63-8613-4853-9336-a8b88b466f07)
<a href="https://beavercheck.com/results/5bea0d63-8613-4853-9336-a8b88b466f07"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fandroidpolice.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fandroidpolice.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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Return on Investment

€383 investment → €3,346/month returns + EUR 120,500,000 risk avoided

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

Investment

€383

4h · 5 findings

Monthly returns

€3,346 /mo

~€40,153 / year

  • Conversions recovered €3,345
  • Bandwidth savings €0.59

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — 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

€383

4.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 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

€10,041,667 / month at risk

~€120,500,007 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

€0.59 /mo

7908.7 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~791 KB per page load
    Saves €0.59/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 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

40
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
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.

3.23 s

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

5.43 s

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

2.23 s

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

0.000

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

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

18.38 s

Detailed Report

Audit breakdown by category with detailed findings.

40

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:114.06 source:map[column:34497 line:1 type:source-location url:https://static0.anpoimages.com/assets/valnet-footer.dd217e3d.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:114.06 source:map[column:34409 line:0 type:source-location url:https://static0.anpoimages.com/assets/valnet-footer.dd217e3d.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
A 3D Google Chrome icon hovering above browser interfaces that showcase the Ver… a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-3d-google-chrome-...52.0 KiB49.8 KiB
The black Huxe app icon surrounded by floating digital podcast cards. a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/the-black-huxe-app-...29.1 KiB23.9 KiB
A dark SUV driving on a road, surrounded by large Android Auto icons. a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-dark-suv-driving-...28.0 KiB22.9 KiB
A smiling man using his smartphone, standing in front of a large phone graphic … a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-smiling-man-using...22.4 KiB21.4 KiB
The Onn Google TV 4K Pro rear ports a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/wm/2024/07/onn-4k-pro-rear-...16.5 KiB15.8 KiB
A hand holding a smartphone displaying a minimalist Android 17 home screen. a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-hand-holding-a-sm...17.6 KiB14.4 KiB
Link Image a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2024/09/google-chrome-1-ap2...12.6 KiB12.0 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-5-IMG
nodeLabel: A hand holding a smartphone displaying a minimalist Android 17 home screen.
path: 1,HTML,1,BODY,16,MAIN,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,DIV,0,PICTURE,1,IMG
selector: a.dc-img-link > div.dc-img > picture > img
snippet: <img width="1486" height="1064" alt="A hand holding a smartphone displaying a minimalist Android 17 home screen." data-img-url="https://static0.anpoimages.com/wordpress/wp-content/uploads/2026/04/a-hand…" src="https://static0.anpoimages.com/wordpress/wp-content/uploads/2026/04/a-hand…">

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.

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

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.

Diagnostics

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.

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 Evaluation4.3 s
Other2.0 s
Script Parsing & Compilation1.1 s
Style & Layout1.1 s
Parse HTML & CSS279 ms
Rendering272 ms
Garbage Collection97 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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: 0.0 ms 58.0 KiB
URLTransfer SizeEst Savings
.design-system--grid{width:100%} …39.9 KiB37.1 KiB
cdn.adsninja.ca/adsninja_client_style.css?v=362021.9 KiB20.8 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

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
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,574 KiB
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 6 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 180 ms
INP breakdown
Avoid large layout shifts
86

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PIXEL LAUNCHER div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE MESSAGES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
PHONES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE CHROME div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
24 div.w-display-card-details > div.w-display-card-extra > a.total-info-number > span.num
ANDROID AUTO div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
10 div.w-display-card-details > div.w-display-card-extra > a.total-info-number > span.num
PRODUCTIVITY div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE MESSAGES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
10 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
13 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
18 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
MORE div.template-grid-tall > div.featured-news > div.sentinel-featuredNews > a.section-view-all-link
SEE MORE section#best-reads > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE section#news > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE section#deals > div.w-hub-widgets > div.hub-header > a.section-view-all-link
10 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
13 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
18 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
45 div.w-display-card-extra > div.total-info > a.total-info-number > span.num
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kindles getting 14 years of support is pretty amazing, actually div.sentinel-home-list > div.display-card > div.w-display-card-content > h5.display-card-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GOOGLE CHROME div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
ANDROID AUTO div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
PRODUCTIVITY div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
GOOGLE MESSAGES div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
Jon Gilbert div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
Karandeep Singh Oberoi div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
Join Our Team div.footer-content-el > ul > li > a.text
Our Audience div.footer-content-el > ul > li > a.text
About Us div.footer-content-el > ul > li > a.text
Press & Events div.footer-content-el > ul > li > a.text
Media Coverage div.footer-content-el > ul > li > a.text
Contact Us div.footer-content-el > ul > li > a.text
Advertising div.footer-content-el > ul.align-right > li > a.text
Careers div.footer-content-el > ul.align-right > li > a.text
Terms div.footer-content-el > ul.align-right > li > a.text
Privacy div.footer-content-el > ul.align-right > li > a.text
Policies div.footer-content-el > ul.align-right > li > a.text

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
Elements use only permitted ARIA attributes
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[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.
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
Unload event listeners are deprecated and will be removed.
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
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
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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

82
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
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.10 s

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

1.46 s

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

172 ms

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

0.002

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

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

4.03 s

Detailed Report

Audit breakdown by category with detailed findings.

82

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:96.923 source:map[column:34497 line:1 type:source-location url:https://static0.anpoimages.com/assets/valnet-footer.dd217e3d.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:96.923 source:map[column:34409 line:0 type:source-location url:https://static0.anpoimages.com/assets/valnet-footer.dd217e3d.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: A hand holding a smartphone displaying a minimalist Android 17 home screen.
path: 1,HTML,1,BODY,18,MAIN,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,DIV,0,PICTURE,1,IMG
selector: a.dc-img-link > div.dc-img > picture > img
snippet: <img width="1486" height="1064" alt="A hand holding a smartphone displaying a minimalist Android 17 home screen." data-img-url="https://static0.anpoimages.com/wordpress/wp-content/uploads/2026/04/a-hand…" src="https://static0.anpoimages.com/wordpress/wp-content/uploads/2026/04/a-hand…">

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.

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
Three smartphones demonstrating the new App Pairing multitasking feature in And… div.w-img > div.bc-img > picture > img
/wordpress/wp-content/uploads/2026/04/three-smartphones-d...33.4 KiB25.1 KiB
A hand holding a smartphone displaying a minimalist Android 17 home screen. a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-hand-holding-a-sm...29.6 KiB22.8 KiB
A 3D Google Chrome icon hovering above browser interfaces that showcase the Ver… a.dc-img-link > div.dc-img > picture > img
/wordpress/wp-content/uploads/2026/04/a-3d-google-chrome-...25.0 KiB19.2 KiB
The Ray-Ban Meta (Gen 2) with the case a.dc-img-link > div.w-img > div.bc-img > img
/wordpress/wp-content/uploads/wm/2026/04/ray-ban-meta-gen...5.8 KiB4.7 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: 472 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

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 Evaluation1.4 s
Style & Layout562 ms
Other526 ms
Script Parsing & Compilation266 ms
Rendering87 ms
Parse HTML & CSS82 ms
Garbage Collection10 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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: 0.0 ms 56.3 KiB
URLTransfer SizeEst Savings
.design-system--grid{width:100%} …39.8 KiB35.7 KiB
cdn.adsninja.ca/adsninja_client_style.css?v=362021.9 KiB20.6 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

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

Max Potential First Input Delay 130 ms
Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,653 KiB
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 8 long tasks found
Avoid non-composited animations 11 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 190 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
87

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PIXEL LAUNCHER div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE MESSAGES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
PHONES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE CHROME div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
ANDROID AUTO div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
PRODUCTIVITY div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
GOOGLE MESSAGES div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
10 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
13 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
18 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
1 DAY AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
SEE MORE section#news > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE section#deals > div.w-hub-widgets > div.hub-header > a.section-view-all-link
10 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
13 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
18 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
45 div.w-display-card-extra > div.total-info > a.total-info-number > span.num
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kindles getting 14 years of support is pretty amazing, actually div.sentinel-home-list > div.display-card > div.w-display-card-content > h5.display-card-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text

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

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEE MORE section#best-reads > div.w-hub-widgets > div.hub-header > a.section-view-all-link
Jon Gilbert div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
Anu Joy div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
Stephen Radochia div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
Ben Khalesi div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
Anu Joy div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
1 div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
Elements use only permitted ARIA attributes
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements 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
`<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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[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.
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.
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
Unload event listeners are deprecated and will be removed.
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
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
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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback