Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 58.5 KiB

URL	Transfer Size	Est Savings
cdn.ampproject.org/v0.mjs	62.2 KiB	33.7 KiB
cdn.ampproject.org/v0/amp-analytics-0.1.mjs	28.5 KiB	24.8 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s

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

●Time to Interactive 3.7 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 291 KiB

●User Timing marks and measures 8 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 4 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

ARIA

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

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

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

●`[role]` values are valid

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.


`head > link`
`head > link`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `rel=canonical`

○robots.txt is valid

○Image elements have `[alt]` attributes