Skip to content
03

Performance &Technical SEO

I start with traces and crawls, not guesses: bundle graphs, render paths, canonical logic, structured data. Then I fix the few things actually costing you speed or visibility, and prove each one.

Typical timeline
3 – 6 weeks
Engagement
Audit or fixed scope
Price
Quoted after a short call
Questions answered
7

Who it is for

Who this is for,and what you get.

Performance work goes wrong when it starts with a list of best practices. It goes right when it starts with a profile: measure the real thing on real devices, find the two or three decisions actually costing the time, and change those. Technical SEO is the layer underneath your content — making sure the pages you have can be crawled, rendered, understood and ranked. Both are systems problems, and both are usually where the losses are.

Businesses whose website or app feels slow on a mid-range phone even when the lab score looks fine.

Teams whose pages are not being indexed, or are indexed incorrectly, and who need to know why.

Owners facing a redesign or migration who cannot afford to lose the rankings they already have.

Outcomes

01A written baseline from real devices and field data before anything changes.

02A prioritised list of fixes, each one measurable on its own.

03Fixes shipped in priority order, with before-and-after figures.

04Budgets or monitoring so the improvement does not quietly erode.

Signals

Signs you needthis work.

  • 01Lighthouse is green in the lab and the field data disagrees.
  • 02Pages are indexed that should not be, and pages are missing that should be.
  • 03A redesign or migration lost traffic and nobody can say exactly where it went.

Process

How the work runs.

Typically 3 – 6 weeks. You get a working build, with a short demo, every week, and on final payment the code, the accounts and the documentation are yours. The full process

01

Baseline

Real devices, real network, real data — recorded before anything changes, plus a crawl of what the machines actually see.

02

Diagnose

Traces and index coverage until each cost is attributable rather than suspected.

03

Fix

The smallest set of changes that moves the number, shipped independently and in priority order.

04

Verify and hold

Re-crawl, field data, and budgets or monitoring so the next release cannot quietly undo it.

Included

What is included

Lighthouse and field-data baseline

Technical audit and crawl analysis

Bundle, dependency and query audit

Schema and JSON-LD implementation

Core Web Vitals remediation

Migration and redirect mapping, when needed

Typical stack

Chrome DevTools

Lighthouse

Search Console

Web Vitals field data

JSON-LD

Bundle analysis

Timeline
3 – 6 weeks
Price
Quoted after a short call

Questions

Questions,answered plainly.

No, and nobody honest does. I can make sure the technical layer stops being the reason you are not ranking; what you publish, and what your competitors do, still matters.

None before I have measured. After the baseline I give you a specific target and the changes required to reach it.

Almost never. Most of the win is removal, not replacement — a dependency nobody remembers adding, a query behind a convenient call, a render that runs four times.

No. I work alongside your writer or agency and make sure what they publish is structured to be found.

Performance improvements register quickly. Crawl and index fixes can move within weeks, and anything promised in days is a sales pitch.

Yes — that is the usual case. I start by reading how it is built, then say what I would change and what I would leave alone.

Preferably. The fixes stick when your team understands why they worked.

The other core services

Design and website work is also available.

Start here

Have a projectthat needs this?

Tell me what you are trying to achieve and I will come back with an honest view on scope, sequence and whether performance & technical seo is really the thing you need first.