Why different tests give different results
Every tool tests your site under its own conditions: from its own server, on an emulated phone or desktop, at a set network speed. If the test server sits in Europe while your customers open the site in Tashkent, Samarkand or Namangan, the picture will not match what they actually experience.
Caching changes the result too, since a first visit and a repeat visit load differently. So do server load at the moment of the test and third-party scripts such as chat widgets, pixels and embeds. The practical rule: compare results from the same tool before and after a change, never numbers from different tools against each other.
Which website speed test to use and when
Tools fall into a few types, and each answers a different question.
- PageSpeed Insights is Google’s free tool. It shows real Chrome user data when a page has enough visits, plus a Lighthouse lab test with a score and recommendations.
- The Core Web Vitals report in Search Console shows the same field data, grouped by page type across the whole site.
- Lighthouse in the browser works for pages closed to outsiders, such as a staging version. Run it in an incognito window without extensions, or the result will depend on your own computer.
- Tests that let you choose location, device and connection, and show a detailed loading waterfall, help you find exactly which file slows a page down.
- Monitoring and web analytics give you a speed graph over time, so you notice when an update or a new script makes things worse.
Which metrics to look at
A single overall score is handy for a report, but decisions are better made on specific metrics.
- Server response time is the foundation. If it is slow, other optimizations help only a little.
- LCP shows when the visitor sees the main element of the first screen: a banner, a product photo, a headline.
- INP, or total blocking time in the lab, shows how quickly the page reacts to taps.
- CLS shows whether the layout jumps while loading, which makes people tap the wrong thing.
- Page weight and number of requests: heavy images and a dozen connected scripts.
How to test a site for an Uzbekistan audience
Most visitors arrive on a phone over mobile internet, often from Instagram or Telegram, where links open in an in-app browser. So start with the mobile version. Open your site on your own smartphone over a mobile network rather than office Wi‑Fi. It is a simple check that complements any online tool.
Test key templates, not just the homepage: a service page, a category, a product card, an article, and the checkout where people pay with Click or Payme. These are the pages where the decision happens. Run several tests in a row and rely on the typical value, not the best or the worst.
How to record results for your developer
Save a link to the report or a screenshot, the date, the page address and the test conditions: device, test location, connection type. Next to it, write down what you decided to fix and in what order.
After the changes, test the same page under the same conditions. Without matching conditions a before-and-after comparison proves nothing, and a conversation with a contractor turns into an exchange of screenshots.
What not to do
The goal is green Core Web Vitals for real people and a site that is comfortable to open on a phone, not a pretty number in a report.
- Chase a score of 100 by removing useful things: a lead form, a map, a chat that brings in customers.
- Draw conclusions from a single measurement.
- Confuse a lab test with the experience of real visitors.
- Compare numbers from different tools with each other.
When the problem is deeper than settings
Sometimes compressing images and removing unnecessary scripts gives a quick win. But if the server, the template or a heavy site builder is slow, tweaks only hide the cause, and rebuilding the site makes more sense.
The markdev team builds turnkey websites in Uzbekistan and plans for mobile speed from the start. If you already have test results and are not sure what to do with them, tell us about your task. We will go through the numbers and suggest what to fix first.
FAQ
Which website speed test should I use?
For regular checks, start with PageSpeed Insights and the Core Web Vitals report in Search Console. To find causes, use a test with a detailed loading waterfall. To watch changes over time, use monitoring or web analytics.
Why do two speed tests show different results?
They measure under different conditions: different servers, devices, networks and metrics. Caching and server load also play a part. Compare results from one tool before and after your changes.
Do I need a score of 100?
No. What matters is that Core Web Vitals are in the green for real visitors and the site works comfortably on a phone. Removing a form or chat for a few extra points is not worth it.
What should I check first?
The mobile version of your key pages: services, categories, products, articles and checkout. Start with server response time and LCP, then look at responsiveness and layout shifts.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.