yodai Academy Build your website

Academy › Build › Create your website

The number that matters: how long your site takes with two bars of signal

You'll know how to measure, on your own phone with weak signal, how long your site really takes to load, and the number that tells you it's time to fix it.

By Yodai · Published September 6, 2026 · Updated October 12, 2026

4 min read

You open your website on your home computer, with fast fiber internet, and it loads in a blink. You figure the problem's solved.

But your customer isn't going to see it that way. They'll open it out on the street, walking or waiting for the bus, with their phone showing two bars of signal.

That's where it gets decided: whether they wait a few seconds staring at an almost blank screen, or go back and click into the next website on the list.

You can't go by someone telling you "it loads fast for me." You need your own number, measured under those conditions, and you need to know at what point that number becomes a problem.

The test that counts, and the one that doesn't

Two ways to check it
On the wifi at home or at your business
  • Fast connection and full signal
  • Your phone connected to strong wifi, not to your carrier's network
  • This measures the best-case scenario for your website, not the normal one
Out on the street, on mobile data
  • Two or three bars, the kind of signal someone gets while walking, driving, or standing inside a building with thick walls
  • Wifi off, mobile data only
  • Measure what someone finds when they open your site from the street

Which one to use: Always measure the second time. The first load only tells you how much worse your site gets once you leave the house, and it's almost always worse than you think.

How to measure it, step by step

The two-bar test
  1. 1Go outside
    On your own phone, turn off wifi and leave only mobile data on. Find a spot with genuinely weak signal: a doorway, a parking garage, a corner where your phone already struggles.
  2. 2Open it like it's the first time
    Your browser saves parts of the page from past visits, and that throws off the timing because it doesn't download everything again. A new tab isn't enough: open it in a private or incognito window, which is a separate session with nothing saved from before, and close every private window between one try and the next.
  3. 3Start counting the moment you tap the link
    Using your phone's own stopwatch, time it until you see the headline, the main photo, and the price or the booking button. You don't need to wait for the whole page to load, just enough to make a decision based on what's on screen.
  4. 4Try it three times
    A single measurement can come out strange because of a bad stretch of coverage right at that moment. With three tries, go with the middle result, not the best or the worst.

The number: what it means and when to act

With that test, you now have your number. What you need next is a way to read it, not just a gut feeling.

Use the same yardstick Google does. In web.dev, Google's speed guide for website builders, a page is doing well if the biggest thing visible on load appears within 2.5 seconds or less, needs work if it takes between 2.5 and 4, and is doing poorly above 4. Google measures this from real visits, not a stopwatch, so your test is an approximation, but it tells you where you stand.

If the essentials show up in 2.5 seconds or less, your site is well prepared for a customer with weak signal. Between 2.5 and 4, you start losing people without realizing it, because someone who gets tired of waiting doesn't call to tell you, they just go somewhere else. Above 4, it's a problem that could be costing you customers, and it's worth fixing this week, not whenever you get a spare minute.

Notice that the goal isn't for the whole website to load fast. It's for whatever decides if someone sticks around, the headline, the main photo, the price, or the booking button, to show up fast. Everything else can arrive a second later without anyone noticing.

That distinction is what you'll use in the next lessons: it's not about making everything lightweight, it's about making the first thing people see lightweight.

How to log your measurement
Site: example-salon.com. Test: on the street, mobile data, 2 bars, building entrance, Wi-Fi off. The headline, photo, and booking button show up in: 5 seconds (the middle of three tries: 4, 5, and 6). Standard: above 4, fix it now. Goal for the next measurement: get it down from 5 to 2.5 seconds or less.
The costly mistake: trusting wifi
A very common mistake is testing the site on your phone while connected to the business's Wi-Fi, and assuming that's the real speed. With fast Wi-Fi, even a heavy site loads quickly, and it looks like there's nothing to fix. The problem only shows up on mobile data with weak signal, which is where your customer lives for a good part of the day: on the street, in the car, on the subway. If you only test on Wi-Fi, you won't see the problem until a customer shows it to you by quietly heading to the site next door instead.
What you'll walk away with
  • You have your own number: how long it takes your website to show up from the street, on mobile data with weak signal.
  • Now you have the standard to judge it by, Google's yardstick: 2.5 seconds or less is good, between 2.5 and 4 is worth watching, more than 4 means fix it now.
  • You know what counts is the speed of the essentials, the headline, photo, price, or button, not the entire page.
  • Next lesson: that photo you uploaded from your phone is heavier than it looks, and it's usually the first suspect when the number comes out high.

In Yodai every site goes live with its padlock, its sitemap and its titles, with nothing to buy or set up. See what the hosting included with your website covers.

NextThe hidden weight in every photo