Designing for Slow Connections and Older Phones

It's easy to build a site on a fast office connection and a powerful laptop and think it loads quickly. Many of your visitors are on weak mobile signals, trains and rural areas, data caps, or older phones. Designing for them makes the site better for everyone.

Who's affected

• People in areas with poor coverage
• Visitors on crowded public Wi-Fi or on the move
• Users with limited data plans
• People with older or budget devices that process pages slowly
• Anyone in the middle of a busy event or building with poor signal

If you serve a local audience, such as customers looking for you while out, these conditions are common.

Test the realistic experience

• Throttle the connection. Browser developer tools let you simulate slow mobile networks and slower CPUs
• Test on real devices, especially an older or mid-range phone
• Test in poor conditions, like a basement or with a weak signal
• Check page weight, the total data a page downloads. See how to test website speed

Lab tests often use throttled mobile settings by default. Real-user data in Search Console shows how actual visitors fare.

Principles for resilient pages

Lead with content. Make sure text and key information appear quickly, before decorative extras. Server-rendered HTML helps.

Keep pages light. Every kilobyte counts. See how to reduce website load time.

Compress and resize images. They're usually the biggest burden. See how to compress images and WebP vs AVIF vs JPEG.

Lazy-load below the fold, but not your main content. See lazy loading.

Avoid autoplay video and giant background media. See optimizing video and embeds.

Limit scripts. Heavy JavaScript hurts older phones even more than slow networks. See third-party scripts and how to improve INP.

Use system fonts or few web fonts. See choosing web fonts.

Cache effectively so repeat visits are fast. See browser caching and page caching.

Use a CDN to shorten distances. See what is a CDN.

Make sure it degrades gracefully. If a script fails or an image doesn't load, the page should still be usable. Alt text, readable text, and working links keep things going.

Make forms resilient

On a flaky connection, a form that fails silently is infuriating. Show clear progress and errors, don't lose typed information, and confirm submission. See accessible forms.

Consider data-saving preferences

Some browsers signal that a visitor wants to save data. You can respond by loading lighter images or skipping non-essential media where supported.

Why it pays off

Faster, lighter pages tend to have better engagement and are friendlier on every device. See why website speed matters and mobile-first design.

The bottom line

Test on slow networks and modest phones, keep pages light, and put content first. A site that works in difficult conditions works brilliantly in easy ones.