Spain · Madrid Completed: Apr 22, 2026 00:33 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 88 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Strong security — your users are well protected.
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.
Mostly compliant — a few items need attention.
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.
1 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
3 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No H1 heading found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
Nothing in this quadrant — good news.
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/c064bca7-ff5e-46b8-a710-170f85c5a642)<a href="https://beavercheck.com/results/c064bca7-ff5e-46b8-a710-170f85c5a642"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ff-droid.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ff-droid.orgThis badge auto-updates with your latest scan result.
Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Addressing the critical issues below would have the most immediate impact on your audience reach.
6 barrier(s) likely increasing bounce by ~21%.
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
3 form field(s) without a label
+6% 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 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.
$750 investment → $0.04/month returns + USD 157,500 risk avoided
$750
8h · 5 findings
$0.04 /mo
~$0.48 / year
USD 157,500
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.
7.5 developer hours at $100/hr
Based on United States rates ($100/hr)
$13,125 / month at risk
~$157,500 / year if left unfixed
$157,500
+4 more
$0.04 /mo
503.2 MB/mo × 0.080 USD/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.
856 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.56 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.192
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
856 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.
1.56 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 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 |
|---|---|---|
| f-droid.org/assets/fdroid-screenshot-en.png | 43200.0 s | 56.9 KiB |
| /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... | 43200.0 s | 11.9 KiB |
| f-droid.org/css/main.css | 43200.0 s | 7.4 KiB |
| /assets/liberapay_donate_button_GHdOOfmFJNeSXjfjnA-98XtIu... | 43200.0 s | 2.2 KiB |
| f-droid.org/assets/ic_search_black_24px.svg | 43200.0 s | 1.6 KiB |
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.
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 | |
|---|---|---|---|
F-Droid Android app screenshot div.article-area > div.download-and-screenshot > div.screenshot > img | f-droid.org/assets/fdroid-screenshot-en.png | 56.7 KiB | 26.3 KiB |
Donate to our Collective ul.donate-options > li.donate-option > a > img | /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... | 11.7 KiB | 8.9 KiB |
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.
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.
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 | |
|---|---|
F-Droid Android app screenshot div.article-area > div.download-and-screenshot > div.screenshot > img | f-droid.org/assets/phone-frame_kEDoOnDDPLnsqH4lVaEun9wfQgM9ivrhk5OiUWWdKHc=.png |
Donate to our Collective ul.donate-options > li.donate-option > a > img | /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... |
F-Droid div.site-wrapper > header.site-header > a.site-title > img | /assets/fdroid-logo-text_S0MUfk_FsnAYL7n2MQye-34IoSNm6QM6... |
Donate via Liberapay ul.donate-options > li.donate-option > a > img | /assets/liberapay_donate_button_GHdOOfmFJNeSXjfjnA-98XtIu... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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 |
|---|---|
العربية
བོད་སྐད་
català
Čeština
Deutsch
English
Español
euskara
فارسی
Français
עב… body > div.site-wrapper > div.main-content > div.sidebar | 0.192 |
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 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 |
|---|
body > div.banner > button.banner--close body > div.banner > button.banner--close |
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 |
|---|
div > form.search-form > div.search-input-wrp > input.search-input div > form.search-form > div.search-input-wrp > input.search-input |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
العربية
བོད་སྐད་
català
Čeština
Deutsch
English
Español
euskara
فارسی
Français
עב… div.sidebar > div.sidebar-widget > form > select#language-chooser-select |
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 |
|---|
https://keepandroidopen.org/ body > div.banner > div.banner--text > a |
Edit on GitLab div.site-description > p > span.edit-this-page-area > a |
These are opportunities to improve the legibility of your content.
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 |
|---|
Instructions to verify the download div.download-and-screenshot > div.download > div.pgp-verification > 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.
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 | |
|---|---|---|---|---|
F-Droid Android app screenshot div.article-area > div.download-and-screenshot > div.screenshot > img | f-droid.org/assets/phone-frame_kEDoOnDDPLnsqH4lVaEun9wfQgM9ivrhk5OiUWWdKHc=.png | 380 x 694 | 413 x 754 | 570 x 1041 |
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.
| Description |
|---|
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser. |
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.
257 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
406 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.029
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
312 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.
406 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.
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 |
|---|---|---|
| f-droid.org/assets/fdroid-screenshot-en.png | 43200.0 s | 56.9 KiB |
| /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... | 43200.0 s | 11.9 KiB |
| f-droid.org/css/main.css | 43200.0 s | 7.4 KiB |
| /assets/liberapay_donate_button_GHdOOfmFJNeSXjfjnA-98XtIu... | 43200.0 s | 2.2 KiB |
| f-droid.org/assets/ic_search_black_24px.svg | 43200.0 s | 1.6 KiB |
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 | |
|---|---|---|---|
F-Droid Android app screenshot div.article-area > div.download-and-screenshot > div.screenshot > img | f-droid.org/assets/fdroid-screenshot-en.png | 56.7 KiB | 26.3 KiB |
Donate to our Collective ul.donate-options > li.donate-option > a > img | /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... | 11.7 KiB | 10.8 KiB |
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.
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.
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 | |
|---|---|
F-Droid Android app screenshot div.article-area > div.download-and-screenshot > div.screenshot > img | f-droid.org/assets/phone-frame_kEDoOnDDPLnsqH4lVaEun9wfQgM9ivrhk5OiUWWdKHc=.png |
div.download-and-screenshot > div.download > div.qr > img div.download-and-screenshot > div.download > div.qr > img | /assets/download-fdroid-qr_rt62kUMmGMIMhgDgUUWjYefCQjazGq... |
Donate to our Collective ul.donate-options > li.donate-option > a > img | /assets/opencollective_button_iIGF0Hixdj0EaYR3Sd7FRigTVcl... |
F-Droid div.site-wrapper > header.site-header > a.site-title > img | /assets/fdroid-logo-text_S0MUfk_FsnAYL7n2MQye-34IoSNm6QM6... |
Donate via Liberapay ul.donate-options > li.donate-option > a > img | /assets/liberapay_donate_button_GHdOOfmFJNeSXjfjnA-98XtIu... |
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 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 |
|---|
body > div.banner > button.banner--close body > div.banner > button.banner--close |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.download-and-screenshot > div.download > div.qr > img div.download-and-screenshot > div.download > div.qr > img |
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 |
|---|
div > form.search-form > div.search-input-wrp > input.search-input div > form.search-form > div.search-input-wrp > input.search-input |
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
العربية
བོད་སྐད་
català
Čeština
Deutsch
English
Español
euskara
فارسی
Français
עב… div.sidebar > div.sidebar-widget > form > select#language-chooser-select |
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 |
|---|
https://keepandroidopen.org/ body > div.banner > div.banner--text > a |
Edit on GitLab div.site-description > p > span.edit-this-page-area > a |
These are opportunities to improve the legibility of your content.
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.
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.
| Description |
|---|
Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured header parser. |
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.download-and-screenshot > div.download > div.qr > img div.download-and-screenshot > div.download > div.qr > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback