Skip to content
Audit Complete

Results for https://www.mathworks.com

Visit site
United Stated United Stated · New York Completed: Apr 7, 2026 20:36 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 69 / 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

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

No <main> landmark found

Accessibility › Landmark Structure
5

No favicon or icon links detected

Accessibility › Favicon & Branding
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mathworks.com)](https://beavercheck.com/results/cd626ec8-76b9-890d-9726-18d98088b21e)
<a href="https://beavercheck.com/results/cd626ec8-76b9-890d-9726-18d98088b21e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mathworks.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.mathworks.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.

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

4.35 s

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

16.34 s

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

1.49 s

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

0.000

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

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

16.54 s

Detailed Report

Audit breakdown by category with detailed findings.

34

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.

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

lhId: page-0-DIV
nodeLabel: MATLAB and Simulink for Engineered Systems Accelerating how engineers design, d…
path: 1,HTML,1,BODY,3,DIV,0,MAIN,0,SECTION,0,DIV,3,DIV,1,DIV,2,DIV,0,DIV,0,DIV,0,DIV
selector: div > div.eventPromotion > div.cqBand > div.band
snippet: <div class="band add_background_color_mediumgray section_upsize add_min_height_150_xs…" style="background-image: url(&quot;https://www.mathworks.com/_jcr_content/mainParsys/e…&quot;);">

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...81.4 KiB69.1 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...62.9 KiB53.4 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...51.2 KiB43.5 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy/mainParsys/column...47.8 KiB41.7 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/targetcontainer/targetContent/ba...24.6 KiB18.0 KiB

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.

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: 300 ms 42.5 KiB

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 Evaluation3.4 s
Other849 ms
Script Parsing & Compilation624 ms
Style & Layout304 ms
Parse HTML & CSS95 ms
Garbage Collection88 ms
Rendering31 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 a sub frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 0.0 ms 5.3 KiB
URLTransfer SizeEst Savings
/etc.clientlibs/mathworks/clientlibs/customer-ui/componen...29.8 KiB5.3 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
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
Avoids enormous network payloads Total size was 2,344 KiB
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 210 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 110 ms
INP breakdown
User Timing marks and measures
Avoid non-composited animations
Avoid large layout shifts
95

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.

Failing Elements
Back to top body.site_lang_en > a#go-top

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.

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
MATLAB and Simulink Events div.panelParsys > div.text > div.mw-text > h4.add_margin_10

These are opportunities to improve keyboard navigation in your application.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements 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.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
AttributionReporting

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

405 ms

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

1.40 s

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

240 ms

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

0.086

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

1.03 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.20 s

Detailed Report

Audit breakdown by category with detailed findings.

85

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.

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

lhId: page-0-DIV
nodeLabel:   MATLAB and Simulink for Engineered Systems Accelerating how engineers design…
path: 1,HTML,1,BODY,3,DIV,0,MAIN,0,SECTION,0,DIV,3,DIV,1,DIV,2,DIV,0,DIV,0,DIV,0,DIV
selector: div > div.eventPromotion > div.cqBand > div.band
snippet: <div class="band add_background_color_mediumgray section_upsize add_min_height_150_xs…" style="background-image: url(&quot;https://www.mathworks.com/_jcr_content/mainParsys/e…&quot;);">

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.

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.cqImage > div.figure_container > figure.figure > img.responsiveImage div.cqImage > div.figure_container > figure.figure > img.responsiveImage
/_jcr_content/mainParsys/band_1857486895_copy/mainParsys/...409.9 KiB376.7 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...81.4 KiB71.2 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...62.9 KiB55.0 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy_73681/mainParsys/...51.2 KiB44.8 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/band_copy_copy/mainParsys/column...47.8 KiB36.7 KiB
div.cqPanel > div.panel > div.panel-heading > img.responsiveImage div.cqPanel > div.panel > div.panel-heading > img.responsiveImage
/_jcr_content/mainParsys/targetcontainer/targetContent/ba...24.6 KiB20.5 KiB

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

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.

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: 40 ms 41.0 KiB

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 a sub frame.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Estimated savings: 0.0 ms 5.3 KiB
URLTransfer SizeEst Savings
/etc.clientlibs/mathworks/clientlibs/customer-ui/componen...29.8 KiB5.3 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
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
JavaScript execution time 0.7 s
Minimizes main-thread work 1.5 s
Avoid long main-thread tasks 5 long tasks found
Avoid non-composited animations 3 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 110 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 40 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
User Timing marks and measures
95

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.

Failing Elements
Back to top body.site_lang_en > a#go-top

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.

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
MATLAB and Simulink Events div.panelParsys > div.text > div.mw-text > h4.add_margin_10

These are opportunities to improve keyboard navigation in your application.

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.
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.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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 the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
AttributionReporting

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback