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.

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
pnpm.io/img/pnpm-light.svg	86400.0 s	297.7 KiB
pnpm.io/img/features/fast-pumpkin.png	86400.0 s	180.2 KiB
pnpm.io/assets/js/main.71aef162.js	86400.0 s	172.3 KiB
i.ytimg.com/vi/ZIKDJBrk56k/sddefault.jpg	7200.0 s	35.4 KiB
pnpm.io/assets/js/2592.fe592440.js	86400.0 s	58.2 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
pnpm.io/assets/css/styles.adcc4d7a.css	86400.0 s	33.0 KiB
buttons.github.io/buttons.js	600.0 s	7.0 KiB
pnpm.io/assets/js/runtime~main.39a68796.js	86400.0 s	10.0 KiB
pnpm.io/img/users/devowlio_min.svg	86400.0 s	9.6 KiB
pnpm.io/img/users/leniolabs.jpg	86400.0 s	6.3 KiB
pbs.twimg.com/profile_images/1765244446650568704/zgjmJiTX_400x400.jpg	604800.0 s	23.7 KiB
pbs.twimg.com/profile_images/1952025282560569345/aNNNtaXm_400x400.jpg	604800.0 s	20.8 KiB
pnpm.io/assets/js/c4f5d8e4.5c703de0.js	86400.0 s	3.6 KiB
/Y6jut5A-dhWRlv7W81kGxVFPtZGjZN97IhBP75uLnx2AVV7ZEJUUUxBK...	86400.0 s	3.0 KiB
pnpm.io/img/users/vitejs.svg	86400.0 s	1.9 KiB
pnpm.io/img/users/bit.svg	86400.0 s	1.6 KiB
pnpm.io/img/users/sanity.svg	86400.0 s	1.6 KiB
pnpm.io/img/users/workleap.svg	86400.0 s	1.3 KiB
pnpm.io/img/users/serpapi.svg	86400.0 s	1.3 KiB
pnpm.io/img/users/coderabbit_min.svg	86400.0 s	1.2 KiB
pnpm.io/img/users/uscreen.svg	86400.0 s	1.2 KiB
pnpm.io/img/users/nx.svg	86400.0 s	1.2 KiB
pnpm.io/img/users/cybozu_min.svg	86400.0 s	1.1 KiB
pnpm.io/img/users/replit_min.svg	86400.0 s	993 B
pnpm.io/img/users/discord_min.svg	86400.0 s	873 B
pnpm.io/img/pnpm-no-name-with-frame.svg	86400.0 s	778 B
pnpm.io/img/users/stackblitz_min.svg	86400.0 s	657 B
pnpm.io/homepage.js	86400.0 s	484 B
pnpm.io/assets/js/a7456010.69f33034.js	86400.0 s	328 B

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.

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

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

title: Preconnected origins

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

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
buttons.github.io/buttons.js	7.0 KiB	754 ms
fonts.googleapis.com/css2?family=Inter:wght@300;400;700&display=swap	821 B	785 ms
fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800&display=swap	1.3 KiB	153 ms
pnpm.io/homepage.js	484 B
pnpm.io/assets/css/styles.adcc4d7a.css	33.0 KiB	454 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	15 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.

	URL	Resource Size	Est Savings
Illustration of pnpm Fast feature. `div.list_F7ag > div.item_MyzK > div.activeImg_GFFh > img.image_V7ep`	pnpm.io/img/features/fast-pumpkin.png	179.9 KiB	148.4 KiB
Ben Vinegar `div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz`	pbs.twimg.com/profile_images/1765244446650568704/zgjmJiTX_400x400.jpg	23.2 KiB	21.9 KiB
Sayantan Ghosh `div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz`	pbs.twimg.com/profile_images/1952025282560569345/aNNNtaXm_400x400.jpg	20.6 KiB	19.2 KiB
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/pumpkin-4.png	7.3 KiB	4.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 410 ms 22.5 KiB

URL	Transfer Size	Est Savings
pnpm.io/assets/css/styles.adcc4d7a.css	32.8 KiB	22.5 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: 690 ms 190.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-RPD4HWL84Z&cx=c&gtm=4e6411	149.2 KiB	64.5 KiB
www.googletagmanager.com/gtag/js?id=UA-91385296-1	114.9 KiB	61.7 KiB
pnpm.io/assets/js/main.71aef162.js	172.2 KiB	42.2 KiB
pnpm.io/assets/js/2592.fe592440.js	58.0 KiB	21.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
pnpm.io/	1.8 s	29 ms	2.7 ms
pnpm.io/assets/js/main.71aef162.js	1.2 s	900 ms	71 ms
Unattributable	618 ms	101 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-RPD4HWL84Z&cx=c&gtm=4e6411	249 ms	191 ms	51 ms
www.googletagmanager.com/gtag/js?id=UA-91385296-1	188 ms	139 ms	42 ms
www.google-analytics.com/analytics.js	120 ms	49 ms	6.5 ms
pnpm.io/assets/js/2592.fe592440.js	111 ms	74 ms	19 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.5 s
Other	1.3 s
Style & Layout	864 ms
Rendering	391 ms
Script Parsing & Compilation	200 ms
Parse HTML & CSS	50 ms
Garbage Collection	29 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
Illustration of pnpm Fast feature. `div.list_F7ag > div.item_MyzK > div.activeImg_GFFh > img.image_V7ep`	pnpm.io/img/features/fast-pumpkin.png
div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo `div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo`	pnpm.io/img/pnpm-light.svg
div.theme-layout-navbar-left > a.navbar__brand > div.navbar__logo > img.themedComponent_JL_G `div.theme-layout-navbar-left > a.navbar__brand > div.navbar__logo > img.themedComponent_JL_G`	pnpm.io/img/pnpm-no-name-with-frame.svg
div.navbar-sidebar__brand > a.navbar__brand > div.navbar__logo > img.themedComponent_JL_G `div.navbar-sidebar__brand > a.navbar__brand > div.navbar__logo > img.themedComponent_JL_G`	pnpm.io/img/pnpm-no-name-with-frame.svg

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,656 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 70 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

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.

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
Fast `div.list_F7ag > div.item_MyzK > div.itemHeader_lCxT > h3.heading_qCKr`
Feross `div.footer_E1OH > div.authorGroup_dpLW > div.authorInfo_O_Ql > h6.heading_qCKr`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo `div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo`

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

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

○Input buttons have discernible text.

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

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

○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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/cloud-1.png	80 x 40 (2.00)	114 x 64 (1.78)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/pumpkin-4.png	126 x 139	126 x 139	189 x 209
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/pumpkin-3.png	92 x 94	92 x 94	138 x 141
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/pumpkin-2.png	95 x 89	95 x 89	143 x 134
div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl `div.container_CeQ8 > div.container_vL3I > div.decorations_IK6D > img.decoration_WPAl`	static.bit.dev/pnpm-io/cloud-1.png	114 x 64	114 x 64	171 x 96

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source Description

Source	Description
pnpm.io/assets/js/main.71aef162.js line 26, col 2805	Docusaurus React Root onRecoverableError: Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rj (https://pnpm.io/assets/js/main.71aef162.js:1:82286) at iY (https://pnpm.io/assets/js/main.71aef162.js:1:132328) at lk (https://pnpm.io/assets/js/main.71aef162.js:1:163415) at https://pnpm.io/assets/js/main.71aef162.js:1:158536 at lc (https://pnpm.io/assets/js/main.71aef162.js:1:158637) at lZ (https://pnpm.io/assets/js/main.71aef162.js:1:181776) at MessagePort.L (https://pnpm.io/assets/js/main.71aef162.js:1:247803) [object Object]
pbs.twimg.com/profile_images/1499215593089556483/VtxQLy6L_400x400.jpg	`Failed to load resource: the server responded with a status of 404 ()`

pnpm.io/assets/js/main.71aef162.js line 26, col 2805

Docusaurus React Root onRecoverableError: Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at rj (https://pnpm.io/assets/js/main.71aef162.js:1:82286)
    at iY (https://pnpm.io/assets/js/main.71aef162.js:1:132328)
    at lk (https://pnpm.io/assets/js/main.71aef162.js:1:163415)
    at https://pnpm.io/assets/js/main.71aef162.js:1:158536
    at lc (https://pnpm.io/assets/js/main.71aef162.js:1:158637)
    at lZ (https://pnpm.io/assets/js/main.71aef162.js:1:181776)
    at MessagePort.L (https://pnpm.io/assets/js/main.71aef162.js:1:247803) [object Object]

pbs.twimg.com/profile_images/1499215593089556483/VtxQLy6L_400x400.jpg

Failed to load resource: the server responded with a status of 404 ()

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
pnpm.io/assets/js/main.71aef162.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

●Page has the HTML doctype

●Properly defines charset

●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

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
next.js `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
n8n `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Material UI `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Vite `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Nuxt `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Vue `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Astro `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Prisma `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Novu `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Slidev `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Turborepo `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Quasar Framework `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Element Plus `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
NextAuth.js `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Ember.js `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Qwik `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
VueUse `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
SvelteKit `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Verdaccio `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Vercel `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`
Nx `section.sectionLayout_kGTe > div.container_CeQ8 > div.grid_Regn > a.link_HZAU`

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo `div.container > div.footer__bottom > div.margin-bottom--sm > img.footer__logo`

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid