What actually makes a WordPress site slow

It usually isn’t the server, and a caching plugin won’t fix it. A look at where the weight really comes from, and why the fastest asset is the one you never ship.

Ask why a WordPress site is slow and you will usually be told to install a caching plugin. Sometimes that helps. More often it hides the problem for logged-out visitors while the underlying site stays heavy, and the first person to reach an uncached page waits to find out.

The honest answer is less satisfying: most slow WordPress sites are slow because they load an enormous amount of code that the page does not use.

Where the weight comes from

A typical multipurpose theme install pulls in something like this on every page load, whether or not the page needs any of it:

  • jQuery, plus two or three plugins that depend on it
  • An icon font with several thousand glyphs, for the six icons in the header
  • A slider library, because one demo used a slider
  • A lightbox library, in case there is a gallery
  • A page builder’s runtime CSS and JS, which is usually the largest single file
  • Google Fonts requested from a third-party domain, blocking render

None of these are individually outrageous. Together they can add up to more than a megabyte before a single image loads, and much of it is render-blocking.

Caching does not fix this

Caching makes the server respond faster. It does nothing about the browser having to download, parse and execute a page builder’s JavaScript before it can paint text. That work happens on the visitor’s device, usually a mid-range phone on a mobile connection, not the laptop the site was designed on.

The fastest asset is the one you never ship.

What we ship instead

Varnify themes have no jQuery, no icon font, no slider library, no page builder and no bundled plugins. Fonts are self-hosted, so there is no third-party connection to negotiate before text can render. The colours, type and spacing are set once in theme.json, and the rest is one stylesheet of the theme’s own, with no framework underneath.

The result is not a clever optimisation. There is simply less there. That is the whole trick, and it is available to any theme willing to give up being everything to everyone.