Gemin Get in touch

Site performance

Sites that perform, not just sites that look good.

What I do to keep a site fast, and what I add so search engines, answer engines and AI agents can read it properly.

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. The scores below are what that adds up to.

Increasingly the first visitor is not a person. It is an AI agent researching or summarizing your business for someone else. I include structured data and machine-readable signals as standard, so search engines, answer engines, and AI agents can understand and cite your site.

lighthouse.report
99

Performance

100

Accessibility

100

Best practices

100

SEO

2/2 Agentic browsing new in Lighthouse

The benchmarks every project is tested against before launch.

AEO and GEO

Built to be cited, not just crawled.

Four artefacts I ship as standard. Each one tells a different kind of machine what your business is and what it can do here.

Machine-readable by default AEO and GEO ready
  • llms.txt 01
    # Gemin Pak
    > Webflow Professional Partner
    
    ## Services
    - Migrate to Webflow

    Tells language models what your product is and which pages to cite, so you are quoted accurately instead of guessed at.

  • JSON-LD 02
    {
      "@type": "ProfessionalService",
      "name": "Gemin Pak",
      "areaServed": "Worldwide"
    }

    Organization, Service, Person and Breadcrumb markup, so engines read structure rather than inferring it from your layout.

  • robots.txt 03
    User-agent: GPTBot
    User-agent: ClaudeBot
    User-agent: PerplexityBot
    Allow: /
    
    Sitemap: /sitemap-index.xml

    Every page discoverable, nothing wasted on crawl budget, and clear rules for which agents get access.

  • WebMCP 04
    {
      "tools": [
        { "name": "book_call" },
        { "name": "get_pricing" }
      ]
    }

    Site actions exposed as tools an agent can actually call, like book a call or pull pricing, instead of guessing from the DOM. Still an emerging standard; I build for it now.

Reach out and see if we are a good fit.

Start a conversation

Currently booking two to four weeks out.