Skip to content
Audit Complete

Results for https://www.fastly.com

Visit site
United Stated United Stated · Santa Clara Completed: Apr 4, 2026 16:23 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 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)

1

Content-Security-Policy header is missing

Security › Security Headers
2

No Content-Security-Policy header found

Security › Content Security Policy
3

10 button(s) with no accessible text

Accessibility › Link & Button Quality
4

7 link(s) with no accessible text

Accessibility › Link & Button Quality
5

165 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fastly.com)](https://beavercheck.com/results/f2e91a06-3972-4a87-b1a2-a6f49114941a)
<a href="https://beavercheck.com/results/f2e91a06-3972-4a87-b1a2-a6f49114941a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fastly.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fastly.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

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

16.09 s

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

2.18 s

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

0.041

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

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

22.26 s

Detailed Report

Audit breakdown by category with detailed findings.

35

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.

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

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
cdn.cookielaw.org/scripttemplates/202601.1.0/otBannerSdk.js86400.0 s127.0 KiB
/signals/config/422860714812843?v=2.9.291&r=stable&domain...1200.0 s38.1 KiB
fastlyinc.widget.insent.ai/insent0.0 ms23.0 KiB
schedule.zoominfo.com/zischedule.js0.0 ms17.1 KiB
tags.clickagy.com/data.js?rnd=62fe5c0e6ad960.0 ms14.1 KiB
ws-assets.zoominfo.com/formcomplete.js3600.0 s14.5 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms11.2 KiB
cdn.bizible.com/scripts/bizible.js86400.0 s25.2 KiB
cdn.speedcurve.com/js/lux.js?id=42726462683600.0 s11.3 KiB
tags.srv.stackadapt.com/events.js5.0 s7.6 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
attachments.insent.ai/fastlyinc/logo-fastlyinc-1766424868451?17664248686000.0 ms7.3 KiB
/logos/b924a052-1698-426b-800c-9042228f9f50/b04f5421-84b6...86400.0 s15.9 KiB
js.zi-scripts.com/zi-tag.js0.0 ms5.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
trk.techtarget.com/tracking.js1200.0 s1.5 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
/st?ga_tracking_id=G-ETDRC9QJ6S&ga_client_id=1949872313.1...0.0 ms1.2 KiB
js.adsrvr.org/universal_pixel.js0.0 ms958 B
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.1 KiB
/st?ga_tracking_id=G-ETDRC9QJ6S&ga_client_id=1949872313.1...0.0 ms582 B
cdn.cookielaw.org/logos/static/ot_close.svg86400.0 s631 B
/collect?v=2&fmt=js&pid=118344%2C4799041&time=17753197197...0.0 ms41 B
/tr/?id=422860714812843&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B

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:42.151 source:map[column:197 line:995 type:source-location url:https://www.fastly.com/metrics/gtm/?id=GTM-W9FKFHD 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:55.222 source:map[type:text value:[unattributed]]] map[reflowTime:42.151 source:map[column:55 line:992 type:source-location url:https://www.fastly.com/metrics/gtm/?id=GTM-W9FKFHD urlProvider:network]] map[reflowTime:40.374 source:map[column:297901 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202601.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:31.196 source:map[column:17590 line:28 type:source-location url:https://tags.srv.stackadapt.com/events.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

URLResource SizeEst Savings
div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha
/cimages/ocb1q9kflo7k/lTEV5zKHt0yMaC6wyjhWa/bc75913d91489...85.0 KiB32.7 KiB
fastly-globe div.kxsh863 > div.ebwo3s0 > div.ebwo3s1 > img
/cimages/ocb1q9kflo7k/1r4vSqbB26Qxu3LWfQ96ik/102e711409f6...32.6 KiB17.0 KiB

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

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.

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

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

CategoryTime Spent
Script Evaluation4.9 s
Other2.1 s
Style & Layout1.0 s
Script Parsing & Compilation608 ms
Rendering184 ms
Parse HTML & CSS178 ms
Garbage Collection131 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

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.

Estimated savings: 0.0 ms 90.2 KiB
URLTransfer SizeEst Savings
.mh9g3z0{bottom:0;box-sizing:content-box;padding:1rem;position:fixed;z-index:1001} …81.6 KiB71.7 KiB
21.4 KiB18.5 KiB

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
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 24 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 11 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 310 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 10 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
89

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.

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.

Failing Elements
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5 div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5
div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5 div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5

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.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi div.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi

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.

Contrast

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

Failing Elements
as of December 31, 2022 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of July 31, 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of March 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of December 31, 2025 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y

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.

Failing Elements
More announcements main > div._1y3v4p30 > div._1y3v4p31 > h6.nbbs0e9

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.

Failing Elements
Cookie Policy div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
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
Elements use only permitted ARIA attributes
ARIA toggle fields have accessible names
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
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
`[accesskey]` values are unique
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
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.

Deprecation / WarningSource
AttributionReporting
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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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.

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

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

907 ms

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

2.30 s

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

199 ms

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

0.008

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

1.66 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.73 s

Detailed Report

Audit breakdown by category with detailed findings.

79

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.

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

RequestCache TTLTransfer Size
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
cdn.cookielaw.org/scripttemplates/202601.1.0/otBannerSdk.js86400.0 s127.0 KiB
/signals/config/422860714812843?v=2.9.291&r=c2&domain=www...1200.0 s38.1 KiB
fastlyinc.widget.insent.ai/insent0.0 ms23.0 KiB
schedule.zoominfo.com/zischedule.js0.0 ms17.1 KiB
tags.clickagy.com/data.js?rnd=62fe5c0e6ad960.0 ms14.0 KiB
ws-assets.zoominfo.com/formcomplete.js3600.0 s14.5 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms11.2 KiB
cdn.bizible.com/scripts/bizible.js86400.0 s25.2 KiB
cdn.speedcurve.com/js/lux.js?id=42726462683600.0 s11.3 KiB
tags.srv.stackadapt.com/events.js5.0 s7.6 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
attachments.insent.ai/fastlyinc/logo-fastlyinc-1766424868451?17664248686000.0 ms7.3 KiB
/logos/b924a052-1698-426b-800c-9042228f9f50/b04f5421-84b6...86400.0 s15.9 KiB
js.zi-scripts.com/zi-tag.js0.0 ms5.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
trk.techtarget.com/tracking.js1200.0 s1.5 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
/st?ga_tracking_id=G-ETDRC9QJ6S&ga_client_id=998175311.17...0.0 ms1.2 KiB
js.adsrvr.org/universal_pixel.js0.0 ms958 B
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.1 KiB
/st?ga_tracking_id=G-ETDRC9QJ6S&ga_client_id=998175311.17...0.0 ms582 B
/collect?v=2&fmt=js&pid=118344%2C4799041&time=17753197465...0.0 ms452 B
cdn.cookielaw.org/logos/static/ot_close.svg86400.0 s631 B
/tr/?id=422860714812843&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B

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:36.576 source:map[column:17543 line:29 type:source-location url:https://tags.srv.stackadapt.com/events.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:42.226 source:map[type:text value:[unattributed]]] map[reflowTime:36.576 source:map[column:17590 line:28 type:source-location url:https://tags.srv.stackadapt.com/events.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG
nodeLabel: div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV,1,DIV,0,IMG
selector: div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha
snippet: <img alt="" class="kj3auha" sizes="(max-width: 768px) 80vw, (max-width: 1280px) 40vw, 520px" src="https://www.fastly.com/cimages/ocb1q9kflo7k/lTEV5zKHt0yMaC6wyjhWa/bc75913d…" srcset="//www.fastly.com/cimages/ocb1q9kflo7k/lTEV5zKHt0yMaC6wyjhWa/bc75913d914894…" data-intellimize-anti-flicker-exp-417234929="true" data-intellimize-anti-flicker-exp-417243965="true">

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.

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

URLResource SizeEst Savings
div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha div.kj3auh1 > div.kj3auh2 > div.kj3auh9 > img.kj3auha
/cimages/ocb1q9kflo7k/lTEV5zKHt0yMaC6wyjhWa/bc75913d91489...85.0 KiB42.2 KiB
div._1v7xp385 > div#5LUhl92675DwlUmQWNreZE > div._1v7xp38d > img div._1v7xp385 > div#5LUhl92675DwlUmQWNreZE > div._1v7xp38d > img
/cimages/ocb1q9kflo7k/2T9oU8g7aGx09vfElGe4fk/0ae920a41dfd...38.1 KiB34.6 KiB
fastly-globe div.kxsh863 > div.ebwo3s0 > div.ebwo3s1 > img
/cimages/ocb1q9kflo7k/1r4vSqbB26Qxu3LWfQ96ik/102e711409f6...32.6 KiB15.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

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.

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

CategoryTime Spent
Script Evaluation1.2 s
Other659 ms
Style & Layout425 ms
Rendering234 ms
Script Parsing & Compilation156 ms
Parse HTML & CSS46 ms
Garbage Collection32 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

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.

Estimated savings: 0.0 ms 88.1 KiB
URLTransfer SizeEst Savings
.mh9g3z0{bottom:0;box-sizing:content-box;padding:1rem;position:fixed;z-index:1001} …81.6 KiB69.7 KiB
21.4 KiB18.4 KiB

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

Max Potential First Input Delay 120 ms
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 24 user timings
JavaScript execution time 1.0 s
Avoid long main-thread tasks 8 long tasks found
Avoid non-composited animations 19 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 70 ms
Server Backend Latencies 150 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 0 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
93

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
as of December 31, 2022 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of July 31, 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of March 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of December 31, 2025 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y

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.

Failing Elements
More announcements main > div._1y3v4p30 > div._1y3v4p31 > h6.nbbs0e9

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.

Failing Elements
div.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi div.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi

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
SaaS/PaaS div.xg4goqb > div.xg4goqs > div.xg4goqx > button.xg4goqt
Digital publishing div.xg4goqb > div.xg4goqs > div.xg4goqx > button.xg4goqt
Digital publishing div.xg4goqb > div.xg4goqs > div.xg4goqx > button.xg4goqt
eCommerce div.xg4goqb > div.xg4goqs > div.xg4goqx > button.xg4goqt
Cookie Policy div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
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
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.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
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
Elements use only permitted ARIA attributes
ARIA toggle fields have accessible names
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
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
`[accesskey]` values are unique
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
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.

Deprecation / WarningSource
AttributionReporting
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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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.

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