Cookie settings

Choose what to allow. The site always stores what it needs; everything else stays off until you turn it on.

Search

Why websites load slowly in Armenia: client site benchmarks

  • 5 November 2026
  • 5 min read
  • Harutyun Elibekyan

The website of a client who came to us for an audit was slow because of page weight and server settings, not because of connection speed or distance to the server. In a mobile lab test, the main content block on the homepage took 3.23 seconds to appear. After the fixes of October 30, 2026, it takes 2.25. Under 2.5 seconds counts as good, and we reached that without changing servers.

What counts as good speed?

The main metric is LCP: the time until the largest content block on the screen appears, usually a heading or an image. According to web.dev, 2.5 seconds or less is good, and over 4.0 seconds is poor. It’s measured at the 75th percentile of real visits, separately for mobile and desktop: three out of four visitors must be within the target.

What kind of internet do your clients have?

Fast. According to DataReportal’s late-2025 figures, based on Ookla tests, the median mobile internet speed in Armenia is 66.66 Mbps and fixed broadband is 71.20 Mbps. As of October 2025, the country had 2.36 million internet users, 80% of the population.

The lab tests used to measure page speed are much harsher. By default, Lighthouse’s mobile profile simulates a 1.6 Mbps connection with 150 ms latency and a CPU slowed down 4x. That’s roughly forty times slower than the median mobile connection in Armenia. So lab numbers show where a page is heavy, not how long a real client in Yerevan waits. The client’s site has no real-user data: there isn’t enough traffic for Google to collect it.

What did the client’s site benchmarks show?

We ran the benchmarks on October 30, 2026, from a computer in Yerevan with Lighthouse 12.8.2, three runs per page; the table shows medians. Mobile profile, simulated throttling.

PageLCP beforeLCP afterFCP beforeFCP afterSize beforeSize after
Homepage3.23 s2.25 s2.26 s1.65 s320 KB265 KB
Service page2.72 s2.12 s2.25 s1.65 s236 KB208 KB

FCP is First Contentful Paint, the time until the first element appears. The Lighthouse score went from 91 to 98 on the homepage and from 94 to 98 on the service page. On desktop, the homepage used to open in 0.70 seconds; now it takes 0.50.

There’s also an unflattering result. I repeated the homepage test with real browser throttling instead of simulated throttling: LCP went from 2.96 to 2.66 seconds, so the gain is smaller, while Total Blocking Time (TBT) barely changed, 212 ms before and 218 ms after. Simulated numbers look better than real ones, and you should know that.

What we fixed

Before the changes, the client’s server delivered the site over HTTP/1.1, compressed files at gzip level 1, and set no cache headers for scripts or fonts. What changed:

  • HTTP/2 was enabled.
  • Compression for scripts, stylesheets, and pages was raised to gzip level 6.
  • Browsers cache scripts and stylesheets for a year and fonts for 30 days.
  • Images are served sized to match their screen space.
  • Dark theme files no longer load for visitors who haven’t turned dark mode on.

Homepage weight dropped by 55 KB, and LCP improved by 0.98 seconds.

Was the server to blame?

No. According to Lighthouse, the server’s response time on the homepage was 9–10 ms, and the server is in Yerevan. Today I measured it again: 15 ms from the start of the request to the first byte, including the secure TLS handshake. How server distance affects speed is covered in our article on hosting in Armenia and abroad.

What slows down Armenian websites besides the server?

For the client’s site, it was the font. Armenian letters need their own set of glyphs, so we split fonts by alphabet: the browser downloads a file only if the page actually uses those letters. On the homepage at a viewport width of 1280 pixels, the browser used to fetch 12 font files totaling 292 KB; now it fetches 4 files totaling 84 KB. That test is from October 2, 2026, and the full breakdown is in our article on Armenian web fonts.

How to test your site in five minutes

Open PageSpeed Insights, paste your URL, and look at the mobile report. It shows two kinds of data. Real-user data comes from the Chrome UX Report for the previous 28 days. If there isn’t enough data for that page, it falls back to site-wide numbers, and if those are missing too, you won’t see real-user data at all, as with the client’s site. Lighthouse lab data shows the causes: it helps you spot oversized images and unnecessary scripts or fonts. Look at three things: LCP, page weight, and the number of requests. If LCP is over 4 seconds, web.dev rates it as poor.

When do you need a developer?

Anyone with an image editor can resize and compress pictures before uploading them. Server configuration (protocol, compression, cache headers) needs server access, and a mistake there hits every visitor at once. Speed is part of my website maintenance service: I check it when I take a site on and then regularly, looking at images, unnecessary scripts, and hosting settings. I have a business interest in this work, but if your mobile LCP is already under 2.5 seconds, don’t overpay.

Sources

  • web.dev: Largest Contentful Paint: 2.5 and 4.0 second thresholds, 75th percentile. Checked November 4, 2026.
  • Lighthouse: network throttling: 150 ms, 1.6 Mbps, CPU 4x slowdown. Checked November 4, 2026.
  • DataReportal: Digital 2026, Armenia: connection speeds, internet users. Checked November 4, 2026.
  • Google PageSpeed Insights: about data: 28-day user data and lab data. Checked November 4, 2026.
  • Internal benchmarks on the website of a client who came to us for an audit, from October 30, 2026 (Lighthouse 12.8.2, headless Chrome, three runs each, median values) and server response time verification on November 4, 2026; server configurations before and after fixes are documented in our changelog.

Related services

  • Website support

    Your site stays online and up to date while you work: monitoring, backups, updates and changes are on us.

Talk to us

Ready to talk about your project?

Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.

Or reach us directly

  • Quick reply to your request or call
  • Languages Armenian, Russian, English
  • Written estimate after the first conversation

Animation is off because your system asks for reduced motion.