Do you build on WordPress or something custom?

Whichever the project justifies. WordPress when you need to edit content constantly and want a familiar admin. A static build when speed and security matter more than a plugin ecosystem. Custom PHP and MySQL when the logic is genuinely yours. The choice is explained in the quote with its trade-offs, not presented as a foregone conclusion.

Can you migrate my Ottawa site without losing rankings?

Yes, and the redirect map is the whole job. Every existing URL is mapped to its new equivalent with a 301 before launch, and anything with no equivalent goes to the closest relevant page rather than the homepage. Sites lose rankings in migration because that mapping was skipped, not because migration is inherently risky.

Will the site actually rank in Ottawa search results?

The build handles what is technically controllable: crawlable HTML, correct headings, structured data, fast pages, a clean sitemap and Search Console set up on day one. Ranking also depends on your competitors, your domain's age and the links pointing at you, which no developer controls. Anyone guaranteeing a position is guessing or lying.

What happens if I am not happy with the result?

Work is delivered in milestones against a written scope, and you review each one on a staging URL before it is paid for. If the delivered milestone does not match the scope, it gets corrected before anything moves forward. That structure exists so disagreement is resolved at the stage it happens rather than at the end when it is expensive.

Can you fix my existing site rather than rebuild it?

Often, yes, and it is usually the cheaper answer. Speed problems, a broken mobile layout, a form that silently fails or missing structured data are all fixable on the site you already have. I will tell you which of the two you need after looking, and a rebuild only gets recommended when the fix would cost more than starting again.

Do you provide ongoing maintenance after launch?

Thirty days of snag fixes are included after launch at no extra cost — anything that does not work as specified gets fixed. Beyond that there are monthly plans for updates, backups, monitoring and small changes. They are optional and cancellable; a site handed over properly does not require a retainer to keep running.

How long does a Ottawa project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

Ontario · Canada

Website speed and performance optimisation in Ottawa

A Lighthouse score on a developer laptop with fibre broadband is not a measurement of your site — it is a measurement of the laptop. The work here is judged on field data from real visitors on real phones, which is also the data Google actually uses. For Ottawa businesses, quoted in CAD from $80, typically live in 4 days.

What website speed and performance optimisation includes for a Ottawa business

Fixed scope, agreed in writing before development starts. From $80, typically live in 4 days.

Field-data baseline from Chrome UX Report where your traffic supports it, plus throttled lab testing where it does not
Largest Contentful Paint work: the actual LCP element identified, then preloaded, resized and served in a modern format
Interaction to Next Paint work, which usually means shipping less JavaScript rather than reordering it
Cumulative Layout Shift eliminated: dimensions on media, reserved space for embeds, metric-matched font fallbacks
Render path fixed — critical CSS, deferred non-essential script, and third-party tags audited for what they cost
Image pipeline: AVIF and WebP with correct srcset, and lazy loading applied below the fold only
Caching and compression configured at the server, including long-lived immutable assets
A before-and-after report with the numbers and the method, so you can reproduce it rather than trust it

The terms for a Canadian client

Starting price	From $80, quoted and invoiced in CAD
Typical timeline	4 days once content is supplied
Tax position	GST/HST at 5–15% depending on province — my invoices are zero-rated exports and carry no Canadian tax
Data protection	PIPEDA federally, with Quebec Law 25 layered on top if you have Quebec customers — resolved by a written DPA naming Pakistan as the processing location, which PIPEDA requires you to disclose to your own customers
Payment rails available	Stripe, Interac e-Transfer for deposits, and Moneris where an existing merchant account has to stay
My day in Ottawa time	00:00–09:00 — a shifted window is agreed in writing instead

Why this matters for Canada specifically

Quebec Law 25 caught a lot of Canadian sites out: consent has to be explicit and granular, and the default cookie banner most agencies drop in does not meet it. I build the consent layer properly rather than bolting on a plugin.

The performance budget every Ottawa build is held to

Pages are built to a hard weight limit rather than optimised afterwards, because retrofitting speed onto a heavy site is several times the work of not making it heavy. In practice that means no framework runtime on a content page, fonts subset to the characters actually used, and images generated at the sizes actually displayed.

For Canada specifically this is a commercial number, not a vanity one. A visitor on mobile data who waits four seconds is frequently a visitor who is gone, and the analytics will record it as a bounce rather than as the lost sale it was. Core Web Vitals is simply the name Google gave to noticing this.

Manufacturing, wholesale and B2B in Ottawa

A B2B site in Ottawa serves two audiences with opposite needs. A buyer wants specifications, tolerances, lead times and a downloadable datasheet. A procurement officer wants your company registration, insurance, certifications and payment terms. Serving both from one undifferentiated "About" page serves neither of them.

The highest-value feature is almost always a searchable product or capability index carrying real part numbers, because that is what engineers search for. It is unglamorous, it is a database problem rather than a design problem, and it produces enquiries that arrive already qualified.

Images shipped at ten times the size they display

A hero photograph exported at 4000 pixels wide and displayed at 400 is the most common single cause of a slow page. The browser downloads all of it and then discards most of it. On a phone over mobile data that is several seconds spent waiting for pixels nobody will ever see.

The fix is generating each image at the sizes actually used, serving AVIF or WebP with a fallback, and setting explicit width and height so the layout does not jump while they load. It is mechanical work with a directly measurable result, which makes it the first thing worth doing on almost any Ottawa site.

What I am not claiming about Ottawa

I have no office, postal address or phone number in Ottawa
I cannot meet you in person, and if that is a requirement you should hire locally
I am not claiming existing clients in Ottawa specifically — my live work is listed on the work page and you can check it
Nothing on this page is a guarantee of search rankings, which no developer can honestly offer