The Art of Less: How Subtracting Weight Makes Websites Faster Everywhere

Colin Chapman, the founder of Lotus Cars, had a design philosophy that most web agencies would benefit from hearing: "Adding power makes you faster on the straights. Subtracting weight makes you faster everywhere." I studied automobile engineering before I started Digi Hotshot in 2019, and that line stuck with me more than anything else in my coursework. It's become the way I think about every Webflow site we build. After 50+ Webflow projects across SaaS, fintech, healthcare, and cybersecurity, I'm convinced the principle translates directly: the best-performing websites are fast because of what they don't have.

Every component on a website carries weight. Not just file size — though that matters — but render time, cognitive load for the visitor, and maintenance burden for the team updating it six months later. Most web projects start by asking "what should we add?" An engineering mindset asks a different question first: "what can we remove without losing function?"

That distinction changes everything about how a site performs, how fast a team can ship, and how long the build stays useful before it needs a full rebuild.

What Is "Weight" on a Website?

Website weight is the total cost of every element on a page — measured in load time (milliseconds), cognitive effort (how hard a visitor has to think), and maintenance overhead (how much work it takes to update). A 4MB hero image, an animation library loaded on every page, a CMS structure with 15 unused fields, a navigation menu with 47 links — each one adds weight. And unlike a race car, where you can weigh the thing on a scale, website weight hides in places most teams never look.

In engineering school, we learned about sprung vs. unsprung mass — the weight your suspension carries versus the weight your wheels carry. Unsprung mass hurts performance disproportionately because it's closer to where the rubber meets the road. Websites have their own version of this. A bloated CSS file or an unnecessary JavaScript library sits right at the point of contact between your site and your visitor's browser. It affects every single page load, every interaction, every scroll.

Google's Core Web Vitals research backs this up. Pages that load in under 2.5 seconds (good LCP score) have significantly lower bounce rates than pages loading in 4+ seconds (web.dev, 2024). But getting there usually has less to do with adding a faster CDN or upgrading your hosting, and more to do with removing the things that are slowing you down in the first place.

Why Do Most Websites Carry Too Much Weight?

The short answer: because most web projects are additive by default.

Someone on the team asks for a parallax section. A designer adds a scroll-triggered animation. The marketing team wants a chatbot widget, a cookie banner, a pop-up, and a sticky CTA bar. The developer includes a JavaScript library for each one. Nobody's tracking the cumulative cost of these additions because each one seems small in isolation.

This is what engineers call "scope creep" in manufacturing, and it kills performance the same way on a website as it does in a car. Every gram matters when you're trying to go fast.

I've seen this pattern across dozens of projects before companies come to us. The site launched clean and fast, then accumulated weight over 18 months of "just add this one thing" requests until page loads crept past 5 seconds and nobody could pinpoint why.

The fix isn't a performance audit tacked on at the end. It's building with a subtraction-first mindset from day one.

How Does Subtraction-First Design Work in Practice?

Here's what subtraction-first design actually looks like when you apply it to real Webflow projects. I'll use three clients we've worked with because the pattern shows up differently depending on the company's stage and needs.

Column Tax: Rebuilding Lighter Each Time

Column Tax is the fastest-growing US tax filing startup in nearly three decades, with $26.8M raised. We've been their Webflow partner since September 2021 — over 4 years now. What makes Column Tax a good example of subtraction is that we've done multiple complete site rebuilds with them as they've grown.

Each rebuild was an opportunity to strip out what wasn't working. The first version had a page structure that required developers for every landing page update. The rebuilt version used a component-based Webflow system that gave their marketing team complete autonomy. Page deployment dropped from weeks to 2-3 days — a 90% reduction in deployment time. Pages load in under 3 seconds.

The interesting part is that each rebuild didn't just add new features for their growth stage. It actively removed complexity from the previous version. Fewer one-off page layouts, fewer custom classes, fewer dependencies. The site got more capable and lighter at the same time. That's the Chapman principle in action — subtract weight, go faster everywhere.

Sisu Clinic: Maximum Scope, Minimum Build Time

Sisu Clinic is a healthcare company with 25+ clinics across 4 countries and $15M raised. Their site needed 85+ pages, 30+ CMS collections, and 4 separate Webflow projects to serve different regions. That's a big, complicated build by any standard.

We built it from scratch in 4 days.

That number sounds aggressive, and it was. But it was only possible because we didn't carry unnecessary weight into the project. No speculative features. No "we might need this later" sections. Every component earned its place on the page. The CMS architecture was structured so tightly that adding new clinic locations and services later took minutes, not days.

Their CMO Spencer called us "literally the definition of a godsend." That wasn't because we added impressive features — it was because we built a system that's fast to update and fast to load for patients across 4 countries on Webflow Enterprise.

Vividly: Staying Light Over 3.5 Years

The hardest test of subtraction-first design isn't launch day — it's Year 3. Vividly is a CPG trade promotion management platform with $63M raised and a $30M Series B. They serve enterprise brands like Liquid Death and Bulletproof. We've been their Webflow partner since June 2022, and we've shipped 50+ projects together, including 62 platform enhancements in 2024 alone.

Over 3.5 years and 4 homepage redesigns, the default pull is always toward accumulation. New features to announce, new customer logos to add, new campaign landing pages. The discipline is in evaluating what to keep and what to strip with each iteration. Their team gets 2-3 day turnaround on new pages because the component library stays lean and well-organized — not because we keep bolting on more tools.

Their CEO reported "marked spikes in traffic and inbound marketing initiatives bringing more leads than ever before." That growth came from a site that got progressively cleaner, not heavier.

What Should You Remove From Your Website?

If you're looking at your own site and wondering where the weight is, here are the most common places we find it across the 50+ Webflow sites we've built since 2019:

This isn't about making a site feel minimal or stripped-down visually. A lightweight site can look rich and detailed. The weight we're removing is structural — the stuff visitors never see but their browsers definitely feel.

The Engineering Mindset vs. The Agency Mindset

Most web agencies approach a project by asking the client what they want, then building all of it. The deliverable is measured by completeness — did we build everything on the list?

An engineering approach measures the deliverable differently. Did we solve the problem with the least possible weight? Is every component earning its place? Can the system be maintained by the people who'll actually use it, without accumulating dead weight over time?

At Digi Hotshot, we've been a Webflow Premium Partner long enough to see what happens to sites 2, 3, 4 years after launch. The ones that stay fast and useful are always the ones that were built light, not the ones that launched with the most features. TenOneTen Ventures, a VC firm with 4 unicorns in their portfolio and $1B+ in realized exits, came to us for a WordPress-to-Webflow migration. We built the site in 6 weeks, and they've had 3+ years of marketing autonomy since — no developer bottlenecks. That kind of durability comes from a light, well-structured build that doesn't accumulate technical debt.

Colin Chapman would've understood web performance intuitively. The goal was never to add more power. It was to remove everything that doesn't make the car faster. Same principle, different medium.

Key Takeaways

Talk to Us

If your site feels slow and you're not sure what's weighing it down, we can take a look. We've done this analysis for 50+ Webflow sites across SaaS, fintech, healthcare, and cybersecurity. Get in touch and we'll walk through it together.