Skip to content
https://prettier.io

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

62

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.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
prettier.io/assets/css/styles.3894af7f.css25.0 KiB413 ms
unpkg.com/@sandhose/prettier-animated-logo@1.0.3/dist/wide.css5.0 KiB771 ms

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.

URLResource SizeEst Savings
div#__docusaurus_skipToContent_fallback > section.syntaxSection_LwdY > a.syntaxLink_eb_h > img div#__docusaurus_skipToContent_fallback > section.syntaxSection_LwdY > a.syntaxLink_eb_h > img
prettier.io/images/syntaxfm/1.webp108.8 KiB104.8 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 10 ms 17.9 KiB
URLTransfer SizeEst Savings
prettier.io/assets/css/styles.3894af7f.css24.9 KiB17.9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 610 ms 105.6 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-T57CP1SG02144.4 KiB61.3 KiB
prettier.io/assets/js/main.977d5f67.js154.4 KiB44.2 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation950 ms
Other895 ms
Style & Layout420 ms
Rendering362 ms
Script Parsing & Compilation138 ms
Parse HTML & CSS37 ms
Garbage Collection8.5 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#__docusaurus_skipToContent_fallback > section.syntaxSection_LwdY > a.syntaxLink_eb_h > img div#__docusaurus_skipToContent_fallback > section.syntaxSection_LwdY > a.syntaxLink_eb_h > img
prettier.io/images/syntaxfm/1.webp
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_yaml.svg
div.theme-layout-navbar-left > a.navbar__brand > div.navbar__logo > img.themedComponent_mlkZ div.theme-layout-navbar-left > a.navbar__brand > div.navbar__logo > img.themedComponent_mlkZ
prettier.io/icon.png
div.navbar-sidebar__brand > a.navbar__brand > div.navbar__logo > img.themedComponent_mlkZ div.navbar-sidebar__brand > a.navbar__brand > div.navbar__logo > img.themedComponent_mlkZ
prettier.io/icon.png
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_md.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_babel.svg
div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img
prettier.io/images/state_of_js_grey.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_danger.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_react.svg
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_wip.svg
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_js.svg
div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img
prettier.io/images/github_grey.svg
div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > a > img
prettier.io/images/npm_grey.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_yarn.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/dropbox_grey.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_jest.svg
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_gql.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_webpack.svg
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_css.svg
div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh div.languageSectionGrid_govu > div > div.languageItem_pwFV > img.languageItemImage_ZVDh
prettier.io/images/languages/tools_html.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_facebook.svg
div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw div.container > div.userSectionGrid_HvHu > a.userItem_re7T > img.userItemImage_WNTw
prettier.io/images/users/used_by_storybook.svg

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

●Use efficient cache lifetimes
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 538 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 6 long tasks found
●Avoid non-composited animations 88 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 120 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 70 ms
○INP breakdown
○LCP request discovery
○Avoid large layout shifts
94

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See others div.container > div.userSectionButtonContainer_A7EE > div > a.button
Check Them Out div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button
See them all div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.plugin-pages html.plugin-pages

These items highlight common accessibility best practices.

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
See them all div.ecosystemGrid_S49d > div.ecosystemGridItem_CCpy > div > a.button
○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
●`[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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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

General

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
prettier.io/assets/js/main.977d5f67.js
●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
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
100

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.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback