Brazil · Sao Paulo Completed: Apr 22, 2026 23:13 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 81 / 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.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
5 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
45 third-party resources (52% of weight)
Performance issues directly impact user engagement and conversion rates.
Cookie '__cf_bm' has no SameSite attribute
Security gaps expose your site and users to attacks, eroding trust.
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/59d4265b-cade-4877-a2bf-385ff7f9ac47)<a href="https://beavercheck.com/results/59d4265b-cade-4877-a2bf-385ff7f9ac47"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsurfshark.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsurfshark.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 3.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
5 barrier(s) likely increasing bounce by ~18%.
Page loads in 3.8s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 1.3s over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
Page feels frozen for 1.6s
+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 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€425 investment → €1,987/month returns + EUR 120,000,000 risk avoided
€425
5h · 5 findings
€1,987 /mo
~€23,841 / year
EUR 120,000,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.
5.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,000,000 / month at risk
~€120,000,004 / year if left unfixed
€120,000,000
+2 more
€0.30 /mo
4049.5 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 3 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.
1.45 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.79 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.60 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.056
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.45 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.
13.44 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.
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.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.6 KiB |
| /signals/config/1690077554448261?v=2.9.303&r=stable&domai... | 1200.0 s | 59.8 KiB |
| collector-52277.us.tvsquared.com/tv2track.js | 600.0 s | 8.7 KiB |
| /d/latest/e/index.js?cu=https://d.surfshark.com/internal/... | 604800.0 s | 7.8 KiB |
| /tv2track.php?action_name=Surfshark%20VPN%20%26%20all-in-... | 0.0 ms | 276 B |
| /tr/?id=1690077554448261&ev=PageView&dl=https%3A%2F%2Fsur... | 0.0 ms | 19 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
A smiling woman with glasses and curly hair looking down at her tablet div._WReJg > div._MOSY0 > div._uChkQ > img._SJjOb | /website/_next/image?url=/website/_next/public/_shared/im... | 128.5 KiB | 101.7 KiB |
A smartphone with a Surfshark logo inside a teal jelly cake, with raspberries a… div._8BkFQ > div._pet5f > div._eEmo9 > img._47ff0 | /website/_next/image?url=/website/_next/public/_shared/im... | 70.2 KiB | 57.0 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| www.googletagmanager.com/gtm.js?id=GTM-N9ZV87V | 160.4 KiB | 59.8 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js | 105.4 KiB | 57.0 KiB |
| www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c>m=4e64k1 | 155.7 KiB | 52.9 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 34.8 KiB |
| /signals/config/1690077554448261?v=2.9.303&r=stable&domai... | 59.6 KiB | 23.5 KiB |
| surfshark.com/website/_next/static/chunks/framework-45926255fd5ae142.js | 58.3 KiB | 22.5 KiB |
| surfshark.com/website/_next/static/chunks/main-5cfc65f1b268bf47.js | 39.7 KiB | 20.9 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.
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 | 3.2 s |
| Other | 742 ms |
| Script Parsing & Compilation | 472 ms |
| Style & Layout | 261 ms |
| Rendering | 167 ms |
| Parse HTML & CSS | 87 ms |
| Garbage Collection | 75 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
We love Surfshark because it is an easy-to-use app that you can download on all… div._pet5f > div._eEmo9 > div._0FMH1 > div._6BvVF |
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Rating: 4.5 out of 5 div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65 |
Rating: 4.5 out of 5 div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65 |
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 |
|---|
MAX & OCCY div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MAX & OCCY |
MRWHOSETHEBOSS div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MRWHOSETHEBOSS |
THE TECH CHAP div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-THE TECH CHAP |
ROSE AND ROSIE div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-ROSE AND ROSIE |
MARCUS HOUSE div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MARCUS HOUSE |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Get Surfshark div._XIYxa > div._7Rqyj > a._fZX0c > span._SzDTn |
Get Surfshark VPN div._eEmo9 > div._TOdK4 > a._fZX0c > span._SzDTn |
These are opportunities to improve the legibility of your content.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c>m=4e64k1 line 594, col 244 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 404 () |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
477 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
882 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
182 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.040
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
715 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.
3.23 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.
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.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.6 KiB |
| /signals/config/1690077554448261?v=2.9.303&r=stable&domai... | 1200.0 s | 59.8 KiB |
| collector-52277.us.tvsquared.com/tv2track.js | 600.0 s | 8.7 KiB |
| /d/latest/e/index.js?cu=https://d.surfshark.com/internal/... | 604800.0 s | 7.8 KiB |
| /tv2track.php?action_name=Surfshark%20VPN%20%26%20all-in-... | 0.0 ms | 276 B |
| /tr/?id=1690077554448261&ev=PageView&dl=https%3A%2F%2Fsur... | 0.0 ms | 16 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
A smiling woman with glasses and curly hair looking down at her tablet div._WReJg > div._MOSY0 > div._uChkQ > img._SJjOb | /website/_next/image?url=/website/_next/public/_shared/im... | 128.5 KiB | 110.2 KiB |
Antivirus that works backstage div._bHx0V > div._G3nog > div._kTS0B > img._rXeRp | /website/_next/image?url=/website/_next/public/home/image... | 41.4 KiB | 13.7 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
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 |
|---|---|---|
| www.googletagmanager.com/gtm.js?id=GTM-N9ZV87V | 160.4 KiB | 59.8 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js | 105.3 KiB | 57.1 KiB |
| www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c>m=4e64k1 | 155.7 KiB | 52.9 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 35.2 KiB |
| /signals/config/1690077554448261?v=2.9.303&r=stable&domai... | 59.6 KiB | 23.5 KiB |
| surfshark.com/website/_next/static/chunks/framework-45926255fd5ae142.js | 58.2 KiB | 22.4 KiB |
| surfshark.com/website/_next/static/chunks/main-5cfc65f1b268bf47.js | 39.6 KiB | 20.8 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Money-back guarantee
Unlimited devices
No-logs policy
24/7 support
High-tech div._8BkFQ > div._pet5f > div._eEmo9 > ul._fOYDg |
We love Surfshark because it is an easy-to-use app that you can download on all… div._pet5f > div._eEmo9 > div._0FMH1 > div._6BvVF |
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Money-back guarantee div._eEmo9 > ul._fOYDg > li._uGwE6 > button#guarantee |
Unlimited devices div._eEmo9 > ul._fOYDg > li._uGwE6 > button#devices |
No-logs policy div._eEmo9 > ul._fOYDg > li._uGwE6 > button#policy |
24/7 support div._eEmo9 > ul._fOYDg > li._uGwE6 > button#support |
High-tech div._eEmo9 > ul._fOYDg > li._uGwE6 > button#tech |
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Rating: 4.5 out of 5 div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65 |
Rating: 4.5 out of 5 div._6tMnV > div._UTQWE > div._uCQHE > div._cJz65 |
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 |
|---|
MAX & OCCY div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MAX & OCCY |
MRWHOSETHEBOSS div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MRWHOSETHEBOSS |
THE TECH CHAP div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-THE TECH CHAP |
ROSE AND ROSIE div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-ROSE AND ROSIE |
MARCUS HOUSE div._eEmo9 > div._0FMH1 > div._6BvVF > button#influencer-MARCUS HOUSE |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Get Surfshark div._XIYxa > div._7Rqyj > a._fZX0c > span._SzDTn |
Get Surfshark VPN div._eEmo9 > div._TOdK4 > a._fZX0c > span._SzDTn |
These are opportunities to improve the legibility of your content.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Money-back guarantee div._pet5f > div._eEmo9 > ul._fOYDg > li._uGwE6 |
Unlimited devices div._pet5f > div._eEmo9 > ul._fOYDg > li._uGwE6 |
No-logs policy div._pet5f > div._eEmo9 > ul._fOYDg > li._uGwE6 |
24/7 support div._pet5f > div._eEmo9 > ul._fOYDg > li._uGwE6 |
High-tech div._pet5f > div._eEmo9 > ul._fOYDg > li._uGwE6 |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | www.googletagmanager.com/gtag/js?id=AW-800656454&cx=c>m=4e64k1 line 594, col 244 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 404 () |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Send Feedback