Spain · Madrid Completed: Apr 22, 2026 20:10 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 79 / 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.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
No favicon or icon links detected
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Cookie '__cf_bm' has no SameSite attribute
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.
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/09d5b808-95ba-4bb1-af4a-3a5541aec902)<a href="https://beavercheck.com/results/09d5b808-95ba-4bb1-af4a-3a5541aec902"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpublications.parliament.uk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpublications.parliament.ukThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. 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.
£263 investment → £0.01/month returns + GBP 50,000 risk avoided
£263
4h · 5 findings
£0.01 /mo
~£0.17 / year
GBP 50,000
if kept compliant
£150 — 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.
3.5 developer hours at £75/hr
Based on United Kingdom rates (£75/hr)
Start here for the best return on investment
£4,167 / month at risk
~£50,000 / year if left unfixed
£50,000
£0.01 /mo
227.3 MB/mo × 0.063 GBP/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 3 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.58 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.71 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
11 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.065
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.53 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.72 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.
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 |
|---|---|---|
| cookiemanager.parliament.uk/cookie-manager-v2.css | 1.6 KiB | 779 ms |
| publications.parliament.uk/styles/global.css | 7.0 KiB |
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.
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 | |
|---|---|---|---|
Business icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_business.jpg | 7.4 KiB | 7.2 KiB |
Publications icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_records_and_publications.jpg | 7.4 KiB | 7.2 KiB |
People icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_members_and_staff.jpg | 7.1 KiB | 7.0 KiB |
About Parliament icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_about_parliament.jpg | 6.9 KiB | 6.8 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.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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.
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#banner > div#banner_top > div#banner_img > a div#banner > div#banner_top > div#banner_img > 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.
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.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
About Parliament includes sections on About MPs, Lords & officers, Living Heri… body > div#contentHolder > table |
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 | |
|---|---|---|---|---|
div#banner_top > div#banner_img > a > img div#banner_top > div#banner_img > a > img | publications.parliament.uk/server-side/images/parliament_logo.gif | 280 x 45 | 280 x 45 | 420 x 68 |
House of Commons icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_house_of_commons.png | 35 x 35 | 35 x 35 | 53 x 53 |
House of Lords icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_house_of_lords.png | 35 x 35 | 35 x 35 | 53 x 53 |
Video and Audio Live icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_parliament_live.png | 35 x 35 | 35 x 35 | 53 x 53 |
People icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_members_and_staff.jpg | 30 x 30 | 30 x 30 | 45 x 45 |
Publications icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_records_and_publications.jpg | 30 x 30 | 30 x 30 | 45 x 45 |
About Parliament icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_about_parliament.jpg | 30 x 29 | 30 x 29 | 45 x 44 |
Business icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_business.jpg | 30 x 29 | 30 x 29 | 45 x 44 |
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.
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Performance issues directly impact user engagement and conversion rates.
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 |
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.
455 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
605 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.137
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
455 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.
605 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.
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 | |
|---|---|---|---|
Business icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_business.jpg | 7.4 KiB | 7.2 KiB |
Publications icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_records_and_publications.jpg | 7.4 KiB | 7.2 KiB |
People icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_members_and_staff.jpg | 7.1 KiB | 7.0 KiB |
About Parliament icon tbody > tr > td > img | publications.parliament.uk/pa/img/icon_about_parliament.jpg | 6.9 KiB | 6.8 KiB |
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 |
|---|---|---|
| publications.parliament.uk/styles/global.css | 7.2 KiB | 72 ms |
| cookiemanager.parliament.uk/cookie-manager-v2.css | 1.6 KiB | 224 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 |
|---|---|
Accessibility A-Z Index Glossary Using this website Contact Us
Home
Visiting
Ab… body > div#contentHolder | 0.137 |
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.
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.
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#banner > div#banner_top > div#banner_img > a div#banner > div#banner_top > div#banner_img > 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.
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.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
About Parliament includes sections on About MPs, Lords & officers, Living Heri… body > div#contentHolder > table |
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.
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Performance issues directly impact user engagement and conversion rates.
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 |
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