A free audit call, measured in a real browser first
Thirty minutes on WhatsApp or by phone, free, no obligation. Before we talk, your site is rendered page by page at five screen widths, with speed, layout and checkout measured rather than estimated. You leave with a straight answer — and a written quote afterwards, only if you want one.
To book: message +1 (213) 426-1571 on WhatsApp with the link to your site and a time that suits you, or call +1 (213) 426-1571, or email contact@alphadigital-studio.com. Replies within one working day, in English or French.
Why an online score is not an audit
Free tools give you a number for one URL, generated on a simulated device. That number is real, and it is also almost useless on its own, because the three most expensive faults I find are invisible to it.
- Sideways overflow. A product name one word too long makes
a grid column refuse to shrink, the page grows wider than the phone, and
the whole thing scrolls left-to-right. The detector is
scrollWidth > clientWidth— a score cannot see it, andoverflow-x: hiddenhides it from you while it keeps happening. - Layout shift from a spike, not an end state. A gallery stacks all six images before it builds itself into a carousel: the page is 6,000 pixels tall for a second and a half, everything below jumps, then it folds back. Screenshot the finished page and it looks perfect. Only sampling the height over time catches it.
- Touch targets under 44 pixels. A link that works fine under a mouse and misses under a thumb. Nobody reports this, they just leave.
None of these are exotic. All three came out of real audits, and each one was costing its owner customers who never said a word.
What gets measured before the call
| Area | What is actually checked |
|---|---|
| Speed | Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift — per page, not site-wide |
| Mobile layout | Every page rendered at 320, 360, 390, 768 and 1440px; overflow measured element by element |
| Touch targets | Every interactive element measured against the 44px threshold, width as well as height |
| Checkout or contact | The path walked end to end: product, options, add to basket, basket, or form submitted |
| Technical SEO | Titles, canonical tags, sitemap, indexability, structured data — verified in the served HTML |
| Broken things | Console errors, dead links, images that never load, forms that go nowhere |
Every check tests for expected content, never just a 200 status. A page can answer perfectly and still show nothing — a shop with a "coming soon" switch left on serves a cheerful holding page with a 200 and zero products. An audit that only checks status codes reports 100% green on a store that is selling nothing at all.
How the call goes
- You book it. WhatsApp, phone or email — send the link to your site and a time. If there is no site yet, say so; the call is still worth having.
- I measure first. Your site is rendered and measured before we speak, so the thirty minutes are spent on findings, not on loading pages together.
- We talk. What was found, what it costs you, what fixing it involves, and whether it is worth fixing at all. Plain English, no score out of 100.
- You get it in writing. A short summary afterwards, yours to keep and to hand to anyone. A quote in US dollars or euros follows only if you ask for one.
The call is free on purpose. An audit paid for by the person who wants the repair contract is not an audit, it is a quote wearing a lab coat. Making it free and separate is what makes the findings worth hearing — including the finding that your site is fine.
Questions people actually ask
Why is it free?
Because it is the first hour of any job I would do for you anyway, and charging for it twice would be dishonest. It also means the findings are not shaped by what I would like to be paid to repair: if your site is fine, I say so, and we both move on.
How is this different from running PageSpeed Insights myself?
Run it — it is free and you should. It gives you a score for one URL on a simulated device. What it cannot tell you is that your category page overflows sideways at 320px, that a block pushes the whole page down for 1.6 seconds before folding back up, or that your checkout breaks between step two and step three on an actual phone. Those are the things that cost you sales, and they only show up when a real browser renders the page and something measures what happened.
What do I actually receive?
The call itself — thirty minutes, in plain English, about what the measurements found and what they mean for your business. Then a short written summary by email or WhatsApp, listing what was found and what fixing it involves, ordered by what costs you the most money. You can hand it to any developer, not just to me.
Do I have to buy anything afterwards?
No. If you want a quote, you get one in writing, in US dollars or euros, the same day or the next. If you do not, the summary is yours and that is the end of it. Nobody follows up three times.
I don't have a website yet. Is the call still useful?
Yes — then it is about the site you need rather than the one you have. Bring what you know about your customers and any site you like the look of; you leave with a clear picture of what to build, what to have ready, and what it would cost.
Do you audit Shopify and Wix sites too?
Yes. The measurements are the same whatever the site runs on. What changes is how much of it you can act on — on a hosted platform some findings are the platform's to fix, not yours, and I say which is which instead of listing things you cannot change.