Skip to content
Scanned
2026-08-18 00:30 UTC
Worker
🇪🇸 Madrid
Duration
37.00s
Vs prev

Global Performance

6/6 locations

Strong global performance — average 151ms across 6 locations, fastest from Amsterdam (21ms), slowest from Singapore (731ms). No CDN detected. Cache-Control header is missing. 1 location above the 500ms target.

Spain - Madrid
Full audit
45ms
DNS 39ms · TLS 4ms
Netherlands - Amsterdam
21ms
DNS 8ms · TLS 9ms
United States - Santa Clara
52ms
DNS 12ms · TLS 16ms
United Stated - New York
30ms
DNS 14ms · TLS 11ms
Brazil - Sao Paulo
28ms
DNS 15ms · TLS 8ms
Singapore - Singapore
731ms
DNS 199ms · TLS 180ms
CDN: No CDN · Avg TTFB: 151ms · Cache: No cache headers

Audit overview

All categories sit comfortably above the 70 threshold; this is a clean audit.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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
Warning: 4

19 third-party resources (100% 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
Warning: 5

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 8.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 8.0s — 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

$717 investment → $13,992/month returns + USD 157,500 risk avoided

Investment
$717
7.2 h · 4 findings
Monthly returns
$13,992
$167,908/yr
Payback
0.1 mo
+23329% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6170.0 mo payback · +27128% 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.
$17 — 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

10 barrier(s) likely increasing bounce by ~31%.

Barriers
10
1 crit 9 warn
Bounce delta
+31pp
added vs baseline
Score
63
C
Speed
2
Trust
1
Usability
1
Content
4
Nav
2
  • Page takes 8.0s to load
    Users abandon at ~3s — you're 5.5s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • High main-thread blocking time
    Page is non-interactive for 251ms 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
  • Viewport disables user zoom
    Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
    → Remove user-scalable=no; drop maximum-scale if it's below 2
  • 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

$717 7.2 developer hours at $100/hr
Quick wins
$17 1 fixes in ~10 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

$8,277 / month at risk ~$99,329 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • Privacy Policy not detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$8,277 /mo

+30.8pp bounce · ~3,077 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.24 /mo

3027.4 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~303 KB per page load
    Saves $0.24/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 3 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

53
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
58
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.

7.84 s

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

7.99 s

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

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

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

8.14 s

Desktop

91
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
58
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.

881 ms

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

1.74 s

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

33 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.35 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.74 s

Categories

8
Avg score 79.2

How you compare

Where this site stands against peers running the same stack.

Babel · 113 peers
You 81
·
Avg 72
+9 above average
0 50 100
Better than 95% of Babel sites See full Babel benchmark →
Cloudflare · 2307 peers
You 81
·
Avg 75
+6 above average
0 50 100
Infrastructure P4Security P91Compliance P13Accessibility P85Performance P76Sustainability P34SEO P37Content P40

Top 10% of Cloudflare sites score 97+ on Infrastructure; you're at 80 — closing this gap is the highest-leverage improvement.

Better than 84% of Cloudflare sites See full Cloudflare benchmark →

Technology stack

Babel, on styled-components

10 technologies detected 2 stack layers 1 with CPE identifier Enterprise

Stack Architecture

Framework
Babel Cloudflare Google Font API HSTS HTTP/3 Quill React Webpack core-js 2.6.12
Runtime
styled-components 5.1.1

All Detected Technologies (10)

Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.

Categories JavaScript frameworks, Development Website https://styled-components.com Detected by BeaverCheck

Babel is a free and open-source transcompiler for writing next generation JavaScript.

Categories Miscellaneous Website https://babeljs.io Detected by BeaverCheck
Categories DNS Detected by BeaverCheck Evidence NS record: frank.ns.cloudflare.com

Google Font API is a web service that supports open-source font files that can be used on your web designs.

Categories Font scripts Website https://fonts.google.com/ Detected by BeaverCheck

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

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck

Quill is a free open-source WYSIWYG editor.

Categories Rich text editors Website https://quilljs.com Detected by BeaverCheck

React is an open-source JavaScript library for building user interfaces or UI components.

Categories JavaScript frameworks Website https://reactjs.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Webpack is an open-source JavaScript module bundler.

Categories Miscellaneous Website https://webpack.js.org/ Detected by BeaverCheck Evidence Chunk pattern: https://app-assets.project1content.com/tour/vendors~main.fec81aa5.js

core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.

Categories JavaScript libraries Website https://github.com/zloirock/core-js Detected by BeaverCheck

Observations (3)

Runtime exposed via X-Powered-By header

The X-Powered-By header reveals 'styled-components 5.1.1'. Remove this header in production to reduce information leakage.

→ Security

No build tool detected

A framework (Babel) 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

10 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%2Fmonstersofcock.com)](https://beavercheck.com/sites/monstersofcock.com)
<a href="https://beavercheck.com/sites/monstersofcock.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmonstersofcock.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmonstersofcock.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 (88)

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

2 findings 0h → B (84)
  • · No <main> landmark found
  • · 19 third-party resources (100% of weight)

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

3 findings 7h → B (88)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback