Is your website slow on real phones? How to tell—and why it costs leads

A real estate client asked us why their lead form submissions had dropped. The site looked the same, content was fine, SEO rankings hadn't changed. We ran a speed test on a throttled 4G connection and the homepage took 11 seconds to load. On their office fiber it was 2 seconds, which is why nobody noticed.

The culprit was familiar: uncompressed hero image at 4MB, three analytics scripts, a chat widget that loaded its own framework, and a cookie banner with more JavaScript than the rest of the page combined — the usual result of plugin and builder creep on CMS sites and the same class of weight on other stacks when nobody enforces a performance budget.

We rebuilt the site as a static React build. Same design, same content, same forms. Load time went to 1.2 seconds on 4G. Form submissions went up 35% in the first month — and that was without changing a single word of copy. For how Google thinks about experience, see Core Web Vitals.

Speed is not a technical vanity metric. It's the difference between someone filling out your contact form and someone hitting the back button. Test your site on a slow phone. That's what your customers actually experience.

If this sounds familiar, our web service workflow shows how we scope rebuilds around measurable performance targets.