SiteFit / Business
SiteFit: useful page measurements when a speed-service result is unavailable
New source work adds direct page-weight evidence, more precise markup findings and broader sitemap sampling.
Work covered: Oct 7, 2026
An unavailable service should not erase all evidence
The October 7 audit work added direct page-weight measurement so a report can still describe the page when a PageSpeed result is unavailable. It records information such as transferred and expanded page size, script presence and eager versus lazy images. This is measured page evidence, not a replacement Core Web Vitals score.
Check what the page actually provides
New findings cover placeholder structured-data values, language alternatives that send an inner page to a homepage, and missing shipping or return-policy details in product offers. The checks report a finding only when the sampled pages provide something to judge. That keeps an absent measurement from being disguised as a clean pass.
Read beyond the wrong first sitemap
The work also corrected sampling that could stop at an unhelpful first child sitemap. It reads a broader bounded set, decodes entities and skips non-page entries. Request pacing was adjusted so a rapid audit is less likely to provoke a storefront response that looks like a broken link but is actually a traffic limit.
Source milestone, separate from deployment
The record includes tests and an exercised report from this code. It does not confirm a later live deployment beyond the separately documented October 6 release. The meaningful advance is richer, better-qualified audit evidence, with clear distinctions between a direct page measurement, a third-party metric and an unmeasured result.
Explore the product
Based on dated development and release records from September 25–October 8, 2026. Availability and acceptance are stated for the recorded milestone.