Both are measurable from outside, in an afternoon. Pick the one that is your problem and I will send you the measurement within 48 hours — free, no call, yours to keep.
One operator, Shopify only. Each sprint is 30 days with a written guarantee.
PageSpeed: median of three mobile runs (98 · 98 · 100), Lighthouse 13.5.0. SEO: 0 failed; the other 7 test product and collection pages, which this site does not have. Raw output
Neither of these is a pitch you have to take on trust. Drag the scrubber; read the check list. Then decide which of the two is costing you more.
Three seconds into the load, one of these two stores has shown nothing. Same store, same connection, before and after the sprint.
Twenty-two technical checks decide whether it can crawl, index and understand your catalogue. The whole list is public, and you can repeat every one of them yourself.
Sold separately, one at a time. Two sprints in one month would mean cutting one of them short, and then neither guarantee is defensible.
Not a PDF attachment. A link to a page on this domain that loads in under half a second — a consultant who emails you an 8 MB file has already answered your question. You pick one track; the shape of the report is the same for both.
On speed, what the delay costs you every month, with the formula and coefficient printed underneath. On SEO, how many of the twenty-two checks you fail — a count, not a currency, because revenue lost to indexing cannot be measured from outside without inventing it.
Same test, same day, same connection. Your store beside two others in your niche — because a second in the abstract means nothing, and a second behind a rival means everything. You name the two; guessing them would produce a false comparison.
Five. Not twenty. A twenty-point report doesn't get read, it gets postponed. Each one says what's happening, what it costs, and what I'd do — with the metric, the source and the date attached. On the SEO track each finding cites the check it comes from.
Written out to the click: which screen in your Shopify admin, which button, and how to check it worked. If you apply it, see the number move, and never speak to me again, the audit did its job.
Three weeks on the speed track, four on SEO — the fourth is the re-crawl, because a schema change nobody has re-crawled is deployed, not finished. Either way this is the entire scope of the sprint, written down. Hand it to your own developer if you'd rather; it's yours.
Where the numbers have been drifting and what the next app install will cost. No drama. Slow stores rarely break on any particular day, which is exactly why they stay slow for years.
Twenty minutes in a calendar, if you want them. No second CTA, no newsletter, no drip sequence disguised as a resource.
PageSpeed Insights for lab data and the CrUX History API for what your real users have been seeing. On the SEO track, your store's own responses — no API keys, nothing you have to grant me.
Its metric, its value, its source and the date it was taken. A number without those four does not appear — the section renders empty instead.
I read it, check the numbers against the live tools, and record the walkthrough. Nothing is sent that I haven't looked at first.
Two slots, one per track, both waiting on real measurements. Public-store teardowns are labelled as teardowns — an unaffiliated demo is worth more than a fabricated client.
Reserved for the first paid speed sprint. Publishing it needs four things: the client's permission, the before capture, the after capture, and the date of each.
What the sprint covers →Reserved for the first paid SEO sprint. Both audit runs, the first and the re-crawl, published side by side with the date of each.
What the sprint covers →You send the store URL and say which track. You get a Loom and a written, prioritised report. No call.
We record the starting numbers together, so the result at the end is not my word against yours. It is also what the guarantee is measured against.
Work happens on a duplicated theme. Nothing goes live until you approve the diff. One track at a time.
The same measurement, run again. On speed that is the closing PageSpeed and vitals; on SEO the re-crawl with every failed check green.
Building and shipping websites since 2014, the last years of it inside ecommerce, where the difference between a fast page and a slow one shows up in the checkout numbers rather than in a report.
I work on the two parts of a store that are not a matter of opinion: how fast it is, and whether a crawler can read it. Both are measurable before I start and measurable when I finish, and both of us can see the number.
Shopify only. One sprint at a time. That is the whole offer.
Placeholder. If you have traffic that is not converting, start with speed. If you have a catalogue that Google barely shows, start with SEO. Both free audits are free — take the one you are less sure about.
Not in the same month. One operator running both sprints at once has to cut one of them short, and then neither guarantee is worth anything. Back to back they fit in 50 days — three weeks of speed, then four of SEO — for $5,150, and both guarantees still stand.
Placeholder. Either I hand over a prioritised diff and they ship it, or I ship it and they review. Both work, and the second is faster.
Placeholder. Staff access to a duplicated theme. The live one is never touched until you approve the diff. The free audit needs nothing at all — just the URL.
Placeholder. No. Both methods are Shopify-specific, which is exactly why each takes 30 days instead of a quarter.
Either audit is free, takes 48 hours, needs nothing but your store URL, and arrives without a call attached.