Spain · Madrid Completed: Apr 22, 2026 20:40 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 80 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Missing signals may be hurting your search visibility.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
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.
External script from challenges.cloudflare.com lacks integrity attribute
Security gaps expose your site and users to attacks, eroding trust.
Page has only 47 words — nearly empty
SEO issues reduce your visibility in search results, lowering organic traffic.
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/78d1cbb4-a7b2-4e36-95d5-2d6e793264a8)<a href="https://beavercheck.com/results/78d1cbb4-a7b2-4e36-95d5-2d6e793264a8"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftranslatewiki.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftranslatewiki.netThis 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.
7 barrier(s) likely increasing bounce by ~16%.
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 Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
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.
$250 investment → $0.05/month returns + USD 150,000 risk avoided
$250
2h · 5 findings
$0.05 /mo
~$0.56 / year
USD 150,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 $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$12,500 / month at risk
~$150,001 / year if left unfixed
$150,000
$0.05 /mo
587.4 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 4 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.40 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.30 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.40 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.30 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.
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 | |
|---|---|---|---|
66 Projects
19k Translators
127k Messages to translate
238 Active languages
Ima… body.skin--responsive > div.grid > main > div.row | translatewiki.net/w/extensions/TwnMainPage/resources/banners/dance.jpg | 158.4 KiB | 30.4 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.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /w/load.php?lang=en&modules=site.styles&only=styles&skin=... | 0 B | 459 ms |
| /w/load.php?lang=en&modules=ext.translate.mainpage.icons%... | 0 B |
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 |
|---|---|---|
| /cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/... | 14400.0 s | 11.4 KiB |
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.
head > meta head > meta |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| translatewiki.net/ | 45.3 KiB | 45.3 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.row > form.five > div.row > textarea.twelve div.row > form.five > div.row > textarea.twelve |
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 |
|---|
aa · Afar
aae · Arbëresh
ab · Abkhazian
abr · Abron
abs · Ambonese Malay
ace · … div.row > form.five > div.row > select.mw-widgets-languageSelectWidget |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.row > div.four > div#twnmp-stat-projects > a div.row > div.four > div#twnmp-stat-projects > a |
div.row > div.four > div#twnmp-stat-translators > a div.row > div.four > div#twnmp-stat-translators > a |
div.row > div.four > div#twnmp-stat-messages > a div.row > div.four > div#twnmp-stat-messages > a |
div.row > div.four > div#twnmp-stat-languages > a div.row > div.four > div#twnmp-stat-languages > a |
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 |
|---|
div.row > form.five > div.row > input.twelve div.row > form.five > div.row > input.twelve |
div.row > form.five > div.row > input.twelve div.row > form.five > div.row > input.twelve |
div.row > form.five > div.row > input.twelve div.row > form.five > div.row > input.twelve |
View translations div.project-tile > div.row > div.twelve > a.translate |
Add your open source project for translation body.skin--responsive > div.grid > main > a.row |
About div.grid > footer > div.row > a.three |
Supported languages div.grid > footer > div.row > a.three |
Support desk div.grid > footer > div.row > a.three |
Help div.grid > footer > div.row > a.three |
Powered by netcup - netcup.de – Webhosting, vServer, Servermanagement div.grid > footer > div.row > a |
Software in the Public Interest associated project div.grid > footer > div.row > a |
Powered by MediaWiki div.grid > footer > div.row > a |
These items highlight common accessibility best practices.
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 |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
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 403 () | |
Refused to apply style from 'https://translatewiki.net/w/load.php?lang=en&modules=ext.translate.mainpage.icons%2Cstyles%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cjquery.uls.grid%7Cmediawiki.ui.button%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles&only=styles&skin=vector-2022' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. | |
Refused to apply style from 'https://translatewiki.net/w/load.php?lang=en&modules=site.styles&only=styles&skin=vector-2022' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. | |
Refused to execute script from 'https://translatewiki.net/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-2022' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
374 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
654 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
6 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.
1.90 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.
1.06 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 |
|---|---|---|
| /w/load.php?lang=en&modules=ext.translate.mainpage.icons%... | 300.0 s | 26.7 KiB |
| /w/load.php?lang=en&modules=startup&only=scripts&raw=1&sk... | 300.0 s | 15.2 KiB |
| /cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/... | 14400.0 s | 11.4 KiB |
| /wikipedia/commons/thumb/b/be/CodevTT_logo.png/120px-Code... | 0.0 ms | 4.4 KiB |
| /wikipedia/commons/thumb/b/b7/Ajapaik_short_logo.png/120p... | 0.0 ms | 4.1 KiB |
| upload.wikimedia.org/wikipedia/commons/a/a6/MediaWiki-2020-icon.svg | 0.0 ms | 2.9 KiB |
| upload.wikimedia.org/wikipedia/commons/d/da/Adiutor_icon.svg | 0.0 ms | 1.4 KiB |
| /w/load.php?lang=en&modules=site.styles&only=styles&skin=... | 300.0 s | 680 B |
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.
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.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /w/load.php?lang=en&modules=ext.translate.mainpage.icons%... | 26.7 KiB | 87 ms |
| /w/load.php?lang=en&modules=site.styles&only=styles&skin=... | 680 B | 127 ms |
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 | |
|---|---|---|---|
66
Projects
19k
Translators
127k
Messages to translate
238
Active languages
Ima… body.skin--responsive > div.grid > main > div.row | translatewiki.net/w/extensions/TwnMainPage/resources/banners/dance.jpg | 158.4 KiB | 30.4 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .mw-editfont-monospace{font-family:monospace,monospace} … | 74.3 KiB | 74.0 KiB |
| /w/load.php?lang=en&modules=ext.translate.mainpage.icons%... | 26.4 KiB | 23.7 KiB |
| .oo-ui-draggableElement-handle:not(.oo-ui-draggableElement-undraggable),.oo-ui-draggableElement-han… | 17.3 KiB | 16.5 KiB |
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 |
|---|---|---|
| /w/load.php?lang=en&modules=ext.checkUser.clientHints%7Ce... | 344.1 KiB | 138.1 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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 |
|---|
English div.mw-widgets-languageSelectWidget-vue-container > div.cdx-multiselect-lookup > div.cdx-chip-input > div.cdx-chip-input__chips |
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English div.mw-widgets-languageSelectWidget-vue-container > div.cdx-multiselect-lookup > div.cdx-chip-input > div.cdx-chip-input__chips |
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.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.row > div.four > div#twnmp-stat-projects > a div.row > div.four > div#twnmp-stat-projects > a |
div.row > div.four > div#twnmp-stat-translators > a div.row > div.four > div#twnmp-stat-translators > a |
div.row > div.four > div#twnmp-stat-messages > a div.row > div.four > div#twnmp-stat-messages > a |
div.row > div.four > div#twnmp-stat-languages > a div.row > div.four > div#twnmp-stat-languages > a |
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.
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 |
|---|---|
| SharedStorage | |
| StorageType.persistent is deprecated. Please use standardized navigator.storage instead. | |
| Fledge |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback