Skip to content
RU · RUB (₽) · Estimated Dev cost: ₽3,500/hr How jurisdiction is detected
Scanned
2026-05-02 15:03 UTC
Worker
🇺🇸 Santa Clara
Duration
2.9m
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 446ms across 6 locations, fastest from Amsterdam (99ms), slowest from Singapore (1465ms). No CDN detected. Cache-Control header is missing. 1 location above the 500ms target.

United States - Santa Clara
Full audit
475ms
DNS 5ms · TLS 5ms
Spain - Madrid
234ms
DNS 64ms · TLS 30ms
Netherlands - Amsterdam
99ms
DNS 2ms · TLS 5ms
United Stated - New York
164ms
DNS 3ms · TLS 10ms
Singapore - Singapore
1465ms
DNS 113ms · TLS 3ms
Brazil - Sao Paulo
241ms
DNS 3ms · TLS 3ms
CDN: No CDN · Avg TTFB: 446ms · Cache: No cache headers

Audit overview

5 categories need attention: Performance, and 4 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

Cookie 'selected_locale' 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
Critical: 5

Page weighs 15.9 MB (6.0 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
What fixing these means. Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 26.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. The 4 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. 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.
Your LCP is 26.7s — 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

₽22,750 investment → ₽218,378/month returns

Investment
₽22 750
6.5 h · 4 findings
Monthly returns
₽218 378
₽2 620 541/yr
Payback
0.1 mo
+11419% Y1
Or — fix only the top 3 findings
₽12 2500.1 mo payback · +21292% 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

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

Barriers
10
4 crit 6 warn
Bounce delta
+36pp
added vs baseline
Score
42
D
Speed
2
Trust
2
Usability
2
Content
3
Nav
1
  • Page takes 26.7s to load
    Users abandon at ~3s — you're 24.2s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 6.4s
    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
  • 3 form field(s) without a label
    Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
    → Associate every input with a visible <label for="…">; add autocomplete attributes
  • 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

₽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

₽218 378 / month at risk ~₽2 620 541 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

₽218 240 /mo

+36.4pp bounce · ~3,637 lost visitors/mo

CPC: RUB 60.00

Bandwidth Waste

₽138 /mo

18970.3 MB/mo × 7.273 RUB/GB

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

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

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

26.69 s

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

6.39 s

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

0.683

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

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

41.03 s

Desktop

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

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

3.38 s

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

1.23 s

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.

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

12.63 s

Categories

8
Avg score 66.2

How you compare

Where this site stands against peers running the same stack.

Google Search Console · 3868 peers
You 65
·
Avg 73
-8 below average
0 50 100
Performance P1Security P1Sustainability P3Accessibility P7Content P10SEO P11Compliance P16Infrastructure P62

Top 10% of Google Search Console sites score 89+ on Performance; you're at 66 — closing this gap is the highest-leverage improvement.

hCaptcha · 28 peers
You 65
·
Avg 75
-10 below average
0 50 100

Technology stack

Google Search Console

3 technologies detected 1 stack layers 1 with CPE identifier Standard

Stack Architecture

Framework
Google Search Console Sentry hCaptcha 1

All Detected Technologies (3)

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=PHuE8i-qvd5hkj5Lx_bHreAhMdaA19ZNO3tLYZ4hYY0

Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.

Categories Issue trackers Website https://sentry.io/ Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

hCaptcha is an anti-bot solution that protects user privacy and rewards websites.

Categories Security Website https://www.hcaptcha.com Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (Google Search Console) 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%2Fwww.avito.ru)](https://beavercheck.com/results/f893a3e2-ff84-4148-840a-c26527e540ac)
<a href="https://beavercheck.com/results/f893a3e2-ff84-4148-840a-c26527e540ac"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.avito.ru" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.avito.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 C (75)

Sprint 1: Quick Wins

+7

Highest ROI — low effort, high impact

3 findings 0h → C (72)
  • · Page weighs 15.9 MB (6.0 MB transferred)
  • · Cookie 'selected_locale' is missing the Secure flag
  • · HSTS header is missing

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

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

Send Feedback