Webflow Web Development

Introduction

Northwind had outgrown a site that took three days and a developer to change a headline. The brief was to keep the look, lose the bottleneck, and stop the page weight climbing every quarter.

Auditing What Was Already There

Before drawing anything we catalogued every page in the existing site and grouped the layouts by what they actually did rather than what they were called. Forty-one templates collapsed into nine repeating patterns, and two of those nine accounted for most of the traffic.

Building a Composable Section Library

We rebuilt the front-end around a small set of composable sections, each configurable from structured content. Editors now assemble pages without touching markup, and the component list is short enough that nobody invents a seventh button style.

• Every section takes typed content, so an empty field degrades to a sensible layout instead of a broken one.
• Variants are props rather than copies, which keeps one place to fix a spacing bug.
• The library is documented against real pages, so an editor can see what a section looks like before choosing it.

Holding the Performance Budget

A rebuild only stays fast if regressions are visible. We set a page-weight budget per template and wired it into the build, so a heavy asset fails the check rather than quietly shipping.

• Images run through the asset pipeline and are served at the width the layout actually requests.
• Client-side JavaScript is scoped to the handful of components that genuinely need it.
• The budget is checked on every build, not audited once at launch.

Conclusion

Load time fell by just over half on mobile, and the first content-heavy launch after handover shipped without engineering involvement. A year on, the section list is still nine entries long.