Manifest position 845 · CrUX rank bucket 1000
https://wise.com
Coverage complete
Coverage complete across 58 atomic checks and four representative public templates plus login and error-state probes.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode probe matched prefers-color-scheme: dark but reported color-scheme: normal and the same light surface/text palette; the dark screenshot remains light. F01 medium: No dark theme is applied when the system requests one. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, getAnimations() still reported two running 3,000 ms animations. F02 medium: Finite decorative motion continues under reduced-motion. |
respect-user-preferencesrespects-contrast | pass | high | Text and controls remained visible in the high-contrast screenshot. |
implement-natural-interactionsview-transitions | issues | high | The platform probe found no active route/state transition treatment for the menu/calculator journey, and clicking Send money navigated abruptly. F03 low: Important state and route changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked parallax, scrollytelling, or reveal interaction was present on the representative templates, so there is no scroll-linked implementation to assess. |
implement-natural-interactionsphysical-gestures | pass | high | Carousels expose Previous/Next buttons and ordinary scrolling remains platform-native; no custom pointermove gesture trap was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Full-page captures exceed 13,000 px while the navigation remains a fixed treatment; no progress or scroll-state response was observed. F04 low: Long pages use static rather than scroll-state-aware navigation chrome. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, context menu, or edge-positioned popover was exposed on the representative paths. |
provide-guided-navigationdirects-attention | pass | high | Strong section headings, selected controls, breadcrumbs on help, and explicit CTAs keep location and next actions understandable. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The help-page mobile screenshot shows a large consent panel and backdrop covering the article immediately on load. F05 high: Cookie consent obscures primary content on entry. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM probes found zero dialog, role=dialog, or popover elements while screenshots show the consent overlay. F06 medium: The cookie overlay is not exposed as a dialog or popover. |
maximize-content-reduce-noisereduced-chrome | pass | high | Outside the consent overlay, layouts dedicate most viewport area to product content and use restrained borders/chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Every measured template reported horizontalOverflowPx 0 and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The probe found 1,524 accessible container rules and components visibly recompose between desktop and 360 px captures. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused first link computed outline was none; the page probe counted 32 rendered controls below 24 px in one dimension. F07 high: Some controls lack a visible focus indicator and many targets are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each page has a specific h1 and prominent next action, including Send money, Open an account, business signup, and article navigation. |
support-core-task-successprimary-flow-completion | pass | high | The quote calculator exposes labelled send/receive amounts and clicking Send money triggered the expected navigation to the authenticated onboarding surface. |
support-core-task-successclear-system-state-and-recovery | pass | high | An invalid route renders a clear lost-page h1 with Help Centre, Log in and Sign up recovery links; calculator status uses alert/status regions. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 4.4 s, TBT 640 ms, Speed Index 8.6 s and performance 55; trace corroborated 356 ms TBT. F08 high: The measured load is slow and interaction-blocked. |
be-fast-and-stablevisual-stability | pass | high | CLS was 0.065 in Lighthouse and 0 to 0.073 across mobile templates, within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded four long tasks, including a 318 ms task; mobile layouts recorded tasks up to 366 ms. F09 high: Long main-thread tasks delay responsiveness. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 108 requests and 9.12 MB transferred, including ten parser-inserted very-high-priority stylesheets and 5.94 MB media. F10 high: A large render-critical and media payload is delivered on initial load. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse found 451 KB unused in the 600 KB app chunk and 184 KB unused CSS (92%) in a 200 KB stylesheet. F11 high: Large amounts of JavaScript and CSS are unused at load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found two unnamed carousel buttons, an image without alt, orphan list items and comparison table cells without headers. F12 high: Several controls and content structures lack accessible semantics. |
be-inclusivesufficient-contrast | pass | high | Lighthouse did not report a color-contrast failure and content remained legible in the contrast-emulated screenshot. |
be-inclusivestructure-and-focus | issues | high | Lighthouse found headings skipping to h5/h4, and the focus probe found no visible outline on the first focused link. F13 high: Heading order and keyboard focus treatment are inconsistent. |
be-inclusivelegible-text | pass | high | Body copy uses comfortable measure and spacing and remains readable without clipping across the selected templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Although all four 360 px layouts reflowed without overflow, the probe counted 32 rendered targets under 24 px in one dimension. F14 medium: Touch-target sizing falls below the inclusive baseline. |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured malformed SVG transform errors and React hydration error #418. F15 medium: The homepage logs rendering and hydration errors. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found 42 images without dimensions, 27 without srcset, 8 oversized and 7 legacy-format assets. F16 medium: Image delivery and sizing are inconsistent. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported missing/403 source maps for large first-party bundles and three BFCache failure reasons tied to no-store responses. F17 medium: The page has platform hygiene regressions. |
be-discoverabletitle-and-description | pass | high | All four templates expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO identified three “Learn more” links, and the DOM probe counted eight generic Learn more/Find out more links. F18 medium: Some link text is not descriptive out of context. |
be-discoverablecanonical-and-indexing-signals | issues | high | robots.txt was available, but /sitemap.xml returned an HTML lost-page response instead of an XML sitemap. F19 medium: The sitemap endpoint is not a sitemap. |
be-discoverablestructured-and-shareable-metadata | issues | high | The help article probe found zero JSON-LD blocks despite the page representing a support article; Open Graph metadata was present. F20 medium: The help article has no article structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HTTPS/HSTS/nosniff, but CSP script-src includes unsafe-inline and unsafe-eval, and no Referrer-Policy header is sent. F21 high: The CSP permits unsafe script execution and Referrer-Policy is absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe found six third-party origins and active Mixpanel, Bing and Google Tag Manager trackers; HAR attributed 13 requests and 458 KB to third parties. F22 medium: Tracking runs across several third-party origins. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appeared on load; login offers a passkey and uses autocomplete="email webauthn" plus current-password. |
be-private-and-securedefensive-browser-policies | issues | high | CSP frame-ancestors and HSTS are present, but Referrer-Policy is missing and the permissive CSP includes connect-src * plus unsafe script directives. F23 medium: Defensive browser policy coverage is incomplete. |
be-resilientprogressive-enhancement | pass | high | Raw HTML retained title/h1/description and 63% to 92% of rendered content; no page was a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Menus, calculator controls, and consent UI stayed within 360 px viewports with no overflow or clipped overlay. |
be-resilientoffline-and-installable | not-applicable | high | Wise transfers and live exchange quotes are intrinsically online; offline installability is not required for these public marketing and transaction-entry pages. |
be-resilientnetwork-and-http-failure-states | pass | high | The missing route presents a useful recovery page rather than a blank shell or infinite spinner. |
be-internationalisedlang-dir-and-logical-properties | pass | high | Pages declare en-GB/en and ltr where applicable, and the homepage publishes 46 hreflang alternatives. |
be-internationalisedlocale-aware-data | pass | high | GBP/EUR amounts use locale grouping and decimals, pages use regional en-GB metadata, and extensive localized variants are linked. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages expose currencies and localized content but no event scheduling or user-visible time-zone/DST calculation. |
be-trustworthyno-dark-patterns | pass | high | Accept and Decline receive equal prominence, prices/fees are displayed before action, and no confirmshaming copy was observed. |
be-trustworthyhumane-error-handling | pass | high | The calculator uses labelled inputs and alert/status regions, while route failure messaging is plain and actionable. |
be-trustworthytrustworthy-input-assistance | pass | high | Email and password fields are labelled and use email webauthn/current-password autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | pass | high | The quote exposes rate, fee and recipient amount before Send money; login offers recovery and passkey options. |
be-sustainableoptimised-assets | issues | high | The image audit found 8 oversized images, 27 without responsive sources and 7 legacy formats. F24 high: Asset selection is not consistently resolution-efficient. |
be-sustainableno-wasteful-work | issues | high | HAR transferred 5.94 MB of media and 1.90 MB of script on load while Lighthouse found substantial unused JS/CSS. F25 high: Below-fold media and unused code are fetched during initial load. |
be-sustainablethird-party-and-media-budget | issues | high | Four media requests transferred 5.94 MB, led by a 3.73 MB WebM, before users interacted; total load reached 9.12 MB. F26 high: The homepage media budget is disproportionate to the primary calculator task. |
be-agent-readystructured-agent-capabilities | issues | high | The site is an agentic-commerce candidate, but recon found only human-facing forms and Lighthouse agentic browsing scored 49 with an ill-formed accessibility tree. F27 low: Wise exposes no structured agent-facing transaction capability. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or language-model task is offered where built-in on-device inference is needed. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 open/close cycles, DOM nodes stayed at 2,679 and used JS heap decreased from 53.4 MB to 46.3 MB. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary contained 1,126,044 nodes/65.0 MB self size; post-interaction snapshot was 1,191,531 nodes/69.2 MB. F28 medium: The initial JavaScript heap footprint is heavy for a marketing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached*, listener or timer constructor appeared in the top summaries, and same-session DOM count remained unchanged after 10 cycles. |
Provenance
Canonical report: results/atomic/reports/0845-wise_com.json
Report SHA-256: 36f55b3983aeb3340e8fce6b0ab47c9929ec60ef17f3c804fcf9c1f94e111990
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/wise_com/2026-07-23T09-36-26-284Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/wise_com/2026-07-23T09-36-26-284Z
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.