Engineering

Modern Web Development: What Actually Moves the Needle

Framework arguments are the most visible part of web development and close to the least important. On the projects we have measured, the difference between a fast application and a slow one almost never came down to which library rendered the view.

  • KeyCode Team
  • 9 July 2026
  • 1 min read

Where the time actually goes

Profile a slow business application and the same three culprits show up, in roughly this order of impact.

  • A query with no supporting index, run once per row of a list.
  • A JavaScript bundle that ships every screen to a user who opened one.
  • Images served at four times the size they are displayed at.

The unglamorous fixes

Route-level code splitting, an index that matches the query plan, and correct cache headers on hashed assets will beat any framework migration — and they take days rather than quarters.

Caching in particular is routinely misconfigured. Asset filenames carrying a content hash can be cached for a year and never revalidated. The HTML entry point cannot: it must be revalidated on every visit, or a freshly deployed site keeps serving yesterday's bundle.

When the framework does matter

It matters for the team, not the browser. A framework your engineers know well, with a component model your designers can work against, will produce a better product than a technically superior one nobody on the team has shipped before.

The takeaway

Measure before optimising. The bottleneck is usually in the database or the network, and it is almost never where the argument is happening.

Want this applied to your business?

Tell us what you are trying to fix. We will come back with a scope, a timeline and a fixed price — usually within one working day.