Skip to content
Audit Complete

Results for https://f5.com

Visit site
Corporate / Enterprise · estimated Tracking: leads
Singapore Singapore · Singapore Completed: Apr 16, 2026 17:08 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 15.5s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

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.

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.

How the composite score is calculated

How you compare

Apple sites average 73
At average
Better than 26% of Apple sites See full Apple benchmark →
Google Search Console sites average 73
At average
Better than 31% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

4 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
4

7 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ff5.com)](https://beavercheck.com/results/71790f7c-b931-4888-b1e4-b6b0aef87a95)
<a href="https://beavercheck.com/results/71790f7c-b931-4888-b1e4-b6b0aef87a95"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ff5.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ff5.com

This badge auto-updates with your latest scan result.

What fixing these means

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.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 4 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (2)

Page takes 15.5s to load

+12% bounce

Users abandon at ~3s — you're 13.0s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 4.0s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning 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% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Navigation (3)

7 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-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% bounce

Keyboard 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

8 broken link(s) on the page

+5% bounce

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

Return on Investment

$550 investment → $0.89/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

$550

6h · 5 findings

Monthly returns

$0.89 /mo

~$11 / year

  • Bandwidth savings $0.89

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$100 — 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.

Full methodology & sources

Estimated Remediation Cost

$550

5.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,511 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$0.89 /mo

11137.8 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves $0.89/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

2.89 s

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

15.51 s

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

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

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

30.67 s

Detailed Report

Audit breakdown by category with detailed findings.

36

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
mktg.tags.f5.com/main/prod/utag.sync.js300.0 s54.6 KiB
mktg.tags.f5.com/main/prod/utag.js300.0 s49.5 KiB
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s25.1 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.3 KiB
js.clrt.ai/11186.js43200.0 s24.1 KiB
/client/63iw3vww/0/stub.js?disableSelector=true&manuallyS...600.0 s11.6 KiB
cdn.bizible.com/scripts/bizible.js86400.0 s25.2 KiB
cdn.speedcurve.com/js/lux.js?id=899484253600.0 s11.8 KiB
static.cloud.coveo.com/coveo.analytics.js/2/coveoua.js86400.0 s21.7 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037300.0 s7.2 KiB
/notice?domain=f5.com&c=teconsent&js=nj&noticeType=bb&tex...3600.0 s6.3 KiB
mktg.tags.f5.com/main/prod/utag.294.js?utv=ut4.48.202604022110300.0 s4.8 KiB
mktg.tags.f5.com/main/prod/utag.273.js?utv=ut4.48.202604022110300.0 s4.1 KiB
mktg.tags.f5.com/main/prod/utag.383.js?utv=ut4.48.202604022110300.0 s4.0 KiB
mktg.tags.f5.com/main/prod/utag.235.js?utv=ut4.48.202604022110300.0 s3.3 KiB
mktg.tags.f5.com/main/prod/utag.117.js?utv=ut4.48.202604022110300.0 s3.3 KiB
scripts.demandbase.com/adobeanalytics/pscSDsz4.min.js0.0 ms3.0 KiB
mktg.tags.f5.com/main/prod/utag.116.js?utv=ut4.48.202604022110300.0 s3.1 KiB
mktg.tags.f5.com/main/prod/utag.110.js?utv=ut4.48.202604022110300.0 s3.1 KiB
mktg.tags.f5.com/main/prod/utag.118.js?utv=ut4.48.202604022110300.0 s3.0 KiB
mktg.tags.f5.com/main/prod/utag.111.js?utv=ut4.48.202604022110300.0 s3.0 KiB
mktg.tags.f5.com/main/prod/utag.272.js?utv=ut4.48.202604022110300.0 s2.8 KiB
mktg.tags.f5.com/main/prod/utag.283.js?utv=ut4.48.202604022110300.0 s2.1 KiB
mktg.tags.f5.com/main/prod/utag.303.js?utv=ut4.48.202604022110300.0 s2.1 KiB
mktg.tags.f5.com/main/prod/utag.280.js?utv=ut4.48.202604022110300.0 s2.0 KiB
mktg.tags.f5.com/main/prod/utag.320.js?utv=ut4.48.202604022110300.0 s2.0 KiB
mktg.tags.f5.com/main/prod/utag.35.js?utv=ut4.48.202604022110300.0 s1.9 KiB
mktg.tags.f5.com/main/prod/utag.243.js?utv=ut4.48.202604022110300.0 s1.8 KiB
mktg.tags.f5.com/main/prod/utag.230.js?utv=ut4.48.202604022110300.0 s1.3 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
mktg.tags.f5.com/main/prod/utag.4.js?utv=ut4.48.202604022110300.0 s1.2 KiB
munchkin.marketo.net/munchkin-beta.js0.0 ms1.1 KiB
js.adsrvr.org/universal_pixel.js0.0 ms957 B
de-de-63iw3vww.app.easyling.com/__inject/fix-meta.js86400.0 s1.1 KiB
tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=f5/main/202604022110&cb=1776359109444300.0 s432 B
/v1/cs?url=https%3A%2F%2Fwww.f5.com%2F&ref=&cb_name=usona...0.0 ms277 B
/collect?v=2&fmt=js&pid=8162&time=1776359114155&li_adsId=...0.0 ms273 B
/lux/?v=4.0402&id=89948425&sid=177635911406972377&uid=177...0.0 ms99 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:32.008 source:map[column:55085 line:1 type:source-location url:https://www.f5.com/_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C 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:12.233 source:map[column:88235 line:0 type:source-location url:https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C urlProvider:network]] map[reflowTime:10.794 source:map[column:6670 line:0 type:source-location url:https://www.f5.com/_next/static/chunks/6210-48cf1d7259058222.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C urlProvider:network]] map[reflowTime:0.55 source:map[column:40635 line:0 type:source-location url:https://www.f5.com/_next/static/chunks/app/layout-27fdefae08c5eb87.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C urlProvider:network]] map[reflowTime:4.503 source:map[column:4110 line:0 type:source-location url:https://www.f5.com/_next/static/chunks/5005-fb93f13cb032b960.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C urlProvider:network]] map[reflowTime:3.928 source:map[column:15997 line:0 type:source-location url:https://www.f5.com/_next/static/chunks/5005-fb93f13cb032b960.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C urlProvider:network]] map[reflowTime:1.54 source:map[column:5 line:16 type:source-location url:https://consent.trustarc.com/asset/notice.js/v/v1.7-1729 urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Validated S3 performance for AI infrastructure and data delivery
path: 1,HTML,1,BODY,42,SECTION,2,DIV,0,DIV,0,DIV,0,DIV,0,SPAN,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.flex > div.relative > div.relative > img.object-cover
snippet: <img alt="Validated S3 performance for AI infrastructure and data delivery" loading="lazy" decoding="async" data-nimg="fill" class="object-cover object-center" src="https://cdn.studio.f5.com/images/k6fem79d/production/bf7a6a95548fe803940f1…" style="position: absolute; height: 100%; width: 100%; inset: 0px;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
GigaOm Radar App & API Security p.d-body-base > div.mx-auto > div > img.inline-block
/_next/image?url=https%3A%2F%2Fcdn.studio.f5.com%2Fimages...49.4 KiB30.6 KiB
From sprawl to strategy: how a platform approach secures and simplifies IT div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/d6b332085e60cb3fd9ac3830b0130...43.1 KiB28.9 KiB
30 years at the application layer div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/86157282e1ac8ccd975c0e1f09832...29.6 KiB12.3 KiB
Validated S3 performance for AI infrastructure and data delivery div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/bf7a6a95548fe803940f1e4d9f82c...8.2 KiB5.5 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 784 ms
URLTime Spent
f5.com/784 ms
www.f5.com/0.0 ms

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation9.3 s
Other4.8 s
Script Parsing & Compilation1.8 s
Rendering964 ms
Style & Layout954 ms
Garbage Collection291 ms
Parse HTML & CSS96 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB
URLTransfer SizeEst Savings
scripts.demandbase.com/adobeanalytics/pscSDsz4.min.js8.4 KiB2.8 KiB

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

Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Reduce unused CSS
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 250 ms
Server Backend Latencies 340 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 50 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
97

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PLATFORM SPOTLIGHT: DEPLOYMENT div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
REPORT Validated S3 performance for AI infrastructure and data delivery div.flex > span.w-full > div.h-full > a.group
WEBINAR From sprawl to strategy: how a platform approach secures and simplifies… div.flex > span.w-full > div.h-full > a.group
BLOG 30 years at the application layer div.flex > span.w-full > div.h-full > a.group
GOVERNMENT SA Power Networks enhances OT cloud security with F5 NGINXaaS South … div.flex > span.w-full > div.h-full > a.group
RETAIL Sheetz fuels secure business growth with F5 Rising cybersecurity inciden… div.flex > span.w-full > div.h-full > a.group
BANKING & FINANCIAL SERVICES TOM Bank scales securely with F5 hybrid environmen… div.flex > span.w-full > div.h-full > a.group
Start a free trial Experience F5 in action by testing our products in your pre-… div.grid-cols-1 > span.w-full > div.h-full > a.group
Contact us We can assess your needs and connect you to with the right cloud pro… div.grid-cols-1 > span.w-full > div.h-full > a.group
MyF5 support Get support and manage your software subscriptions and BIG-IP VE r… div.grid-cols-1 > span.w-full > div.h-full > a.group
Find a reseller We're dedicated to building partnerships that drive your busine… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Blog Explore the F5 blog for insights, trends, and expert advice on digital … div.grid-cols-1 > span.w-full > div.h-full > a.group
Office of the CTO Strategic insights on the future of app services, the evoluti… div.grid-cols-1 > span.w-full > div.h-full > a.group
Newsroom The latest news, awards, recognition, and announcements about F5 and N… div.grid-cols-1 > span.w-full > div.h-full > a.group
Events calendar Discover events to connect, learn, and network—online or in-per… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 DevCentral A community of F5 experts collaborating to solve challenges, shar… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Labs Get the who, what, when, and what’s next in cyberattacks to inform your… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Education Develop knowledge and hands-on skills to deploy, configure, and ma… div.grid-cols-1 > span.w-full > div.h-full > a.group
Partner Central Sales and marketing resources and support for F5 partners. div.grid-cols-1 > span.w-full > div.h-full > a.group
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
Image elements have `[alt]` attributes
`[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
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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.
`[lang]` attributes have a valid value
Deprecated ARIA roles were not used
`[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
`<frame>` or `<iframe>` elements have a title
`<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
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.
`<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
Image elements do not have `[alt]` attributes that are redundant text.
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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser.
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 rP (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:34103) at oU (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:83631) at ic (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:112390) at https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:108438 at u5 (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:108539) at iH (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:129983) at MessagePort.w (https://www.f5.com/_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:55324)
Failed to load resource: the server responded with a status of 401 ()

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
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
Displays images with correct aspect ratio
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 DOM-based XSS with Trusted Types
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

857 ms

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

4.05 s

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
mktg.tags.f5.com/main/prod/utag.sync.js300.0 s54.6 KiB
mktg.tags.f5.com/main/prod/utag.js300.0 s49.5 KiB
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s25.1 KiB
js.adsrvr.org/up_loader.1.1.0.js0.0 ms12.3 KiB
js.clrt.ai/11186.js43200.0 s24.1 KiB
/client/63iw3vww/0/stub.js?disableSelector=true&manuallyS...600.0 s11.6 KiB
cdn.bizible.com/scripts/bizible.js86400.0 s25.2 KiB
cdn.speedcurve.com/js/lux.js?id=899484253600.0 s11.8 KiB
static.cloud.coveo.com/coveo.analytics.js/2/coveoua.js86400.0 s21.7 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
mktg.tags.f5.com/main/prod/utag.2.js?utv=ut4.48.202512190037300.0 s7.1 KiB
/notice?domain=f5.com&c=teconsent&js=nj&noticeType=bb&tex...3600.0 s6.3 KiB
mktg.tags.f5.com/main/prod/utag.294.js?utv=ut4.48.202604022110300.0 s4.8 KiB
mktg.tags.f5.com/main/prod/utag.273.js?utv=ut4.48.202604022110300.0 s4.1 KiB
mktg.tags.f5.com/main/prod/utag.383.js?utv=ut4.48.202604022110300.0 s4.0 KiB
mktg.tags.f5.com/main/prod/utag.235.js?utv=ut4.48.202604022110300.0 s3.3 KiB
mktg.tags.f5.com/main/prod/utag.117.js?utv=ut4.48.202604022110300.0 s3.3 KiB
scripts.demandbase.com/adobeanalytics/pscSDsz4.min.js0.0 ms3.0 KiB
mktg.tags.f5.com/main/prod/utag.116.js?utv=ut4.48.202604022110300.0 s3.1 KiB
mktg.tags.f5.com/main/prod/utag.110.js?utv=ut4.48.202604022110300.0 s3.1 KiB
mktg.tags.f5.com/main/prod/utag.118.js?utv=ut4.48.202604022110300.0 s3.0 KiB
mktg.tags.f5.com/main/prod/utag.111.js?utv=ut4.48.202604022110300.0 s3.0 KiB
mktg.tags.f5.com/main/prod/utag.272.js?utv=ut4.48.202604022110300.0 s2.8 KiB
mktg.tags.f5.com/main/prod/utag.283.js?utv=ut4.48.202604022110300.0 s2.1 KiB
mktg.tags.f5.com/main/prod/utag.303.js?utv=ut4.48.202604022110300.0 s2.1 KiB
mktg.tags.f5.com/main/prod/utag.280.js?utv=ut4.48.202604022110300.0 s2.0 KiB
mktg.tags.f5.com/main/prod/utag.320.js?utv=ut4.48.202604022110300.0 s2.0 KiB
mktg.tags.f5.com/main/prod/utag.35.js?utv=ut4.48.202604022110300.0 s1.9 KiB
mktg.tags.f5.com/main/prod/utag.243.js?utv=ut4.48.202604022110300.0 s1.8 KiB
mktg.tags.f5.com/main/prod/utag.230.js?utv=ut4.48.202604022110300.0 s1.3 KiB
munchkin.marketo.net/munchkin.js0.0 ms1.2 KiB
mktg.tags.f5.com/main/prod/utag.4.js?utv=ut4.48.202604022110300.0 s1.2 KiB
munchkin.marketo.net/munchkin-beta.js0.0 ms1.1 KiB
js.adsrvr.org/universal_pixel.js0.0 ms957 B
/collect?v=2&fmt=js&pid=8162&time=1776359188664&li_adsId=...0.0 ms452 B
de-de-63iw3vww.app.easyling.com/__inject/fix-meta.js86400.0 s1.1 KiB
tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=f5/main/202604022110&cb=1776359183973300.0 s431 B
/v1/cs?url=https%3A%2F%2Fwww.f5.com%2F&ref=&cb_name=usona...0.0 ms277 B
/lux/?v=4.0402&id=89948425&sid=177635918859696058&uid=177...0.0 ms76 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B
skawa-easyling.cdn.easyling.com/client/63iw3vww/reporter/en-US.js600.0 s0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
SA Power Networks enhances OT cloud security with F5 NGINXaaS div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/9faf287761490ffcbd5af2a8500c3...65.3 KiB59.5 KiB
Sheetz fuels secure business growth with F5 div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/6c7d61f4329dcfd5663907a59691a...45.5 KiB41.5 KiB
From sprawl to strategy: how a platform approach secures and simplifies IT div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/d6b332085e60cb3fd9ac3830b0130...43.1 KiB39.3 KiB
30 years at the application layer div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/86157282e1ac8ccd975c0e1f09832...29.6 KiB25.0 KiB
TOM Bank scales securely with F5 hybrid environment div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/1c83695ff8ddee7d5f0fd3db98ec9...12.0 KiB10.9 KiB
Validated S3 performance for AI infrastructure and data delivery div.flex > div.relative > div.relative > img.object-cover
/images/k6fem79d/production/bf7a6a95548fe803940f1e4d9f82c...8.2 KiB7.5 KiB
body.!pointer-events-auto > section.h-auto > div.absolute > img.h-full body.!pointer-events-auto > section.h-auto > div.absolute > img.h-full
/images/k6fem79d/production/78301c41dc41b07bc9e54aefdb95a...32.0 KiB5.8 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-6-IMG
nodeLabel: body.!pointer-events-auto > section.h-auto > div.absolute > img.h-full
path: 1,HTML,1,BODY,42,SECTION,0,DIV,0,IMG
selector: body.!pointer-events-auto > section.h-auto > div.absolute > img.h-full
snippet: <img alt="" loading="lazy" width="2560" height="500" decoding="async" data-nimg="1" class="h-full object-cover object-center" src="https://cdn.studio.f5.com/images/k6fem79d/production/78301c41dc41b07bc9e54…" style="color: transparent;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 214 ms
URLTime Spent
f5.com/214 ms
www.f5.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.4 s
Other1.4 s
Script Parsing & Compilation440 ms
Rendering304 ms
Style & Layout259 ms
Garbage Collection85 ms
Parse HTML & CSS28 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB
URLTransfer SizeEst Savings
scripts.demandbase.com/adobeanalytics/pscSDsz4.min.js8.4 KiB2.8 KiB

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

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Reduce unused CSS
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 7 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 250 ms
Server Backend Latencies 260 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 70 ms
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
94

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PLATFORM SPOTLIGHT: DEPLOYMENT div.container > div.grid > div.space-y-gutter-md > h6.d-supplementary

These are opportunities to improve keyboard navigation in your application.

Best practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open search div.container > div.ml-auto > div.relative > button.inline-flex

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
REPORT Validated S3 performance for AI infrastructure and data delivery div.flex > span.w-full > div.h-full > a.group
WEBINAR From sprawl to strategy: how a platform approach secures and simplifies… div.flex > span.w-full > div.h-full > a.group
BLOG 30 years at the application layer div.flex > span.w-full > div.h-full > a.group
GOVERNMENT SA Power Networks enhances OT cloud security with F5 NGINXaaS South … div.flex > span.w-full > div.h-full > a.group
RETAIL Sheetz fuels secure business growth with F5 Rising cybersecurity inciden… div.flex > span.w-full > div.h-full > a.group
BANKING & FINANCIAL SERVICES TOM Bank scales securely with F5 hybrid environmen… div.flex > span.w-full > div.h-full > a.group
Start a free trial Experience F5 in action by testing our products in your pre-… div.grid-cols-1 > span.w-full > div.h-full > a.group
Contact us We can assess your needs and connect you to with the right cloud pro… div.grid-cols-1 > span.w-full > div.h-full > a.group
MyF5 support Get support and manage your software subscriptions and BIG-IP VE r… div.grid-cols-1 > span.w-full > div.h-full > a.group
Find a reseller We're dedicated to building partnerships that drive your busine… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Blog Explore the F5 blog for insights, trends, and expert advice on digital … div.grid-cols-1 > span.w-full > div.h-full > a.group
Office of the CTO Strategic insights on the future of app services, the evoluti… div.grid-cols-1 > span.w-full > div.h-full > a.group
Newsroom The latest news, awards, recognition, and announcements about F5 and N… div.grid-cols-1 > span.w-full > div.h-full > a.group
Events calendar Discover events to connect, learn, and network—online or in-per… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 DevCentral A community of F5 experts collaborating to solve challenges, shar… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Labs Get the who, what, when, and what’s next in cyberattacks to inform your… div.grid-cols-1 > span.w-full > div.h-full > a.group
F5 Education Develop knowledge and hands-on skills to deploy, configure, and ma… div.grid-cols-1 > span.w-full > div.h-full > a.group
Partner Central Sales and marketing resources and support for F5 partners. div.grid-cols-1 > span.w-full > div.h-full > a.group
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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[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
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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
`[lang]` attributes have a valid value
Deprecated ARIA roles were not used
`[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 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
`<frame>` or `<iframe>` elements have a title
`<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
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.
`<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
Image elements do not have `[alt]` attributes that are redundant text.
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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser.
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 rP (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:34103) at oU (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:83631) at ic (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:112390) at https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:108438 at u5 (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:108539) at iH (https://www.f5.com/_next/static/chunks/4bd1b696-643ad7e1253fdab5.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:129983) at MessagePort.w (https://www.f5.com/_next/static/chunks/1684-c2a4dfbf19bd03d1.js?dpl=dpl_42ZhdrupKm1c1MNy1ynneW52JM8C:1:55324)
Failed to load resource: the server responded with a status of 401 ()

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
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
Displays images with correct aspect ratio
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 DOM-based XSS with Trusted Types
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback