{"id":7095,"date":"2026-11-10T18:35:07","date_gmt":"2026-11-10T18:35:07","guid":{"rendered":"https:\/\/itsolutions.ee\/uncategorized\/website-speed-test\/"},"modified":"2026-11-10T18:35:07","modified_gmt":"2026-11-10T18:35:07","slug":"website-speed-test","status":"publish","type":"post","link":"https:\/\/itsolutions.ee\/en\/blog\/website-speed-test\/","title":{"rendered":"Website Speed Test: How to Check Your Site and Read the Results"},"content":{"rendered":"
\n

In short:<\/strong> A website speed test takes 5 minutes: open PageSpeed Insights, enter the page address and look at the mobile result first. The key numbers are the three Core Web Vitals: LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1. A score of 90\u2013100 is good, but it varies from run to run, so test 3 times and compare the median. Google ranks on real-visitor data, not on the score of one lab test.<\/p>\n<\/div>\n

Website speed affects both your Google rankings and whether a visitor stays or leaves for a competitor. The good news: you can check speed for free and without a developer. This guide shows how to run a website speed test<\/strong>, how to read the results and why the same page sometimes scores 86 and sometimes 97. For why speed matters for SEO, read website speed and SEO<\/a>.<\/p>\n

Which tool should you use for a website speed test?<\/h2>\n

There are many free tools, but most business owners need just two: PageSpeed Insights for a quick check of one page and Google Search Console for the whole site.<\/p>\n\n\n\n\n\n\n\n\n\n
Tool<\/th>\nBy<\/th>\nWhat it shows<\/th>\nBest for<\/th>\n<\/tr>\n<\/thead>\n
PageSpeed Insights<\/td>\nGoogle<\/td>\nLab and field data, recommendations<\/td>\nQuick check of one page<\/td>\n<\/tr>\n
Search Console \u2192 Core Web Vitals<\/td>\nGoogle<\/td>\nReal-visitor data for the whole site<\/td>\nStatus of all pages and issues<\/td>\n<\/tr>\n
Lighthouse (Chrome DevTools)<\/td>\nGoogle<\/td>\nLab test on your own computer<\/td>\nDevelopers, before and after a change<\/td>\n<\/tr>\n
WebPageTest<\/td>\nCatchpoint<\/td>\nDetailed loading waterfall, choice of location<\/td>\nHunting complex problems<\/td>\n<\/tr>\n
IT Solutions website audit<\/a><\/td>\nIT Solutions<\/td>\nSpeed + SEO + security in one go<\/td>\nThe big picture for owners<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Website speed test step by step<\/h2>\n
    \n
  1. Open pagespeed.web.dev<\/strong> and enter the full page address including https.<\/li>\n
  2. Test several pages<\/strong>: the home page, your most important service or product page and a blog post. The home page is often the fastest, but visitors from Google frequently land straight on inner pages.<\/li>\n
  3. Look at the mobile result first.<\/strong> Google indexes sites by their mobile version, and most visitors in Estonia come from phones.<\/li>\n
  4. Read the top block \u201cDiscover what your real users are experiencing\u201d.<\/strong> That is field data from real visitors. If there is none, the page has too few visits and you rely on the lab test.<\/li>\n
  5. Check the score and the five metrics<\/strong> (FCP, LCP, TBT, CLS, Speed Index).<\/li>\n
  6. Repeat the test 3 times<\/strong> and take the middle result. One run is not reliable.<\/li>\n
  7. Open \u201cDiagnostics\u201d<\/strong>: it lists the actual files and images slowing the page down.<\/li>\n<\/ol>\n

    What is a good website speed test result?<\/h2>\n

    Google\u2019s Core Web Vitals measure three things: how fast the main content appears, how fast the page reacts to a click and whether content jumps while loading. The thresholds apply to the 75th percentile, so 3 out of 4 visitors must get at least that experience.<\/p>\n\n\n\n\n\n\n\n
    Metric<\/th>\nWhat it measures<\/th>\nGood<\/th>\nNeeds improvement<\/th>\nPoor<\/th>\n<\/tr>\n<\/thead>\n
    LCP (Largest Contentful Paint)<\/td>\nWhen the largest image or text block appears<\/td>\nup to 2.5 s<\/td>\n2.5\u20134 s<\/td>\nover 4 s<\/td>\n<\/tr>\n
    INP (Interaction to Next Paint)<\/td>\nResponse to clicks and taps<\/td>\nup to 200 ms<\/td>\n200\u2013500 ms<\/td>\nover 500 ms<\/td>\n<\/tr>\n
    CLS (Cumulative Layout Shift)<\/td>\nContent jumping while loading<\/td>\nup to 0.1<\/td>\n0.1\u20130.25<\/td>\nover 0.25<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    INP replaced the older FID metric in March 2024. If an older guide talks about FID, that part is out of date.<\/p>\n

    The PageSpeed Insights score from 0 to 100 is calculated from five lab metrics with different weights:<\/p>\n\n\n\n\n\n\n\n\n\n
    Metric<\/th>\nWeight in score<\/th>\nWhat it means<\/th>\n<\/tr>\n<\/thead>\n
    Total Blocking Time (TBT)<\/td>\n30%<\/td>\nHow long JavaScript blocks the page<\/td>\n<\/tr>\n
    Largest Contentful Paint (LCP)<\/td>\n25%<\/td>\nMain content appearing<\/td>\n<\/tr>\n
    Cumulative Layout Shift (CLS)<\/td>\n25%<\/td>\nContent shifting<\/td>\n<\/tr>\n
    First Contentful Paint (FCP)<\/td>\n10%<\/td>\nFirst content appearing<\/td>\n<\/tr>\n
    Speed Index<\/td>\n10%<\/td>\nHow quickly the visible area fills in<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    A score of 90\u2013100 is green (good), 50\u201389 orange (needs improvement) and 0\u201349 red (slow).<\/p>\n

    What is the difference between field data and lab data?<\/h2>\n