Open to full-time roles
Hire me
Site speed

A fast site is part of the design.

Visitors do not wait for a slow page, and Google notices when they leave. I build Webflow sites to be fast from the start, and I fix sites that have become slow over time, without losing the design or the animations.

Why it matters

A slow page costs more than a few seconds.

People leave

Most visitors on a phone will not wait for a page that takes several seconds to show something useful. They go back to the search results.

Search rankings drop

Core Web Vitals are part of how Google ranks pages. A slow site competes with one hand tied behind its back.

Ads cost more

Paid traffic that lands on a slow page bounces before it converts, so every click is worth less.

Why Webflow sites get slow

Webflow is fast. What we add to it is not always.

Most slow Webflow sites I see have the same few problems. None of them are hard to fix once you know where to look.

Huge images

A 4 MB photo uploaded for a card that shows it at 400 pixels wide. Multiply that by a CMS list and the page gets heavy fast.

Too many scripts

Chat widgets, trackers, heatmaps and old embeds, all loading before the page is ready.

Heavy animation setup

Big Lottie files, autoplay videos in the hero, or interactions that run on every scroll event.

Fonts loaded the long way

Several font families and weights, some never used, blocking text from showing.

Layout that jumps

Images and embeds without a set size, so the page shifts while it loads.

Unused CSS and classes

Years of edits leave styles nobody uses, and the stylesheet keeps growing.

Core Web Vitals

The three numbers Google looks at.

You can check your own site for free. Open PageSpeed Insights, paste your URL and look at the mobile result first. The field data at the top shows what real visitors experience.

Open PageSpeed Insights

LCP, Largest Contentful Paint

How long until the main content shows, usually the hero image or heading.

Good: 2.5 seconds or less

INP, Interaction to Next Paint

How quickly the page reacts when someone taps or clicks.

Good: 200 milliseconds or less

CLS, Cumulative Layout Shift

How much the page jumps around while it loads.

Good: 0.1 or less
AI and me

AI finds the problems fast. I fix them properly.

I use AI tools for the slow, repetitive part of an audit. The decisions and the actual fixes are my work.

What the tools do

Crawls every page and CMS template, including pages nobody remembers

Runs speed tests across the whole site and reads the raw data

Groups hundreds of warnings into a few root causes

Drafts the first version of the report

What I do

Decide what is worth fixing for your goals

Build every fix by hand in Webflow, on your class system

Keep the design and animations exactly as they are

Test on real phones and slow networks

Explain the changes in plain language, with a Loom video

How a speed project works

From first test to fixed site.

Step 01

Measure

I test every page type on mobile and desktop and write down the starting numbers.

Step 02

Find the causes

Warnings are grouped into root causes, like one oversized image used across many pages.

Step 03

Plan the fixes

Each fix is ranked by impact and effort, so the biggest wins come first.

Step 04

Fix in Webflow

Images, scripts, fonts, embeds and interactions, fixed by hand without changing how the site looks.

Step 05

Test again

Every page is tested again and compared with the starting numbers.

Step 06

Hand over

A short report and a Loom video, so your team knows what changed and how to keep it fast.

How I can help

Three ways to work on speed.

Audit

Speed audit

A clear report of what slows your site down and what to fix first. Useful if your own team will do the work.

Ask for an audit
Fix

Audit and fixes

I find the problems and fix them in your Webflow project, then show you the before and after.

Fix my site
Build

Fast from the start

For new builds and redesigns, speed is part of every phase, not a task at the end.

Start a project
Questions

Things people usually ask.

Will my site look different after the fixes?

No. The design, content and animations stay the same. Only how they load changes.

Do you need access to my Webflow project?

For fixes, yes, usually as a guest or editor on the workspace. For an audit, the live site is enough.

Can you promise a 100 score?

No, and nobody honestly can. Third-party scripts you need may cost a few points. I aim for good Core Web Vitals for real visitors, which is what matters.

How long does it take?

An audit is quick. Fixes depend on the size of the site and what we find. You get a clear plan before any work starts.

Is your Webflow site slower than it should be?