On-page SEO
Title, meta description, headings, canonical, structured data and indexability of the exact page you enter.
Free SEO and Core Web Vitals audit
What the free audit checks
Core Web Vitals
A real Lighthouse score with the LCP, INP and CLS that Google ranks on, measured through PageSpeed Insights.
Crawlability
robots.txt, indexability headers and whether search engines can reach and index your pages.
AI crawler access
Whether ChatGPT, Claude, Perplexity and Google AI can crawl and cite your store, and whether you ship an llms.txt file.
Structured data
JSON-LD schema for rich results in Google and citations in AI answers.
Sitemaps & i18n
Sitemap health, URL coverage and hreflang for multi-language and multi-region stores.
Images
Alt text, explicit dimensions, modern formats (WebP/AVIF) and responsive srcset. These are the image issues that hurt LCP and CLS.
Social & icons
Open Graph and Twitter/X cards, plus favicon, apple-touch-icon and web manifest in the right sizes.
Security
Security headers like HSTS, CSP and X-Frame-Options, plus accidental exposure of .git or .env.
Privacy & consent
Third-party trackers and whether a cookie-consent banner is in place. These are your GDPR signals.
Delivery & stack
Compression, caching, CDN, TLS version, HTTP/2 or 3 and the JS framework running the site.
Sustainability
Page weight and an estimated CO₂ per visit. Lighter pages are greener and convert better.
1. Audit
This free report plus a manual deep-dive on your store.
2. Plan
A prioritized, fixed-scope plan with effort and impact.
3. Fix
I turn the findings into real fixes for speed, SEO and conversion.
Want these issues fixed? I'm a senior frontend architect for eCommerce. I turn audits into faster, higher-converting sites, whatever stack you run.
Discuss your project100+ stores audited and rebuilt across 30+ industries over 10+ years.
Questions about the free audit
Is the audit really free?
Yes, and there is nothing to sign up for. Paste a URL, read the report. No account, no card, and no email needed to see your results. At the end you can ask for a copy by email, and that is the only point where you hand over an address. If you do, it reaches me directly, because I read them myself.
What does the audit actually check?
Around 60 signals in three groups. Technical SEO covers indexability, canonicals, robots.txt, sitemaps and internationalization. Performance runs Lighthouse for lab metrics and pulls Chrome's field data for the same URL where it exists. The third group is the one most checkers skip: whether AI crawlers can reach you at all, llms.txt, security headers and structured data. You get one health score plus the per-signal detail behind it.
Why does my report show lab metrics instead of real-user data?
Because Chrome only reports field data for a URL once enough real visits have accumulated, and plenty of legitimate sites never reach that threshold. When it is missing, the report falls back to Lighthouse, which is one synthetic run on a throttled device rather than a measurement of your visitors. That is still useful for finding a cause, but it is not what Search Console grades. Reading a failed Core Web Vitals assessment covers the difference and what to do when you have no field data at all.
How long does the audit take?
Under a minute in most cases. The technical checks return quickly and Lighthouse is the slow part, because it loads your page on a throttled connection twice, once as mobile and once as desktop. A heavy page can push past a minute. The finished report is cached for six hours, so running the same URL again comes back instantly.
Do you store the URL I audit?
The finished report is cached for six hours against that URL, which is what makes a repeat run instant, and it expires on its own. That is the whole of it: no account is created, nothing is published, and the site you check is not added to any list. If you enter an email to receive the report, that address is used to send it and to reply to you about it.
The score is low. What should I fix first?
Order the work by how predictable the fix is rather than by how bad the number looks. Layout shift is usually a missing width and height, or a banner injected above the fold, and reserving the space removes it outright. Largest contentful paint is usually an oversized hero image, or an element that cannot start loading until JavaScript has run. Interaction latency comes last, because it lives in the component architecture rather than in a setting. The full order and the reasoning is in the Core Web Vitals write-up.