Skip to content
Audit Complete

Results for https://pnpm.io

Visit site
United Stated United Stated · New York Completed: Apr 4, 2026 18:43 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

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

1 image(s) missing alt attribute

Accessibility › Alt Text Quality
4

2 image-only link(s) without alt text

Accessibility › Link & Button Quality
5

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fpnpm.io)](https://beavercheck.com/results/ad2eba47-d1c1-4dbd-9682-0f3050428f79)
<a href="https://beavercheck.com/results/ad2eba47-d1c1-4dbd-9682-0f3050428f79"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpnpm.io" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fpnpm.io

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.

54
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.
88
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.23 s

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

7.94 s

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

607 ms

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

0.013

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

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

10.52 s

Detailed Report

Audit breakdown by category with detailed findings.

54

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
pnpm.io/img/pnpm-light.svg86400.0 s297.7 KiB
pnpm.io/img/features/fast-pumpkin.png86400.0 s180.2 KiB
pnpm.io/assets/js/main.71aef162.js86400.0 s172.3 KiB
i.ytimg.com/vi/ZIKDJBrk56k/sddefault.jpg7200.0 s35.4 KiB
pnpm.io/assets/js/2592.fe592440.js86400.0 s58.2 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
pnpm.io/assets/css/styles.adcc4d7a.css86400.0 s33.0 KiB
buttons.github.io/buttons.js600.0 s7.0 KiB
pnpm.io/assets/js/runtime~main.39a68796.js86400.0 s10.0 KiB
pnpm.io/img/users/devowlio_min.svg86400.0 s9.6 KiB
pnpm.io/img/users/leniolabs.jpg86400.0 s6.3 KiB
pbs.twimg.com/profile_images/1765244446650568704/zgjmJiTX_400x400.jpg604800.0 s23.7 KiB
pbs.twimg.com/profile_images/1952025282560569345/aNNNtaXm_400x400.jpg604800.0 s20.8 KiB
pnpm.io/assets/js/c4f5d8e4.5c703de0.js86400.0 s3.6 KiB
/Y6jut5A-dhWRlv7W81kGxVFPtZGjZN97IhBP75uLnx2AVV7ZEJUUUxBK...86400.0 s3.0 KiB
pnpm.io/img/users/vitejs.svg86400.0 s1.9 KiB
pnpm.io/img/users/bit.svg86400.0 s1.6 KiB
pnpm.io/img/users/sanity.svg86400.0 s1.6 KiB
pnpm.io/img/users/workleap.svg86400.0 s1.3 KiB
pnpm.io/img/users/serpapi.svg86400.0 s1.3 KiB
pnpm.io/img/users/coderabbit_min.svg86400.0 s1.2 KiB
pnpm.io/img/users/uscreen.svg86400.0 s1.2 KiB
pnpm.io/img/users/nx.svg86400.0 s1.2 KiB
pnpm.io/img/users/cybozu_min.svg86400.0 s1.1 KiB
pnpm.io/img/users/replit_min.svg86400.0 s993 B
pnpm.io/img/users/discord_min.svg86400.0 s873 B
pnpm.io/img/pnpm-no-name-with-frame.svg86400.0 s778 B
pnpm.io/img/users/stackblitz_min.svg86400.0 s657 B
pnpm.io/homepage.js86400.0 s484 B
pnpm.io/assets/js/a7456010.69f33034.js86400.0 s328 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.

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.

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
Illustration of pnpm Fast feature. div.list_F7ag > div.item_MyzK > div.activeImg_GFFh > img.image_V7ep
pnpm.io/img/features/fast-pumpkin.png179.9 KiB148.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.jpg23.2 KiB21.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.jpg20.6 KiB19.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.png7.3 KiB4.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

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: 410 ms 22.5 KiB
URLTransfer SizeEst Savings
pnpm.io/assets/css/styles.adcc4d7a.css32.8 KiB22.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.

Estimated savings: 690 ms 190.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 reduce Javascript execution time.

URLTotal CPU TimeScript EvaluationScript Parse
pnpm.io/1.8 s29 ms2.7 ms
pnpm.io/assets/js/main.71aef162.js1.2 s900 ms71 ms
Unattributable618 ms101 ms0.0 ms
www.googletagmanager.com/gtag/js?id=G-RPD4HWL84Z&cx=c&gtm=4e6411249 ms191 ms51 ms
www.googletagmanager.com/gtag/js?id=UA-91385296-1188 ms139 ms42 ms
www.google-analytics.com/analytics.js120 ms49 ms6.5 ms
pnpm.io/assets/js/2592.fe592440.js111 ms74 ms19 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

CategoryTime Spent
Script Evaluation1.5 s
Other1.3 s
Style & Layout864 ms
Rendering391 ms
Script Parsing & Compilation200 ms
Parse HTML & CSS50 ms
Garbage Collection29 ms

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

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

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

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

Best Practices

User Experience

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

URLAspect 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.png80 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.

URLDisplayed sizeActual sizeExpected 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.png126 x 139126 x 139189 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.png92 x 9492 x 94138 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.png95 x 8995 x 89143 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.png114 x 64114 x 64171 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

SourceDescription
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]
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.

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
83

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

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.

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

93
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

877 ms

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

1.57 s

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

4 ms

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

0.005

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

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

1.78 s

Detailed Report

Audit breakdown by category with detailed findings.

93

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
pnpm.io/img/pnpm-light.svg86400.0 s297.7 KiB
pnpm.io/img/features/fast-pumpkin.png86400.0 s180.2 KiB
pnpm.io/assets/js/main.71aef162.js86400.0 s172.3 KiB
i.ytimg.com/vi/ZIKDJBrk56k/sddefault.jpg7200.0 s35.4 KiB
pnpm.io/assets/js/2592.fe592440.js86400.0 s58.1 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
pnpm.io/assets/css/styles.adcc4d7a.css86400.0 s32.9 KiB
buttons.github.io/buttons.js600.0 s7.0 KiB
pbs.twimg.com/profile_images/657699734673485824/0UIcBpjO_400x400.jpg604800.0 s45.3 KiB
pnpm.io/assets/js/runtime~main.39a68796.js86400.0 s10.0 KiB
pnpm.io/img/users/devowlio_min.svg86400.0 s9.6 KiB
pbs.twimg.com/profile_images/1963593369306750976/7gPWqEa8_400x400.jpg604800.0 s38.1 KiB
pbs.twimg.com/profile_images/1783856060249595904/8TfcCN0r_400x400.jpg604800.0 s32.7 KiB
pnpm.io/img/users/leniolabs.jpg86400.0 s6.3 KiB
pbs.twimg.com/profile_images/1765244446650568704/zgjmJiTX_400x400.jpg604800.0 s23.3 KiB
pnpm.io/img/users/next-auth_min.svg86400.0 s5.5 KiB
pbs.twimg.com/profile_images/1952025282560569345/aNNNtaXm_400x400.jpg604800.0 s20.8 KiB
pnpm.io/assets/js/c4f5d8e4.5c703de0.js86400.0 s3.6 KiB
/Y6jut5A-dhWRlv7W81kGxVFPtZGjZN97IhBP75uLnx2AVV7ZEJUUUxBK...86400.0 s3.0 KiB
pnpm.io/img/users/emberjs.svg86400.0 s2.1 KiB
pnpm.io/img/users/sveltekit_min.svg86400.0 s1.9 KiB
pnpm.io/img/users/vitejs.svg86400.0 s1.9 KiB
pnpm.io/img/users/bit.svg86400.0 s1.7 KiB
pnpm.io/img/users/sanity.svg86400.0 s1.5 KiB
pnpm.io/img/users/quasar_min.svg86400.0 s1.4 KiB
pnpm.io/img/users/workleap.svg86400.0 s1.3 KiB
pnpm.io/img/users/serpapi.svg86400.0 s1.3 KiB
pnpm.io/img/users/coderabbit_min.svg86400.0 s1.2 KiB
pnpm.io/img/users/uscreen.svg86400.0 s1.2 KiB
pnpm.io/img/users/nx.svg86400.0 s1.2 KiB
pnpm.io/img/users/cybozu_min.svg86400.0 s1.1 KiB
pnpm.io/img/users/element-plus_min.svg86400.0 s1.1 KiB
pnpm.io/img/users/mui.svg86400.0 s1.1 KiB
pnpm.io/img/users/turborepo_min.svg86400.0 s1.0 KiB
pnpm.io/img/users/replit_min.svg86400.0 s993 B
pnpm.io/img/users/vue-use_min.svg86400.0 s979 B
pnpm.io/img/users/slidev_min.svg86400.0 s975 B
pnpm.io/img/users/qwik_min.svg86400.0 s884 B
pnpm.io/img/users/verdaccio_min.svg86400.0 s870 B
pnpm.io/img/pnpm-no-name-with-frame.svg86400.0 s830 B
pnpm.io/img/users/discord_min.svg86400.0 s800 B
pnpm.io/img/users/nuxt_min.svg86400.0 s762 B
pnpm.io/img/users/stackblitz_min.svg86400.0 s663 B
pnpm.io/img/users/vue.svg86400.0 s591 B
pnpm.io/homepage.js86400.0 s484 B
pnpm.io/assets/js/a7456010.69f33034.js86400.0 s327 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:18.222 source:map[column:247564 line:1 type:source-location url:https://pnpm.io/assets/js/main.71aef162.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:0.932 source:map[column:20838 line:34 type:source-location url:https://pnpm.io/assets/js/main.71aef162.js urlProvider:network]] map[reflowTime:17.29 source:map[column:2491 line:32 type:source-location url:https://pnpm.io/assets/js/main.71aef162.js urlProvider:network]] map[reflowTime:4.043 source:map[type:text value:[unattributed]]]]

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

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.

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
Illustration of pnpm Fast feature. div.container_CeQ8 > div.grid_RKHx > div.visual_SL05 > img.image_V7ep
pnpm.io/img/features/fast-pumpkin.png179.9 KiB157.5 KiB
Itay Mendelawy div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz
pbs.twimg.com/profile_images/657699734673485824/0UIcBpjO_400x400.jpg45.1 KiB44.6 KiB
Cory House div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz
pbs.twimg.com/profile_images/1963593369306750976/7gPWqEa8_400x400.jpg37.6 KiB37.1 KiB
Guillermo Rauch div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz
pbs.twimg.com/profile_images/1783856060249595904/8TfcCN0r_400x400.jpg32.5 KiB32.0 KiB
Ben Vinegar div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz
pbs.twimg.com/profile_images/1765244446650568704/zgjmJiTX_400x400.jpg23.2 KiB22.7 KiB
Sayantan Ghosh div.authorGroup_dpLW > div.avatar_U_Zy > div.root_sUrf > img.image_c9mz
pbs.twimg.com/profile_images/1952025282560569345/aNNNtaXm_400x400.jpg20.6 KiB20.2 KiB
Leniolabs_ a.sponsorLink_ICpe > div.logoContainer_iSgy > div.root_sUrf > img.image_c9mz
pnpm.io/img/users/leniolabs.jpg6.1 KiB5.5 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.png7.3 KiB4.4 KiB

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

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: 80 ms 22.4 KiB
URLTransfer SizeEst Savings
pnpm.io/assets/css/styles.adcc4d7a.css32.8 KiB22.4 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.

Estimated savings: 40 ms 191.6 KiB

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

URL
Illustration of pnpm Fast feature. div.container_CeQ8 > div.grid_RKHx > div.visual_SL05 > 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

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

Time to Interactive 1.8 s
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,067 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 0.4 s
Minimizes main-thread work 1.2 s
Avoid long main-thread tasks 1 long task 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 60 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 3 layout shifts found
INP breakdown
LCP request discovery
90

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
Search div.navbarSearchContainer_actP > button.DocSearch > span.DocSearch-Button-Container > span.DocSearch-Button-Placeholder

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

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

Best Practices

User Experience

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

URLAspect 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.png80 x 40 (2.00)114 x 64 (1.78)

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

SourceDescription
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]
Failed to load resource: the server responded with a status of 404 ()
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.

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
Serves images with appropriate resolution
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
83

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

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.

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

Send Feedback