A speed report in plain English, backed by the real numbers
See exactly what your visitors wait through when your site loads on a phone.
Most owners have never watched their own site load on a phone the way a visitor does. So my team built shaka-perf: it loads your site like a real visitor, films every second, and reads it back in plain English, with the real numbers behind it.
Justin Gordon, founder, ShakaCode
You send one URL. I send back a short report by email, usually within a few days. No call, no signup.
A real report, nothing staged
Watch your site load the way a visitor does
This is babybathwater.com loading on a real visitor's phone, over mobile data, filmed frame for frame. I only test public pages anyone can already load; yours stays private to you.
On a phone, over mobile data
Blank for about 3 seconds, then it loads. Your visitor sits through that wait; you rarely watch it yourself, because you open your own site on a fast desktop or wifi.
Here is what the tool found on babybathwater.com, in three numbers.
of blank screen before the homepage shows its main content
on the slowest page (the Events page), the wait runs even longer
key pages the report flags "needs improvement"
"The page takes about 3 to 4 seconds to show its main content - slower than ideal - but once it does, it runs smoothly and doesn't stutter."
The report's own plain-English read on the babybathwater.com homepage
Every one of those blank seconds is a moment a visitor can decide they're done and leave - and you never know they were there. If you pay to bring that traffic in, you are paying to send people to a screen that is still blank when some of them leave. Your site has seconds like these too; you just haven't watched them yet.
Whatever your site runs on - Shopify, a course or funnel platform, a custom app - the things that slow a page down are the same underneath. ShakaCode has been a React and Rails shop since 2015, and we maintain React on Rails, open-source tooling teams around the world build on.
The tool checks every page, then points you at the worst one
The slowest page here is the Events page - and this is what's holding it back
The tool loads every key page the way a real visitor does, then hands you the bottleneck: the one page costing you the most, with the specific reason it's slow.
before the main content appears on the Events page - longer than most visitors will wait
downloaded across 80+ separate files before the page settles
of it loads before anything appears on screen at all
Every site has one page quietly costing it the most. On babybathwater it's the Events page: the main content takes about four seconds to appear, because the page loads about two-thirds of a megabyte across 80+ separate files, and most of it lands before anything shows on screen. That's the page's own weight, and it's fixable once you know which page it is. Send me your URL and I'll find yours.
Why not just run PageSpeed?
A score tells you there's a problem. This shows you where it is.
You can get a Google PageSpeed score in thirty seconds. The trouble is it hands you a number and a list of jargon, then leaves you to decode what it means for your business. This gives you the real numbers too - but read back in plain English, with the slow page filmed so you can see it.
A PageSpeed score
- A number out of 100 and a list of technical audits
- One URL, measured once
- Acronyms with no plain-English read
- Leaves you to figure out what it means for your business
This report
- The real numbers, plus a plain-English sentence per page on what they mean
- Every key page, plus the scrolls and clicks real visitors make
- A frame-by-frame film of the load - you watch what your visitor stares at
- The slowest page named, and the reason it's slow - not one score for one URL
What you get back
A short report anyone on your team can read
Not a fix-it ticket - a clear diagnosis, in plain language, of where the time is going:
- Which of your key pages is slowest, and by how much - in plain English, with the real numbers.
- A frame-by-frame film of each page loading - exactly what your visitors watch while they wait.
- Where the weight is - how many separate files load before anyone sees anything.
- A read on whether it's a quick fix or something structural - named plainly, so your team knows where to look.
Who's behind it
We've been fixing slow sites since 2015, and we maintain React on Rails
The offer
Want this report for your site?
Send me the URL you care about most. I'll run shaka-perf on your key pages and send you a report just like the one above - the load filmed frame by frame, the plain-English read, and the one page slowing you down most. You get a quick note that I have it, then the report in the same thread, usually within a few days. It's free.
Or just email me at [email protected]. I only test pages anyone can already visit - nothing behind a login - and whatever you send stays between us: I'm not adding you to a list, and there's no follow-up unless you reply.
A few honest answers
Questions you're probably asking
Is this going to turn into a sales call?
No call unless you ask for one. You get a written report by email; if it makes you want to talk, you reply - and if it doesn't, that's genuinely fine.
What if I already have developers?
Even better. Hand it straight to your team or agency - they get a clear picture of what's slow and where, with none of the guesswork. The report is yours to run with; there's no move here to step in on anyone's work.
What if my site is already fast?
Then I'll tell you that in one line, and you'll have something in writing to show your team. The sites that are already quick get a fast all-clear - that's worth knowing too.
Does it matter what my site is built on?
No. Shopify, WordPress, a course or funnel platform, a custom app, a SaaS dashboard - the things that slow a page down are mostly the same underneath.
How do you measure it?
The tool loads your pages as an emulated mid-range phone on a throttled mobile connection, in real Chrome - the standard mobile profile. Each page runs a few times, so the read is steady, not one lucky or unlucky load.
What if I want to fix what it finds?
Up to you, and up to whoever you trust - your own team or anyone you bring in. If you do make changes, the same tool measures the before and after, running each side several times, so you see how much faster each page really got, not a one-off guess.