Why your site is slow on a phone (and what fast actually means)

Pull up your website on your phone, on cellular data, standing in your driveway. Count how long it takes before you can read the first line and tap your phone number. That number matters more than how the site looks on your office computer.

What "fast" means

A good rule of thumb: the main content should appear in about two and a half seconds or less on a typical phone connection. Past that, a noticeable share of visitors give up and hit the back button — usually straight to a competitor.

The usual culprits

• Giant photos. A photo straight off a modern phone can be several megabytes. On a website it should usually be a few hundred kilobytes at most. This is the single most common problem we fix.
• Too many add-ons. Chat widgets, review sliders, social feeds, and tracking scripts each add weight. Five of them can double a page's load time.
• Web fonts. Loading four different fonts in four weights means visitors wait for all of them.
• Slow servers. If every page has to be built from a database on every visit, the server's response alone can take a second.
• Auto-playing video backgrounds. They look great on office Wi-Fi and terrible on one bar of signal.

What we do when a site moves in

When we bring a site over to Flagstage, it's served as finished static files from a content delivery network — copies of your site kept close to your visitors, so there's no database step and less distance for every page to travel. Images, stylesheets, and scripts are cached so returning visitors load them instantly.

From there, the biggest wins usually come from right-sizing photos and removing add-ons nobody uses. Those are ordinary change requests, and you'll see the result in a preview before anything goes live.

Check it yourself

Free tools like Google's PageSpeed Insights will grade your page and list what's slowing it down. Don't chase a perfect score — chase a site that loads quickly on your own phone in your own service area.