Skip to content
https://svoyaaptechka.ru Export & share
RU · RUB (₽) · Estimated Dev cost: ₽3,500/hr How jurisdiction is detected
Scanned
2026-05-23 23:40 UTC
Worker
🇪🇸 Madrid
Duration
53.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 728ms across 6 locations, fastest from Amsterdam (229ms), slowest from Sao Paulo (1190ms). No CDN detected. Cache-Control disables caching (no-store). 4 locations above the 500ms target.

Spain - Madrid
Full audit
280ms
DNS 84ms · TLS 63ms
Netherlands - Amsterdam
229ms
DNS 93ms · TLS 44ms
United Stated - New York
601ms
DNS 234ms · TLS 110ms
United States - Santa Clara
974ms
DNS 441ms · TLS 175ms
Singapore - Singapore
1091ms
DNS 487ms · TLS 199ms
Brazil - Sao Paulo
1190ms
DNS 515ms · TLS 223ms
CDN: No CDN · Avg TTFB: 728ms · Cache: no-store

Audit overview

Compliance needs attention; the rest of the 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

9 button(s) with no accessible text

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Accessibility › Link & Button Quality
Warning: 2

1 font preload(s) missing `crossorigin` -- font will be downloaded twice

Performance issues directly impact user engagement and conversion rates.

Performance › Resource Hints
Warning: 3

116 inline style attribute(s) detected

Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.

Security › CSP Inline-Style Readiness
Warning: 4

6 link(s) open in a new tab without rel=noopener

target="_blank" without rel="noopener" lets the destination tab navigate the original via window.opener -- a reverse-tabnabbing phishing primitive.

Security › Cross-Origin Tab Safety
Warning: 5

6 render-blocking stylesheet(s) -- recommended: <=3

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Performance › CSS Performance Depth
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 5.8s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your audience reach.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 5.8s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
2 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

₽23,625 investment → ₽310,878/month returns

Investment
₽23 625
6.8 h · 4 findings
Monthly returns
₽310 878
₽3 730 535/yr
Payback
0.1 mo
+15691% Y1
Or — fix only the top 3 findings
₽22 7500.1 mo payback · +16298% 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.
₽2 625 — 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

4 barrier(s) likely increasing bounce by ~23%.

Barriers
4
2 crit 2 warn
Bounce delta
+23pp
added vs baseline
Score
74
B
Speed
1
Trust
1
Usability
0
Content
0
Nav
2
  • Page takes 5.8s to load
    Users abandon at ~3s — you're 3.3s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 41 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab
  • 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
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Remediation cost

₽23,625 6.8 developer hours at ₽3500/hr
Quick wins
₽2,625 2 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

₽247 417 / month at risk ~₽2 969 010 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

₽247 386 /mo

+23.5pp bounce · ~2,346 lost visitors/mo

CPC: RUB 105.45

Bandwidth Waste

₽31 /mo

4314.6 MB/mo × 7.273 RUB/GB

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

74
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
85
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.01 s

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

5.81 s

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

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

4.64 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.06 s

Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
90
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
85
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.

332 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.066

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

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

849 ms

Categories

8
Avg score 82.4

How you compare

Where this site stands against peers running the same stack.

Cart Functionality · 550 peers
You 84
·
Avg 73
+11 above average
0 50 100
Compliance P1Security P99Accessibility P98Performance P96Sustainability P84Infrastructure P33Content P34SEO P61

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

Better than 98% of Cart Functionality sites See full Cart Functionality benchmark →
Debian · 15 peers
You 84
·
Avg 74
+10 above average
0 50 100
Better than 93% of Debian sites See full Debian benchmark →

Technology stack

Debian, on Apache/PHP, hosted on Apache HTTP Server

8 technologies detected 5 stack layers 3 with CPE identifier Complex

Stack Architecture

Ecommerce
Cart Functionality
Framework
Debian HSTS Open Graph Priority Hints
Runtime
PHP
Server
Apache 2.4.67
Hosting
Apache HTTP Server 2.4.67

All Detected Technologies (8)

Categories Server Website https://httpd.apache.org Detected by BeaverCheck Evidence Server header: Apache/2.4.67 (Debian)

Apache is a free and open-source cross-platform web server software.

Categories Web servers Website https://httpd.apache.org/ Detected by BeaverCheck
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 →

Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.

Categories Ecommerce Website https://www.wappalyzer.com/technologies/ecommerce/cart-functionality Detected by BeaverCheck

Debian is a Linux software which is a free open-source software.

Categories Operating systems Website https://debian.org 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

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck

Observations (3)

Server version exposed in headers

The Server header reveals 'Apache 2.4.67'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.

→ Security

No build tool detected

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

8 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%2Fsvoyaaptechka.ru)](https://beavercheck.com/results/e962dd87-5e08-4ff0-94fe-2436fa682232)
<a href="https://beavercheck.com/results/e962dd87-5e08-4ff0-94fe-2436fa682232"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsvoyaaptechka.ru" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsvoyaaptechka.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 · 7h total → projected A (90)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 1h → B (88)
  • · 9 button(s) with no accessible text
  • · 6 render-blocking stylesheet(s) -- recommended: <=3
  • · 6 link(s) open in a new tab without rel=noopener

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

2 findings 6h → A (90)
  • · 1 font preload(s) missing `crossorigin` -- font will be downloaded twice
  • · 116 inline style attribute(s) detected

Send Feedback