Website review, no card needed
vbr.ru website review
Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 89 checks
This review found 35 issues worth fixing on vbr.ru, 13 of them high impact, across 89 checks. The most urgent: reduce initial server response time. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 197 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 193 ms |
| Jun 20, 2026 | 194 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 197 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 189 ms |
| Sep 12, 2026 | 191 ms |
| Sep 19, 2026 | 192 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 183 ms |
| Oct 24, 2026 | 185 ms |
| Oct 31, 2026 | 192 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
Reduce initial server response time
1.0 sReduce initial server response time. Google estimates savings of 1.0 s on a phone.
Document request latency
1.0 sThe HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (viberu.ru, Google Tag Manager and Yandex Metrica and others), adding 1.5 MB and 576 ms of main-thread time.
Reduce unused CSS
600 ms · 107 KiBAbout 107 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 66 KiB8 files are served with short cache lifetimes, so returning visitors download them again (66 KiB).
viberu.ru adds 301 ms
301 msviberu.ru costs a phone 301 ms of main-thread work and 1.2 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
2,836 HTML elements
The page has 2,836 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.1 s
1.1 sYour server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
250 ms · 228 KiB6 images could be 228 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 548 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.1 s
9.1 sThe page becomes fully interactive after 9.1 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 197 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 547 ms
547 msReal visitors wait 547 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 196 ms
196 msScripts block the page for only 196 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
app.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 64.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.9 MB in 104 requests
1.9 MBYour homepage downloads 1.9 MB in 104 requests on a phone: images 750 KiB (44), scripts 643 KiB (31) and other files 344 KiB (25). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
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 (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “Выберу.ру — финансовый маркетплейс банковских, страховых и инвестиционных продуктов и усл…”.
Meta description is long (186 characters)
Your meta description is 186 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
464 internal links, 52 external
The homepage links to 464 pages on vbr.ru and 52 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Персональный подбор финансовых решений”.
Canonical URL set
The canonical URL is https://www.vbr.ru/.
Structured data in place
Structured data found: Organization and WebPage.
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://www.vbr.ru/sitemap.xml.
AI search readiness
No llms.txt
There is no /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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (475 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages with very little text
/regiony and /pds 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 199 found) and read each the way a search engine does.
7 checks passed
Linked pages load
2 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 2 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.vbr.ru/api/analytics/pixel/mobileapp?serve=316926503667465045&siteSection=Drugoe.
10 small tap targets
10 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 454 words of copy
The homepage carries about 454 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
7 other companies contacted
Loading the homepage contacts 7 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 vbr.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
- HLL
Company
- Employees
- 120
- Founded
- 2015
- Headquarters
- Russia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on vbr.ru, including 13 speed issues, 2 SEO issues and 5 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.