Manifest position 946 · CrUX rank bucket 1000
https://www.ilovepdf.com
Coverage complete
Coverage complete across 58 atomic checks and seven representative paths. Excluded duplicate tool templates and authenticated account/checkout internals; merge and compress represent the file-tool family.
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 | The dark-mode screenshot is pixel-identical to the light screenshot; computed body background remains rgb(245,245,250) and html color-scheme is normal. F01 medium: The site ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The page reports prefers-reduced-motion=true and zero active animations; default also has zero animations. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors capture preserves visible text, borders, icons, and consent actions. |
implement-natural-interactionsview-transitions | issues | high | The upload flow changes from picker to ordering workspace to download page; DOM/CSS inspection found no view-transition naming or transition evidence. F27 low: Major route and workflow state changes swap abruptly without View Transition integration. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling surface exists on the representative paths. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No swipe, pull, carousel, or gesture-driven task exists on the representative paths. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The fixed header consistently preserves current tool context without scroll-jank across long listing/pricing pages. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip/popover positioning surface is required in the representative primary flow. |
provide-guided-navigationdirects-attention | pass | high | Upload produces a dedicated ordering workspace with two thumbnails and the success state offers clear continuation tools. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | At 360x800 the 336px-tall panel covers the tool filters and cards; it appears on homepage, merge, compress, pricing, and 404 before interaction. F02 high: The consent panel obscures primary content on every public page tested, especially on mobile. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The platform probe finds #ck_set and #okck as anchors without href, and no dialog/popover primitive exists. F03 high: Consent controls are custom anchor-like elements rather than semantic dialog/buttons. |
maximize-content-reduce-noisereduced-chrome | pass | high | Tool pages devote the viewport to a single heading and primary file action with minimal application framing. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Homepage, compress, and Arabic routes all report horizontalOverflowPx 0 at 360px with viewport metadata. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Cards, tool actions, pricing, and navigation recompose from desktop to 360px without clipping or overflow. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatically focused login links, inputs, submit button, and merge picker all compute outline-style none and no focus box-shadow; some tested controls are only 40px tall. F04 high: Keyboard focus is not visibly indicated on primary controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home states the PDF-tool purpose; Merge and Compress expose one dominant Select PDF files action. |
support-core-task-successprimary-flow-completion | pass | high | Two valid PDFs were uploaded, ordered, merged, and reached “PDFs have been merged!” with a Download merged PDF action. |
support-core-task-successclear-system-state-and-recovery | issues | high | The before and after blank-submit screenshots are visually identical; fields remain without aria-invalid or error text. F05 medium: Blank login submission provides no visible validation or recovery guidance. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 3.3s on merge and 3.2s on pricing, while the homepage was 2.3s. CLS was 0 and TBT remained low. F06 medium: Primary secondary templates miss the good LCP threshold in lab runs. |
be-fast-and-stablevisual-stability | pass | high | Observed CLS is 0 on homepage/compress and Lighthouse CLS is 0 on home, merge, and pricing. |
be-fast-and-stableefficient-main-thread | pass | high | Homepage trace has zero long tasks/TBT 0; Lighthouse TBT is 0–12.5ms across three templates. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse flags LCP discovery and dependency-tree insights; HAR identifies a parser-blocking stylesheet and five font files totaling 102KB. F07 medium: Critical rendering depends on CSS/font chains and homepage LCP discovery is delayed. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR records GTM at 164,953 bytes, 31% of all 527,903 transferred bytes, larger than the 90,854-byte first-party bundle. F08 medium: Third-party analytics is the single largest script on the initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse finds an unlabeled merge file input, three pricing images without alt, and FAQ menuitem roles without required parents. Login inputs also have no labels. F09 high: Core controls and pricing content have missing or invalid accessible semantics. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reports 4.35:1 white-on-red for Select PDF files and 4.22–4.25:1 consent actions, below 4.5:1; similar failures occur on pricing. F10 medium: Several primary controls narrowly fail WCAG text contrast. |
be-inclusivestructure-and-focus | issues | high | Lighthouse finds no main landmark on merge and pricing, skipped heading levels on pricing, and invalid menuitem/list relationships; focus indicators are absent. F11 high: Key templates lack a main landmark and contain invalid heading/FAQ structure. |
be-inclusivelegible-text | pass | high | Headings and body copy are readable, consistently aligned, and reflow without clipping in English and Arabic mobile captures. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Computed pricing button size is 40x44 and login submit height is 42px; reflow itself succeeds without horizontal overflow. F12 medium: Some interactive targets fall below the inclusive 44px target recommendation. |
follow-best-practicesno-console-errors | pass | high | All three Lighthouse runs score best-practices 1.0 and report no console-error audit failure. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive reports missing width/height on 13/13 homepage images and 100/100 pricing images. F13 medium: Images omit intrinsic dimensions across the sampled templates. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports the large app.08252df.js has no source map and the mutationobserver shim map lacks sourcesContent. F14 low: The merge application ships incomplete source-map support. |
be-discoverabletitle-and-description | pass | high | Homepage and merge have descriptive titles and meta descriptions in both raw HTML and rendered DOM. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Navigation uses real descriptive href links, viewport meta is present, and Lighthouse SEO is 1.0 on home/merge and 0.92 on pricing. |
be-discoverablecanonical-and-indexing-signals | issues | high | The page exposes dozens of language routes but the pricing probe finds zero hreflang links; direct /robots.txt and /sitemap.xml requests returned 403. F15 medium: Localized pages are not connected with hreflang, and robots/sitemap requests rejected the audit client. |
be-discoverablestructured-and-shareable-metadata | issues | high | Homepage recon finds zero JSON-LD blocks despite organization/service content; pricing exposes plans and offers without detected structured data. F16 low: Rich entities have social metadata but no structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive confirms HTTPS and HSTS but no CSP and no X-Content-Type-Options; the one cookie is Secure/HttpOnly but SameSite=None. F17 high: The main document lacks a Content-Security-Policy and nosniff protection. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Trackers detects GTM and Google Analytics on initial load; HAR records five third-party requests and a GA collect request marked consent denied/npa=1. F18 high: Google analytics requests occur before the visitor makes a consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission prompt appears on load; login offers password plus a key/passkey-style option and social choices. |
be-private-and-securedefensive-browser-policies | issues | high | No clickjacking protection, Referrer-Policy, Permissions-Policy, or CSP frame-ancestors is present; HSTS is correctly enabled. F19 high: Several browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Homepage is not a JS shell with 89% content coverage; merge raw HTML preserves title, H1, description, and task entry UI. |
be-resilientresilient-runtime-behaviour | pass | high | The upload, ordering, processing, and result states stabilized and remained usable without clipped overlays. |
be-resilientoffline-and-installable | not-applicable | high | The core product uploads files to a remote processing service and is intrinsically online; installability/offline processing was judged out of scope. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent route presents “Page not found” and a prominent Back to homepage recovery action. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Arabic is correctly lang=ar and dir=rtl with no mobile overflow, yet the CSS probe counts 0 logical-property rules and 291 left/right rules. F20 medium: RTL works visually, but the stylesheet relies overwhelmingly on physical directions. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited localized surfaces contain no user-facing dates, decimal quantities, or locale-formatted data requiring an Intl judgement. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited surfaces expose no events, stored times, recurrence, or time-zone-sensitive concepts. |
be-trustworthyno-dark-patterns | issues | high | Across screenshots, first-layer choices are Manage options and Accept all; rejecting requires additional steps while acceptance is one click. F21 high: The consent prompt offers a prominent Accept all action but no equally direct Reject all action. |
be-trustworthyhumane-error-handling | issues | high | Blank submission produces no visible field message, summary, aria-invalid state, or changed screenshot. F22 medium: Login errors are not surfaced after user submission. |
be-trustworthytrustworthy-input-assistance | issues | high | The email and password inputs return empty autocomplete values and label count 0. F23 medium: Login fields omit autofill tokens and persistent labels. |
be-trustworthysafe-commercial-and-account-flows | pass | high | Pricing clearly distinguishes free, £5/month billed annually, and business contact options; login offers recovery and account creation. |
be-sustainableoptimised-assets | issues | high | Five homepage images use PNG, five omit srcset, and every sampled image omits intrinsic dimensions, although most icons use SVG. F24 medium: Homepage imagery is not consistently optimized for stable, efficient delivery. |
be-sustainableno-wasteful-work | pass | high | Homepage transfers a modest 528KB and trace records no long tasks or ongoing animation work; waste is isolated to the separately reported third party. |
be-sustainablethird-party-and-media-budget | issues | high | GTM alone transfers 165KB of the 528KB load, while all first-party scripts together are smaller; trackers also contacts Analytics. F25 medium: Analytics consumes a disproportionate share of a relatively light page. |
be-agent-readystructured-agent-capabilities | issues | high | The platform probe finds no WebMCP surface; Lighthouse agentic-browsing scores merge and pricing at 0.5, and merge’s unlabeled file input weakens the accessibility tree. F26 low: The PDF workflow has no structured agent-facing capability. |
be-agent-readyon-device-inference | not-applicable | high | The representative merge/compress tasks are deterministic document operations, not inference use cases. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 50 representative category switches, snapshot node count decreased 205,186→205,035 and self size decreased 11,882,122→11,869,495 bytes. |
be-memory-efficientbounded-footprint | pass | high | Homepage snapshot self size is 11.9MB; Performance memory reports 7.2MB used JS heap and 1,107 live DOM elements, proportionate to the tool directory. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated interaction does not increase total nodes/self size and no Detached* constructor appears among the retained top constructors. |
Provenance
Canonical report: results/atomic/reports/0946-www_ilovepdf_com.json
Report SHA-256: e7a7e35a04154516c526d51634bcfedfa83aeb5168209595c7de4148c4bafa24
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilovepdf_com/2026-07-24T01-31-37-879Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ilovepdf_com/2026-07-24T01-31-37-879Z
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.