C — https://ampproject.org | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

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.

Good content signals with minor gaps.

Lean and efficient — low environmental impact per visit.

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

Framework sites average 74

At average

Better than 77% of Framework sites

Google Domains sites average 75

At average

Better than 86% of Google Domains sites See full Google Domains benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

1 control(s) without accessible label

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

Accessibility › Form Accessibility

1 link(s) with no accessible text

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

Accessibility › Link & Button Quality

8 button(s) with no accessible text

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

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fampproject.org)](https://beavercheck.com/results/0dff2537-fa1c-4abe-8192-a5c8ed16368f)

HTML

<a href="https://beavercheck.com/results/0dff2537-fa1c-4abe-8192-a5c8ed16368f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fampproject.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fampproject.org

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

3 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 4 warning

5 barrier(s) likely increasing bounce by ~19%.

Speed (1)

Page loads in 2.7s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 215ms over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Trust (1)

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 (1)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Navigation (2)

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

31 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

€468 investment → €331/month returns + EUR 120,500,000 risk avoided

Payback period: ~1 months First-year ROI: +748%

Investment

€468

6h · 5 findings

Monthly returns

€331 /mo

~€3,967 / year

Conversions recovered €330
Bandwidth savings €0.07

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

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

€468

5.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€85 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,001 / 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

+19 more

Bandwidth Waste

€0.07 /mo

893.0 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~89 KB per page load
Saves €0.07/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

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

2.60 s

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

2.71 s

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

17 ms

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

0.000

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

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

3.66 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	604800.0 s	52.0 KiB
amp.dev/static/fonts/noto-sans-v7-latin-regular.woff2	604800.0 s	9.8 KiB
amp.dev/static/fonts/noto-sans-v7-latin-700.woff2	604800.0 s	9.6 KiB
amp.dev/static/fonts/poppins-v5-latin-700.woff2	604800.0 s	7.8 KiB

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.

	URL	Resource Size	Est Savings
Bento `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	51.9 KiB	36.1 KiB

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

Diagnostics

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 58.5 KiB

URL	Transfer Size	Est Savings
cdn.ampproject.org/v0.mjs	62.2 KiB	33.7 KiB
cdn.ampproject.org/v0/amp-analytics-0.1.mjs	28.5 KiB	24.8 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: 1.6 s

URL	Time Spent
ampproject.org/	797 ms
www.ampproject.org/	788 ms
amp.dev/	0.0 ms

●Time to Interactive 3.7 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 291 KiB

●User Timing marks and measures 8 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bento Introducing Bento December 8, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Web Stories call to action buttons get an upgrade September 15, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Websites Easy TikTok embedding with the new amp-tiktok September 13, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Richer interactions in Web Stories August 26, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
Stories Better video performance in Web Stories August 24, 2021 `amp-base-carousel#teaser-carousel-news > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites Teads brings AMP'd mobile video inventory to nearly 100 publishers Adv… `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites Carved increases conversion rate by 75% with AMP and PWA E-Commerce `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`
websites WompMobile consistently improves e-commerce clients’ conversion rates … `amp-base-carousel#success-stories > div.i-amphtml-carousel-content > div.i-amphtml-carousel-scroll > a.-nr`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
`body.ap--websites > main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news`
`body.ap--websites > main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories`

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-news > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`
main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na `main.ap--main > section.-nn > amp-selector#teaser-carousel-pagination-success-stories > div.-na`

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper `section.ap-formats > aside.ap-formats-navigation > div.ap-formats-navigation-wrapper > button.ap-formats-navigation-icon-wrapper`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`

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.-l > ul.-h > li.-p > a.ap-a-ico `div.-l > ul.-h > li.-p > a.ap-a-ico`

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.

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
Easily create websites with a great page experience out-of-the-box using AMP’s … `section.ap-formats > div#ap-formats-format-websites > div.ap-formats-format-content > h5.ap-h5`
Immerse readers in visual and tappable stories they can share anywhere on the o… `section.ap-formats > div#ap-formats-format-stories > div.ap-formats-format-content > h5.ap-h5`
Send emails of the future with personalized dynamic content and interactive ele… `section.ap-formats > div#ap-formats-format-email > div.ap-formats-format-content > h5.ap-h5`
Serve lightning fast and secure eye-catching creatives. `section.ap-formats > div#ap-formats-format-ads > div.ap-formats-format-content > h5.ap-h5`
Stories `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Got it! `body.ap--websites > amp-consent#consent > div#consent-popup > button.ap-a-btn`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

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

●`[role]` values are valid

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

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

●`[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 use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

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

●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 `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Image elements have `[alt]` attributes

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

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.


`head > link`
`head > link`

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 have descriptive text

●Links are crawlable

●Document has a valid `rel=canonical`

○robots.txt is valid

○Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

749 ms

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

788 ms

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

0 ms

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

0.000

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

749 ms

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

790 ms

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	604800.0 s	121.7 KiB
amp.dev/static/img/success-stories/carved/teaser_carved.jpg	604800.0 s	82.5 KiB
amp.dev/static/img/success-stories/teads/teaser_teads.jpg	604800.0 s	61.1 KiB
/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	604800.0 s	52.0 KiB
/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	604800.0 s	49.0 KiB
/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	604800.0 s	48.3 KiB
amp.dev/static/img/success-stories/washington_post/teaser_washington_post.jpg	604800.0 s	42.0 KiB
amp.dev/static/img/success-stories/womp/teaser_wompmobile.jpg	604800.0 s	33.1 KiB
amp.dev/static/img/success-stories/washington_post/washington_post_logo.png	604800.0 s	20.4 KiB
amp.dev/static/fonts/noto-sans-v7-latin-regular.woff2	604800.0 s	9.8 KiB
amp.dev/static/fonts/noto-sans-v7-latin-700.woff2	604800.0 s	9.6 KiB
amp.dev/static/fonts/poppins-v5-latin-700.woff2	604800.0 s	7.8 KiB
amp.dev/static/img/success-stories/womp/wompmobile_logo.png	604800.0 s	4.8 KiB
amp.dev/static/img/success-stories/teads/teads_logo.png	604800.0 s	4.6 KiB
amp.dev/static/img/success-stories/carved/carved_logo.png	604800.0 s	2.9 KiB

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.

	URL	Resource Size	Est Savings
Stories `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	121.6 KiB	105.8 KiB
Carved `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/carved/teaser_carved.jpg	82.3 KiB	60.7 KiB
Teads `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/teads/teaser_teads.jpg	61.0 KiB	39.4 KiB
Bento `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	51.9 KiB	36.1 KiB
Stories `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	48.8 KiB	33.1 KiB
Stories `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	/static/remote/https%3A%2F%2Fblog.amp.dev%2Fwp-content%2F...	48.2 KiB	32.4 KiB
Washington Post `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/washington_post/teaser_washington_post.jpg	41.8 KiB	25.4 KiB
WompMobile `div.-ni > div.-nc > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/womp/teaser_wompmobile.jpg	33.0 KiB	20.1 KiB
Washington Post `div.-np > div.-nh > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/washington_post/washington_post_logo.png	20.3 KiB	19.4 KiB
WompMobile `div.-np > div.-nh > amp-img.i-amphtml-layout-fill > img.i-amphtml-fill-content`	amp.dev/static/img/success-stories/womp/wompmobile_logo.png	4.6 KiB	4.2 KiB

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

Diagnostics

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

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 57.1 KiB

URL	Transfer Size	Est Savings
cdn.ampproject.org/v0.mjs	62.2 KiB	32.3 KiB
cdn.ampproject.org/v0/amp-analytics-0.1.mjs	28.5 KiB	24.8 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: 483 ms

URL	Time Spent
ampproject.org/	238 ms
www.ampproject.org/	245 ms
amp.dev/	0.0 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.8 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 761 KiB

●User Timing marks and measures 8 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.3 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-prev-slot > button`
div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button `div.i-amphtml-carousel-content > div.i-amphtml-base-carousel-arrows > div.i-amphtml-base-carousel-arrow-next-slot > button`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EN DE FR AR ES IT ID JA KO PT RU TR ZH PL VI `header.ap-header > div.ap-header-main > div.ap-language-selector > select`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.-l > ul.-h > li.-p > a.ap-a-ico `div.-l > ul.-h > li.-p > a.ap-a-ico`

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.

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Easily create websites with a great page experience out-of-the-box using AMP’s … `section.ap-formats > div#ap-formats-format-websites > div.ap-formats-format-content > h5.ap-h5`
Immerse readers in visual and tappable stories they can share anywhere on the o… `section.ap-formats > div#ap-formats-format-stories > div.ap-formats-format-content > h5.ap-h5`
Send emails of the future with personalized dynamic content and interactive ele… `section.ap-formats > div#ap-formats-format-email > div.ap-formats-format-content > h5.ap-h5`
Serve lightning fast and secure eye-catching creatives. `section.ap-formats > div#ap-formats-format-ads > div.ap-formats-format-content > h5.ap-h5`
Stories `a.-nr > div.-ni > div.-nf > h6`
Bento `a.-nr > div.-ni > div.-nf > h6`
Stories `a.-nr > div.-ni > div.-nf > h6`
Websites `a.-nr > div.-ni > div.-nf > h6`
Stories `a.-nr > div.-ni > div.-nf > h6`
Stories `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`
websites `a.-nr > div.-ni > div.-nf > h6`

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Got it! `body.ap--websites > amp-consent#consent > div#consent-popup > button.ap-a-btn`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

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

●`[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 use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

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

●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

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements 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

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

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

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

Content Best Practices

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.


`head > link`
`head > link`

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 have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `rel=canonical`

○robots.txt is valid

Results for https://ampproject.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (1)

Usability (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Navigation

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Navigation

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts