Why is my website slow? How to check it without a developer
A plain-English way to find out if your site is really slow, what usually causes it, and the exact message to send your developer or AI tool to fix it.
· 6 min read · No tech skills needed
Open your site on your phone, on mobile data, in a private window, and count. If the main text or picture appears within about two and a half seconds and the page doesn't jump around, your site is fine for most visitors. If it takes longer, run Google's free PageSpeed Insights test: it tells you which part is slow. Most slow small sites have one of a few common causes, and each one can be fixed by sending a short message to your developer or AI tool.
Is it slow, or does it only feel slow to you?
Your own computer is the worst place to judge your site. It is often fast, on good Wi-Fi, and it keeps a saved copy of pages you've visited before (that's called the cache). Your visitors usually see the site for the first time, on a phone, on a weaker connection.
So test it the way they see it:
- Use your phone and turn off Wi-Fi. Mobile data is what many of your visitors have.
- Open a private window. In Chrome that's "New Incognito tab", in Safari "Private". It starts without a saved copy of your site.
- Type your address and count seconds. Note two moments: when the main thing on the page (the headline, the big photo, the product) appears, and when you can tap a button and something happens.
- Watch for jumping. If text moves down just as you try to tap it, because a picture or banner loaded above it, that's a problem too. Google counts it.
- Repeat on two or three pages. The home page is often fast and the shop or dashboard page is the slow one.
Google publishes the targets it uses. The main content should appear within 2.5 seconds, the page should react to a tap within 200 milliseconds (a fifth of a second), and the layout should barely shift while loading. These three measures are called Core Web Vitals, and web.dev explains how the thresholds were chosen. You don't need to remember the names. "Appears fast, reacts fast, doesn't jump" is the whole idea.
Get a second opinion from Google's free test
Counting seconds tells you something is wrong. Google's free tool tells you what.
- Go to PageSpeed Insights at pagespeed.web.dev and paste your site's address.
- Look at the "Mobile" tab first. Phones are where slow sites hurt most.
- Read the top part, if it's there. "Discover what your real users are experiencing" shows data from real Chrome visitors over the last 28 days. A small or new site often doesn't have enough visitors yet, and that section stays empty. That's normal, not a fault.
- Read the lower part. "Diagnose performance issues" is a single test load in Google's lab. The score from 0 to 100 is from this test, and it changes a little each time you run it. Don't chase a perfect 100.
- Scroll to the list of suggestions. Each one says roughly how much time it would save. The ones at the top matter most.
Google's guide to PageSpeed Insights explains the difference between the real-visitor data and the lab test. In short, real-visitor data is what Google uses when it judges your site; the lab test is the best tool for finding the cause.
The usual reasons a small site is slow
You don't need to fix these yourself. It helps to recognise them in the report, so you know what to ask for.
- Huge pictures. A photo straight from a phone or a stock site can be several megabytes. It looks the same on screen at a fraction of the size. In the report this shows up as "Properly size images" or "Serve images in modern formats".
- The server is slow to answer. Before anything appears, your hosting has to reply. On cheap or free hosting, or on apps that "go to sleep" when nobody visits, that first reply can take seconds. The report calls it "server response time".
- Too much code to download. Sites made with AI builders often send a lot of JavaScript (the code that makes buttons and menus work) before showing anything. Chat widgets, several analytics tools and fancy animations add more.
- Files that aren't compressed or remembered. The server can shrink files before sending them, and can tell browsers to keep a copy for next time. When those settings are missing, every visit downloads everything again, at full size.
- Pictures with no size set. If the page doesn't know how big a picture will be, the text jumps when it arrives. That's the "jumping" from your phone test.
If your site appeared on Google and then slipped, or never showed up at all, speed is rarely the only reason. Check the basics in our guide on why AI-built sites don't show up in search as well.
Send this to your developer or AI tool
Once you know the site is slow, don't ask for "make it faster". That invites a big rewrite. Give the facts and ask for small, safe changes. Copy this, fill in the brackets, and send it to your developer, or paste it into Lovable, Bolt, Cursor or whatever built your site:
My site [your site address] loads slowly on phones.
What I measured:
- On my phone, on mobile data, the main content appears after about [X] seconds.
- PageSpeed Insights (mobile) suggestions at the top: [paste the first 3-5 lines].
- The slowest page is [page address].
Please:
- Fix the causes in that list, starting with the biggest time saving.
- Resize and compress large images, and set width and height on them.
- Make sure files are compressed and cached by the server.
- Don't change the design, the text or how anything works.
- List every file you changed, and tell me what to check afterwards.
When the change is published, run the same phone test and PageSpeed Insights again. Compare the seconds, not just the score. If something else stopped working after the update, our plain guide on checking that an update didn't break your site walks you through it.
Keep it fast after the next update
Speed is not fixed once. Every new picture, plugin, widget or AI-generated feature can slow the site down again, and nobody notices because the person who added it is on fast Wi-Fi.
- Shrink pictures before you upload them. A free image compressor in the browser is enough.
- Be careful with add-ons. Each chat bubble, popup or tracking tool has a cost. Remove the ones nobody uses.
- Re-test after big changes. A new home page or a new shop section deserves a two-minute phone test.
- Look at the trend, not one number. One slow result can be bad luck. Slower every week is a real problem.
ScanYourSite can do the watching part for you. The free check opens your page in a real browser and tells you, in plain words, how long the server takes to answer, when the main content appears, whether the page ignores taps while it loads and whether the layout jumps. It also looks for uncompressed pages, missing caching and too much JavaScript. Try it on your own site at scanyoursite.app/?check=yourdomain.com.
On the Free plan that's one site, checked once a week, with a weekly summary email, and three findings explained in full with a fix. Pro ($19 a month) covers three sites, checks every day and after each deploy, and sends an alert as soon as something gets worse. The deeper probes, like looking for exposed configuration files, run only on Pro, after you verify the domain. For speed, the free check already sees what your visitors see.