Spain · Madrid Completed: Apr 16, 2026 16:55 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
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.
Strong compliance posture across regulations.
Good content signals with minor gaps.
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.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
69 third-party resources (100% 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.
Cookie 'ct0' is missing the HttpOnly flag
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/18c3e462-2a2b-4482-ac8a-b18244aaaaad)<a href="https://beavercheck.com/results/18c3e462-2a2b-4482-ac8a-b18244aaaaad"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftwitter.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftwitter.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 13.3s 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.
8 barrier(s) likely increasing bounce by ~30%.
Page takes 13.3s to load
+12% bounceUsers abandon at ~3s — you're 10.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
High main-thread blocking time
+2% bouncePage is non-interactive for 238ms after first paint
Fix: Defer third-party scripts and split large bundles
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
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
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
5 broken link(s) on the page
+5% 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 → €0.39/month returns + EUR 120,500,000 risk avoided
€425
5h · 5 findings
€0.39 /mo
~€4.69 / year
EUR 120,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.
5.0 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,667 / month at risk
~€120,500,005 / year if left unfixed
€120,500,000
+2 more
€0.39 /mo
5281.0 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 2 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.
9.51 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.31 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
238 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.
9.51 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
13.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.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| abs.twimg.com/fonts/v1/chirp-extended-heavy-web.woff2 | 30 ms |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js | 86400.0 s | 17.4 KiB |
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 |
|---|---|
| twitter.com/ | 920 ms |
| x.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 |
|---|---|---|
| abs.twimg.com/responsive-web/client-web/main.52d81e4a.js | 286.9 KiB | 147.9 KiB |
| abs.twimg.com/responsive-web/client-web/vendor.7ef16aaa.js | 345.5 KiB | 103.0 KiB |
| abs.twimg.com/responsive-web/client-web/modules.audio.184d9faa.js | 75.8 KiB | 75.3 KiB |
| accounts.google.com/gsi/client | 95.4 KiB | 68.7 KiB |
| abs.twimg.com/responsive-web/client-web/i18n/en.f19ad19a.js | 178.9 KiB | 41.9 KiB |
| abs.twimg.com/responsive-web/client-web/loader.AppModules.219d882a.js | 32.7 KiB | 23.9 KiB |
| abs.twimg.com/responsive-web/client-web/modules.common.469fbc7a.js | 21.0 KiB | 20.7 KiB |
| /responsive-web/client-web/shared~bundle.AudioSpaceDetail... | 22.5 KiB | 20.3 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 |
|---|---|---|---|
| abs.twimg.com/responsive-web/client-web/main.52d81e4a.js | 3.0 s | 2.8 s | 94 ms |
| abs.twimg.com/responsive-web/client-web/vendor.7ef16aaa.js | 1.5 s | 1.2 s | 127 ms |
| Unattributable | 639 ms | 32 ms | 0.0 ms |
| x.com/ | 245 ms | 37 ms | 105 ms |
| /responsive-web/client-web/shared~bundle.Routes~bundle.Lo... | 190 ms | 170 ms | 17 ms |
| abs.twimg.com/responsive-web/client-web/ondemand.s.a759306a.js | 162 ms | 156 ms | 1.5 ms |
| abs.twimg.com/responsive-web/client-web/modules.audio.184d9faa.js | 58 ms | 36 ms | 21 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 4.6 s |
| Other | 698 ms |
| Script Parsing & Compilation | 560 ms |
| Garbage Collection | 145 ms |
| Style & Layout | 114 ms |
| Parse HTML & CSS | 56 ms |
| Rendering | 19 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 |
| SharedWorkerWithNoActiveClient | 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.
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 |
|---|
Terms of Service div.css-175oi2r > div.css-146c3p1 > a.css-1jxf684 > span.css-1jxf684 |
Cookie Use. div.css-175oi2r > div.css-146c3p1 > a.css-1jxf684 > span.css-1jxf684 |
These are opportunities to improve the legibility of your content.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|---|
Not signed in with the identity provider. |
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.
1.19 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.86 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
353 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.299
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.27 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.
2.86 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.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| abs.twimg.com/fonts/v1/chirp-extended-heavy-web.woff2 | 30 ms |
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js | 86400.0 s | 17.4 KiB |
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 |
|---|---|
| twitter.com/ | 368 ms |
| x.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
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
Happening now
Join today.
Sign up with Google
Sign up with Apple
OR
Create acco… div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > main.css-175oi2r | 0.235 |
div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 | 0.030 |
div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 | 0.018 |
div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 div.css-175oi2r > div.css-175oi2r > div.css-175oi2r > svg.r-4qtqp9 | 0.016 |
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 |
|---|---|---|
| abs.twimg.com/responsive-web/client-web/main.52d81e4a.js | 286.9 KiB | 146.3 KiB |
| abs.twimg.com/responsive-web/client-web/vendor.7ef16aaa.js | 345.5 KiB | 102.3 KiB |
| abs.twimg.com/responsive-web/client-web/modules.audio.184d9faa.js | 75.8 KiB | 75.3 KiB |
| accounts.google.com/gsi/client | 95.4 KiB | 68.7 KiB |
| abs.twimg.com/responsive-web/client-web/i18n/en.f19ad19a.js | 178.9 KiB | 41.9 KiB |
| abs.twimg.com/responsive-web/client-web/loader.AppModules.219d882a.js | 32.7 KiB | 24.5 KiB |
| /responsive-web/client-web/shared~bundle.AudioSpaceDetail... | 22.5 KiB | 20.2 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 |
| SharedWorkerWithNoActiveClient | 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.
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 |
|---|
Terms of Service div.css-175oi2r > div.css-146c3p1 > a.css-1jxf684 > span.css-1jxf684 |
Cookie Use. div.css-175oi2r > div.css-146c3p1 > a.css-1jxf684 > span.css-1jxf684 |
These are opportunities to improve the legibility of your content.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
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 |
|---|---|
Not signed in with the identity provider. |
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