Compare
SiteRune vs PageSpeed Insights
· Configuration notes, not a newsroom.
PageSpeed Insights is Lighthouse on a Google URL. SiteRune does not run Chrome. Use PSI for LCP/INP proof. Use SiteRune for headers, robots, schema, and the CMS playbook.
PADifferent instruments
PageSpeed Insights executes a browser, records a filmstrip, and scores Core Web Vitals in lab (and field if CrUX has you). That is the right proof after you change a hero image.
SiteRune fetches HTML and headers, walks interior URLs, fingerprints the CMS, and writes nginx / Vercel / WordPress snippets. It will not give you INP. It will tell you GPTBot is banned and /docs is noindex.
When to use which
- PSI: you shipped next/image and need LCP in writing.
- SiteRune: you need the configuration chapter and a paste-ready CSP/HSTS/llms.txt.
- Both: SiteRune playbook first, then PSI on the money URL to prove runtime.
Capability table
| Capability | SiteRune | PageSpeed Insights |
|---|---|---|
| Lab Core Web Vitals | No | Yes |
| Field CrUX when available | No | Yes |
| Multi-page crawl | Yes | One URL |
| Security headers | Yes | No |
| robots.txt / AI-bot policy | Yes | No |
| CMS-specific playbook | Yes | No |
| Paste-ready config files | Yes | No |
| Free | Yes | Yes |
FAQ
Does SiteRune replace pagespeed?
No. Use the comparison table. SiteRune is a hosted configuration brief with CMS dialect and ship files. It does not replace rank tracking, backlink graphs, lab Core Web Vitals, or a desktop site-wide crawl.
What does a SiteRune scan actually fetch?
HTML and headers from this vantage point, robots.txt, sitemap, llms.txt, security.txt, and a polite walk of same-origin interiors. No headless Chrome. No exploits.
Run it on a live URL
Same scan engine. Guest scans stay free.