Skip to content
EN
Free · 30 minConsultation →
05 Pricing Prices and packages 07 About me Who I am, how I work
Language
PLPolskiEN (US)Englishcoming soonEN (CA)EnglishRUРусскийcoming soonITItalianocoming soonESEspañolcoming soonDEDeutschcoming soonFRFrançaiscoming soon
01 Services
Not sure where to start?Short quiz, 1 minute. I’ll suggest what will bring you customers fastest.→
02 Industries All →
03 Cities All →
60cities and towns 6up to 700 km from Winnipeg 36further, over Zoom
Clients in Winnipeg, the rest of Canada online
04 Case studies All →
06 Knowledge All →
Core Web Vitals · mobile speed · light code

Website speed
optimization

Website speed optimization usually means patching a heavy site with more plugins. I take the other route: pages built light from the start, with sized images, minimal scripts and nothing loaded that the visitor doesn't need. Fast on a bus, in a basement, on a rural connection.

Free: a 30-minute call, an action plan and a price range in writing.

Website speed optimization: man at a bus stop waiting for a slow web page to load on his phone
Why sites get slow

Seconds that
cost customers

Slow sites are rarely slow for one reason. Usually it's a pile of small things that grew over the years.

Photos straight from the camera

A 6 MB hero image shown in a 400-pixel box on a phone. Multiply by a gallery of twenty.

Images

Every plugin loads everywhere

The booking widget, the slider and three trackers all load on every page, even where they're not used.

Scripts

Heavy first screen

Four font families and an autoplay background video before the headline appears.

Fonts and video
How I build fast

Speed decided
at the design
stage

Hand-written code

No builder markup, no theme options, only the code each page uses.

Responsive images

Several sizes and modern formats generated automatically; the browser picks the right one.

Scripts on demand

Maps, chat and booking load only where needed, often only after a tap.

Fonts kept lean

One or two families, limited weights, loaded so text shows immediately.

Stable layout

Space reserved for images and banners, so nothing jumps while the page loads.

Process

From slow
to light

1

Measure

Lab and field data for key pages on mobile, and what slows them.

2

Decide

If the site is mine, I fix it. If not, I explain why a rebuild is the real fix.

3

Rebuild

New light site on your domain, content and rankings carried over.

4

Verify

Real-device tests and field data after launch.

Pricing

What a fast
site costs

I don't sell speed patches for sites built by others. Final prices in Canadian dollars.

Fast landing page[01]
from $1,300 CAD

For ads that land on a slow page today.

  • Ready from 10 days
  • Light code
  • Tracking included
Landing pages→
■ Rebuild on your domain[02]
from $3,000 CAD

A new light business website with your content and redirects.

  • Hand-coded or custom CMS
  • Redirect map
  • Speed checked before launch
Website redesign→

Why website speed optimization matters for a local business

Website speed optimization isn't about winning a test. It's about the person standing in a store parking lot in Sudbury or riding the SkyTrain in Vancouver, searching for your service on a phone with patchy signal. If your page takes too long to show something useful, they tap back and choose the next result. You never see them in your enquiries; they simply don't exist for you.

For businesses running ads, speed has a direct price. Every visitor who leaves before the page loads is a click you paid for that never had a chance.

What actually makes a page slow

From the sites I review, the usual culprits are:

  • Oversized images. Photos uploaded straight from a camera or phone, shown at a fraction of their size.
  • Scripts loaded everywhere. Booking widgets, chat bubbles, sliders and several tracking tools on every page.
  • Builder and theme overhead. Layers of generated code for features the site doesn't use.
  • Fonts. Several families and weights, loaded before any text appears.
  • Embedded media. Map and video embeds that pull in large amounts of code before anyone presses play.
  • Layout shifts. Banners and images that push content around as they load, which feels slow even when it isn't.

Core Web Vitals in plain words

Google measures page experience with three numbers. Largest Contentful Paint asks how quickly the main content appears. Interaction to Next Paint asks how quickly the page responds when someone taps. Cumulative Layout Shift asks whether things jump around while loading. I design and build with all three in mind: the main content is light and loads first, scripts are kept small, and space is reserved for every image so nothing shifts. The broader technical side is covered in technical SEO.

Why I rebuild instead of patching

Speed patches on someone else's site usually mean caching plugins, script delays and image compression tools stacked on top of the problem. They can improve a test score while making the site more fragile. The next theme update, a new plugin or a change by another developer undoes them.

So I'm direct about it: I don't patch sites built by others. If your site is slow, I build a new, light one on your domain, move your content and set up redirects so you keep your rankings. If only your ads suffer, a fast landing page can solve the urgent part in about ten days. The hand-coded website page explains why my sites are light from the start.

What you can check yourself

Open your site on your own phone with Wi-Fi off. Count how long until you can read the headline and see a way to contact you. Then try a page with a gallery. If it feels slow to you, it feels slower to a stranger who doesn't know your business yet. For a list of quick fixes you can try before a rebuild, read slow website fixes.

Hosting, briefly

Hosting matters, but less than people think. A light site on modest hosting usually beats a heavy site on expensive hosting. Hosting and domain are agreed individually with each client, and I'd rather spend your budget on clean pages than on server upgrades that hide the real issue.

After launch

Speed degrades over time as tracking tags, widgets and large images get added. I show you how to upload images properly through the edit panel, which resizes them automatically, and I check new tags before they go on the site when I manage it. Field data in Search Console shows how real visitors experience the site month to month.

Related

Faster pages,
more leads

FAQ

Speed
questions

Can you guarantee a PageSpeed score?

No, and be wary of anyone who does. Scores depend on hosting, tracking tags you add later, embedded videos and Google's own changes to the test. What I control is the code and images: they won't be what slows your site down. I check real-device loading before launch and field data afterwards.

Why won't you just speed up my current site?

Because on a site built by someone else, especially an old theme with many plugins, speed fixes are fragile. Removing one script breaks a feature, caching plugins clash, and the next update undoes the work. A rebuild on the same domain is more predictable and leaves you with code you own.

Does speed affect Google rankings?

Page experience, including Core Web Vitals, is one of many signals Google uses. It rarely outweighs relevant content, but between similar pages it can tip the balance. The bigger effect is on people: slow pages lose visitors before they see your offer, especially from ads.

Will a fast site still have photos and video?

Yes. Speed isn't about removing content, it's about delivering it sensibly: right-sized images, video that loads only when played, galleries that load as you scroll. A portfolio full of photos can still open quickly.

Is your site
slow on a phone?

Send me the address. I'll look at what slows it down and tell you honestly whether it needs a rebuild, within one business day.