PageSpeed Sampler
Measures a whole site instead of one URL. It finds the sitemap, groups the URLs by collection, samples up to ten per collection and one hundred in total, then measures every sample on mobile and desktop and averages the result.
Software I Own And Operate
Four products, all live, all running without me in the loop. Services are how you hire me and deliverables are what an engagement hands you. This collection is the third thing: the systems I built and operate myself, published here as evidence that the way I work is backed by software rather than by slides.
Products, Deliverables And Services
The site already separates two things, and this is the third. The boundary matters, because otherwise these pages get read as an offer, which none of them are.
| Section | The unit | What it answers |
|---|---|---|
| Services | The unit of sale | How you hire me |
| Deliverables | The unit of scope | What gets handed to you |
| Products | Software I own and operate | What I have built and run |
A product here is named, live, addressable software with its own URL that runs without me in the loop. A deliverable is a document an engagement produces. Two of these products exist to produce deliverables and a third exists to store them, but none of them are sold, and none of them are a substitute for the engagement.
The Four Products
Ordered by how open they are, starting with the one that needs nothing from you.
AuditBuilder
Findings management for SEO audits. Brands, then audits, then findings, with every finding stored as a structured record rather than a bullet in a document, which is what makes an audit sortable, exportable and comparable over time.
Analytics
A standalone app with its own auth and backend that connects to Google Search Console and GA4 and runs the same repeatable analysis across whatever it finds. It prefers the Search Console bulk export over the API wherever that export exists.
Client Portal
A client-facing deliverable store. Clients, then engagements, then deliverables as items inside an engagement, each holding named links and uploaded files. One permanent address, and the archive belongs to the client.
Why These Exist
None of these started as a product. Each one started as a part of my own work that did not hold up, and the fix turned out to be software rather than discipline.
- Measuring one URL was never the question. Performance lives in templates, so the sampler measures across templates and averages, which is what PageSpeed Insights will not do for you.
- An audit written as prose cannot be worked. Storing the finding as a forty-field record is what makes an audit sortable, exportable, and comparable against the last one.
- The same analysis was being rebuilt every engagement. Building it once, against a repeatable framework, is worth more than building it well once per client.
- Delivered work should not decay in an inbox. A permanent client address turns the archive into the client's property instead of a retrieval request aimed at me.
Two of them, AuditBuilder and PageSpeed Sampler, are open to anybody. The other two run for my clients. All four are described here at the same level of detail, including the parts that are deliberately missing.