Skip to content
Scanned
2026-07-29 19:46 UTC
Worker
🇪🇸 Madrid
Duration
5.0m
Vs prev

Global Performance

6/6 locations

High global latency — average 689ms across 6 locations, fastest from Amsterdam (157ms), slowest from Singapore (1710ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.

Spain - Madrid
Full audit
378ms
DNS 68ms · TLS 32ms
Netherlands - Amsterdam
157ms
DNS 6ms · TLS 8ms
United Stated - New York
461ms
DNS 7ms · TLS 95ms
United States - Santa Clara
582ms
DNS 6ms · TLS 149ms
Brazil - Sao Paulo
848ms
DNS 8ms · TLS 214ms
Singapore - Singapore
1710ms
DNS 5ms · TLS 243ms
CDN: No CDN · Avg TTFB: 689ms · Cache: No cache headers

Audit overview

3 categories need attention: Accessibility, and 2 others.

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

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

Cookie '__ddg10_' 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: 3

Cookie '__ddg1_' 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 '__ddg8_' 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 '__ddg9_' 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

₽14,000 investment → ₽221,094/month returns

Investment
₽14 000
4.0 h · 5 findings
Monthly returns
₽221 094
₽2 653 130/yr
Payback
0.1 mo
+18851% Y1
Or — fix only the top 3 findings
₽12 2500.1 mo payback · +21558% 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.
₽3 500 — 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

6 barrier(s) likely increasing bounce by ~37%.

Barriers
6
4 crit 2 warn
Bounce delta
+37pp
added vs baseline
Score
54
D
Speed
2
Trust
2
Usability
2
Content
0
Nav
0
  • Page takes 27.9s to load
    Users abandon at ~3s — you're 25.4s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 5.1s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • 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

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

Remediation cost

₽14,000 4.0 developer hours at ₽3500/hr
Quick wins
₽3,500 4 fixes in ~60 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

₽221 094 / month at risk ~₽2 653 130 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

₽220 921 /mo

+36.8pp bounce · ~3,682 lost visitors/mo

CPC: RUB 60.00

Bandwidth Waste

₽173 /mo

23827.7 MB/mo × 7.273 RUB/GB

  • Optimize transfer: save ~2.4 MB per page load
    Saves ₽173/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

Mobile

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

14.81 s

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

27.91 s

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

5.11 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.423

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

36.33 s

Desktop

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

1.11 s

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

4.79 s

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

870 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.006

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

6.47 s

Categories

6
Avg score 67.8

How you compare

Where this site stands against peers running the same stack.

Cloudflare · 2264 peers
You 70
·
Avg 75
At average
0 50 100
Sustainability P1Compliance P5Performance P25Infrastructure P30Security P67Accessibility P49

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

Better than 6% of Cloudflare sites See full Cloudflare benchmark →
DDoS-Guard · 10 peers
You 70
·
Avg 71
At average
0 50 100
Better than 20% of DDoS-Guard sites See full DDoS-Guard benchmark →

Technology stack

Cloudflare

5 technologies detected 1 stack layers Standard

Stack Architecture

Framework
Cloudflare DDoS-Guard Google Search Console Google Workspace HSTS

All Detected Technologies (5)

Categories DNS Detected by BeaverCheck Evidence NS record: carl.ns.cloudflare.com

DDoS-Guard is a Russian Internet infrastructure company which provides DDoS protection, content delivery network services, and web hosting services.

Categories Security Website https://ddos-guard.net Detected by BeaverCheck
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=YgAUd05F_rt5eZSHmLOEQicarDdll3Y2QU_IgEcmV6E
Categories Email Detected by BeaverCheck Evidence TXT SPF record includes _spf.google.com: v=spf1 include:_spf.google.com -all

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 (Cloudflare) 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%2Fpermsk.stores-apple.com)](https://beavercheck.com/sites/stores-apple.com)
<a href="https://beavercheck.com/sites/stores-apple.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpermsk.stores-apple.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fpermsk.stores-apple.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 · 4h total → projected C (79)

Sprint 1: Quick Wins

+9

Highest ROI — low effort, high impact

4 findings 1h → C (79)
  • · Cookie '__ddg10_' is missing the Secure flag
  • · Cookie '__ddg1_' is missing the Secure flag
  • · Cookie '__ddg8_' is missing the Secure flag
  • · Cookie '__ddg9_' is missing the Secure flag

Sprint 2: Core Fixes

Medium effort, high structural impact

1 findings 3h → C (79)
  • · Content-Security-Policy header is missing

Send Feedback