nu.edu.kz website review

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

A phone's processor spends 5.5 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

110 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).

6 images could be 6.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 690 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

7 third-party services load with your homepage (YouTube, Google Tag Manager and userway.org and others), adding 1.3 MB and 897 ms of main-thread time.

Your mobile performance score is 66 (desktop: 57). Pages that score under 90 lose visitors before the first paint.

YouTube costs a phone 688 ms of main-thread work and 979 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.

About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

12 long tasks block the main thread while loading, the longest for 291 ms. During a long task the page ignores taps.

The page has 1,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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.

For real visitors the layout shifts by 0.33 (75th percentile). Good is under 0.1.

The page becomes fully interactive after 33.3 s. Good is under 3.8 s.

Visually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “NU Achieves Second Consecutive 100-Place Rise in Global Ran…”.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 316 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

7 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 169 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.2 MB in 137 requests on a phone: images 7.4 MB (26), scripts 1.4 MB (48) and stylesheets 205 KiB (49). Under 2 MB keeps phones on slow connections fast.

img_4506.jpg weighs 6.2 MB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example img_4506.jpg at 3,861 px wide, shown at 60 px. Resized copies would save about 6.6 MB.

5 images (6.7 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.

4 images further down the page (6.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.60 g of CO₂e: 312.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 dropdowns have no label.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 12 elements on the page fail this check, rated serious by axe-core.

11 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: 33 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

29 visible links have no text or label, so screen readers cannot say where they go.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h6 and h1 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 71 characters, so Google will cut it off around 60: “Nazarbayev University - Leading University in Central Asia & Kazakhstan”.

There are 2 <h1> headlines (“NU Hosts High-Level Roundtable on a Key Kazakhsta…” and “Info-Session for NU MSc in Finance program”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 255 pages on nu.edu.kz and 67 external pages.

There is no https://nu.edu.kz/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.

https://nu.edu.kz/kk and https://nu.edu.kz/ru declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://nu.edu.kz/admissions/how-to-apply/foundation-undergraduate/regular-admissions and https://nu.edu.kz/admissions/how-to-apply/masters/regular-admissions-masters all use the title “Regular Admissions - Nazarbayev University”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nu.edu.kz/kk, https://nu.edu.kz/ru, https://nu.edu.kz/admissions/announcements and https://nu.edu.kz/admissions/testimonials have no meta description, so Google writes the search snippet from whatever text it finds.

https://nu.edu.kz/admissions/how-to-apply/foundation-undergraduate/regular-admissions and https://nu.edu.kz/admissions/how-to-apply/masters/regular-admissions-masters use the same meta description. A description written for each page earns more clicks.

https://nu.edu.kz/kk and https://nu.edu.kz/ru 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.

We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.

5 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 384 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

Opening the homepage sets 4 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.