United States · Santa Clara Completed: Apr 16, 2026 16:55 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 74 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
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.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/926df245-5b2f-4282-a400-10c65c792350)<a href="https://beavercheck.com/results/926df245-5b2f-4282-a400-10c65c792350"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgoogle.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgoogle.comThis badge auto-updates with your latest scan result.
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.
10 barrier(s) likely increasing bounce by ~38%.
Page takes 8.3s to load
+12% bounceUsers abandon at ~3s — you're 5.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 1.3s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
1 form field(s) without a label
+2% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks 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% bounceNo 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, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€383 investment → €5,140/month returns + EUR 500,000 risk avoided
€383
4h · 5 findings
€5,140 /mo
~€61,676 / year
EUR 500,000
if kept compliant
€128 — 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.
4.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€41,667 / month at risk
~€500,002 / year if left unfixed
€500,000
+2 more
€0.17 /mo
2257.7 MB/mo × 0.074 EUR/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.86 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.27 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.
3.29 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
8.34 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /xjs/_/ss/k=xjs.hm.TvsfKjyCrkQ.L.B1.O/am=ABAgAAAAAAAAAAAA... | 22 B | 175 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| google.com/ | 777 ms |
| www.google.com/ | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/am=AAAAAAAAAAAAA... | 336.4 KiB | 165.0 KiB |
| /og/_/js/k=og.qtm.en_US.6_fIyx0zU_k.2019.O/rt=j/m=qabr,q_... | 81.2 KiB | 54.2 KiB |
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/am=AAAAAAAAAAAAA... | 64.4 KiB | 44.2 KiB |
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/ck=xjs.hm.TvsfKj... | 72.5 KiB | 36.0 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/am=AAAAAAAAAAAAA... | 1.2 s | 908 ms | 101 ms |
| www.google.com/ | 838 ms | 259 ms | 38 ms |
| Unattributable | 326 ms | 25 ms | 0.0 ms |
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/ck=xjs.hm.TvsfKj... | 264 ms | 184 ms | 31 ms |
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/am=AAAAAAAAAAAAA... | 241 ms | 158 ms | 64 ms |
| /xjs/_/js/k=xjs.hm.en.BXFDxW4_j_c.2019.O/ck=xjs.hm.TvsfKj... | 168 ms | 91 ms | 4.9 ms |
| /og/_/js/k=og.qtm.en_US.6_fIyx0zU_k.2019.O/rt=j/m=qabr,q_... | 160 ms | 113 ms | 27 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.8 s |
| Other | 778 ms |
| Style & Layout | 287 ms |
| Script Parsing & Compilation | 269 ms |
| Parse HTML & CSS | 90 ms |
| Rendering | 65 ms |
| Garbage Collection | 22 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| :root{--COEmY:#1f1f1f;--xhUGwc:#fff} … | 11.5 KiB | 10.8 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Google Search div > div.A7Yvie > div.zGVn2e > div.a4bIc |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.A7Yvie > div.zGVn2e > div.dRYYxd > button.xOchs div.A7Yvie > div.zGVn2e > div.dRYYxd > button.xOchs |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
spaceballs trailer
bluesky down
burger king employee grease dumping
dji osmo po… div#main > div.JwzvB > div.bLgP0e > ul.o5j3Ue |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
spaceballs trailer div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
bluesky down div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
burger king employee grease dumping div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
dji osmo pocket 4 div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
aurora borealis forecast div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
shigella infection
Shigella — Bacteria div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
neanderthal infants div.JwzvB > div.bLgP0e > ul.o5j3Ue > li |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
888 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
109 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.
888 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.16 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /xjs/_/ss/k=xjs.hd.PXzalCcgL7k.L.B1.O/am=AAARAgAAAAAAAAAA... | 1.3 KiB | 64 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| google.com/ | 227 ms |
| www.google.com/ | 0.0 ms |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /xjs/_/js/k=xjs.hd.en.2uQT5UPEd6Q.2019.O/am=AAAAAAAAAAAAA... | 360.1 KiB | 177.0 KiB |
| /xjs/_/js/k=xjs.hd.en.2uQT5UPEd6Q.2019.O/ck=xjs.hd.PXzalC... | 164.5 KiB | 125.1 KiB |
| /og/_/js/k=og.asy.en_US.7NLpafgNJ_w.2019.O/rt=j/m=_ac,_aw... | 79.9 KiB | 49.6 KiB |
| /xjs/_/js/k=xjs.hd.en.2uQT5UPEd6Q.2019.O/am=AAAAAAAAAAAAA... | 79.8 KiB | 49.6 KiB |
| /xjs/_/js/k=xjs.hd.en.2uQT5UPEd6Q.2019.O/am=AAAAAAAAAAAAA... | 40.8 KiB | 25.9 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| h1,ol,ul,li,button{margin:0;padding:0} … | 14.1 KiB | 12.7 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback