Dew Advisors
← SEO claims board Cluster 05 ยท 13 claims

Page experience: Core Web Vitals, mobile-first indexing and HTTPS

The site-side half is clean: HTTPS, redirects, HSTS, mixed content, resource crawlability and mobile/desktop parity all pass across about 180 URLs. The failures are all in field data, and the trend matters more than the level. Mobile LCP improved sharply, while desktop LCP, mobile INP and CLS all got worse. A single 28-day window would have shown none of that. 5.8 stays Pending: 12 of 25 pages gate content behind a click, and no vetted tool yet tests whether that content is absent from what Google indexes, so the verdict fails toward Pending.

8
Pass
2
Gap
1
Partial
1
N/A
1
Pending
5.1Gap
Largest Contentful Paint (LCP), how quickly the main content renders, should occur within 2.5 seconds of the page starting to load to be rated 'good'.

LCP p75 was about 4.4 s on mobile against the 2.5 s threshold, and about 2.8 s on desktop. The breakdown points at resource discovery, not server speed: the largest single contributor was the delay before the LCP image began downloading. The history series tells two stories. Mobile improved 46% from late June, then plateaued at 1.75 times the threshold. Desktop passed in early August, then regressed. Limit: the 28-day window spans at least four production deployments, so the p75 averages different versions of the site. A single window would have shown none of this.

checked 2026-09-01result mobile fail, desktop failtool crux-field-data
5.2Partial
Interaction to Next Paint (INP) should be under 200 milliseconds; INP is now the stable responsiveness metric that replaced FID.

INP p75 was about 450 ms on mobile against the 200 ms threshold, and about 150 ms on desktop. The direction matters more than the level: mobile INP worsened 94% across the history series while the performance work was focused on LCP. The same deployment caveat as 5.1 applies.

checked 2026-09-01result mobile fail and worsening, desktop passtool crux-field-data
5.3Gap
Cumulative Layout Shift (CLS), visual stability, should be less than 0.1.

CLS p75 was 0.30 on mobile and 0.17 on desktop against a threshold below 0.10. This is the sharpest regression in the cluster: mobile CLS was 0.03 in late June and rose roughly tenfold, and desktop doubled. Lab testing had pointed at one template, but the field data shows the problem is site-wide. The same deployment caveat as 5.1 applies.

checked 2026-09-01result both fail, sharp sustained regressiontool crux-field-data
5.4Pass
Core Web Vitals are assessed on real-user field data at the 75th percentile of page loads, measured separately for mobile and desktop.

The Chrome UX Report returns p75 values over a 28-day real-user window, separately for phone and desktop, as the claim says. The two form factors differ materially. Limit: all 50 URL-level probes returned no data, because Chrome holds too few samples for any single page. Per-page field assessment is unavailable at this site's traffic, which is a property of its volume, not a defect.

checked 2026-09-01result origin level confirmed, URL level unavailabletool crux-field-data
5.5N/A
There is no single 'page experience signal'; Google's core ranking systems look at a variety of page-experience signals (CWV, HTTPS, mobile-friendliness, avoiding intrusive ads) and reward good page experience, but relevance can still outrank a page with sub-par experience.

Describes how Google's ranking systems weigh page experience. It asserts nothing a site can pass or fail, so it is not measurable.

checked 2026-09-01result site-level
5.6Pass
Google indexes and ranks using the mobile version of a page, crawled with the smartphone Googlebot user-agent (mobile-first indexing).

URL Inspection reports crawledAs: MOBILE for all 25 priority pages, with recent crawl times, so this is current behaviour.

checked 2026-09-01result 25 of 25 Passtool gsc-url-inspection
5.7Pass
The mobile version must contain the same primary content, the same structured data, equivalent title/meta-description and robots meta tags, and the same image alt text as the desktop version.

No mobile/desktop differences across a stratified sample of about 180 URLs. Each URL was fetched with both smartphone and desktop Googlebot user agents and compared on title, meta description, meta robots, h1 count, JSON-LD, image alt text and word count.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check
5.8Pending
Do not lazy-load primary content behind user interaction; Google will not trigger interactions (swipe/click/type) to load content, so interaction-gated content is effectively not indexed. Use native loading="lazy" for off-screen (not primary) media.

12 of 25 pages show content behind a 'load more' click in the browser. The claim turns on whether that content is missing from the document Google indexes, and no vetted tool yet makes that comparison, so the verdict stays Pending.

result reported, no verdict
5.9Pass
Let Googlebot crawl the resources (CSS, JS, images) the page needs to render; don't block them with a robots.txt disallow rule, since a matched disallow prevents the crawler from accessing that URI.

Of about 36,000 subresources referenced across the sample, including scripts, stylesheets, images and iframes, none is disallowed to Googlebot.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check
5.10Pass
Serving pages over HTTPS is part of a good page experience and a lightweight ranking consideration; Google explicitly checks whether pages are served securely.

All sampled URLs are served over HTTPS, including the few that returned errors. Three transient 502s returned 200 on immediate recheck, so they are recorded as an availability observation.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check
5.11Pass
Redirect HTTP to HTTPS with server-side 301 (permanent) redirects and set the canonical link to the HTTPS URL so search engines treat HTTPS as canonical.

All sampled http:// URLs return a server-side 301 to the https:// URL. The canonical half is corroborated by 2.2 and 2.3: canonicals are self-referential on https:// pages.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check
5.12Pass
Use HTTP Strict Transport Security (the Strict-Transport-Security header) so clients connect over HTTPS directly on subsequent visits, preventing SSL-stripping downgrades.

Every sampled response carries Strict-Transport-Security with a one-year max-age and includeSubDomains. The preload directive is absent, but the claim does not require it.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check
5.13Pass
Avoid mixed content: load all subresources (scripts, styles, images, fonts) over HTTPS, because HTTP subresources on an HTTPS page are unprotected and browsers may block them.

No http:// subresources among about 36,000 on the sampled pages. Limit: this was measured on the Googlebot HTML view, so a subresource injected at runtime by JavaScript would not appear.

checked 2026-09-01result about 180 URLs, all Passtool page-experience-check

Want this run on your site?

We test your site against the same claims, record a verdict and the evidence for each one, and tell you what to fix first.

Start a conversation