Website review, no card needed
ranepa.ru website review
Visit site (opens in a new tab)Reviewed 17 November 202657 issues · 94 checks
This review found 57 issues worth fixing on ranepa.ru, 24 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.6 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 143 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 141 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 141 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 151 ms |
| Nov 7, 2026 | 383 ms |
| Nov 14, 2026 | 383 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
Use efficient cache lifetimes
4.7 s · 17.1 MB166 files are served with short cache lifetimes, so returning visitors download them again (17.1 MB).
Render-blocking requests
5.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Reduce unused JavaScript
2.2 s · 719 KiBAbout 719 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Reduce unused CSS
1.1 s · 1.3 MBAbout 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Document request latency
1.1 sThe HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.0 sReduce initial server response time. Google estimates savings of 1.0 s on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,184 HTML elements
The page has 4,184 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.2 MB12 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
5 third-party services on the page
5 third-party services load with your homepage (yastatic-net.ru, Yandex Metrica and mail.ru and others), adding 795 KiB and 705 ms of main-thread time.
yastatic-net.ru adds 440 ms
440 msyastatic-net.ru costs a phone 440 ms of main-thread work and 426 KiB 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.
Legacy JavaScript
300 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 332 ms. During a long task the page ignores taps.
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.
Minify JavaScript
150 ms · 46 KiB46 KiB could be saved by minifying JavaScript.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
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.
First Contentful Paint: 13.4 s
13.4 sThe first text or image appears after 13.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 15.2 s
15.2 sYour largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Приходите, чтобы увидеть ведущий вуз страны изнутри, познак…”.
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 222% slower for real visitors
+222%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 120 ms to 383 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 504 ms
504 msScripts block taps and scrolling for 504 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 184 ms
184 msReal visitors wait 184 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.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 19.6 MB in 208 requests
19.6 MBYour homepage downloads 19.6 MB in 208 requests on a phone: images 16.2 MB (140), HTML 1.7 MB (2) and scripts 1.1 MB (26). Under 2 MB keeps phones on slow connections fast.
21 images far larger than shown
2.8 MB21 images are downloaded at several times the size a phone draws them, for example n1701xjz6fo52s69dzbvbdt6xdln1clf.jpg at 2,560 px wide, shown at 292 px. Resized copies would save about 2.8 MB.
1 image over 500 KB
n1701xjz6fo52s69dzbvbdt6xdln1clf.jpg weighs 533 KiB. On a phone connection a single image that size takes seconds.
23 images below the first screen load straight away
23 images further down the page (5.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
18 images in older formats
18 images (4.8 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 5.5 g of CO₂ per visit
5.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.55 g of CO₂e: 666.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (19 elements)
Alternative text of images should not be repeated as text: 19 elements on the page fail this check, rated minor by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “РАНХиГС - обучение в Москве | Официальный сайт Президентской академии”.
Meta description is long (235 characters)
Your meta description is 235 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 3 (line 3 )”.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
207 internal links, 131 external
The homepage links to 207 pages on ranepa.ru and 131 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Это простопраздниккакой-то”.
Canonical URL set
The canonical URL is https://www.ranepa.ru/.
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.ranepa.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://www.ranepa.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 page without an H1
https://www.ranepa.ru/mfc has no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.ranepa.ru/olimpiada-ya-professional, https://www.ranepa.ru/ballno-reytingovaya-sistema-v-akademii, https://www.ranepa.ru/akademicheskiy-otpusk, https://www.ranepa.ru/psikhologicheskaya-sluzhba-rankhigs, https://www.ranepa.ru/molodezhnaya-politika and https://www.ranepa.ru/sport-v-prezidentskoy-akademii and 3 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 94 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
17 small tap targets
17 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
9 third-party cookies
9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 139 words
The homepage has only about 139 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
1 short form
A short form (1 field at most) is right on the homepage.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
8 other companies contacted
Loading the homepage contacts 8 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 ranepa.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
- Stormnetworks
Company
- Founded
- 1921
- Headquarters
- Troparyovo-Nikulino District
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on ranepa.ru, including 25 speed issues, 4 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.