Website review, no card needed
ncfu.ru website review
Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 81 checks
This review found 33 issues worth fixing on ncfu.ru, 10 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 106 ms |
| Jun 20, 2026 | 106 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 114 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 118 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 112 ms |
| Nov 7, 2026 | 111 ms |
| Nov 14, 2026 | 110 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
900 ms · 1.3 MB11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
80 ms · 290 KiBAbout 290 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 80 ms faster on a phone.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 610 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
205 KiBAbout 205 KiB of CSS is downloaded but never applied on this page.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Yandex Metrica and mail.ru), adding 115 KiB and 158 ms of main-thread time.
Document request latency
111 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Use efficient cache lifetimes
73 KiB5 files are served with short cache lifetimes, so returning visitors download them again (73 KiB).
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 143 ms
143 msYour server sent the HTML in 143 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: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.4 s
10.4 sThe page becomes fully interactive after 10.4 s. Good is under 3.8 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Гордость Отечества”.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 955 ms
955 msReal visitors wait 955 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, 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).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 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.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
1 image over 500 KB
skfu_banner_721x961.png weighs 496 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.4 MB in 54 requests
3.4 MBYour homepage downloads 3.4 MB in 54 requests on a phone: images 2.4 MB (28), scripts 570 KiB (9) and stylesheets 219 KiB (4). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (2.0 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.
An image on the first screen is lazy-loaded
skfu_banner_721x961.png 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 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.1 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
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
ARIA role should be appropriate for the element (17 elements)
ARIA role should be appropriate for the element: 17 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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 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.
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.
171 internal links, 72 external
The homepage links to 171 pages on ncfu.ru and 72 external pages.
6 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Контактная информация, Образование, учёные степени и учёные звания, Дополнительное образование, Повышение квалификации,…”.
One H1 headline
Your main headline reads: “«Северо-Кавказский федеральный университет»”.
Title: 41 characters
Your title is a healthy 41 characters: “Северо-Кавказский федеральный университет”.
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://ncfu.ru/sitemap.xml.
AI search readiness
robots.txt blocks 1 AI answer engine crawler
1 of 6Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://ncfu.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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
Other pages
14 pages with very little text
https://ncfu.ru/abiturientu/priemnaya-kampaniya-2026, https://ncfu.ru/university, https://ncfu.ru/university/rukovodstvo, https://ncfu.ru/university/uchenyy-sovet, https://ncfu.ru/university/zakupki and https://ncfu.ru/university/bezopasnost and 8 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.
3 pages slow to respond
https://ncfu.ru/university/nablyudatelnyy-sovet-skfu, https://ncfu.ru/university/uchenyy-sovet and https://ncfu.ru/university/zakupki took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 142 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
127 small tap targets
127 of 197 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
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: 2 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.
Only about 74 words
The homepage has only about 74 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.
2 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: 11 phone links and 1 email 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
4 other companies contacted
Loading the homepage contacts 4 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 ncfu.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
- PJSC "Vimpelcom"
Company
- Founded
- 2012
- Headquarters
- Stavropol
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on ncfu.ru, including 11 speed issues, 3 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.