Website review, no card needed
esphere.ru website review
Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 85 checks
This review found 41 issues worth fixing on esphere.ru, 19 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 3.1 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 142 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 123 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 131 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 133 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 115 ms |
| Oct 31, 2026 | 115 ms |
| Nov 7, 2026 | 118 ms |
| Nov 14, 2026 | 127 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
Improve image delivery
7.7 s · 1.9 MB8 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.7 s faster on a phone.
Use efficient cache lifetimes
5.9 s · 1.7 MB25 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused JavaScript
2.4 s · 436 KiBAbout 436 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
2.8 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Mobile performance score: 18
18/100Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
750 ms · 87 KiBAbout 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 714 ms. During a long task the page ignores taps.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (sber247.ru, Yandex Metrica and AdRiver and others), adding 312 KiB and 342 ms of main-thread time.
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.
1 checks passed
Server response: 64 ms
64 msYour server sent the HTML in 64 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.
Real-user CLS: 0.92
0.92For real visitors the layout shifts by 0.92 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 38.8 s
38.8 sYour largest element takes 38.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Теперь мы – Сбер2B Сервисы для электронного документооборот…”.
Time to Interactive: 39.0 s
39.0 sThe page becomes fully interactive after 39.0 s. Good is under 3.8 s.
Speed Index: 14.9 s
14.9 sVisually, the page fills in at 14.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.934
0.934The layout shifts by 0.934 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 800 ms
800 msScripts block taps and scrolling for 800 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 663 ms
663 msReal visitors wait 663 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 157 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.0 MB in 87 requests
7.0 MBYour homepage downloads 7.0 MB in 87 requests on a phone: other files 2.8 MB (20), images 2.8 MB (24) and scripts 1.2 MB (25). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (1.5 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.
1 image far larger than shown
140 KiB1 image is downloaded at several times the size a phone draws it, for example Aktsiya-_-EDO-za-0r_2.png at 1,011 px wide, shown at 273 px. Resized copies would save about 140 KiB.
About 2.0 g of CO₂ per visit
1.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 238.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Images must have alternative text (4 elements)
Images must have alternative text: 4 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”.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 5 failed. 2 mores 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.
Meta description is long (193 characters)
Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
35 internal links, 13 external
The homepage links to 35 pages on esphere.ru and 13 external pages.
6 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Сбер2B ЭДО — ведущий оператор электронного документооборота”.
Canonical URL set
The canonical URL is https://esphere.ru/.
Structured data in place
Structured data found: Organization.
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://esphere.ru/sitemap.xml.
AI search readiness
No llms.txt
There is no https://esphere.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.
2 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.
Other pages
1 page without a meta description
https://esphere.ru/press has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://esphere.ru/company, https://esphere.ru/company/clients, https://esphere.ru/company/career, https://esphere.ru/products/edo, https://esphere.ru/products/edi and https://esphere.ru/products/etrn and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://esphere.ru/products, https://esphere.ru/support, https://esphere.ru/blog, https://esphere.ru/contacts, https://esphere.ru/company/clients and https://esphere.ru/company/kejsy and 7 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.
1 page slow to respond
https://esphere.ru/products/etax took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
10 third-party cookies
10 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
29 of 36 tappable elements near the top are at least 24 px.
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: 1 trust badge. 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.
Only about 49 words
The homepage has only about 49 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
9 other companies contacted
Loading the homepage contacts 9 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 esphere.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Sberkorus Sberkorus Llc
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on esphere.ru, including 18 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.