C — https://web.dev | BeaverCheck Audit

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

How is this calculated?

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

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

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

Top Priorities (5)

'unsafe-eval' found in script source

Security › Content Security Policy

'unsafe-inline' found in script source

Security › Content Security Policy

6 link(s) with no accessible text

Accessibility › Link & Button Quality

No H1 heading found

Accessibility › Heading Hierarchy

is missing width/height — may cause layout shift

Performance › Image Optimization

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fweb.dev)](https://beavercheck.com/results/845ddeb6-3b54-44bd-8f30-a00b757548b2)

HTML

<a href="https://beavercheck.com/results/845ddeb6-3b54-44bd-8f30-a00b757548b2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fweb.dev" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fweb.dev

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

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.

11.74 s

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

12.87 s

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

679 ms

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

0.001

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

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

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

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

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

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2	45 ms
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	25 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBA.woff2	10 ms

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

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:14.561 source:map[column:53 line:254 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.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:90.388 source:map[type:text value:[unattributed]]] map[reflowTime:2.371 source:map[column:224 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.41 source:map[column:330 line:243 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:1.891 source:map[column:59 line:242 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.148 source:map[column:249 line:247 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:4.635 source:map[column:348 line:7 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_devsite_header_module.js urlProvider:network]] map[reflowTime:14.484 source:map[column:720 line:241 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:5.069 source:map[column:441 line:22 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_devsite_book_nav_module.js urlProvider:network]] map[reflowTime:6.224 source:map[column:168 line:3348 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_custom_elements_module.js urlProvider:network]]]

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

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

URL	Transfer Size	Duration
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	153.3 KiB	5.4 s
/css?family=Google+Sans:400,500\|Roboto:400,400italic,500,...	3.3 KiB	790 ms
/css2?family=Material+Icons&family=Material+Symbols+Outli...	982 B	158 ms

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

Request	Cache TTL	Transfer Size
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.2 KiB

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

	URL	Resource Size	Est Savings
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`	web.dev/static/images/home-blue_856.png	32.5 KiB	28.9 KiB
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/identity/image/hero-identity_480.png	21.7 KiB	20.4 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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

Estimated savings: 1.4 s 130.2 KiB

URL	Transfer Size	Est Savings
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	152.8 KiB	130.2 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.

Estimated savings: 300 ms 269.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-64EQFFKSHW&l=atDataLayer&cx=c&gtm=4e6411	142.0 KiB	61.0 KiB
www.googletagmanager.com/gtag/js?id=G-18JR3Q8PJ8&cx=c&gtm=4e6420h2	145.9 KiB	60.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-NDV7K7V5&l=atDataLayer	128.9 KiB	60.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-MZWCJPP	135.5 KiB	59.7 KiB
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	58.2 KiB	28.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
web.dev/	1.1 s	28 ms	2.2 ms
Unattributable	492 ms	37 ms	0.0 ms
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	466 ms	90 ms	1.2 ms
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	425 ms	321 ms	23 ms
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	418 ms	194 ms	190 ms
www.googletagmanager.com/gtm.js?id=GTM-MZWCJPP	407 ms	328 ms	75 ms
www.googletagmanager.com/gtag/js?id=G-18JR3Q8PJ8&cx=c&gtm=4e6420h2	322 ms	263 ms	56 ms
www.googletagmanager.com/gtag/js?id=G-64EQFFKSHW&l=atDataLayer&cx=c&gtm=4e6411	293 ms	242 ms	49 ms
www.googletagmanager.com/gtm.js?id=GTM-NDV7K7V5&l=atDataLayer	279 ms	223 ms	53 ms
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	76 ms	0.0 ms	0.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	2.0 s
Other	1.0 s
Style & Layout	932 ms
Script Parsing & Compilation	510 ms
Parse HTML & CSS	90 ms
Rendering	83 ms
Garbage Collection	26 ms

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

	URL
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/images/ai-feature_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/images/inp-icon-only_480.jpg
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/identity/image/hero-identity_480.png
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`	web.dev/static/images/home-blue_856.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,465 KiB

●User Timing marks and measures 20 user timings

●Avoid long main-thread tasks 14 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

Failing Elements
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Read the blog `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe `div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe`

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.

Failing Elements
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
image `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
web `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
timer `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○Ensure CSP is effective against XSS attacks

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
web.dev/explore/ai	Learn more
/explore/how-to-optimize-inp?utm_source=web.dev&utm_mediu...	Learn more
web.dev/identity	Learn more
web.dev/html	Learn more
web.dev/css	Learn more
web.dev/javascript	Learn more

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

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.

1.07 s

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

1.69 s

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

60 ms

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

0.028

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

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

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

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2	80 ms
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	25 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBA.woff2	15 ms

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:40.47 source:map[column:18 line:227 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.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:0.777 source:map[column:330 line:243 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:41.437 source:map[column:224 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.17 source:map[column:249 line:247 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:25.668 source:map[type:text value:[unattributed]]] map[reflowTime:6.069 source:map[column:348 line:7 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_devsite_header_module.js urlProvider:network]] map[reflowTime:16.054 source:map[column:106 line:165 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:0.049 source:map[column:59 line:242 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_module.js urlProvider:network]] map[reflowTime:13.876 source:map[column:441 line:22 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_devsite_book_nav_module.js urlProvider:network]] map[reflowTime:1.19 source:map[column:168 line:3348 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_custom_elements_module.js urlProvider:network]] map[reflowTime:2.048 source:map[column:226 line:3303 type:source-location url:https://www.gstatic.com/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424f5334bce4dd1449f7f3a599cf8e09/js/devsite_app_custom_elements_module.js urlProvider:network]]]

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

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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.

URL	Transfer Size	Duration
/css2?family=Material+Icons&family=Material+Symbols+Outli...	590 B
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	153.3 KiB	703 ms
/css?family=Google+Sans:400,500\|Roboto:400,400italic,500,...	3.6 KiB	238 ms

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

Request	Cache TTL	Transfer Size
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.2 KiB

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

	URL	Resource Size	Est Savings
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/identity/image/hero-identity_480.png	21.7 KiB	21.0 KiB
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`	web.dev/static/images/home-blue_720.png	26.4 KiB	13.3 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 200 ms 131.8 KiB

URL	Transfer Size	Est Savings
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	152.8 KiB	131.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.

Estimated savings: 160 ms 438.5 KiB

URL	Transfer Size	Est Savings
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	302.3 KiB	169.2 KiB
www.googletagmanager.com/gtag/js?id=G-64EQFFKSHW&l=atDataLayer&cx=c&gtm=4e6411h1	141.9 KiB	60.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-NDV7K7V5&l=atDataLayer	128.9 KiB	60.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-MZWCJPP	135.5 KiB	59.9 KiB
www.googletagmanager.com/gtag/js?id=G-18JR3Q8PJ8&cx=c&gtm=4e6420h2	145.9 KiB	59.9 KiB
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	58.2 KiB	28.8 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.5 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.5 KiB
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	302.3 KiB
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	153.3 KiB
/devrel-devsite/prod/vb4124e0eb36966d1f5cf3a7ca116e70a424...	152.9 KiB
www.googletagmanager.com/gtag/js?id=G-18JR3Q8PJ8&cx=c&gtm=4e6420h2	145.9 KiB
www.googletagmanager.com/gtag/js?id=G-64EQFFKSHW&l=atDataLayer&cx=c&gtm=4e6411h1	142.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-MZWCJPP	135.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-NDV7K7V5&l=atDataLayer	129.3 KiB
fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2	125.6 KiB

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

	URL
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`	web.dev/static/images/home-blue_720.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/learn/html/card_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/learn/css/card_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/learn/javascript/card_480.png
div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img `div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > picture > img`	web.dev/static/images/blog-header_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/identity/image/hero-identity_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/images/ai-feature_480.png
figure.devsite-landing-row-item-image > a > picture > img `figure.devsite-landing-row-item-image > a > picture > img`	web.dev/static/images/inp-icon-only_480.jpg

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 20 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 5 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 7 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Start course `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`
Read the blog `div.devsite-landing-row-item-description > div.devsite-landing-row-item-body > div.devsite-landing-row-item-buttons > a.button`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Failing Elements
div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe `div.devsite-landing-row-group > div.devsite-landing-row-item > devsite-iframe > iframe`

Failing Elements
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
image `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
web `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
timer `div.devsite-landing-row-group > div.devsite-landing-row-item > div.devsite-landing-row-item-description > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`
div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a `div.devsite-landing-row-item > div.devsite-landing-row-item-media > figure.devsite-landing-row-item-image > a`

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.

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

Failing Elements
More `devsite-tabs.upper-tabs > nav.devsite-tabs-wrapper > tab.devsite-overflow-tab > button#tab-overflow-button-iE9T`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○Ensure CSP is effective against XSS attacks

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
web.dev/explore/ai	Learn more
/explore/how-to-optimize-inp?utm_source=web.dev&utm_mediu...	Learn more
web.dev/identity	Learn more
web.dev/html	Learn more
web.dev/css	Learn more
web.dev/javascript	Learn more

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`

Results for https://web.dev

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts