Skip to content
RU · RUB (₽) · Estimated Dev cost: ₽3,500/hr How jurisdiction is detected
Scanned
2026-04-16 17:49 UTC
Worker
🇺🇸 Santa Clara
Duration
4.2m
Vs prev

Audit overview

Security and Accessibility 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
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 'CID' 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

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Security › Security Headers
Critical: 4

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

23 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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your server takes 996ms to respond — every other performance metric inherits that delay. Addressing the critical issues below would have the most immediate impact on your user trust.
4 security gaps detected — browsers may warn visitors about your site.
1 performance issue — Akamai's research found 53% of mobile users abandon pages over 3s.

Business case

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

Return on investment

₽22,750 investment → ₽129,778/month returns

Investment
₽22 750
6.5 h · 4 findings
Monthly returns
₽129 778
₽1 557 334/yr
Payback
0.2 mo
+6745% Y1
Or — fix only the top 3 findings
₽12 2500.1 mo payback · +12613% 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.
₽1 750 — 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

3 barrier(s) likely increasing bounce by ~22%.

Barriers
3
1 crit 2 warn
Bounce delta
+22pp
added vs baseline
Score
84
B
Speed
0
Trust
2
Usability
1
Content
0
Nav
0
  • 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

₽22,750 6.5 developer hours at ₽3500/hr
Quick wins
₽1,750 2 fixes in ~30 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

₽129 778 / month at risk ~₽1 557 334 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

₽129 776 /mo

+21.6pp bounce · ~2,163 lost visitors/mo

CPC: RUB 60.00

Bandwidth Waste

₽1,91 /mo

263.1 MB/mo × 7.273 RUB/GB

  • Optimize transfer: save ~26 KB per page load
    Saves ₽1,91/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

94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
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.
92
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.

2.19 s

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

2.39 s

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

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

4.04 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.39 s

Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
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.
92
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.

835 ms

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

835 ms

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

0 ms

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

0.030

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

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

835 ms

Categories

6
Avg score 74.8

How you compare

Where this site stands against peers running the same stack.

Nginx · 1033 peers
You 72
·
Avg 75
At average
0 50 100
Accessibility P1Infrastructure P7Sustainability P84Compliance P82Performance P81Security P63

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

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

Technology stack

with Nginx CDN

1 technologies detected 1 stack layers 1 with CPE identifier Minimal

Stack Architecture

CDN
Nginx

All Detected Technologies (1)

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 →

Observations (1)

Minimal technology footprint

Only 1 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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

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 · 6h total → projected B (82)

Sprint 1: Quick Wins

+7

Highest ROI — low effort, high impact

3 findings 0h → C (79)
  • · Cookie 'CID' is missing the Secure flag
  • · HSTS header is missing
  • · 23 third-party resources (100% of weight)

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

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

Send Feedback