Singapore · Singapore Completed: Apr 4, 2026 16:46 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 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
No Content-Security-Policy header found
147 HTTP requests — consider bundling or reducing
Cross-Origin-Embedder-Policy header is missing
Cross-Origin-Opener-Policy header is missing
[](https://beavercheck.com/results/709e86bf-1ff0-4522-97e4-28759dbcd933)<a href="https://beavercheck.com/results/709e86bf-1ff0-4522-97e4-28759dbcd933"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnuxt.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fnuxt.comThis 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.
4.09 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.88 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.47 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.
4.76 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.68 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.
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 |
|---|---|---|
| nuxt.com/_nuxt/entry.CBf5wA1z.css | 32.6 KiB | 301 ms |
| nuxt.com/_nuxt/index.DsfVClIb.css | 361 B | |
| nuxt.com/_nuxt/ModuleItem.C7BbMZUj.css | 607 B |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| raw.githubusercontent.com/nuxt/modules/main/icons/nuxt.svg | 300.0 s | 1.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.
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 |
|---|---|---|
| nuxt.com/_nuxt/Beu1Wg--.js | 339.4 KiB | 157.2 KiB |
| nuxt.com/_nuxt/C0X4-dmO.js | 59.8 KiB | 34.3 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.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| Unattributable | 3.0 s | 1.2 s | 0.0 ms |
| nuxt.com/_nuxt/Beu1Wg--.js | 2.7 s | 2.4 s | 6.5 ms |
| nuxt.com/ | 2.3 s | 567 ms | 3.5 ms |
| nuxt.com/_nuxt/CJYNbdVL.js | 187 ms | 86 ms | 0.3 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 |
|---|---|
| Script Evaluation | 4.3 s |
| Other | 2.5 s |
| Style & Layout | 1.1 s |
| Garbage Collection | 237 ms |
| Rendering | 213 ms |
| Parse HTML & CSS | 142 ms |
| Script Parsing & Compilation | 21 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Internal error. | Not actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
| URL | Transfer Size |
|---|---|
| nuxt.com/api/search.json | 946.6 KiB |
| nuxt.com/api/contributors | 506.1 KiB |
| nuxt.com/_nuxt/sqlite3.DBpDb1lf.wasm | 395.4 KiB |
| nuxt.com/_nuxt/Beu1Wg--.js | 339.6 KiB |
| nuxt.com/api/v1/modules | 103.1 KiB |
| nuxt.com/_nuxt/C0X4-dmO.js | 60.0 KiB |
| nuxt.com/_payload.json?25613cc7-3e8b-4ef7-99e7-cab5814ebabf | 52.3 KiB |
| nuxt.com/ | 36.7 KiB |
| ipx.nuxt.com/f_auto&s_80x80/gh_avatar/harlan-zw | 34.3 KiB |
| nuxt.com/_nuxt/entry.CBf5wA1z.css | 32.6 KiB |
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.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
| Failing Elements |
|---|
Minimal div.relative > div.flex > div.relative > button#reka-tabs-v-0-0-14-0-trigger-0 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
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.
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.
659 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
941 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
269 ms
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.
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.
2.67 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.
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.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| raw.githubusercontent.com/nuxt/modules/main/icons/nuxt.svg | 300.0 s | 1.2 KiB |
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 |
|---|---|
| nuxt.com/_nuxt/entry.CBf5wA1z.css | 32.6 KiB |
| nuxt.com/_nuxt/index.DsfVClIb.css | 361 B |
| nuxt.com/_nuxt/ModuleItem.C7BbMZUj.css | 609 B |
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.
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 |
|---|---|---|
| nuxt.com/_nuxt/Beu1Wg--.js | 339.4 KiB | 157.1 KiB |
| nuxt.com/_nuxt/C0X4-dmO.js | 59.8 KiB | 34.3 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
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.1 s |
| Other | 712 ms |
| Style & Layout | 313 ms |
| Rendering | 58 ms |
| Garbage Collection | 58 ms |
| Parse HTML & CSS | 24 ms |
| Script Parsing & Compilation | 7.5 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
| Failure reason | Failure type |
|---|---|
| Internal error. | Not actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
| Failing Elements |
|---|
Minimal div.relative > div.flex > div.relative > button#reka-tabs-v-0-0-14-0-trigger-0 |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
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.
| Failing Elements |
|---|
60K header.bg-default/75 > div.w-full > div.flex > a.rounded-md |
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.
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