Spain · Madrid Completed: Apr 22, 2026 20:23 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 72 / 100
Based on 6 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Solid infrastructure — fast server responses across the board.
Several regulatory requirements are not yet met.
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.
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.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Opener-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Nothing in this quadrant — good news.
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/f145edfe-39ec-4b0a-b22e-b84c2ba8d733)<a href="https://beavercheck.com/results/f145edfe-39ec-4b0a-b22e-b84c2ba8d733"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftldp.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftldp.orgThis 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.
3 barrier(s) likely increasing bounce by ~22%.
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
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">
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€225 investment → €0.00/month returns + EUR 120,000,000 risk avoided
€225
2h · 5 findings
€0.00 /mo
~€0.05 / year
EUR 120,000,000
if kept compliant
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.
2.5 developer hours at €90/hr
Based on Germany rates (€90/hr)
Start here for the best return on investment
€10,000,000 / month at risk
~€120,000,000 / year if left unfixed
€120,000,000
+2 more
€0.00 /mo
56.9 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.
900 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
900 ms
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.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
900 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.
900 ms
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.
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 |
|---|---|---|
| tldp.org/images/ldp.gif | 0.0 ms | 3.6 KiB |
| tldp.org/images/flags/t_es.gif | 0.0 ms | 820 B |
| tldp.org/images/flags/t_fr.gif | 0.0 ms | 423 B |
| tldp.org/images/flags/t_it.gif | 0.0 ms | 346 B |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
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.
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.
| URL | |
|---|---|
Spanish LDP nobr > font > a > img | tldp.org/images/flags/t_es.gif |
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 |
|---|
Non-English info td > nobr > a > font |
Translation effort td > nobr > a > font |
Translated Guides td > nobr > a > font |
Translated HOWTOs td > nobr > a > font |
Printed books td > nobr > a > font |
FAQ td > nobr > a > font |
History td > nobr > a > font |
Job Descriptions td > nobr > a > font |
Feedback td > nobr > a > font |
LDP Author Guide td > nobr > a > font |
Contribute / Help td > nobr > a > font |
Resources td > nobr > a > font |
How To Submit td > nobr > a > font |
GIT repository td > nobr > a > font |
Downloads td > nobr > a > font |
Contacts td > nobr > a > font |
Links nobr > form#searchbox_017644269519104757279:gm62gtzaoky > a > font |
OMF search nobr > form#searchbox_017644269519104757279:gm62gtzaoky > a > font |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
td > nobr > form#searchbox_017644269519104757279:gm62gtzaoky > input td > nobr > form#searchbox_017644269519104757279:gm62gtzaoky > input |
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.
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 |
|---|
Español td > nobr > font > a |
Français td > nobr > font > a |
Italian td > nobr > font > a |
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.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.google.com/cse | Allowed with warning |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
The Linux Documentation Project tbody > tr > td > img | tldp.org/images/ldp.gif | 300 x 120 | 300 x 120 | 450 x 180 |
Spanish LDP nobr > font > a > img | tldp.org/images/flags/t_es.gif | 25 x 14 | 25 x 14 | 38 x 21 |
French LDP nobr > font > a > img | tldp.org/images/flags/t_fr.gif | 25 x 14 | 25 x 14 | 38 x 21 |
Italian LDP nobr > font > a > img | tldp.org/images/flags/t_it.gif | 25 x 14 | 25 x 14 | 38 x 21 |
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
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.
323 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
323 ms
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.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
387 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.
323 ms
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.
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 |
|---|---|---|
| tldp.org/images/ldp.gif | 0.0 ms | 3.6 KiB |
| tldp.org/images/flags/t_es.gif | 0.0 ms | 856 B |
| tldp.org/images/flags/t_fr.gif | 0.0 ms | 364 B |
| tldp.org/images/flags/t_it.gif | 0.0 ms | 346 B |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
| URL | |
|---|---|
Spanish LDP nobr > font > a > img | tldp.org/images/flags/t_es.gif |
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 |
|---|
Non-English info td > nobr > a > font |
Translation effort td > nobr > a > font |
Translated Guides td > nobr > a > font |
Translated HOWTOs td > nobr > a > font |
Printed books td > nobr > a > font |
FAQ td > nobr > a > font |
History td > nobr > a > font |
Job Descriptions td > nobr > a > font |
Feedback td > nobr > a > font |
LDP Author Guide td > nobr > a > font |
Contribute / Help td > nobr > a > font |
Resources td > nobr > a > font |
How To Submit td > nobr > a > font |
GIT repository td > nobr > a > font |
Downloads td > nobr > a > font |
Contacts td > nobr > a > font |
Links nobr > form#searchbox_017644269519104757279:gm62gtzaoky > a > font |
OMF search nobr > form#searchbox_017644269519104757279:gm62gtzaoky > a > font |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
td > nobr > form#searchbox_017644269519104757279:gm62gtzaoky > input td > nobr > form#searchbox_017644269519104757279:gm62gtzaoky > input |
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.
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 |
|---|
Spanish LDP td > nobr > font > a |
Español td > nobr > font > a |
French LDP td > nobr > font > a |
Français td > nobr > font > a |
Italian LDP td > nobr > font > a |
Italian td > nobr > font > a |
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.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.google.com/cse | Allowed with warning |
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Performance issues directly impact user engagement and conversion rates.
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
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