Skip to content
Scanned
2026-04-21 20:04 UTC
Worker
🇪🇸 Madrid
Duration
2.2m
Vs prev

Audit overview

3 categories need attention: Accessibility, and 2 others.

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers
Critical: 2

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy
Critical: 3

No <main> landmark found

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Accessibility › Landmark Structure
Critical: 4

No favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
Warning: 5

25 third-party resources (99% of weight)

Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.

Performance › Page Weight Inventory
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.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.
2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 4.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

$667 investment → $12,915/month returns + USD 157,500 risk avoided

Investment
$667
6.7 h · 4 findings
Monthly returns
$12,915
$154,977/yr
Payback
0.1 mo
+23147% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6170.0 mo payback · +25031% Y1
Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.
$67 — 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.

Conversion barriers

8 barrier(s) likely increasing bounce by ~36%.

Barriers
8
2 crit 6 warn
Bounce delta
+36pp
added vs baseline
Score
62
C
Speed
2
Trust
1
Usability
1
Content
3
Nav
1
  • Page takes 4.3s to load
    Users abandon at ~3s — you're 1.8s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • High main-thread blocking time
    Page is non-interactive for 228ms after first paint
    → Defer third-party scripts and split large bundles
  • No Content-Security-Policy header
    Higher XSS blast radius — one compromised script can exfiltrate the checkout form
    → Ship a reporting-only CSP first, then enforce once violations are clean
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

$667 6.7 developer hours at $100/hr
Quick wins
$67 2 fixes in ~40 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Team composition

Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

$9,660 / month at risk ~$115,924 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

Bounce-Rate Cost

$9,660 /mo

+35.9pp bounce · ~3,591 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.13 /mo

1617.5 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~162 KB per page load
    Saves $0.13/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

71
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
80
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.25 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.32 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

228 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.

4.25 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.

4.60 s

Desktop

97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
80
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

955 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

955 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

10 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.

955 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.01 s

Categories

8
Avg score 72.0

How you compare

Where this site stands against peers running the same stack.

Amazon Route 53 · 1018 peers
You 72
·
Avg 72
At average
0 50 100
Compliance P3Content P8Accessibility P10Performance P81SEO P20Security P75Infrastructure P70Sustainability P64

Top 10% of Amazon Route 53 sites score 86+ on Compliance; you're at 66 — closing this gap is the highest-leverage improvement.

Better than 34% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple · 1279 peers
You 72
·
Avg 73
At average
0 50 100
Compliance P2Accessibility P6Content P8Performance P83SEO P25Security P69Infrastructure P67Sustainability P55

Top 10% of Apple sites score 85+ on Compliance; you're at 66 — closing this gap is the highest-leverage improvement.

Better than 31% of Apple sites See full Apple benchmark →

Technology stack

Amazon Route 53, hosted on AWS, with AWS CloudFront CDN

11 technologies detected 3 stack layers Enterprise

Stack Architecture

Framework
Amazon Route 53 Apple Facebook Google Search Console HSTS Microsoft Microsoft 365
CDN
AWS CloudFront Amazon CloudFront
Hosting
AWS Amazon Web Services

All Detected Technologies (11)

Categories CDN Website https://aws.amazon.com/cloudfront Detected by BeaverCheck Evidence x-amz-cf-id: yHYNeI600zpEYyfaCh7-isrB-P2DYReDl6iXTU8KpNUn0QG6KVUn5g==

Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.

Categories CDN Website https://aws.amazon.com/cloudfront/ Detected by BeaverCheck
Categories Hosting Website https://aws.amazon.com Detected by BeaverCheck · Medium Evidence Header: X-Amz-Cf-Pop

Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.

Categories PaaS Website https://aws.amazon.com/ Detected by BeaverCheck
Categories DNS Detected by BeaverCheck Evidence NS record: ns-1127.awsdns-12.org
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: apple-domain-verification=R8oTKC18LB83pxox
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=ru12x2he93icxu2xebu5undtr1oyot
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=oXs77JQpQ5vLhxUM3QUXjKZa1ooX6nKtFErqmGL7Rx4

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms78911389
Categories Email Detected by BeaverCheck Evidence MX record: seattletimes-com.mail.protection.outlook.com

Observations (2)

No build tool detected

A framework (Amazon Route 53) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.

Complex technology stack detected

11 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

Show your score

Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fseattletimes.com)](https://beavercheck.com/results/abf6c990-0fa2-49a9-86b3-3cbe18df3ca1)
<a href="https://beavercheck.com/results/abf6c990-0fa2-49a9-86b3-3cbe18df3ca1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fseattletimes.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fseattletimes.com

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

Fix Plan

Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.

Three-week fix plan

2 sprints · 7h total → projected B (81)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 1h → C (76)
  • · No <main> landmark found
  • · No favicon or icon links detected
  • · 25 third-party resources (99% of weight)

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

2 findings 6h → B (81)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback