United Stated · Santa Clara Completed: Apr 7, 2026 20:36 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
HSTS header is missing
No Content-Security-Policy header found
4 button(s) with no accessible text
Cross-Origin-Embedder-Policy header is missing
[](https://beavercheck.com/results/d72d6cb5-9cdf-a84c-81a9-2e08fbc4e861)<a href="https://beavercheck.com/results/d72d6cb5-9cdf-a84c-81a9-2e08fbc4e861"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhuggingface.co" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fhuggingface.coThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
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.
2.25 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.78 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.21 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.33 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.
14.30 s
Audit breakdown by category with detailed findings.
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 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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Hugging Face models main.flex > div.container > div.relative > img.pointer-events-none | huggingface.co/front/assets/homepage/models-mobile.webp | 61.3 KiB | 56.1 KiB |
Google's profile picture div.grid > article.overview-card-wrapper > a.flex > img.mr-3 | /v1/production/uploads/5dd96eb166059660ed1ee413/WtA3YYite... | 6.9 KiB | 6.8 KiB |
Grammarly's profile picture div.grid > article.overview-card-wrapper > a.flex > img.mr-3 | /v1/production/uploads/60985a0547dc3dbf8a976607/rRv-Tjtvh... | 5.5 KiB | 5.4 KiB |
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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| /css2?family=Source+Sans+Pro:ital,wght@0,200;0,300;0,400;... | 1.3 KiB | 825 ms |
| fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;600;700&display=swap | 1.1 KiB | 167 ms |
| huggingface.co/front/build/kube-83b7db8/style.css | 77.3 KiB | 1.2 s |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| js.stripe.com/v3/ | 120.0 s | 225.1 KiB |
| m.stripe.network/out-4.5.45.js | 300.0 s | 16.5 KiB |
| huggingface.co/js/script.js | 60.0 s | 3.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| huggingface.co/ | 2.3 s | 23 ms | 4.6 ms |
| Unattributable | 1.9 s | 228 ms | 0.0 ms |
| de5282c3ca0c.edge.sdk.awswaf.com/de5282c3ca0c/526cf06acb0d/challenge.js | 1.5 s | 1.2 s | 173 ms |
| js.stripe.com/v3/ | 412 ms | 276 ms | 134 ms |
| huggingface.co/front/build/kube-83b7db8/index-client-Dv_OgQZo.js | 208 ms | 151 ms | 1.0 ms |
| huggingface.co/front/build/kube-83b7db8/style.css | 115 ms | 0.0 ms | 0.0 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
| Category | Time Spent |
|---|---|
| Other | 2.3 s |
| Script Evaluation | 1.9 s |
| Style & Layout | 1.5 s |
| Rendering | 339 ms |
| Script Parsing & Compilation | 326 ms |
| Parse HTML & CSS | 148 ms |
| Garbage Collection | 90 ms |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| de5282c3ca0c.edge.sdk.awswaf.com/de5282c3ca0c/526cf06acb0d/challenge.js | 500.8 KiB | 261.1 KiB |
| js.stripe.com/v3/ | 193.1 KiB | 140.7 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Hugging Face models main.flex > div.container > div.relative > img.pointer-events-none | huggingface.co/front/assets/homepage/models-mobile.webp |
Younes Belkada Hugging Face profile div.container > div.mx-auto > div.shadow-xs > img.ml-auto | huggingface.co/front/assets/homepage/younes.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| Failing Elements |
|---|
div.w-full > div.flex > div.flex > button.relative div.w-full > div.flex > div.flex > button.relative |
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden |
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
Starting at $0.60/hour for GPU div.shadow-xs > div.px-5 > div.flex > p.text-smd |
These are opportunities to improve the legibility of your content.
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 |
|---|
google/gemma-4-31B-it a.flex > div.w-full > header.flex > h4.text-md |
OmniVoice div.text-white > div.flex > div.mb-0.5 > h4.overflow-hidden |
ianncity/KIMI-K2.5-1000000x a.flex > div.w-full > header.flex > h4.text-md |
Ai2 a.flex > div.overflow-hidden > div.flex > h4.truncate |
Transformers div.container > div.relative > a.relative > h4.leading-tight! |
These are opportunities to improve keyboard navigation in your application.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
634 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
905 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
116 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.018
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
777 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.11 s
Audit breakdown by category with detailed findings.
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 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.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Hugging Face models main.flex > div.container > div.relative > img.pointer-events-none | huggingface.co/front/assets/homepage/models.webp | 115.3 KiB | 92.6 KiB |
Google's profile picture div.grid > article.overview-card-wrapper > a.flex > img.mr-3 | /v1/production/uploads/5dd96eb166059660ed1ee413/WtA3YYite... | 6.9 KiB | 6.8 KiB |
Grammarly's profile picture div.grid > article.overview-card-wrapper > a.flex > img.mr-3 | /v1/production/uploads/60985a0547dc3dbf8a976607/rRv-Tjtvh... | 5.5 KiB | 5.4 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
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.
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.
| URL | Transfer Size | Duration |
|---|---|---|
| /css2?family=Source+Sans+Pro:ital,wght@0,200;0,300;0,400;... | 1.6 KiB | 293 ms |
| fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;600;700&display=swap | 774 B | 59 ms |
| huggingface.co/front/build/kube-83b7db8/style.css | 77.3 KiB | 231 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| js.stripe.com/v3/ | 120.0 s | 224.7 KiB |
| m.stripe.network/out-4.5.45.js | 300.0 s | 16.5 KiB |
| huggingface.co/js/script.js | 60.0 s | 3.2 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.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| de5282c3ca0c.edge.sdk.awswaf.com/de5282c3ca0c/526cf06acb0d/challenge.js | 500.9 KiB | 261.1 KiB |
| js.stripe.com/v3/ | 224.3 KiB | 163.4 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| URL | |
|---|---|
Younes Belkada Hugging Face profile div.container > div.mx-auto > div.shadow-xs > img.ml-auto | huggingface.co/front/assets/homepage/younes.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
| Failing Elements |
|---|
ul.flex > li > div.relative > button.px-2 ul.flex > li > div.relative > button.px-2 |
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden |
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
| Failing Elements |
|---|
NEW ul.flex > li.hover:text-blue-800 > a.group > span.ml-1.5 |
Starting at $0.60/hour for GPU div.shadow-xs > div.px-5 > div.flex > p.text-smd |
These are opportunities to improve the legibility of your content.
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 |
|---|
google/gemma-4-31B-it a.flex > div.w-full > header.flex > h4.text-md |
OmniVoice div.text-white > div.flex > div.mb-0.5 > h4.overflow-hidden |
ianncity/KIMI-K2.5-1000000x a.flex > div.w-full > header.flex > h4.text-md |
Ai2 a.flex > div.overflow-hidden > div.flex > h4.truncate |
Transformers div.container > div.relative > a.relative > h4.leading-tight! |
These are opportunities to improve keyboard navigation in your application.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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.
Send Feedback