Compare
SiteRune vs GTmetrix and WebPageTest
· Configuration notes, not a newsroom.
Filmstrip tools run a browser. SiteRune does not. Use them for LCP waterfalls. Use SiteRune for TTFB from this vantage point, cache headers, and the CMS punch list.
GTLab Chrome vs a fetch
GTmetrix and WebPageTest execute the page, block third parties, show waterfalls. That is how you debug a hero image. SiteRune records TTFB of the HTML fetch and whether Cache-Control is no-store. No INP. No filmstrip.
Order of operations
If TTFB is 2s on SiteRune, the filmstrip is a funeral. Cache the document, then go to WebPageTest. If GPTBot is banned, the filmstrip will not tell you. Different instruments.
Capability table
| Capability | SiteRune | GTmetrix |
|---|---|---|
| Browser filmstrip / waterfall | No | Yes |
| LCP / INP lab metrics | No | Yes |
| HTML TTFB from the crawler | Yes | Yes |
| Cache-Control on the document | Yes | Partial |
| Technical SEO + robots + schema | Yes | No |
| Security headers | Yes | No |
| CMS playbook | Yes | No |
FAQ
Does SiteRune replace gtmetrix?
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.