Spain · Madrid Completed: Apr 22, 2026 21:57 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 74 / 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.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Reasonable footprint with room for optimization.
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 <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
19 third-party resources (51% of weight)
Performance issues directly impact user engagement and conversion rates.
Cross-Origin-Embedder-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.
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/b6e0776e-48ce-4bb4-ae4c-414ac6e4f1e1)<a href="https://beavercheck.com/results/b6e0776e-48ce-4bb4-ae4c-414ac6e4f1e1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fseattle.gov" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fseattle.govThis 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 10.3s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.
9 barrier(s) likely increasing bounce by ~38%.
Page takes 10.3s to load
+12% bounceUsers abandon at ~3s — you're 7.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 824ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
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">
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
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.
$500 investment → $4,754/month returns + USD 157,500 risk avoided
$500
5h · 5 findings
$4,754 /mo
~$57,048 / year
USD 157,500
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.
5.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,504 / year if left unfixed
$157,500
+4 more
$0.31 /mo
3842.6 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 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.
4.43 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.33 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
824 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.
5.45 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.
10.37 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.
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.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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 |
|---|---|---|
| seattle.gov/cms_resources/pe/sea-global.css | 20.4 KiB | 333 ms |
| www.trumba.com/scripts/spuds.js | 12.5 KiB | 1.3 s |
| /libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0... | 66.2 KiB | 2.1 s |
| fonts.googleapis.com/css?family=Open+Sans:400,700,800,600,300 | 2.3 KiB | 832 ms |
| seattle.gov/cms_resources/js/siteimprove_analytics.js | 829 B |
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 | |
|---|---|---|---|
li > article.card > div.avatar > img li > article.card > div.avatar > img | seattle.gov/images/Departments/Court/Homepage/2021JudgesGroup_300x300.png | 136.5 KiB | 133.9 KiB |
Children in colorful clothing climb steps on a forest trail in Seattle li > article.card > picture > img.thumbnail | seattle.gov/images/Global/Home_Parks_Spring_Programs_Promo.jpg | 53.1 KiB | 34.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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.
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 |
|---|---|---|
| /_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ... | 118.2 KiB | 93.6 KiB |
| www.googletagmanager.com/gtag/js?id=G-CGFRM1LP6G&cx=c>m=4e64k0 | 160.0 KiB | 64.8 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-PXQBQ2 | 159.5 KiB | 63.6 KiB |
| /libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0... | 65.9 KiB | 43.6 KiB |
| siteimproveanalytics.com/js/siteanalyze_15203573.js | 30.8 KiB | 23.2 KiB |
| seattle.gov/cms_resources/pe/sea-global.js | 61.0 KiB | 22.2 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 |
|---|---|---|---|
| seattle.gov/ | 772 ms | 9.8 ms | 2.5 ms |
| seattle.gov/cms_resources/js/Subsetter/fontawesome.min.js | 491 ms | 367 ms | 4.4 ms |
| Unattributable | 380 ms | 15 ms | 0.0 ms |
| www.googletagmanager.com/gtag/js?id=G-CGFRM1LP6G&cx=c>m=4e64k0 | 371 ms | 304 ms | 39 ms |
| www.googletagmanager.com/gtm.js?id=GTM-PXQBQ2 | 336 ms | 287 ms | 45 ms |
| seattle.gov/cms_resources/js/Subsetter/solid.min.js | 259 ms | 74 ms | 27 ms |
| seattle.gov/cms_resources/pe/sea-global.js | 247 ms | 230 ms | 1.0 ms |
| /_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ... | 164 ms | 120 ms | 36 ms |
| siteimproveanalytics.com/js/siteanalyze_15203573.js | 91 ms | 31 ms | 14 ms |
| /libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0... | 69 ms | 52 ms | 15 ms |
| seattle.gov/cms_resources/js/Subsetter/light.min.js | 51 ms | 40 ms | 4.8 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 | 1.6 s |
| Other | 748 ms |
| Style & Layout | 505 ms |
| Script Parsing & Compilation | 206 ms |
| Rendering | 154 ms |
| Garbage Collection | 60 ms |
| Parse HTML & CSS | 58 ms |
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 |
|---|---|---|
| seattle.gov/cms_resources/pe/sea-global.css | 19.9 KiB | 16.7 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.
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 |
|---|
header.bg_blue > div.contained > div.header_subLayout > button#search-btn header.bg_blue > div.contained > div.header_subLayout > button#search-btn |
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.
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.
954 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
48 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.144
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.08 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.05 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.
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.
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.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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 | |
|---|---|---|---|
li > article.card > div.avatar > img li > article.card > div.avatar > img | seattle.gov/images/Departments/Court/Homepage/2021JudgesGroup_300x300.png | 136.5 KiB | 133.9 KiB |
Children in colorful clothing climb steps on a forest trail in Seattle li > article.card > picture > img.thumbnail | seattle.gov/images/Global/Home_Parks_Spring_Programs_Promo.jpg | 53.1 KiB | 24.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 |
|---|---|---|
| www.trumba.com/scripts/spuds.js | 12.5 KiB | 704 ms |
| fonts.googleapis.com/css?family=Open+Sans:400,700,800,600,300 | 2.3 KiB | 281 ms |
| /libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0... | 66.2 KiB | 424 ms |
| seattle.gov/cms_resources/js/siteimprove_analytics.js | 830 B | |
| seattle.gov/cms_resources/pe/sea-global.css | 20.4 KiB | 109 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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 |
|---|---|---|
| /_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ... | 118.2 KiB | 93.6 KiB |
| www.googletagmanager.com/gtag/js?id=G-CGFRM1LP6G&cx=c>m=4e64k0 | 160.0 KiB | 64.8 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-PXQBQ2 | 159.5 KiB | 64.2 KiB |
| /libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0... | 65.9 KiB | 43.6 KiB |
| siteimproveanalytics.com/js/siteanalyze_15203573.js | 30.8 KiB | 23.2 KiB |
| seattle.gov/cms_resources/pe/sea-global.js | 61.0 KiB | 22.1 KiB |
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 |
|---|---|---|
| seattle.gov/cms_resources/pe/sea-global.css | 19.9 KiB | 15.5 KiB |
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 |
|---|---|
Home Page
City of Seattle Official Website
Featured Content
Register for Spri… body.aws102 > main#content | 0.100 |
Home Page
City of Seattle Official Website
Featured Content
Register for Spri… body.aws102 > main#content | 0.041 |
Search
a#search-btn | 0.003 |
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.
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