Performance Core Web Vitals Kazakhstan

A slow website costs more than development: the real price of poor performance in 2026

May 20, 2026 10 min read Amanix Studio

Open your website right now on a mobile phone. Time how long it takes from tap to full page load. If it's 1–2 seconds — great, this article isn't for you. If it's 3–5 seconds — you have a problem, and it's costing your business money every day. If it's more than 5 seconds — you're losing not just occasional leads, but half of all potential customers, every single day, without even knowing it.

In 2026, website loading speed is not a "programmer's technical whim." It's a concrete factor directly affecting revenue, Google rankings, brand perception, and advertising costs.

The math of losses from a slow website

Google has published data on how loading speed affects user behavior. Here's the picture:

1 second
9%
3 seconds
32%
5 seconds
90%
6+ seconds
~100%

Probability of user bounce depending on page load time

In commercial terms: each second of delay reduces conversion by roughly 7%. This is data from Amazon, Walmart, Booking — large services that publicly shared results from their own experiments.

Say a website gets 5,000 unique visitors per month with a 3% conversion rate (150 leads). Average order value — 50,000 tenge. That's 7.5 million per month. If the site loads in 5 seconds instead of 1.5 — that's a 3.5-second difference. At minus 7% per second, you lose 24% of conversions. That's 36 leads per month and 1.8 million tenge in lost revenue. Over a year — 21.6 million tenge. Simply because the site is slow.

And this doesn't account for indirect effects: lower Google rankings due to poor Core Web Vitals, higher cost-per-click due to reduced "landing page quality" in Google Ads and Yandex Direct, and fewer returning visitors.

Mobile traffic: where Kazakhstani websites lose most of their customers

70%+
of traffic to commercial websites in Kazakhstan comes from mobile devices. For food delivery, taxis, e-commerce — up to 85–90%. Yet most Kazakhstani websites are optimized for desktop.

What's typical of a "responsive but not mobile-first" website:

  • Heavy images not optimized for small screens. Load times of 5–10 seconds.
  • Forms aren't optimized: fields too small for fingers, no automatic keyboard switching for field type.
  • Header and footer take up a third of the screen, barely any content is visible.
  • Buttons placed awkwardly — difficult to tap with a finger.

A parallel problem: mobile networks. Outside of Kazakhstan's city centers, 4G coverage is unstable and 5G is just being rolled out. A site that loads in 3 seconds on good WiFi takes 8–10 seconds on a slow mobile network. If the architecture isn't optimized — it's a disaster.

Why Tilda and WordPress are slow

Tilda
The site is served from servers physically located in Russia. Every request from a Kazakhstani user adds 50–150 ms of network latency. Tilda loads universal CSS and JS files for all possible block types on every page — regardless of whether you use them or not. Dozens of unnecessary HTTP requests and hundreds of kilobytes of excess assets.
WordPress
Each request triggers dozens of database queries. Without caching — it's slow. Cache must be invalidated on changes, caching plugins conflict with each other. Most WP themes load fonts, jQuery, slider scripts, and a dozen other assets that aren't needed on the specific page.
Megagroup, Wix, uKit
Slightly faster than Tilda, slightly slower than WordPress — but on average these are slow sites with the same typical issues: unnecessary HTTP requests, unoptimized images, no lazy loading.

Core Web Vitals: measurable speed that affects Google

Google introduced three key metrics that affect search rankings. You can check them for free via Google PageSpeed Insights. On most Tilda and WordPress sites without serious optimization — all three are in the red zone.

  • LCP (Largest Contentful Paint) — time to render the largest visible element. Goal: under 2.5 seconds.
  • INP (Interaction to Next Paint) — delay between user action and site response. Goal: under 200 ms.
  • CLS (Cumulative Layout Shift) — visual stability: when images load and shift the text. Goal: under 0.1.

What actually speeds up a website in 2026

1
Server-Side Rendering (SSR)
The server delivers ready-made HTML with content. Users see content instantly without waiting for JavaScript. SEO works perfectly.
2
Image optimization
Conversion to WebP (25–35% lighter than JPEG at the same quality), generating multiple sizes for different screens, lazy loading only when scrolled into view.
3
Minification and gzip compression
CSS, JS, and HTML are compressed and minified at build time. Gzip compression saves 60–80% of file size for text assets.
4
Critical CSS inlined
CSS for the first screen is embedded directly in HTML. The rest loads asynchronously. Eliminates page jumps during load — improves CLS.
5
Multi-level caching
Browser cache for static assets set to one year. Redis for frequently-requested data. CDN for static assets so users in Almaty and Astana get resources from the nearest servers.
6
HTTP/2 or HTTP/3
Modern protocols allow loading many files in parallel over a single connection, which dramatically speeds up pages with dozens of assets.
7
Code splitting
JavaScript is split into separate bundles. Each page loads only the code it needs. The homepage doesn't drag in checkout page logic.
8
Prefetch for key resources
The browser starts loading resources needed for the next page in advance. When the user clicks a link — the page appears almost instantly.
9
Server localization
The server is physically located in Kazakhstan or geographically nearby data centers. Eliminates 50–150 ms of network latency on every request.
10
Bundle size budget
Target JavaScript size stays below a defined threshold (200–300 KB). Keeps development disciplined and prevents the site from accumulating unnecessary code over time.

How to check your website speed right now

Google PageSpeed Insights
pagespeed.web.dev
Enter a URL — get a Performance, SEO, Accessibility score. Below 80 on desktop or 60 on mobile means there are issues.
WebPageTest
webpagetest.org
Detailed analysis: waterfall diagram with load times for each resource. Pinpoints specific bottlenecks.
Chrome Lighthouse
F12 → Lighthouse tab
Built into the browser. The same report as PageSpeed Insights, but locally — no data sent to external servers.
GTmetrix
gtmetrix.com
Alternative tool with its own metrics and measurement history — convenient for monitoring trends over time.

How speed affects advertising costs

A point many overlook. Google Ads and Yandex Direct use "landing page quality" as one of the factors in cost-per-click. The worse your Core Web Vitals and user experience — the more expensive every paid ad click becomes.

×2
If your site loads in 5 seconds and a competitor's loads in 2 seconds — the competitor pays 1.5–2× less per click. A business with a 1 million tenge monthly budget overpays 300–500 thousand tenge just due to "landing page quality" on a slow site.
About the studio

Speed is our baseline standard, not an option

Amanix has been doing custom website development for businesses in Kazakhstan since 2023. What we do by default on every project:

  • SSR via Nuxt 3 for all public pages
  • Image optimization with auto-conversion to WebP and lazy loading
  • Minification and gzip compression of CSS, JS, HTML
  • Code splitting by page
  • Redis caching for frequently-requested data
  • HTTP/2 and HTTP/3 in server configuration
  • Servers in Kazakhstan data centers for minimal network latency
85+
PageSpeed on desktop for our projects
75+
PageSpeed on mobile devices
×2-3
faster than typical Tilda / WordPress solutions