Testing your website speed on Google: what score is good and what slows your site down

The short answer
Test your site free on Google PageSpeed Insights (pagespeed.web.dev) and read the phone result first. A score of 90–100 is good, 50–89 needs improvement and 0–49 is poor; the phone score is usually lower because Google simulates a mid-range phone on a slower mobile connection. Run it 3 to 5 times and take the middle score. The most common causes of a slow site are heavy images, too many plugins or apps, big sliders, chat and tracking scripts, and weak hosting.
Someone taps your ad on Instagram, on a phone, on a mobile data package — and waits. If the page takes too long, they go back to scrolling and you paid for nothing. Google gives you a free tool to see how fast your site really is. Here is how to use it, what the numbers mean, and what usually slows Egyptian sites down (checked November 2026).
How to test your website speed on Google, step by step
- Open PageSpeed Insights at pagespeed.web.dev.
- Paste the full address of the page — your home page first, then a product or sign-up page, because each page scores on its own.
- Press Analyze and wait about a minute.
- Look at the two tabs at the top: Mobile and Desktop. Read the phone tab first.
- Read the circle marked Performance. That is the speed score. The other three circles (accessibility, best practices, SEO) are useful, but they are not speed.
- Run the test 3 to 5 times and write down the middle score, not the best one or the worst one.
Why several runs? The network, your server’s load and third-party scripts change from one run to the next, so the score moves. Google’s Lighthouse team, who build the test, recommend running it several times and using the median — they note that the median of 5 runs is about twice as stable as a single run.
What score is good?
| Colour | Score | What it means |
|---|---|---|
| Green | 90–100 | Good |
| Orange | 50–89 | Needs improvement |
| Red | 0–49 | Poor |
These are Google’s own bands. A sensible target is 90 or more on the phone test. A 100 is nice, but chasing the last few points rarely changes anything for a customer; going from 40 to 90 does.
One honest note: the score does not decide your place on Google by itself. Google says it shows the most relevant content first, even when the page experience is not great, and that good Core Web Vitals do not guarantee a top position. Speed matters most when your page and a competitor’s are equally useful — and it always matters for the visitors you already paid to bring.
Why the phone score is lower
Most people are surprised that the same site scores 95 on a computer and 50 on a phone. That is by design. Google runs the phone test as a mid-range phone on a slower mobile connection, and the computer test as a desktop on a wired connection. A heavy photo or a big script that a computer handles in a blink takes much longer on the slower setup.
That makes the phone test closer to many real visitors in Egypt, who arrive from Facebook, Instagram or TikTok ads on their phones. If you can only fix one number, fix the phone one.
Core Web Vitals, and real visitors versus the lab
Under the score, PageSpeed shows the three numbers Google calls Core Web Vitals:
| Metric | Good | Poor | What it measures |
|---|---|---|---|
| LCP (Largest Contentful Paint) | 2.5 seconds or less | over 4 seconds | When the biggest thing on the screen, usually the main photo or headline, appears |
| INP (Interaction to Next Paint) | 200 milliseconds or less | over 500 milliseconds | How fast the page reacts when someone taps a button or a menu |
| CLS (Cumulative Layout Shift) | 0.1 or less | over 0.25 | Whether things jump around while the page loads |
INP replaced the older FID measure in March 2024, so guides that still talk about FID are out of date.
The page shows two kinds of results, and they answer different questions:
- Real visitors (field data) — the top section, “Discover what your real users are experiencing”. It comes from Chrome users who visited your site over the last 28 days, judged at the 75th percentile, so it reflects your slower visits, not your best ones. Google shows it only when the site has enough visitors, so new or small sites often see “No data” here.
- The lab test — the section below, “Diagnose performance issues”. This is one simulated visit, and the Performance score comes from it. It is the part that tells you what to fix.
If the two disagree, trust the real visitors for how the site feels, and use the lab test to find the cause.
What usually slows Egyptian sites down
When we test sites for businesses here, the same causes come up again and again:
- Heavy images. Photos uploaded straight from the camera or the designer, several megabytes each, shown on a phone screen a few hundred pixels wide.
- Too many plugins or apps. Every WordPress plugin or Shopify app can add its own files to every page, even pages that never use it. WordPress’s own documentation names the number of plugins as a big factor in speed.
- Big sliders at the top. A home page with five full-width banners rotating on their own. The slider often holds the biggest image on the screen, so it decides your LCP.
- Chat and tracking scripts. A chat bubble, a WhatsApp button plugin, and separate codes for Meta, TikTok, Snapchat and Google, each loading on its own. Google’s guides name third-party scripts as a common cause of slow pages; many popular embeds carry over 100 KB of JavaScript, some far more.
- Weak hosting. A cheap shared server that answers slowly before the page even starts loading. WordPress’s documentation is plain about it: the server has a huge impact on speed.
- Heavy ready-made themes and page builders. They carry many features for every possible site, and your site loads code it never uses.
A short fix list
- Shrink every image to the size it is shown at, and save it as WebP.
- Delete plugins and apps you do not use — delete, not just switch off.
- Replace the slider with one strong image and one clear button.
- Load chat and video only when tapped: show a light button that looks like the chat or the video, and load the real thing on the tap.
- Keep only the tracking codes you use, and load them so they do not block the page.
- Turn on page caching, so the server sends a ready page instead of building it for every visitor.
- Move to better hosting if the server answers slowly even with caching on.
- Test again — logged out, 3 to 5 runs, phone tab first — and compare the middle scores.
If you are about to pay for a new site, ask for the phone score in writing before you sign; we explain why in our guide to website design prices in Egypt. And if you only need one page for an ad campaign, a landing page is often the easiest way to be fast.
Our own sites, measured the same way
Every case page on our site shows its Google PageSpeed scores, with the date of the test and a link to run it yourself:
| Site | Phone score | Computer score | Tested |
|---|---|---|---|
| Dr. Ashraf Moharam (campaign site) | 100 | 100 | 31 Oct 2026 |
| Marassi Rowing (sign-up site) | 98 | 100 | 5 Oct 2026 |
| Legends Camp (sign-up and payment) | 97 | 98 | 5 Oct 2026 |
| NENA’S (WooCommerce store) | 96 | 100 | 21 Oct 2026 |
| SHUZAR (WooCommerce store) | 95 | 94 | 5 Oct 2026 |
| Sports Legends (tournament sign-up) | 91 | 100 | 5 Oct 2026 |
Scores move a little from one test to the next, which is why each one carries its date. The two stores run on our own WooCommerce theme, built from scratch for speed instead of a heavy ready-made one — the story is on the SHUZAR case page.
Want a site that is fast on phones?
We build WordPress sites and stores for phones first — every site in the table above scores over 90 on Google’s phone test — and we measure each one the way this guide describes before we hand it over. See our WordPress websites service, or ask for a free consultation through the form on our site.
Questions about this
What is a good PageSpeed score?
Google colours 90–100 green (good), 50–89 orange (needs improvement) and 0–49 red (poor). Aim for 90 or more on the phone test, because that is the harder one and the one most visitors are closer to.
Why is my phone score so much lower than my computer score?
Google runs the phone test as a mid-range phone on a slower mobile connection, and the computer test on a desktop with a wired connection. Heavy images and scripts cost far more on the slower setup.
Why does my score change every time I test?
The network, your server’s load, ads and other scripts change from one run to the next. Google’s own Lighthouse team recommends several runs and the median, so run the test 3 to 5 times and take the middle score.
Does a 100 score put me first on Google?
No. Google says it shows the most relevant content first, and that good Core Web Vitals do not guarantee a top position. Speed helps when pages are equally useful, and it keeps the visitors you already paid for.
Why does PageSpeed show “No data” for real users?
Real-user data comes from Chrome visitors over the last 28 days, and Google shows it only when the site has enough of them. New or small sites usually see only the lab test, which is still useful for finding problems.
Who wrote this
By the GRWPTH team — GRWPTH is a growth agency: we build websites and online stores, automate the work around them, and grow them with performance marketing, in Arabic and English.
See our workThe service behind this article
Websites for your company or event, fast and in two languages.





