Website speed matters because it shapes whether visitors stay, whether they contact you, and how Google evaluates the experience your pages deliver. We learned that firsthand when we redesigned our own site in 2026: our Google PageSpeed Insights mobile score went from 47 to 96, and desktop went from 74 to 100. The fixes weren’t exotic. We removed the weight that had built up over time and changed when certain scripts load.
This post walks through what was slowing us down, what we changed, why it matters for any business website, and how you can check your own site.
Where We Started
Like a lot of business websites, ours had grown in layers. It ran on a popular multipurpose theme with a visual page builder, which made it easy to add sections, sliders and effects over the years. Marketing tools were added as we needed them. Each addition made sense on its own. Together, they produced a mobile PageSpeed Insights score of 47 and a desktop score of 74.
That was uncomfortable for a company that builds websites and offers speed optimization. It was also a useful reminder: slow sites usually aren’t the result of one bad decision. They’re the sum of many reasonable ones that nobody went back to review.
What Was Slowing Our Site Down
When we dug into the PageSpeed Insights and Lighthouse reports, four causes stood out.
1. A heavy multipurpose theme and page builder
Multipurpose themes are designed to do everything: portfolios, shops, magazines, landing pages. To support all those possibilities, they tend to load large CSS and JavaScript files on every page, whether or not that page uses those features. Page builders add their own layer of markup and assets on top. The result was a lot of code the browser had to download and process before it could show our content.
2. Render-blocking scripts
Some scripts and stylesheets loaded in a way that made the browser stop and wait before drawing the page. On a fast desktop connection, the delay was tolerable. On a mid-range phone with a cellular signal, it was the difference between a page that appears almost immediately and one that sits blank.
3. Third-party tags loading up front
Our analytics, an advertising pixel and a live chat widget all loaded as soon as the page did. Third-party scripts are especially costly because they come from other servers, often pull in additional files, and compete with your own content for the browser’s attention. The chat widget alone was a significant chunk of code that most visitors never used.
4. Unoptimized images and fonts
Some images were larger than they needed to be for the space they filled, and not all were in modern formats. Fonts loaded from an external service, which meant extra connections and potential delays before text rendered in the right typeface.
What We Changed
We approached the redesign with one rule: every element on the page had to justify its weight.
Lightweight custom templates for the main pages
Instead of building our most important pages, such as the homepage and core service pages, with the multipurpose theme and page builder, we created lean custom templates. Each template loads only the code that page needs. That reduced the amount of CSS and JavaScript dramatically and gave us direct control over how each page renders.
Delaying tracking and chat scripts until visitors interact
We didn’t remove our analytics, ad pixel or chat. We changed when they load. Those scripts now wait until a visitor interacts with the page (scrolling, tapping or moving the mouse) or until a few seconds have passed, before they load. The visitor sees our content first, and the tools still load for anyone who engages. This was one of the biggest single improvements, and it’s a technique many businesses can apply without a full redesign.
It does involve tradeoffs. Delaying analytics can mean a visitor who leaves without any interaction isn’t recorded the same way. We decided that was an acceptable cost for a much faster first impression, but it’s a decision each business should make deliberately.
Optimized images and self-hosted fonts
We resized images to the dimensions they actually display at, served them in modern formats, and made sure images below the fold load lazily while the main image at the top loads right away. We also moved our fonts onto our own server and limited the number of font weights we use. Fewer files from fewer places means faster text rendering.
Page caching
Caching stores a ready-made version of each page so the server doesn’t rebuild it from scratch for every visitor. Combined with lighter pages, it helps the first byte of each page arrive quickly.
The Result
After the redesign, Google PageSpeed Insights reported a mobile score of 96, up from 47, and a desktop score of 100, up from 74.
We’ll be honest about what those numbers are and aren’t. They’re lab scores from a standardized test, which makes them excellent for diagnosing problems and comparing before and after. They aren’t a business result by themselves. It’s too early for us to claim changes in traffic or leads, and we won’t. What we can say is that the site now loads its content quickly on phones, where most visitors first meet a business.
Why Website Speed Matters for Your Business
For visitors
People decide quickly whether a page is worth waiting for. A visitor on a phone who taps a search result and sees a blank screen often goes back and taps a competitor. Speed is the first impression your website makes, before any of your design or copy has a chance.
For conversions
Slow pages don’t just lose visitors at the start. Laggy buttons, shifting layouts and forms that respond late create friction at the exact moment someone is trying to call, book or request a quote. A fast, stable page removes that friction.
For SEO and Core Web Vitals
Google uses Core Web Vitals as part of its page experience signals. The three metrics measure loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint, which replaced First Input Delay in March 2024) and visual stability (Cumulative Layout Shift). Speed won’t outrank better content on its own, but when competing pages are similar, a better experience helps, and a poor one can hold you back. Our plain-English guide to Core Web Vitals: LCP, INP and CLS explains each metric and its thresholds.
For AI search
AI-powered search features rely on pages that crawlers can fetch and process efficiently. Lean, well-structured HTML is easier to crawl and interpret than pages buried under scripts. Speed alone won’t earn citations, but it removes an obstacle.
How to Check Your Own Site
You can run the same test we did in a couple of minutes:
- Go to Google PageSpeed Insights and enter your homepage URL.
- Look at the mobile results first. Mobile scores are usually lower and more representative of real visitors.
- Check whether a “Discover what your real users are experiencing” section appears. That’s field data from real Chrome users, and it’s what Google uses for Core Web Vitals. Not every site has enough traffic to show it.
- Review the diagnostics for patterns like ours: unused JavaScript, render-blocking resources, large images and third-party code.
- Test your most important service page and contact page too, not just the homepage.
If the report looks overwhelming, our walkthrough on how to read a PageSpeed Insights report and what to fix first explains lab vs field data and the order to tackle issues.
Lessons Any Business Can Use
- Audit your third-party scripts. List every tag on your site and ask whether each one still earns its place, and whether it needs to load immediately.
- Question your theme. If your site runs on a do-everything theme, much of its code may be serving features you don’t use.
- Size images for their real display size and use modern formats.
- Re-test after every major change. Speed tends to decay as new plugins, widgets and tags get added.
Frequently Asked Questions
Is a PageSpeed Insights score of 100 necessary?
No. The score is a diagnostic tool, not a goal in itself. What matters most is passing Core Web Vitals in field data and giving visitors a fast, stable experience. A site scoring in the 90s on mobile is in excellent shape.
Will delaying scripts break my analytics or chat?
They still work, but they load after the visitor interacts with the page. Some visitors who leave without any interaction may not be tracked the same way. Weigh that against the speed benefit and test carefully after making the change.
Do I need a full redesign to speed up my site?
Not always. Delaying third-party scripts, optimizing images and adding caching can make a meaningful difference on an existing site. A redesign makes sense when the theme or builder itself is the main source of the weight, as it was for us.
Speed Is a Feature You Can See
Our own redesign confirmed what we tell clients: most slow websites can become fast ones when someone takes the time to find what’s weighing them down and fix it methodically. If your PageSpeed Insights report looks like our old one, our website speed optimization service applies the same process to your site.