What the analysis checks
We run the site through seven blocks. One — robot access: robots.txt, meta robots, status codes, the sitemap.xml map. Two — speed: Core Web Vitals (LCP, INP, CLS) on mobile and desktop, page weight, redirect chains, image and script sizes. Three — duplicates: repeated content, URL parameters, canonical correctness. Four — internal links: broken, circular, orphan pages with no inbound links. Five — the server: headers, caching, HTTPS, 5xx errors in logs. Six — mobile version and markup. Seven — security: outdated libraries, mixed content. The result is 30–80 findings, each with a description, a priority and a fix instruction.
P1–P3 priorities: what to fix first
Not all errors matter equally, and fixing them "top-down through the list" is a mistake. We rank findings in three levels. P1 — growth blockers: robots.txt closing important sections, pages dropped from the index, critical server errors, LCP above 4 seconds. P2 — significant: duplicates without canonicals, heavy images, broken links in navigation. P3 — hygiene: minor validation notes, outdated libraries without exploits. Every finding in the report carries its level, an impact estimate and the effort required — you can see where the most effect per ruble sits. In our experience 20% of fixes deliver 80% of the effect, and those go first in the plan.
Speed and Core Web Vitals
Speed is a direct commercial factor: every extra half-second of delay eats up to 10% of conversions, and both Yandex and Google rank faster sites higher. We measure Core Web Vitals on real pages and locate the bottlenecks: unoptimized images, render-blocking scripts, missing cache, heavy fonts, surplus widgets. The report names specific files and recommendations — what to compress, what to defer, what to remove. For most sites the list is enough to bring LCP into the green zone within 1–2 developer-days. If you prefer, we implement it ourselves — we run a separate speed-up service with metric-based control.
Who needs a tech analysis
Scenario one — the site "suddenly" lost traffic: the analysis quickly finds the technical cause (index dropout, server errors, a botched redesign). Two — before starting SEO: tech is always the first layer, without it everything else works at half strength. Three — after a redesign or migration: verifying nothing was lost and redirects work. Four — regular hygiene: twice a year a tech analysis catches accumulated problems before they hit rankings. And five — buying or selling a site: an independent assessment of technical state is part of due diligence.
Cost and timelines
Technical analysis — from 12 000 RUB: sites up to 500 pages, report in 3 working days. Up to 5 000 pages — from 20 000 RUB (4–5 days), large portals — from 35 000 RUB (up to 7 days). The price includes crawling, speed measurements, log review (if provided) and a walkthrough session. The express "tech minimum" version (speed + indexing + top-10 errors) — from 6 000 RUB in 1 day — fits a quick assessment before a deal. Fixing the findings is a separate estimate or a support contract; a typical P1 fix package starts at 15 000 RUB.
Why clients order analysis from ZXY
We read tech like engineers, not like a checklist: 12 years of site maintenance and our own development work teach us which findings are real and which are theoretical nitpicks. Every report item is written so a developer can take it and do it — no "improve performance" filler. We verify the result: after rollout, a repeat run shows the metric dynamics. We work with any CMS — Bitrix, WordPress, custom systems. And if you already have an SEO contractor, we hand the report over in a format they can implement without translation.
