The six-second web: how slow Baltic websites really are on a phone
The median Baltic homepage takes about six seconds to show its main content on a phone. Google's bar for good is 2.5 seconds. Two thirds of sites rate poor.
“Why is my website slow” is one of the questions owners actually type into Google, usually right after watching their own homepage crawl onto a phone screen in a café. For the Baltics, we can now answer with data instead of anecdote: we measured the speed of the region’s web, country by country, as part of the Baltic Web Audit, our near-census of the Latvian, Estonian and Lithuanian web in August 2026.
In short
The median Baltic homepage takes about six seconds to show its main content on a phone: 6.60 seconds in Latvia, 6.33 in Lithuania, 5.73 in Estonia. Google’s published bar for a good mobile experience is 2.5 seconds, and over 4 seconds counts as poor. Fewer than one site in five clears the good bar in Latvia and Lithuania (15% and 18%; Estonia manages 22%), and in every country a clear majority of sites (71% in Latvia, 68% in Lithuania, 63% in Estonia) sit in the poor band. If your site is slow, it is not unusual. It is the regional default, which is exactly why fixing it is worth so much.
What “six seconds” measures
The number is Largest Contentful Paint, or LCP: the time from tapping a link to the page’s main content actually appearing. Not the spinner, not the background colour, the thing you came to see. Google times it on real pages, publishes the thresholds, and states in its page experience documentation that Core Web Vitals, of which LCP is the largest, are used by its ranking systems. If you want the full tour of the timing metrics and how they relate, we wrote a plain-language guide to TTFB, FCP and LCP; this article stays with the one number Google grades hardest.
The thresholds are worth restating because everything below hangs on them: Google’s own definition is 2.5 seconds or less for good, anything over 4.0 seconds is poor, and the space between is “needs improvement”.
The numbers, country by country
These are not figures from a handful of test sites. They rest on 44,279 PageSpeed measurements in Latvia, 69,021 in Estonia and 80,917 in Lithuania.
Latvia is the slowest of the three: a median mobile LCP of 6.60 seconds, with only 15% of sites clearing Google’s good bar and 71% rated poor. Lithuania is barely better at 6.33 seconds median, 18% good, 68% poor. Estonia leads, as it does on most measurements in the audit, and still posts a median of 5.73 seconds with 63% of its sites in the poor band.
Read that back slowly: in every Baltic country, the typical site takes more than twice as long as Google’s good threshold, and the poor band is not a fringe of neglected sites, it is the majority.
There is one twist that saves the region from a failing report card, and we would be telling the story wrong to leave it out. Slowness is the Baltic web’s only failing grade. The median layout-stability score is approximately zero shift in every country, meaning Baltic pages do not jump around under your finger, and the average best-practices, accessibility and technical SEO scores from the same measurement runs are all comfortably in the eighties and nineties. The region’s web is stable and standards-clean. It is just slow, and slow precisely where its visitors are: on phones. Part of the reason is that many of these sites are genuinely fast on the desktop monitors they were built and approved on; the desktop-to-mobile gap is its own finding, and the report’s speed chapter tells it in full.
Why sites end up here
Six seconds is rarely one villain. Across the slow sites we are asked to rescue, the same short list keeps appearing:
- Images shipped at full size. A 4,000-pixel photo scaled down by the browser looks identical to a properly sized one and costs many times the download. This is the single most common cause and the cheapest to fix.
- A theme or builder that loads everything everywhere. Page builders and multipurpose themes tend to load their entire toolbox, every script and stylesheet, on every page, whether that page uses the tools or not.
- Plugin and script accumulation. Analytics, chat widgets, sliders, fonts from three different services. Each one is small; the sum is the six seconds.
- Hosting that answers slowly. If the server takes two seconds to send the first byte, no front-end work can make the page fast. Cheap shared hosting is often where the budget decision from five years ago still bills the business daily.
What you can fix yourself, and what needs a developer
An owner with admin access and an afternoon can usually do three things without any code: run the site through PageSpeed Insights and read the mobile tab, recompress and resize the heaviest images it names, and remove the plugins and third-party widgets nobody has looked at in a year. On a large share of slow sites, that alone moves the number visibly.
What genuinely needs a developer is the structural half: getting the server’s response time down, cutting the theme or builder payload without breaking the design, setting up proper caching, and making images load lazily and in modern formats site-wide rather than one upload at a time. That is ordinary, well-understood work, not wizardry, and it is what our speed optimization service exists for.
The regional context is the closing argument. When two thirds of your country’s websites rate poor on the measurement Google says its ranking systems use, meeting the 2.5-second bar does not make you merely acceptable. It puts you ahead of roughly four in five sites in your market.