Skip to content
Scanned
2026-07-31 16:31 UTC
Worker
🇪🇸 Madrid
Duration
5.0m
Vs prev

Global Performance

6/6 locations

High global latency — average 597ms across 6 locations, fastest from New York (179ms), slowest from Singapore (1187ms). No CDN detected. Cache-Control disables caching (no-store). 4 locations above the 500ms target.

Spain - Madrid
Full audit
661ms
DNS 33ms · TLS 29ms
United Stated - New York
179ms
DNS 7ms · TLS 8ms
United States - Santa Clara
216ms
DNS 53ms · TLS 23ms
Netherlands - Amsterdam
643ms
DNS 4ms · TLS 11ms
Brazil - Sao Paulo
696ms
DNS 116ms · TLS 122ms
Singapore - Singapore
1187ms
DNS 6ms · TLS 176ms
CDN: No CDN · Avg TTFB: 597ms · Cache: no-store

Audit overview

Accessibility and Compliance need attention; the other categories are in good shape.

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
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

'unsafe-eval' found in script source

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Security › Content Security Policy
Critical: 2

'unsafe-inline' found in script source

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Security › Content Security Policy
Critical: 3

Cookie 'PHPSESSID' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 4

Cookie 'SRV' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 5

Cookie 'random_sfw_tour' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
What fixing these means. 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.
5 security gaps detected — browsers may warn visitors about your site.

Business case

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

Return on investment

€1,084 investment → €10,123/month returns + EUR 120,000,000 risk avoided

Investment
€1.084
12.8 h · 5 findings
Monthly returns
€10.123
€121.471/yr
Payback
0.1 mo
+11108% Y1
Regulatory risk avoided EUR 120.000.000
Or — fix only the top 3 findings
€1.0410.1 mo payback · +11566% 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.
€64 — 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

5 barrier(s) likely increasing bounce by ~34%.

Barriers
5
3 crit 2 warn
Bounce delta
+34pp
added vs baseline
Score
64
C
Speed
1
Trust
2
Usability
2
Content
0
Nav
0
  • Page takes 4.2s to load
    Users abandon at ~3s — you're 1.7s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Severe layout shift during page load
    Users mis-click when content jumps — converting intent into frustration
    → Reserve space for images, ads, and embeds with explicit width/height
  • 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">
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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

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

Remediation cost

€1,084 12.8 developer hours at €85/hr
Quick wins
€64 3 fixes in ~45 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

€7.575 / month at risk ~€90.904 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€120.000.000

ePrivacy DirectiveAVG
  • No privacy policy link detected
    AVG: EUR 10.000 – EUR 20.000.000
  • 2 non-essential cookie(s) set without consent banner
    AVG: EUR 5.000 – EUR 10.000.000
  • 2 non-essential cookie(s) set without consent banner
    AVG: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€7.575 /mo

+34.4pp bounce · ~3,443 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,77 /mo

10340.2 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.0 MB per page load
    Saves €0,77/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 5 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

Categories

6
Avg score 72.0

How you compare

Where this site stands against peers running the same stack.

HSTS · 2691 peers
You 73
·
Avg 75
At average
0 50 100
Compliance P9Infrastructure P18Sustainability P34Security P61Performance P59Accessibility P46

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

Better than 27% of HSTS sites See full HSTS benchmark →
Nginx · 1024 peers
You 73
·
Avg 75
At average
0 50 100
Compliance P8Infrastructure P25Security P74Sustainability P40Performance P58Accessibility P52

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

Better than 35% of Nginx sites See full Nginx benchmark →

Technology stack

HSTS, on PHP, with Nginx CDN

3 technologies detected 3 stack layers 2 with CPE identifier Standard

Stack Architecture

Framework
HSTS
Runtime
PHP
CDN
Nginx

All Detected Technologies (3)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

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

Observations (1)

No build tool detected

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

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%2Fmomlover.com)](https://beavercheck.com/sites/momlover.com)
<a href="https://beavercheck.com/sites/momlover.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmomlover.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmomlover.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 · 13h total → projected B (81)

Sprint 1: Quick Wins

+7

Highest ROI — low effort, high impact

3 findings 1h → B (80)
  • · Cookie 'PHPSESSID' is missing the Secure flag
  • · Cookie 'SRV' is missing the Secure flag
  • · Cookie 'random_sfw_tour' is missing the Secure flag

Sprint 3: Strategic Improvements

+1

Higher effort, long-term payoff

2 findings 12h → B (81)
  • · 'unsafe-eval' found in script source
  • · 'unsafe-inline' found in script source

Send Feedback