Website review, no card needed
ancor.ru website review
Visit site (opens in a new tab)Reviewed 30 October 202636 issues · 78 checks
This review found 36 issues worth fixing on ancor.ru, 14 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 122 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 156 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 136 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 115 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
3.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused JavaScript
1.6 s · 383 KiBAbout 383 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Improve image delivery
2.9 MB21 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
280 ms · 76 KiBAbout 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
Legacy JavaScript
200 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Yandex Metrica and ancor-group.com), adding 114 KiB and 180 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
112 KiB9 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 363 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Real-user TTFB: 849 ms
849 msReal visitors wait 849 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.7 s
3.7 sYour largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Наша работа — находить решения, чтобы каждый добивался лучш…”. Most of its time is element render delay (9.0 s).
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.13
0.13The layout shifts by 0.13 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 117 ms
117 msScripts block the page for only 117 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.5 MB in 59 requests
4.5 MBYour homepage downloads 4.5 MB in 59 requests on a phone: images 3.7 MB (40), scripts 551 KiB (6) and fonts 196 KiB (3). Under 2 MB keeps phones on slow connections fast.
21 images below the first screen load straight away
21 images further down the page (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
18 images in older formats
18 images (3.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
73 text elements with low contrast
73 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
210 internal links, 11 external
The homepage links to 210 pages on ancor.ru and 11 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Лидер в области рекрутмента, аутсорсинга HR и других бизнес функций, кадрового консалтинга. Лучшие вакансии рынка труда…”.
Title: 40 characters
Your title is a healthy 40 characters: “ANCOR – движущая сила кадровой индустрии”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://ancor.ru/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://ancor.ru/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
1 linked page is broken
Your homepage links to https://ancor.ru/vacancy/reviews, which answers with an error. Visitors hit a dead end and search engines drop it.
6 pages without a meta description
https://ancor.ru/vacancy/cv-constructor, https://ancor.ru/services/consulting/career_new, https://ancor.ru/vacancy/advice, https://ancor.ru/vacancy/career-guide, https://ancor.ru/about/work-in-ancor and https://ancor.ru/vacancy/principles have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://ancor.ru/about/work-in-ancor has no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://ancor.ru/vacancy, https://ancor.ru/vacancy/catalog, https://ancor.ru/salarydata, https://ancor.ru/services/consulting/career_new, https://ancor.ru/vacancy/advice and https://ancor.ru/vacancy/career-guide and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 116 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
34 small tap targets
34 of 62 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 8-field form
Your longest form asks for 8 fields (6 required). Every extra field lowers completion.
Only about 90 words
The homepage has only about 90 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Yandex Metrica (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ancor.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Stormnetworks
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on ancor.ru, including 11 speed issues, 3 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.