Slow website: why your site lags and how to fix it

You open your company's site on your phone, on 4G, and the screen stays blank. Then the text shows up, and the hero image arrives last. Or you tap the WhatsApp button and nothing happens for a second. For you, who already knows what's there, it's just annoying. For someone who came from Google and doesn't know your company, it's a reason to go back and click on a competitor.

Slow sites aren't the exception. According to the performance chapter of the 2025 Web Almanac, published by HTTP Archive in January 2026, only 48% of sites pass all three of Google's speed metrics on mobile. On desktop, it's 56%. In other words, half the sites you visit on your phone fall short of the target. The good news is that the cause is usually one of a few, and you can find out which in an afternoon.

Measure first, then blame someone

The usual reaction is to call the hosting company or whoever built the site and ask them to “make it faster.” Without numbers, that conversation goes nowhere. Measure first.

Use PageSpeed Insights, Google's free tool. Paste your URL and look at two sections:

• Real-user data. This is what Google collected from Chrome users who visited your site in recent weeks. This is the data that counts. If it says “failed,” the problem is real.
• Lab diagnostics. A simulated test, with a score from 0 to 100 and a list of what's slowing things down. Use it to find the cause, not to celebrate the score.

According to the web.dev article explaining how they were defined, Google has three targets:

1. Loading (LCP): the largest element on screen, usually the hero image or headline, must appear in 2.5 seconds or less. Over 4 seconds is considered poor.
2. Responsiveness (INP): after a tap or click, the page must react in 200 milliseconds or less. Over 500 is poor.
3. Stability (CLS): elements can't jump around while the page loads. The score must stay at 0.1 or less.

Google measures at the 75th percentile. In practice, 3 out of 4 visits need to hit the target. It doesn't help that the site opens fast on your office computer.

The three most common causes

The Web Almanac shows where the bottleneck is. On mobile, 81% of sites have good stability and 77% respond well to taps. But only 62% load the largest element in time. Loading is the metric that fails the most sites. And it's almost always where the problem is.

1. The hero image is heavy or arrives late

According to the same report, on 76% of mobile pages the largest element on screen is an image. If that photo is several megabytes, was exported at billboard size, or uses an old format, the whole site feels slow.

There's an even simpler mistake. About 17% of mobile pages use lazy loading on the main image itself. Lazy loading tells the browser to wait before downloading the image, which is great for photos in the footer and terrible for the photo that should appear first. It's one line of code, and many people don't even know it's there.

2. The server is slow to respond

Before showing anything, the browser waits for the server to send the first piece of the page. Google considers it good when this takes less than 0.8 seconds. According to the Web Almanac, only 44% of mobile sites get there.

A slow server usually comes from crowded shared hosting, a database that builds the page from scratch on every visit, or a site with no cache. Here, switching hosting or setting up caching does fix it.

3. Too much code before the content

A floating chat widget, an ad pixel, a map, a background video, a carousel, three different fonts, a theme with features you never used. Each one seems light on its own. Together, they freeze the visitor's phone, delay button taps, and push the content down.

This is common on sites made with visual builders or on WordPress with lots of plugins. We explained the differences in our article on coded sites vs. Wix, Framer and WordPress.

Why this costs you money

Speed isn't technical vanity. In its Search Central documentation, Google says it strongly recommends good speed metrics and that this “aligns with what our core ranking systems seek to reward.” It isn't the one factor that decides rankings, but it matters between similar pages.

The most direct impact is on sales. Someone who clicks an ad and waits sees a blank screen, goes back, and you've already paid for the click. People coming from organic search have no patience either.

And there's a cost that never shows up in any report. A visitor who gave up doesn't complain, call, or send a message. They just never become a lead. You only notice the effect: ad spend stays the same, traffic looks fine, and WhatsApp rings less than it should. That's why it pays to check your site's speed as often as you check your campaign results. We showed a measured case, with the conversion gain after speeding up the pages, in our article on landing page speed and conversion.

What you can fix in a week

If the diagnosis points to images, the server, or too many scripts, there are quick fixes:

• Compress and resize images. Export them at the size they're displayed, in a modern format like WebP or AVIF.
• Remove lazy loading from the main image and give it loading priority.
• Remove what nobody uses. Deactivated plugins, scripts from canceled tools, pixels from campaigns that already ended.
• Turn on caching and a CDN. The finished page is stored close to visitors, and the server doesn't have to build it all over again.
• Reserve space for images and banners so nothing jumps around while loading.

After each change, measure again. Real-user data takes a few weeks to fully reflect the improvement, so save a screenshot of the before.

When fixing isn't worth it

Sometimes the diagnosis shows something else. The theme loads code for dozens of features the site doesn't use. The plugins depend on each other, and every update breaks a page. The PHP version is no longer supported. Every optimization becomes a new bill, and the score goes up 5 points only to drop again the next month.

In these cases, rebuilding usually costs less than patching. A company website or landing page in custom code, with no theme or plugins, is lightweight from day one. We listed other signs that it's time in our article on rebuilding your company website.

How we do it at the Studio

When a slow site comes to us, the first step is discovery. We measure with real-user data, point out what's weighing it down, and tell you honestly whether it can be fixed or should be rebuilt. The price is fixed after discovery, and the deadline is written into the contract.

When we build a new site, it's custom code, with no builder and no plugins, live on our server and with SEO and GEO from day one. The course sales page conversaovisual.com.br scored 99 out of 100 on Google Lighthouse in October 2026. Code, domain, and logins are in the client's name, so you never depend on us to change what's yours.

If your company's site is slow and you don't know whether to fix or rebuild, the Studio's project rescue starts with exactly that answer.