Service

Performance & SEO

Core Web Vitals and technical SEO fixed at the source, with the numbers to prove it.

Two things are usually true of a site that is not performing: it is slower than its owner believes, and it is invisible for reasons that have nothing to do with content. This service fixes both, at the cause, and shows you the measurements either side.

Performance, in the order that works

There is a correct order, and most sites are optimised in the wrong one. Queries first. A home page running unbounded queries, a category page loading every term, a plugin fetching remote data on every request — no amount of caching makes that architecture good, it just hides it from the person testing.

Then the critical path. Render-blocking CSS and JavaScript, fonts loaded from a third-party domain or, worse, injected by a JavaScript load listener so the headline paints last. Fonts get self-hosted as subset woff2, with the display face preloaded and everything else on font-display: swap.

Then images. Modern formats, explicit width and height so nothing shifts, lazy loading everywhere except the LCP image, which gets fetchpriority="high" instead.

Caching last. Configured, with the sitemap, robots.txt and the REST API excluded — because a cache that stores a 404 at your sitemap URL will serve it to Googlebot for weeks while every browser you test with sees a perfectly good page.

Technical SEO, at the source

The audit looks for the things that quietly cap a site: duplicate or missing titles, no meta descriptions, multiple h1 elements per page, headings that skip levels, orphan pages nothing links to, thin pages competing with each other, and canonicals that point somewhere unhelpful.

Then the fixes: a title and description pattern that is unique on every URL and editable per page, one h1 per page, a heading structure that reflects the actual outline, self-referencing canonicals, visible breadcrumbs that are also marked up, and internal links that give every page a path in.

Structured data that validates

A single JSON-LD graph rather than five plugins arguing: Organization and Person so the brand resolves as an entity, WebSite with a search action, plus Service, Article, FAQPage, BreadcrumbList and product types where they apply. Every template is validated against the Rich Results Test before launch — not assumed to be correct because a plugin emitted it.

Ranking for your own name

If you cannot be found for your own brand, the problem is almost never keywords — it is that the brand string does not appear in your title, your heading, or your first hundred words, and that nothing off-site links back with a consistent name. That is an entity problem. The fix is on-page and off-page together, and where a same-name competitor already exists, it takes four to ten weeks to settle even once everything is correct. Anyone promising days is selling something.

What you receive

The audit, the fixes, and re-measurement of every template — plus Search Console and Bing Webmaster verified, the sitemap submitted, indexing requested, and a short written record of what changed and why. No badge, no monthly report that says “improving”.

What you get

Everything below ispart of the build.

  • A measured audit: lab and field data, not a plugin's score badge
  • LCP, INP and CLS fixed at the cause — queries, render-blocking assets, fonts, images
  • Self-hosted fonts, correct preloads, and images in modern formats with dimensions set
  • Titles and meta descriptions unique on every URL, editable per page
  • A structured data graph: Organization, Person, Service, Article, FAQ, Breadcrumbs
  • A sitemap and robots.txt that return 200 to a bot, verified with a plain request

How it works

From first callto launch day.

  1. 01

    Measure

    Lighthouse on the templates that matter, field data where it exists, then a crawl to find the duplicate titles, the orphan pages and the URLs that 404 only for bots.

  2. 02

    Fix at the source

    Query and asset work before caching. Caching is the last step, never the fix.

  3. 03

    Verify and submit

    Re-measure every template, validate the structured data, then Search Console and Bing: verified, sitemap submitted, indexing requested.

Tech

  • Lighthouse
  • Core Web Vitals
  • Search Console
  • Schema.org
  • WordPress
  • PHP 8

Questions

Asked before.

Let's build something that earns trust — and converts.

Tell me what you are building. You get a straight answer on scope, timeline and cost — not a sales sequence.