Netherlands · Amsterdam Completed: Apr 16, 2026 17:04 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 70 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
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
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
4 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
7 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/e85d92d5-5f44-42e2-88fe-18852ef1b7c9)<a href="https://beavercheck.com/results/e85d92d5-5f44-42e2-88fe-18852ef1b7c9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnginx.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fnginx.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~22%.
Page loads in 3.7s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 1.2s over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
Page feels frozen for 3.5s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
7 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
2 broken link(s) on the page
+3% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€440 investment → €1,874/month returns + EUR 120,500,000 risk avoided
€440
6h · 5 findings
€1,874 /mo
~€22,483 / year
EUR 120,500,000
if kept compliant
€80 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
5.5 developer hours at €80/hr
Based on France rates (€80/hr)
Start here for the best return on investment
€10,041,667 / month at risk
~€120,500,007 / year if left unfixed
€120,500,000
+7 more
€0.61 /mo
8192.6 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
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.90 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.72 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.54 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.086
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.29 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.
20.30 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| mktg.tags.f5.com/main/prod/utag.sync.js | 300.0 s | 54.6 KiB |
| mktg.tags.f5.com/main/prod/utag.js | 300.0 s | 49.5 KiB |
| skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js | 600.0 s | 25.1 KiB |
| js.clrt.ai/11186.js | 43200.0 s | 24.3 KiB |
| /client/63iw3vww/0/stub.js?disableSelector=true&manuallyS... | 600.0 s | 11.6 KiB |
| /notice?domain=f5.com&c=teconsent&js=nj¬iceType=bb&tex... | 3600.0 s | 13.2 KiB |
| mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037 | 300.0 s | 7.5 KiB |
| de-de-63iw3vww.app.easyling.com/__inject/fix-meta.js | 86400.0 s | 1.1 KiB |
| tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=f5/main/202604022110&cb=1776358894018 | 300.0 s | 434 B |
| skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js | 600.0 s | 0 B |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| www.f5.com/css/prism.css | 1.0 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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| nginx.com/ | 816 ms |
| www.nginx.com/ | 991 ms |
| www.f5.com/products/nginx | 0.0 ms |
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.f5.com/products/nginx | 1.3 s |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl... | 1.9 s | 751 ms | 1.2 s |
| /_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42Z... | 1.3 s | 1.1 s | 41 ms |
| skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js | 1.1 s | 1.1 s | 47 ms |
| Unattributable | 1.1 s | 9.7 ms | 0.0 ms |
| www.f5.com/products/nginx | 695 ms | 29 ms | 66 ms |
| mktg.tags.f5.com/main/prod/utag.js | 503 ms | 354 ms | 28 ms |
| mktg.tags.f5.com/main/prod/utag.sync.js | 230 ms | 171 ms | 28 ms |
| consent.trustarc.com/asset/notice.js/v/v1.7-1729 | 220 ms | 161 ms | 24 ms |
| /notice?domain=f5.com&c=teconsent&js=nj¬iceType=bb&tex... | 118 ms | 82 ms | 6.3 ms |
| mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037 | 102 ms | 86 ms | 4.0 ms |
| /_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl... | 74 ms | 35 ms | 36 ms |
| /client/63iw3vww/0/stub.js?disableSelector=true&manuallyS... | 62 ms | 56 ms | 4.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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 4.0 s |
| Script Parsing & Compilation | 1.7 s |
| Other | 1.2 s |
| Style & Layout | 448 ms |
| Garbage Collection | 213 ms |
| Parse HTML & CSS | 157 ms |
| Rendering | 75 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl... | 1.5 MiB | 1.5 MiB |
| mktg.tags.f5.com/main/prod/utag.sync.js | 54.2 KiB | 41.6 KiB |
| /_next/static/chunks/8274-5040ec944eb9c798.js?dpl=dpl_42Z... | 37.8 KiB | 34.0 KiB |
| mktg.tags.f5.com/main/prod/utag.js | 49.0 KiB | 28.6 KiB |
| /_next/static/chunks/3564-1cb1b7fade2873c4.js?dpl=dpl_42Z... | 34.6 KiB | 27.9 KiB |
| consent.trustarc.com/asset/notice.js/v/v1.7-1729 | 36.0 KiB | 22.0 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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Featured div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
NGINX One
The core NGINX data plane software enhanced with SaaS-based tools for… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 WAF for NGINX and F5 DoS for NGINX
Comprehensive WAF security and denial-of-… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINXaaS for Azure
An Infrastructure-as-a-Service version of NGINX that enables… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 NGINXaaS for Google Cloud
Enhance app delivery and security in Google Cloud … div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Plus
An all-in-one, cloud-native load balancer, reverse proxy, web server… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 WAF for NGINX
A comprehensive WAF security solution designed to protect apps… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Instance Manager
Identify, secure, manage, and monitor all NGINX Open Sou… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Ingress Controller
Implements unified API gateways, load balancers, and i… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Gateway Fabric
Streamlines app, service, and API connectivity across hybr… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX One Console
Configure, secure, monitor and manage NGINX instances at scal… div.grid-cols-1 > span.w-full > div.h-full > a.group |
2024 TrustRadius Top Rated Award div.grid-cols-1 > span.w-full > div.h-full > a.group |
Contact us
Find out how F5 products and solutions can enable you to achieve you… div.flex > div.flex > div.w-full > a.group |
Explore packaging options
Explore the best options for your organization.
Explo… div.flex > div.flex > div.w-full > a.group |
Try NGINX One for Free
Try the NGINX ecosystem with data plane and traffic mana… div.flex > div.flex > div.w-full > a.group |
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
Performance issues directly impact user engagement and conversion rates.
| Description |
|---|
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser. |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
907 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.98 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
685 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.68 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.
4.26 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| mktg.tags.f5.com/main/prod/utag.sync.js | 300.0 s | 54.6 KiB |
| mktg.tags.f5.com/main/prod/utag.js | 300.0 s | 49.5 KiB |
| skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js | 600.0 s | 25.1 KiB |
| js.clrt.ai/11186.js | 43200.0 s | 24.2 KiB |
| /client/63iw3vww/0/stub.js?disableSelector=true&manuallyS... | 600.0 s | 11.6 KiB |
| /notice?domain=f5.com&c=teconsent&js=nj¬iceType=bb&tex... | 3600.0 s | 13.2 KiB |
| mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037 | 300.0 s | 7.5 KiB |
| de-de-63iw3vww.app.easyling.com/__inject/fix-meta.js | 86400.0 s | 1.1 KiB |
| tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=f5/main/202604022110&cb=1776358964741 | 300.0 s | 432 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
2024 TrustRadius Top Rated Award a.group > div.flex > div.flex > img.mb-1 | /images/k6fem79d/production/30ceeba432f569f1105e645d0caaf... | 82.4 KiB | 76.7 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| www.f5.com/css/prism.css | 912 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| nginx.com/ | 264 ms |
| www.nginx.com/ | 343 ms |
| www.f5.com/products/nginx | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl... | 1.5 MiB | 1.5 MiB |
| mktg.tags.f5.com/main/prod/utag.sync.js | 54.2 KiB | 41.6 KiB |
| /_next/static/chunks/8274-5040ec944eb9c798.js?dpl=dpl_42Z... | 37.8 KiB | 34.0 KiB |
| mktg.tags.f5.com/main/prod/utag.js | 49.0 KiB | 28.6 KiB |
| /_next/static/chunks/3564-1cb1b7fade2873c4.js?dpl=dpl_42Z... | 34.6 KiB | 27.9 KiB |
| consent.trustarc.com/asset/notice.js/v/v1.7-1729 | 36.0 KiB | 22.0 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /_next/static/chunks/549ca77c-9261eb57d3bef9bc.js?dpl=dpl... | 511 ms | 222 ms | 283 ms |
| skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js | 307 ms | 302 ms | 3.9 ms |
| /_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42Z... | 288 ms | 254 ms | 11 ms |
| Unattributable | 273 ms | 7.4 ms | 0.0 ms |
| www.f5.com/products/nginx | 262 ms | 6.9 ms | 18 ms |
| mktg.tags.f5.com/main/prod/utag.js | 119 ms | 94 ms | 11 ms |
| mktg.tags.f5.com/main/prod/utag.sync.js | 99 ms | 69 ms | 21 ms |
| /_next/static/chunks/main-app-d41d56f775a954bb.js?dpl=dpl... | 57 ms | 56 ms | 0.5 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.2 s |
| Script Parsing & Compilation | 429 ms |
| Other | 313 ms |
| Style & Layout | 146 ms |
| Garbage Collection | 50 ms |
| Rendering | 42 ms |
| Parse HTML & CSS | 31 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Featured div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary |
These are opportunities to improve keyboard navigation in your application.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Open search div.container > div.ml-auto > div.relative > button.inline-flex |
These items highlight common accessibility best practices.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
NGINX One
The core NGINX data plane software enhanced with SaaS-based tools for… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 WAF for NGINX and F5 DoS for NGINX
Comprehensive WAF security and denial-of-… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINXaaS for Azure
An Infrastructure-as-a-Service version of NGINX that enables… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 NGINXaaS for Google Cloud
Enhance app delivery and security in Google Cloud … div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Plus
An all-in-one, cloud-native load balancer, reverse proxy, web server… div.grid-cols-1 > span.w-full > div.h-full > a.group |
F5 WAF for NGINX
A comprehensive WAF security solution designed to protect apps… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Instance Manager
Identify, secure, manage, and monitor all NGINX Open Sou… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Ingress Controller
Implements unified API gateways, load balancers, and i… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX Gateway Fabric
Streamlines app, service, and API connectivity across hybr… div.grid-cols-1 > span.w-full > div.h-full > a.group |
NGINX One Console
Configure, secure, monitor and manage NGINX instances at scal… div.grid-cols-1 > span.w-full > div.h-full > a.group |
2024 TrustRadius Top Rated Award div.grid-cols-1 > span.w-full > div.h-full > a.group |
Contact us
Find out how F5 products and solutions can enable you to achieve you… div.flex > div.flex > div.w-full > a.group |
Explore packaging options
Explore the best options for your organization.
Explo… div.flex > div.flex > div.w-full > a.group |
Try NGINX One for Free
Try the NGINX ecosystem with data plane and traffic mana… div.flex > div.flex > div.w-full > a.group |
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
Performance issues directly impact user engagement and conversion rates.
| Description |
|---|
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser. |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback