GF Builder GF Builder

Speed

A page only downloads what is on it.

Most builders ship their whole framework to every page. GF Builder splits its CSS by block family and its JavaScript by block, and WordPress loads each piece only where that block renders.

CSS

Per block family

A base sheet plus 21 group sheets. A page with no cards never downloads card styles. Animation CSS loads only where something animates, and the phone drawer only on sites that use it.

JAVASCRIPT

Per block

Only 30 of the 80 blocks ship any front-end JavaScript, each as its own file loaded where the block appears. A typical page carries a few kilobytes of GF script.

SERVER

Nothing built per request

CSS and JS are compiled ahead of time. No content scanner, no per-request CSS build, and no Node needed on your host.

Measured, not guessed

Around 100 KB of CSS and JavaScript per page, compressed.

We measure every release by building real pages from our own patterns and weighing every stylesheet and script the HTML asks for. The figures include WordPress's own Interactivity runtime. They exclude images and fonts, which depend on your content.

Test pageCSS + JS, gzip
Hero page≈ 101 KB
Shop page≈ 98 KB
Blog post≈ 102 KB
Portfolio page≈ 113 KB

Release 2.32 baseline. Later releases split the editor bundle and trimmed the base sheet further.

On live sites

Google PageSpeed, desktop.

Measured October 25, 2026. Scores move run to run. Run them yourself with the links above.

Keep it fast

The plugin is lean. The rest is up to your site.

Large hero photos, slow hosting and heavy third-party plugins cost more than any builder. These habits keep scores high, especially on phones.

  • Compress and resize your hero image. It is usually the biggest thing on the page.
  • Use the post loop's built-in image sizing rather than full-width images in grids.
  • Audit plugins that load scripts on every page, such as chat widgets, sliders and link tools.
  • Do not paste raw HTML with its own style or script tags. If you keep needing to, tell us which control is missing.
  • Use page caching and a CDN from your host.

Start lean. Stay lean.