Performance optimisation

Less to load. Faster to use.

We find what slows a site, store or portal down and take it out: scripts nobody needs, heavy images and fonts, unused code. Then we measure it again on a phone.

Start a project See the work
scripts on a rebuilt homepage
73 → 2
seconds to main content on a phone
0.3–0.5

[01] What you get

Where the weight goes.

An audit on real phones
Core Web Vitals from Chrome users where they exist, and a throttled phone test where they do not.
Scripts and apps cleared out
Tracking tags, page builders and apps that load on every page but help on few.
Images and fonts
Right sizes and modern formats, fonts trimmed to what the page uses.
Code weight
Unused CSS and JavaScript removed, the rest loaded only where it is needed.
Layout that holds still
Space reserved for images and banners so nothing jumps while the page loads.
Before and after
The same tests run before and after the work, on the same settings, so the numbers compare.

[02] Recent work

What we built and what changed.

Clients we have permission to name are named. The rest are described by what they do, with the real figures.

Client · Two WordPress sites rebuilt as static sites

Page builders out, two or three scripts left

A fire-safety firm and an industrial screening maker both ran on WordPress with a page builder. We rebuilt both as static Astro sites. The old homepages loaded 73 and 75 scripts. The new ones load two and three, and the HTML is a fraction of the size.

Figures are the homepage HTML of the live WordPress site against our rebuild, measured on the same day.

  • 73 → 2 and 75 → 3 scripts
  • Homepage HTML 324 KB → 129 KB and 253 KB → 83 KB
Homepage before and afterScript tags and HTML size, live WordPress site against our rebuild.
  • Fire-safety firm: scriptsBefore 73After 2
  • Screening maker: scriptsBefore 75After 3
  • Fire-safety firm: HTMLBefore 324 KBAfter 129 KB
  • Screening maker: HTMLBefore 253 KBAfter 83 KB

Dmsons Metal

A fast site from the first day

The Dmsons rebuild has no page builder and almost no JavaScript. In the pre-launch review the main content showed on a phone in 0.3 to 0.5 seconds, and nothing on the page moved while it loaded.

  • 0.3 to 0.5 s to main content on a phone
  • No layout shift
  • No page builder

Client · An apparel brand’s Shopify store

A lighter header on every page

The store’s header was 147 KB of HTML on every page, with icons pasted in as text. We rebuilt it so it lays itself out in CSS before any script runs, moved the icons into cached files and removed code nothing used. Measured on the development theme, the header dropped to 56 KB.

  • Header HTML 147 KB → 56 KB
  • Menu drawer 84 KB → 4 KB
  • Measured on the development theme

[03] How it works

How a project runs.

  1. 01

    Measure

    Phone tests and field data on the pages that matter: home, product, category, checkout.

  2. 02

    Find the weight

    Every script, app and file listed by how much it costs and what it does.

  3. 03

    Cut and rebuild

    Remove what is unused, rebuild what is heavy, keep what earns its place.

  4. 04

    Measure again

    Same tests, same settings, with the numbers side by side.

[04] Also from the shop

The rest of the workshop.

Contact

Tell us about the project.

A line on where things are now is enough. We will reply with what we would do first.

Rather email? [email protected]

Press ⌘/Ctrl + Enter to send.

Got it. Thanks.

Your enquiry is with us. Our reply will come from [email protected].