01 / HTMLClient rendering can delay the useful page
A JavaScript application may eventually paint a complete interface while its first HTML response contains little more than an empty root element and script references. Modern search engines can render JavaScript, but rendering costs time, introduces another failure point and may separate discovery from understanding. A strong server response exposes the page title, primary heading, useful copy and crawlable links immediately.
This checker counts visible words and anchors in the returned source rather than the hydrated browser DOM. Fewer than 50 words and fewer than three links are warning thresholds, not universal ranking rules. A login screen may legitimately be sparse; a commercial landing page usually should not be.
02 / CACHEA CDN can serve the wrong release perfectly fast
Edge caching improves performance when the cache policy matches the content. It becomes dangerous when HTML is cached as if it were an immutable asset. A deployment can succeed at the origin while the canonical address continues returning an older document. Visitors, validators and search crawlers then observe different realities depending on the cache key.
The tool requests the page normally and with a unique query parameter. It compares status, title, canonical, H1, word volume and link volume. A meaningful mismatch is reported as possible stale cache. Small dynamic changes are intentionally ignored; the aim is to find structural divergence, not timestamps or rotating labels.
03 / INTERPRETATIONUse the verdict as a diagnostic, not a ranking score
“Server-rendered” means the primary document is materially present in HTML and consistent across both requests. It does not certify content quality, indexation or search performance. “Likely client-rendered” means the source is unusually thin and deserves inspection. “Possible stale cache” means the two retrieval paths expose different core documents.
Review canonical URLs, hreflang, JSON-LD and the H1 list alongside the verdict. Those fields reveal whether the correct page identity and structure survived the delivery path. If the result is unexpected, repeat the check after a deployment and inspect your framework output, reverse-proxy rules and CDN cache configuration.
