Manifest position 481 · CrUX rank bucket 1000
https://www.rightmove.co.uk
Coverage complete
Coverage-complete agentic audit of seven representative public states. Authenticated account changes, financial applications and real agent-contact submission were excluded to avoid credentials or external side effects.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Under emulated prefers-color-scheme: dark, the body remained rgb(255,255,255), text remained rgb(83,83,95), and computed color-scheme was normal. The dark screenshot is visually identical to the light capture. f-dark medium: Dark preference is ignored |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce the media query matched and no active animations remained. |
respect-user-preferencesrespects-contrast | pass | high | Forced colors and high contrast matched; text became white on black and primary controls retained visible 2px borders. |
implement-natural-interactionsview-transitions | pass | medium | The consent surface dismisses with a short visual transition and the resulting property-search state remains coherent. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling or scroll-linked reveal was present on the sampled routes, so there was no scroll-linked motion implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | medium | Native scrolling remained responsive, showed no horizontal overflow and did not expose custom gesture behavior fighting the platform. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The listing scroll video shows the same full filter/header chrome while content moves; no progress or reduced chrome state appears. f-scroll-chrome low: Persistent chrome does not react to scroll state |
provide-guided-navigationanchored-positioning | pass | medium | Menus and filters remained visually attached to their controls in sampled states; no edge drift was observed. |
provide-guided-navigationdirects-attention | pass | high | Active search tabs, result count, breadcrumbs, map view and clear property CTAs preserve orientation across templates. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and 360px screenshots on every representative route show a modal covering the primary content before interaction. On mobile it occupies most of the viewport. f-consent-interstitial high: Cookie consent blocks the entire first view |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM probe found aria-modal=1 but zero <dialog> elements and zero popovers on home, listing, detail and valuation routes. f-consent-semantics medium: The modal is not implemented with the native dialog primitive |
maximize-content-reduce-noisereduced-chrome | pass | medium | Outside the consent interruption, the primary search and property content dominate the viewport and mobile chrome collapses appropriately. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Every sampled mobile route reported horizontalOverflowPx=0 and scrollWidth=clientWidth=360 with a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | medium | Components reflow across all five templates without overflow; home inline CSS includes @container and uses logical properties. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The DOM probes found at least 30 visible controls below 24px in one dimension; the listing clear button also lacks an accessible name. Focus itself was visible. f-targets medium: Several controls have undersized pointer targets |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home clearly offers Buy/Rent/Sold search; listing identifies 28,228 South London results; detail exposes contact actions; valuation asks for a postcode. |
support-core-task-successprimary-flow-completion | pass | medium | The public journey from search intent to listing to a live property detail and agent-contact affordance was reachable without authentication; real submission was excluded to avoid side effects. |
support-core-task-successclear-system-state-and-recovery | issues | high | A deliberately unknown URL returned HTTP 200 rather than 404. The captured first view remained behind the consent interstitial, weakening error recognition and recovery. f-recovery high: Unknown routes return a misleading success response |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured listing LCP at 33,720ms, TBT at 1,121.5ms and performance 0.38. Home LCP was 2,646.6ms and TBT 634.5ms. f-cwv high: The listing template is far outside good load thresholds |
be-fast-and-stablevisual-stability | pass | high | Observed CLS was 0 to 0.000009 across sampled mobile routes; Lighthouse listing CLS was 0 and home CLS 0.00138. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse measured 1,121.5ms TBT on listing and 634.5ms on home; the trace also recorded a 92.87ms long task. f-main-thread high: Heavy script work blocks the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | The home HAR recorded 65 requests and 2.93MB transferred, including 1.99MB script and 2.46MB third-party bytes. It also found a parser-inserted stylesheet and script candidates plus an uncompressed JS resource. f-delivery high: The initial network is dominated by script and third parties |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 1,514,686 bytes of unused JavaScript and 46,116 bytes of unused CSS; a featured-customer bundle appears repeatedly in the waste list. f-unused-code high: The listing ships large amounts of unused and duplicated code |
be-inclusivenames-roles-labels | issues | high | Lighthouse found an unnamed clear button, an unlabeled sort select, prohibited aria-label on a roleless div, and repeated visible Contact labels that do not match their accessible names. f-a11y-names high: Listing controls have broken names, roles and labels |
be-inclusivesufficient-contrast | pass | high | Lighthouse listing color-contrast passed and forced-colors preserved visible text and primary control borders. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed heading-order on listing; its footer jumps to H4. DOM probes also show H1 followed directly by H3 on listing and article routes. f-a11y-structure medium: Heading structure skips levels on key templates |
be-inclusivelegible-text | pass | medium | Headings and body copy remain readable with comfortable line lengths and no clipping on the sampled templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | All five mobile layouts had zero horizontal overflow and viewport scaling was allowed, but probes repeatedly found at least 30 visible controls smaller than 24px in one dimension. f-a11y-targets medium: Mobile reflow works, but target sizing remains inadequate |
follow-best-practicesno-console-errors | issues | high | Lighthouse and the HAR recorded repeated HTTP 401 failures from the Elastic APM RUM intake endpoint. f-console medium: A monitoring endpoint fails during normal load |
follow-best-practicessound-document-and-assets | issues | high | The image probe found all four home images missing width/height, all four oversized and three legacy JPEGs; Lighthouse found multiple estate-agent logos rendered at aspect ratios that do not match source assets. f-assets medium: Images are unsized, oversized or distorted |
follow-best-practicesbrowser-platform-hygiene | issues | medium | Lighthouse found many large first-party scripts with missing maps and several advertised .map URLs returning 400/404. f-platform-hygiene low: Production bundles expose broken or absent source-map links |
be-discoverabletitle-and-description | pass | high | All sampled public routes have unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Representative pages have viewport metadata, real href links and crawler-visible content; Lighthouse SEO scored 1.0 on home and listing. |
be-discoverablecanonical-and-indexing-signals | issues | high | Home and valuation probes found no canonical URL, while an unknown route returned HTTP 200. The site does provide robots.txt, a large sitemap and canonical URLs on listing/detail/article templates. f-indexing-signals high: Canonical and status signals are inconsistent |
be-discoverablestructured-and-shareable-metadata | issues | high | The property detail and listing probes found zero JSON-LD blocks; home also lacked Organization/WebSite JSON-LD. The article template was the only sampled route with JSON-LD. f-structured-data medium: Commercial entity pages lack structured data |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirmed HTTPS but found no CSP, HSTS or X-Content-Type-Options. The cookies primitive reported all eight observed cookies without Secure. f-security-headers high: Core transport and content defenses are absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before consent choice, the HAR recorded 49 third-party requests and 2.46MB third-party transfer. The tracker probe found 11 third-party origins and five known tracker domains; the dialog names 215 partners. f-third-parties high: Tracking starts with a very large third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login probe found an email input with no autocomplete token and no passkey/WebAuthn text or code signal. No permission prompt appeared on sampled page loads. f-auth medium: Authentication lacks modern autofill and passkey signals |
be-private-and-securedefensive-browser-policies | issues | high | Headers inspection found no frame protection, Referrer-Policy or Permissions-Policy in addition to missing CSP and HSTS. Several first-party cookies use SameSite=None without Secure. f-browser-policies high: Browser-enforced defensive policies are missing |
be-resilientprogressive-enhancement | pass | high | Raw HTML retained 74% to 92% of rendered content tokens; none of the five routes was a JS shell and each preserved an H1/title. |
be-resilientresilient-runtime-behaviour | pass | medium | Sampled overlays, filters and scrolling remained within the viewport and no runtime blank state was observed. |
be-resilientoffline-and-installable | not-applicable | high | This live property marketplace depends on current inventory and contact services; offline operation is not a meaningful core journey. A manifest appears only on valuation and no service worker controls sampled routes. |
be-resilientnetwork-and-http-failure-states | issues | high | The unknown-route test returned 200 OK rather than a 404 status, so caches, crawlers and users cannot reliably distinguish failure from success. f-http-failure high: HTTP failure semantics are not resilient |
be-internationalisedlang-dir-and-logical-properties | issues | high | Sampled pages use en, en-GB and en-US despite UK content. Inline-CSS probing found logical-property use on home but not on listing, detail, article or valuation templates. f-i18n-structure medium: Language and directional foundations are inconsistent |
be-internationalisedlocale-aware-data | pass | medium | Sampled UK listings and editorial content present pounds sterling and human-readable UK property dates consistently. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public routes contain no scheduled cross-time-zone event flow or user-entered time data to assess. |
be-trustworthyno-dark-patterns | pass | medium | The consent dialog gives Accept all and Reject all equal prominence, names the partner count and provides settings; sampled listing prices and contact actions are plainly labelled. |
be-trustworthyhumane-error-handling | issues | high | The valuation probe found postcodeInput is not required; its empty value reports checkValidity() true, aria-invalid is absent, and no alert/error text was present. f-form-errors medium: The valuation postcode field has no enforceable empty-state feedback |
be-trustworthytrustworthy-input-assistance | issues | high | The login email field has an empty autocomplete value, the valuation postcode has none, and location search explicitly uses autocomplete=off. f-autocomplete medium: Key inputs opt out of useful browser assistance |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login surface offers email continuation only; the probe found no WebAuthn/passkey signal and the email input lacks autocomplete. Actual account changes were excluded to avoid side effects. f-account-flow medium: The sign-in entry does not advertise phishing-resistant authentication |
be-sustainableoptimised-assets | issues | high | All four probed home images were oversized for their rendered size, four lacked intrinsic dimensions and three used JPEG; below-fold images were not lazy-loaded. f-sustainable-assets medium: Asset delivery wastes image bytes |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimated 1.51MB unused JS on listing, while home loads repeated analytics/advertising tags and sends APM requests that fail with 401. f-wasteful-work high: Large unused scripts and failed telemetry consume resources |
be-sustainablethird-party-and-media-budget | issues | high | On home, 49 of 65 requests and 2.46 of 2.93MB transferred were third-party; Google Tag Manager alone accounted for about 1.25MB. f-third-party-budget high: Third-party code is disproportionate to first-view value |
be-agent-readystructured-agent-capabilities | issues | medium | The sampled routes expose no WebMCP/agent tool signals, property pages lack JSON-LD, robots.txt blocks GPTBot, and Lighthouse agentic-browsing scored 0.33 on listing. f-agent-ready low: Property capabilities are not exposed in a structured agent-facing form |
be-agent-readyon-device-inference | not-applicable | high | No built-in AI inference is required for the sampled property search, listing, detail, editorial or valuation tasks. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten down/up scroll cycles, DOM nodes stayed at 630 and used JS heap decreased from 37,769,460 to 37,702,009 bytes. |
be-memory-efficientbounded-footprint | pass | low | Fresh snapshots were about 39.9MB to 41.6MB self-size; live metrics showed about 37.8MB JS heap and 630 DOM elements, proportionate though worth monitoring for a large marketplace. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | low | Across ten repeated scroll cycles DOM count remained exactly 630 and JS heap fell slightly; this gives no sign of unbounded retained DOM in the exercised interaction, though listener internals were not independently counted. |
Provenance
Canonical report: results/atomic/reports/0481-www_rightmove_co_uk.json
Report SHA-256: 7733589592faef192805025fdab42f5e3a49febe9acaefc8e06a61cff2542cde
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_rightmove_co_uk/2026-07-21T02-23-46-685Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_rightmove_co_uk/2026-07-21T02-23-46-685Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.