Why your Wix site loads in seven seconds (and what that costs you)

If you run a Malton roofer’s business on a Wix site or a heavy template, there is a good chance the homepage takes six or seven seconds to load on a phone over rural 4G. That number sounds like a technical detail. It is not. It is the reason the enquiry form is empty.

The argument is simple. Speed is not vanity. Speed is the difference between the customer landing on your site and the customer giving up before they ever see your phone number.

What seven seconds actually does to a website

Google has measured the relationship between page load time and bounce rate for years, and the pattern is uncomfortably consistent. A page that takes one second to load loses around nine percent of visitors before they engage. By three seconds, the loss is closer to a third. By five seconds, more than ninety percent of mobile visitors are gone.

Seven seconds is past the cliff. By the time the Wix homepage finishes assembling its hero image, its embedded widgets, its three tracking scripts and its cookie banner, most of the people who tapped your Google result are already back on the search page tapping the next one.

The roofer who set the site up five years ago is not seeing this. The site looks fine on his laptop, in his office, over the broadband he installed last spring. He has no idea the same site behaves like wet cement on a customer’s iPhone in a kitchen in Pickering.

Why Wix sites in particular are slow

It is not because Wix is bad software. It is because Wix ships every site as a generalised platform, not a focused page. Each page loads its drag-and-drop editor scaffolding, its global navigation logic, its animation engine, and a dozen third-party scripts you never asked for. Most of that runs whether you use any of it or not.

The result is the same problem covered in what Core Web Vitals actually mean for a Harrogate cafe: the Largest Contentful Paint number sits around four or five seconds on a good day and seven on a bad one. Google notices. So does the customer.

A hand-built site for a roofer needs to load three things: a headline, a phone number, and a photo of a finished roof. There is no reason any of that should take seven seconds on a phone.

What this costs in real money

Take a Malton roofer doing twenty website enquiries a month. Halve the load time and the conversion data suggests you recover somewhere between thirty and sixty percent of the visitors you were quietly losing. That is six to twelve extra enquiries a month. At a typical job value, the maths is not subtle.

The lost enquiries do not show up in any report. They do not bounce on the contact page. They never arrive. You only see them if you measure load time on a real phone, over a real connection, on the kind of day a customer is actually searching.

The fix is mostly a foundation problem

A site built on a focused stack, with images sized for the screen they appear on and none of the third-party junk you never use, will load in under two seconds on the same connection that crushes your Wix homepage. None of that is clever. It is the kind of work you only notice three months later, when the enquiries start arriving from people you have never met.

Open your own site on your phone right now. Switch off WiFi. Type the URL fresh. Count the seconds before you can read the headline and tap the phone number. If it is more than three, the site is costing you work, and no amount of clever SEO will recover what the speed is losing.