Skip to content
Audit Complete

Results for https://mysql.com

Visit site
Spain Spain · Madrid Completed: Apr 16, 2026 17:37 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

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

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.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

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

Boomerang sites average 71
At average
Better than 51% of Boomerang sites See full Boomerang benchmark →
dc.js sites average 72
At average
Better than 36% of dc.js sites See full dc.js 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

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

1 control(s) without accessible label

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

Accessibility › Form Accessibility
5

44 link(s) with no accessible text

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

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Fmysql.com)](https://beavercheck.com/results/78b18e27-f257-4c21-a3e6-b1cf9fb1d4e6)
<a href="https://beavercheck.com/results/78b18e27-f257-4c21-a3e6-b1cf9fb1d4e6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmysql.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmysql.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. Addressing the critical issues below would have the most immediate impact on your user trust.

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

Conversion Barriers

1 critical 9 warning

10 barrier(s) likely increasing bounce by ~31%.

Speed (1)

Page takes 15.4s to load

+12% bounce

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

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

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

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

44 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

2 broken link(s) on the page

+3% 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

$450 investment → $0.87/month returns + USD 157,500 risk avoided

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

Investment

$450

4h · 5 findings

Monthly returns

$0.87 /mo

~$10 / year

  • Bandwidth savings $0.87

Regulatory risk avoided

USD 157,500

if kept compliant

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

$150 — 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

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 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,510 / 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

+2 more

Bandwidth Waste

$0.87 /mo

10871.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves $0.87/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.

49
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.86 s

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

15.43 s

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

191 ms

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

0.150

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

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

15.46 s

Detailed Report

Audit breakdown by category with detailed findings.

49

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
/ci/ws/get/w/2/co/[{"avatar_image":"/euf/assets/images/ch...0.0 ms37.8 KiB
www.oracle.com/us/assets/metrics/ora_code.js1800.0 s43.4 KiB
static.atgsvcs.com/js/atgsvcs.js0.0 ms36.5 KiB
www.oracle.com/asset/web/css/oracle-chat.css1800.0 s30.0 KiB
sc-oal-en.widget.custhelp.com/euf/rightnow/RightNow.Client.js900.0 s20.4 KiB
www.oracle.com/asset/web/js/oracle-chat.js1800.0 s11.3 KiB
/ci/ws/get/w/7/co/[{"c":"17","chat_login_page":"/app/mobi...0.0 ms8.1 KiB
www.oracle.com/asset/web/css/oracle-chat.css1800.0 s8.6 KiB
www.oracle.com/asset/web/analytics/infinity_common.js1800.0 s6.7 KiB
s.go-mpulse.net/boomerang/E6BB6-B37B4-898B7-F97BA-BBCDB604800.0 s56.8 KiB
/notice?domain=oracle.com&c=teconsent&js=bb&noticeType=bb...3600.0 s6.8 KiB
static.atgsvcs.com/js/pp.js0.0 ms3.5 KiB
sc-oal-en.widget.custhelp.com/euf/assets/images/chat.jpg900.0 s3.2 KiB
www.rnengage.com/api/1/javascript/acs.js0.0 ms2.9 KiB
www.rnengage.com/api/1/javascript/acs.js0.0 ms2.9 KiB
sc-oal-en.widget.custhelp.com/euf/assets/images/orcl_logo.png900.0 s2.5 KiB
sc-oal-en.custhelp.com/rnt/rnw/javascript/vs/1/vsapi.js86400.0 s5.4 KiB
www.oracle.com/assets/truste-oraclelib.js1800.0 s1.8 KiB
/euf/assets/css/syndicated_widgets/standard/ProactiveChat...900.0 s1.3 KiB
labs.mysql.com/common/css/page-20250803.min.css604800.0 s11.7 KiB
labs.mysql.com/common/css/main-20250803.min.css604800.0 s10.3 KiB
sc-oal-en.custhelp.com/vs/1/vsopts.js300.0 s822 B
/euf/assets/css/syndicated_widgets/standard/ConditionalCh...900.0 s726 B
/vs/site/oal_ces/visitor/10684eXZRMnk4fg9O7dMlFZNo7SV2fIL...0.0 ms438 B
/vs/site/oal_ces/visitor/10684eXZRMnk4fg9O7dMlFZNo7SV2fIL...0.0 ms434 B
/vs/site/oal_ces/visitor/10684eXZRMnk4fg9O7dMlFZNo7SV2fIL...0.0 ms434 B
/ci/dqa/publish/data/[{"action":{"offers":1,"w":"7"},"typ...0.0 ms416 B
/ci/dqa/publish/data/[{"action":{"offers":1,"w":"2"},"typ...0.0 ms416 B
labs.mysql.com/common/css/print-20250803.min.css604800.0 s849 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.150119] map[node:map[boundingRect:map[bottom:562 height:121 left:61 right:351 top:441 width:290] lhId:page-5-DIV nodeLabel:Accept all Decline all View and change cookie preferences path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,0,DIV,0,DIV,3,DIV selector:div > div.mainContent > div > div.pdynamicbutton snippet:<div class="pdynamicbutton" style="visibility: visible;"> type:node] score:0.076478] map[node:map[boundingRect:map[bottom:562 height:121 left:61 right:351 top:441 width:290] lhId:page-5-DIV nodeLabel:Accept all Decline all View and change cookie preferences path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,0,DIV,0,DIV,3,DIV selector:div > div.mainContent > div > div.pdynamicbutton snippet:<div class="pdynamicbutton" style="visibility: visible;"> type:node] score:0.052805 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:649 height:20 left:291 right:351 top:629 width:60] lhId:page-16-IMG nodeLabel:Company logo for TrustArc path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,1,DIV,0,DIV,4,A,0,IMG selector:div.footer > div.left > a > img.inline-3siarw snippet:<img class="inline-3siarw" alt="Company logo for TrustArc" src="https://consent.trustarc.com/get?name=Powered-By-TrustArc.png" target="_blank"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:659 height:41 left:41 right:371 top:618 width:330] lhId:page-4-DIV nodeLabel:Privacy Policy | Powered by path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,1,DIV selector:div.wrapper > div > div.footer snippet:<div class="footer" style=""> type:node] score:0.012874] map[node:map[boundingRect:map[bottom:562 height:121 left:61 right:351 top:441 width:290] lhId:page-5-DIV nodeLabel:Accept all Decline all View and change cookie preferences path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,0,DIV,0,DIV,3,DIV selector:div > div.mainContent > div > div.pdynamicbutton snippet:<div class="pdynamicbutton" style="visibility: visible;"> type:node] score:0.002721 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:649 height:20 left:291 right:351 top:629 width:60] lhId:page-16-IMG nodeLabel:Company logo for TrustArc path:1,HTML,1,BODY,7,DIV,0,DIV,2,DIV,a,#document-fragment,1,DIV,0,DIV,1,DIV,0,DIV,4,A,0,IMG selector:div.footer > div.left > a > img.inline-3siarw snippet:<img class="inline-3siarw" alt="Company logo for TrustArc" src="https://consent.trustarc.com/get?name=Powered-By-TrustArc.png" target="_blank"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:823 height:72 left:0 right:412 top:751 width:412] lhId:page-10-DIV nodeLabel:Start chat path:1,HTML,1,BODY,16,DIV selector:body.no-sidebar > div.ochat_slideout snippet:<div class="ochat_slideout" data-trackas="ochat_slideout"> type:node] score:0.00194]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.009826] map[node:map[boundingRect:map[bottom:823 height:72 left:215 right:412 top:751 width:197] lhId:page-11-UL nodeLabel:Start chat path:1,HTML,1,BODY,16,DIV,0,UL selector:body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2 snippet:<ul class="ochat_slidew2 active"> type:node] score:0.008768] map[node:map[boundingRect:map[bottom:823 height:73 left:215 right:288 top:750 width:73] lhId:page-14-LI nodeLabel:chat path:1,HTML,1,BODY,16,DIV,0,UL,1,LI selector:body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2 > li.ochaticon1 snippet:<li class="ochaticon1"> type:node] score:0.000115] map[node:map[boundingRect:map[bottom:823 height:73 left:215 right:288 top:750 width:73] lhId:page-14-LI nodeLabel:chat path:1,HTML,1,BODY,16,DIV,0,UL,1,LI selector:body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2 > li.ochaticon1 snippet:<li class="ochaticon1"> type:node] score:0.000114] map[node:map[boundingRect:map[bottom:823 height:73 left:215 right:288 top:750 width:73] lhId:page-14-LI nodeLabel:chat path:1,HTML,1,BODY,16,DIV,0,UL,1,LI selector:body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2 > li.ochaticon1 snippet:<li class="ochaticon1"> type:node] score:0.000114] map[node:map[boundingRect:map[bottom:823 height:73 left:215 right:288 top:750 width:73] lhId:page-14-LI nodeLabel:chat path:1,HTML,1,BODY,16,DIV,0,UL,1,LI selector:body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2 > li.ochaticon1 snippet:<li class="ochaticon1"> type:node] score:0.000114]]

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.

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.

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
div#main > div#banners > div#fp-banner4 > div#fp-banner-image4 div#main > div#banners > div#fp-banner4 > div#fp-banner-image4
labs.mysql.com/common/themes/sakila/banners/b2560-mysql-ai-generic2.en.jpg2.0 MiB911.1 KiB
MySQL Early Access div#fp-banner-image1 > div > div > img
www.mysql.com/common/logos/mysql-early-access.png254.8 KiB227.2 KiB
div.rw > div.col-1-of-2 > div.fp-product-icon > div#fp-product-icon-ai div.rw > div.col-1-of-2 > div.fp-product-icon > div#fp-product-icon-ai
labs.mysql.com/common/themes/sakila/mysql-ai.png7.3 KiB6.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:944.488 label:Time to first byte subpart:timeToFirstByte] map[duration:1428.614 label:Resource load delay subpart:resourceLoadDelay] map[duration:460.587 label:Resource load duration subpart:resourceLoadDuration] map[duration:13558.762 label:Element render delay subpart:elementRenderDelay]]
lhId: page-3-DIV
nodeLabel:
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV
selector: div#main > div#banners > div#fp-banner2 > div#fp-banner-image2
snippet: <div class="fp-banner-image" id="fp-banner-image2">

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-3-DIV
nodeLabel:
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV
selector: div#main > div#banners > div#fp-banner2 > div#fp-banner-image2
snippet: <div class="fp-banner-image" id="fp-banner-image2">

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
value: no origins were preconnected
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: 1.2 s
URLTime Spent
mysql.com/1.2 s
www.mysql.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Accept all Decline all View and change cookie preferences div > div.mainContent > div > div.pdynamicbutton
0.076
Accept all Decline all View and change cookie preferences div > div.mainContent > div > div.pdynamicbutton
0.053
Privacy Policy | Powered by div.wrapper > div > div.footer
0.013
Start chat body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2
0.009
Accept all Decline all View and change cookie preferences div > div.mainContent > div > div.pdynamicbutton
0.003
Start chat body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2
0.002
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000
Start chat body.no-sidebar > div.ochat_slideout
0.000

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 24.4 KiB
URLTransfer SizeEst Savings
www.oracle.com/asset/web/css/oracle-chat.css30.0 KiB24.4 KiB

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

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

Estimated savings: 910 ms 102.1 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.

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 Evaluation1.6 s
Other1.3 s
Style & Layout610 ms
Rendering280 ms
Script Parsing & Compilation154 ms
Garbage Collection107 ms
Parse HTML & CSS56 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
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

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

Max Potential First Input Delay 100 ms
Optimize DOM size
Forced reflow
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoid long main-thread tasks 11 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 160 ms
Server Backend Latencies 310 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 430 ms
INP breakdown
User Timing marks and measures
Avoid non-composited animations
80

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MySQL HeatWave div.col-1-of-2 > div.fp-product > h2 > a
MySQL AI div.col-1-of-2 > div.fp-product > h2 > a
MySQL Enterprise Edition div.col-1-of-2 > div.fp-product > h2 > a
MySQL for OEM/ISV div.col-1-of-2 > div.fp-product > h2 > a
MySQL Cluster CGE div.col-1-of-2 > div.fp-product > h2 > a
Q&A with MySQL Experts Tuesday, May 12, 2026 div.rw > div.col-1-of-2 > ul > li
MySQL Global Forum – Built on 30 Years of Innovation On-Demand div.rw > div.col-1-of-2 > ul > li
MySQL Enterprise Edition: Onboarding and Latest Innovation Highlights On-Demand div.rw > div.col-1-of-2 > ul > li
Accept all div.mainContent > div > div.pdynamicbutton > a.call
Decline all div.mainContent > div > div.pdynamicbutton > a.required
Powered by div > div.footer > div.left > label

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
More Countries » div#footer-bottom > div.footer-contact > div#footer-contact-numbers > a.darker-blue
privacy policy div.mainContent > div > div#cookieConsentDescription > a

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu ... Products   |- MySQL HeatWave   |- MySQL Enterprise Edition   |- MySQL … div#footer-links > div#site-footer-links > div#footer-nav > select#footer-select

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link div#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4
div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal
div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin
div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook
div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter
div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay
div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco
div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon
div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber
div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify
div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix
div.fp-logo-container > div#fp-logos > div > a.fp-logo-github div.fp-logo-container > div#fp-logos > div > a.fp-logo-github
div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking
div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos
div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer
div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm
div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba
div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat
div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent
div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao
div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb
div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start chat body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.no-sidebar > div#pop-div2014185780280426152 > div#pop-div3024974372408668077 > div#pop-frame0034404405713043484 body.no-sidebar > div#pop-div2014185780280426152 > div#pop-div3024974372408668077 > div#pop-frame0034404405713043484

These are opportunities to improve keyboard navigation in your application.

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
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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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.
73

Best Practices

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
MySQL Early Access div#fp-banner-image1 > div > div > img
www.mysql.com/common/logos/mysql-early-access.png380 x 434 (0.88)1132 x 434 (2.61)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Oracle Logo div > div#cookieMainHeader > span.logo > img
consent.trustarc.com/get?name=oralogo-black.gif133 x 18133 x 18200 x 27

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
Unload event listeners are deprecated and will be removed.
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
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
 Live Sales Chat body.no-sidebar > div#oReactiveChatContainer > div#atgchat-flyout > a#rn_sccl_4499221_Link

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
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

62
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
81
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.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.91 s

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

4.41 s

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

0 ms

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

0.034

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

5.57 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.42 s

Detailed Report

Audit breakdown by category with detailed findings.

62

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.

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.

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.

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
MySQL Early Access div#fp-banner-image1 > div > div > img
www.mysql.com/common/logos/mysql-early-access.png254.8 KiB245.8 KiB
div#main > div#banners > div#fp-banner4 > div#fp-banner-image4 div#main > div#banners > div#fp-banner4 > div#fp-banner-image4
labs.mysql.com/common/themes/sakila/banners/b1280-mysql-ai-generic2.en.jpg220.8 KiB150.0 KiB
div.rw > div.col-1-of-2 > div.fp-product-icon > div#fp-product-icon-ai div.rw > div.col-1-of-2 > div.fp-product-icon > div#fp-product-icon-ai
labs.mysql.com/common/themes/sakila/mysql-ai.png7.3 KiB6.4 KiB
div#main > div#banners > div#fp-banner3 > div#fp-banner-image3
labs.mysql.com/common/themes/sakila/banners/b1280-mysql-ee-generic2.en.jpg74.3 KiB5.5 KiB
div#main > div#banners > div#fp-banner2 > div#fp-banner-image2
labs.mysql.com/common/themes/sakila/banners/b1280-mysql-global-forum-2.en.jpg74.1 KiB5.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:752.5670009765626 label:Time to first byte subpart:timeToFirstByte] map[duration:662.9479990234375 label:Resource load delay subpart:resourceLoadDelay] map[duration:413.758 label:Resource load duration subpart:resourceLoadDuration] map[duration:13616.194 label:Element render delay subpart:elementRenderDelay]]
lhId: page-4-DIV
nodeLabel:
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV
selector: div#main > div#banners > div#fp-banner2 > div#fp-banner-image2
snippet: <div class="fp-banner-image" id="fp-banner-image2">

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-4-DIV
nodeLabel:
path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV
selector: div#main > div#banners > div#fp-banner2 > div#fp-banner-image2
snippet: <div class="fp-banner-image" id="fp-banner-image2">

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
value: no origins were preconnected
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: 691 ms
URLTime Spent
mysql.com/691 ms
www.mysql.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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 120 ms 34.7 KiB

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

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

Estimated savings: 120 ms 98.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
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

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

Layout shift culprits
Optimize DOM size
Forced reflow
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,661 KiB
JavaScript execution time 0.1 s
Minimizes main-thread work 0.9 s
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 160 ms
Server Backend Latencies 270 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 200 ms
Avoid large layout shifts 15 layout shifts found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
81

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MySQL HeatWave div.col-1-of-2 > div.fp-product > h2 > a
MySQL AI div.col-1-of-2 > div.fp-product > h2 > a
MySQL Enterprise Edition div.col-1-of-2 > div.fp-product > h2 > a
MySQL for OEM/ISV div.col-1-of-2 > div.fp-product > h2 > a
MySQL Cluster CGE div.col-1-of-2 > div.fp-product > h2 > a
Q&A with MySQL Experts Tuesday, May 12, 2026 div.rw > div.col-1-of-2 > ul > li
MySQL Global Forum – Built on 30 Years of Innovation On-Demand div.rw > div.col-1-of-2 > ul > li
MySQL Enterprise Edition: Onboarding and Latest Innovation Highlights On-Demand div.rw > div.col-1-of-2 > ul > li
Powered by div > div.footer > div.left > label

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
More Countries » div#footer-bottom > div.footer-contact > div#footer-contact-numbers > a.darker-blue
privacy policy div.mainContent > div > div#cookieConsentDescription > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link div#banners > div#fp-banner4 > div#fp-banner-image4 > a.fp-banner-link
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4
div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube div.fp-logo-container > div#fp-logos > div > a.fp-logo-youtube
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal div.fp-logo-container > div#fp-logos > div > a.fp-logo-paypal
div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin div.fp-logo-container > div#fp-logos > div > a.fp-logo-linkedin
div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook div.fp-logo-container > div#fp-logos > div > a.fp-logo-facebook
div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter div.fp-logo-container > div#fp-logos > div > a.fp-logo-twitter
div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay div.fp-logo-container > div#fp-logos > div > a.fp-logo-ebay
div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco div.fp-logo-container > div#fp-logos > div > a.fp-logo-cisco
div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon div.fp-logo-container > div#fp-logos > div > a.fp-logo-verizon
div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber div.fp-logo-container > div#fp-logos > div > a.fp-logo-uber
div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify div.fp-logo-container > div#fp-logos > div > a.fp-logo-shopify
div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix div.fp-logo-container > div#fp-logos > div > a.fp-logo-netflix
div.fp-logo-container > div#fp-logos > div > a.fp-logo-github div.fp-logo-container > div#fp-logos > div > a.fp-logo-github
div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart div.fp-logo-container > div#fp-logos > div > a.fp-logo-walmart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking div.fp-logo-container > div#fp-logos > div > a.fp-logo-booking
div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos div.fp-logo-container > div#fp-logos > div > a.fp-logo-zappos
div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer div.fp-logo-container > div#fp-logos > div > a.fp-logo-bankamer
div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart div.fp-logo-container > div#fp-logos > div > a.fp-logo-flipkart
div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm div.fp-logo-container > div#fp-logos > div > a.fp-logo-paytm
div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba div.fp-logo-container > div#fp-logos > div > a.fp-logo-alibaba
div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat div.fp-logo-container > div#fp-logos > div > a.fp-logo-wechat
div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent div.fp-logo-container > div#fp-logos > div > a.fp-logo-tencent
div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao div.fp-logo-container > div#fp-logos > div > a.fp-logo-taobao
div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb div.fp-logo-container > div#fp-logos > div > a.fp-logo-airbnb
div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota div.fp-logo-container > div#fp-logos > div > a.fp-logo-toyota

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start chat body.no-sidebar > div.ochat_slideout > ul.ochat_slidew2

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.no-sidebar > div#pop-div207600460717170132 > div#pop-div305614978466657037 > div#pop-frame01921641062792574 body.no-sidebar > div#pop-div207600460717170132 > div#pop-div305614978466657037 > div#pop-frame01921641062792574

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
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot1
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot2
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot3
div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4 div#banners > div.fp-banner-dots > div.fp-banner-dots-center > a#fp-dot4

These items highlight common accessibility best practices.

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
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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
MySQL Early Access div#fp-banner-image1 > div > div > img
www.mysql.com/common/logos/mysql-early-access.png380 x 434 (0.88)1132 x 434 (2.61)

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
Unload event listeners are deprecated and will be removed.
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
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
 Live Sales Chat body.no-sidebar > div#oReactiveChatContainer > div#atgchat-flyout > a#rn_sccl_4499221_Link

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback