Case study 01: kleto.com

We did this to our own site first.

Before asking anyone to pay for the process, we ran it on kleto.com. This page is the honest record: what we found, what we changed, what moved, and what did not. It updates as the numbers change.

Situation

A site with the exact problems we fix

In August 2026 kleto.com had them all. Fonts and icons loaded from third-party servers, slowing every visit. Two pages were silently broken. The structured data in the page head described content that was no longer on the page. The 404 page did not work. The FAQ was invisible to crawlers.

What we changed

One week of implementation

Measured result

Before and after, lab tested

Google Lighthouse, run on this site before and after the week of work. Lab numbers move a few points between runs. We show the trend, not a cherry-picked best.

LighthouseBeforeAfter
Accessibility8694
Performance6670 to 75 across runs
Best practices100100

What did not move yet: the Lighthouse SEO score, still 69, because the biggest remaining items are content, not code. That work is in progress. We publish the score either way.

AI mentions

Does ChatGPT mention kleto.com?

Not yet, and we will not pretend otherwise. AI answers change slowly and this site is young. We monitor mentions of kleto.com in AI answers with the same tooling we set up for clients, and we will publish them here as they appear. That is the honest version of this section.

Timeframe

One week

Everything above happened in one week of August 2026, alongside other work. A client project gets the same process with more hands-on hours: six weeks, start to handoff.

Your site next

Tell us what you sell.

A founder replies within two business days. Or start with the free mini-audit.

Get started