Site performance

Fast pages. Clear structure. Measured results.

I optimize the images, the scripts and the interactions, then test representative pages before launch. I also check the technical foundations that help search engines find and understand the content.

A slow site wastes the traffic you paid to acquire, usually for the same few reasons: oversized hero images, third-party scripts on every page, and animations that make the browser work harder than it needs to.

I build for performance from the start: optimized images, deferred scripts, clean markup and lightweight interactions, then test representative pages before launch rather than after it.

The other half is whether machines can read the site at all. Clear content, crawlable pages and accurate structured data help a search engine or an assistant understand what the business does. None of it promises a ranking or a citation.

lighthouse.report

Performance

100

Accessibility

100

Best practices

100

SEO

Agent readiness

3 / 3

Targets rather than results: what I build to and test against before launch. Scores move with the page, its content and the conditions of the run.

Technical search foundations

Readable by machines, not just by people.

The first two are checks I run on every build. The last two are optional, and the second of them is an emerging standard rather than something a visitor's assistant can be assumed to support.

Machine-readable by default Technical search foundations

llms.txt 01
```
# MigrateToAstro
> Webflow Professional Partner

## Services
- Migrate to Webflow
```
An optional overview of the site and its important pages, for the tools that support the format. No search engine requires one.
JSON-LD 02
```
{
  "@type": "ProfessionalService",
  "name": "MigrateToAstro",
  "areaServed": "Worldwide"
}
```
Relevant JSON-LD describing the business, the services and how the pages relate, validated against what the page visibly says.
robots.txt 03
```
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: PerplexityBot
Allow: /

Sitemap: /sitemap-index.xml
```
Sitemaps, canonical addresses and crawler settings checked against the pages you intend to be indexed. Robots rules manage crawling; private content needs access controls rather than a rule.
Agent actions 04
```
{
  "tools": [
    { "name": "book_call" },
    { "name": "get_pricing" }
  ]
}
```
Where it is useful, structured actions implemented and tested for compatible browser agents, with the ordinary interface alongside them. WebMCP is an emerging standard, so the definitions below are illustrative of the shape rather than a guarantee that a given assistant supports it.

Next step

Want to know what is slowing your site down?

Send the URL and what you are seeing. I will look at the site and tell you which changes are worth doing first.

Discuss your site

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.