Manifest position 568 · CrUX rank bucket 1000
https://linktr.ee
Coverage complete
Atomic coverage complete across 58 checks and seven representative logged-out paths. No account was created, authenticated dashboard audited, or destructive/external transaction completed.
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 | Dark-emulated screenshot remains the same bright lime/white palette as the default capture; computed root color-scheme is normal. F01 medium: Dark preference is not reflected |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, document.getAnimations() returned zero active animations and CSS contains a reduced-motion media rule. |
respect-user-preferencesrespects-contrast | issues | high | The high-contrast capture retained the default palette and the complete readable stylesheet set contained no prefers-contrast or forced-colors rule. F02 medium: High-contrast preferences have no dedicated treatment |
implement-natural-interactionsview-transitions | issues | medium | The browser supports document.startViewTransition, but 289,901 bytes of readable CSS contain no view-transition rule or name; route navigation is ordinary full-page navigation. F03 low: Route changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | medium | No scroll-linked reveal/parallax behavior was observed, and CSS contains no scroll/view timeline that would need main-thread replacement. |
implement-natural-interactionsphysical-gestures | pass | high | Stylesheet evidence includes both scroll-snap and overscroll-behavior; mobile pages scroll natively without horizontal drag traps. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The long 10,430px mobile page has fixed navigation but no scroll-state/container query or progress indicator in the complete readable CSS. F04 low: Long-page navigation does not react to scroll state |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, edge-positioned popover, or contextual menu was present on the audited logged-out surfaces, so there is no anchored overlay to assess. |
provide-guided-navigationdirects-attention | pass | high | A visible skip link, descriptive navigation labels, clear selected pricing toggle, and strong heading hierarchy guide attention across the sampled routes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | On every sampled entry surface, the on-load privacy panel covers roughly the lower half to two-thirds of the 390x844 viewport and obscures the primary content. F05 high: Consent panel obscures core content on every fresh entry |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent overlay and mobile navigation are DIV-based role=dialog implementations; no native dialog or popover elements were found, and the consent dialog lacks aria-modal. F06 medium: Overlays use custom DIV dialogs instead of native primitives |
maximize-content-reduce-noisereduced-chrome | pass | high | Behind the consent layer, the landing, pricing, registration, profile, templates, and blog surfaces use restrained navigation and devote most space to their content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, scrollWidth and clientWidth are both 360 with zero horizontal overflow and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The site reuses cards, navigation, pricing tiers, and profile links at many widths, but the complete readable CSS contains no @container rule. F07 low: Reusable components do not use container queries |
adapt-to-the-form-factorinput-modality-aware | issues | high | Keyboard focus is generally visible, but Lighthouse found multiple controls below the 24px minimum safe target, including a 16x21 dismiss target and tightly packed footer/nav links. F08 medium: Several touch targets are undersized or crowded |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport states “A link in bio built for you” and exposes Log in, Sign up free, and Get started actions; pricing and registration have equally direct H1s. |
support-core-task-successprimary-flow-completion | pass | medium | The homepage CTAs reach the registration form, the email field is labelled, federated sign-up alternatives are available, and pricing commitments are visible before account creation. No account was created. |
support-core-task-successclear-system-state-and-recovery | issues | high | The tested missing route clearly says the page does not exist but offers no Home, Back, search, retry, or other recovery action. F09 medium: The 404 state has no recovery action |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 6.4s and TBT 292ms (performance 0.71); the independent trace measured LCP 1.86s, showing a materially poor throttled mobile load despite a fast local trace. F10 high: Throttled mobile LCP is 6.4 seconds |
be-fast-and-stablevisual-stability | issues | high | The mobile layout observer measured CLS 0.110 from a shift at about 1.07s, above the good <=0.1 range, although Lighthouse’s separate run measured 0. F11 medium: Observed layout shift exceeds the good threshold |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded a 190.58ms long task and 140.58ms TBT; Lighthouse measured 292ms TBT. F12 medium: Startup includes a long main-thread task |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR shows a 704ms longest dependency chain and uncached 90KB consent script; DOM confirmation shows GTM and most app scripts are async, so they were not misclassified as parser-blocking. F13 medium: Resource delivery has avoidable dependency and cache cost |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 179KiB unused JavaScript and 47KiB unused CSS; four listed JS chunks are >99% unused in the audited load. F14 medium: Large portions of shipped JS and CSS are unused |
be-inclusivenames-roles-labels | issues | high | axe found the carousel region landmark is not uniquely labelled; otherwise names, labels, image-alt, button-name, and link-name rules passed. F15 low: Carousel landmark is not uniquely labelled |
be-inclusivesufficient-contrast | pass | medium | axe color-contrast and Lighthouse color-contrast audits passed; six dynamic nodes were left for manual review and sampled screenshots remain legible. |
be-inclusivestructure-and-focus | issues | high | axe reports a non-unique carousel landmark; focus probing confirms a skip link and visible :focus-visible treatment on sampled interactive elements. F15 low: Carousel landmark is not uniquely labelled |
be-inclusivelegible-text | pass | high | Headings and body copy remain unclipped and readable at mobile and desktop widths across all representative templates. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Reflow succeeds with no overflow and scaling is allowed, but Lighthouse found numerous undersized or tightly spaced targets; the only video is muted decorative media and passed its caption audit. F08 medium: Several touch targets are undersized or crowded |
follow-best-practicesno-console-errors | issues | high | Lighthouse captured repeated 403 resource failures for CSS, scripts, logo imagery, and hero media during a fresh load. F16 medium: Fresh loads emit many failed-resource console errors |
follow-best-practicessound-document-and-assets | issues | high | Doctype and UTF-8 charset pass, but Lighthouse found four images rendered at aspect ratios that do not match their intrinsic assets. F17 low: Several images are rendered at incorrect aspect ratios |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found a deprecated unload listener in cep.min.js and four BFCache blockers including an unload handler and no-store responses; prompt-on-load and paste prevention audits passed. F18 medium: Deprecated unload handling blocks BFCache |
be-discoverabletitle-and-description | pass | high | Home, pricing, templates, profile, and blog all expose titles and meta descriptions; the registration auth surface has a descriptive title but is not a public SEO landing page. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links use real hrefs, viewport metadata is present, Lighthouse link/anchor/robots audits pass, and Googlebot/Bingbot are allowed except /admin. |
be-discoverablecanonical-and-indexing-signals | pass | high | Audited public pages return usable content with canonical URLs; robots.txt names multiple live sitemap locations and explicitly allows major search crawlers. |
be-discoverablestructured-and-shareable-metadata | pass | high | Home and pricing include JSON-LD, the creator profile includes two JSON-LD blocks, and the homepage exposes seven Open Graph and seven Twitter metadata fields. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and nosniff are present, but HSTS is absent, CSP contains only frame-ancestors, and three year-long consent cookies lack Secure. F19 high: Transport policy and consent cookies are under-protected |
be-private-and-securedata-minimisation-and-third-parties | issues | high | A fresh load makes 13 third-party requests transferring 349,165 bytes, including 185KB GTM; tracker detection found GTM and Google advertising origins before a consent choice. F20 high: Tracking code loads before the user chooses consent |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | Lighthouse confirms no geolocation or notification prompt on load; registration offers Apple and Google sign-in alongside email rather than forcing a password-only path. |
be-private-and-securedefensive-browser-policies | issues | high | Clickjacking and nosniff defenses are present, but HSTS and Permissions-Policy are missing and the CSP has no script-src/object-src XSS restriction. F21 medium: Defensive browser policies are incomplete |
be-resilientprogressive-enhancement | pass | high | Raw HTML contains 91% of rendered content words and preserves title, H1, and description; the crawler screenshot is not a blank shell. |
be-resilientresilient-runtime-behaviour | pass | medium | Navigation and pricing/register/profile surfaces render coherently at the narrow viewport; no clipped overlay menu or unstable async blank state was observed. |
be-resilientoffline-and-installable | not-applicable | high | The audited logged-out surface is public marketing/content plus public profile pages, not an installed application journey; offline authoring/dashboard behavior was outside logged-out scope. |
be-resilientnetwork-and-http-failure-states | issues | high | The representative 404 state explains the failure but offers no actionable recovery control. F09 medium: The 404 state has no recovery action |
be-internationalisedlang-dir-and-logical-properties | issues | medium | Pages declare valid en/en-US language, but no explicit dir is present and the 289KB readable stylesheet includes both logical and physical left/right properties, leaving RTL resilience incomplete. F22 medium: RTL resilience is incomplete |
be-internationalisedlocale-aware-data | not-applicable | medium | No rendered dates, locale-dependent numeric values, or currency amounts were present in the captured above-the-fold states used for this check. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, timestamps, recurring intervals, or time-zone-sensitive concepts occur in the audited logged-out flows. |
be-trustworthyno-dark-patterns | pass | high | Reject All and Accept All are equally prominent, marketing consent is unchecked, and pricing says “cancel anytime”; no disguised ad or forced continuity was observed. |
be-trustworthyhumane-error-handling | issues | high | After rejecting consent and activating Continue with an empty email, the input still reports valid=true, no aria-invalid, no validation message, and no alert. F23 medium: Empty registration submission gives no error feedback |
be-trustworthytrustworthy-input-assistance | issues | high | The registration email field has an accessible label but autocomplete is empty instead of email/username, reducing autofill assistance. F24 low: Registration email does not advertise autofill semantics |
be-trustworthysafe-commercial-and-account-flows | pass | high | Pricing clearly labels monthly vs annual billing, annual savings, Free tier, and “cancel anytime”; marketing consent is optional and unchecked in registration. |
be-sustainableoptimised-assets | issues | high | Image inspection found 12 images more than 2x displayed width and 10 without responsive srcset; repeated 1600px Lottie posters display at about 312px. F25 medium: Decorative and poster imagery is oversized |
be-sustainableno-wasteful-work | issues | high | A simple fresh first viewport loads 28 scripts (575KB), including 185KB GTM and several >99% unused chunks, while the trace records a 190ms long task. F26 medium: Initial load performs disproportionate script work |
be-sustainablethird-party-and-media-budget | issues | high | Third parties account for 349KB (38.6% of 904KB transferred), and two decorative poster images add about 236KB before deeper content is viewed. F27 medium: Third parties and decorative media dominate the page budget |
be-agent-readystructured-agent-capabilities | pass | high | Linktree publishes a detailed llms.txt, robots content signals and sitemaps, 91% server-rendered content coverage, canonical metadata, and labelled forms. No WebMCP tools are exposed, but audited capabilities are primarily navigation/content discovery. |
be-agent-readyon-device-inference | not-applicable | high | The audited logged-out marketing, pricing, profile-link, and registration surfaces have no inference task whose local execution would materially improve the experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | low | After ten full-page down/up traversals, the heap summary grew from 66.2MB to 73.2MB as lazy content was exercised; no Detached constructor appeared. This bounded single-run delta is not evidence of unbounded retention. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries were 66.2MB at baseline and 73.2MB after loading the full 10,430px page, proportionate to the rich media-heavy landing page and stable enough to remain usable. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary lists a Detached* constructor; the repeated traversal did not produce direct detached-DOM evidence. Listener/timer growth was not observable via page APIs, so confidence is moderate. |
Provenance
Canonical report: results/atomic/reports/0568-linktr_ee.json
Report SHA-256: 971de0c21fecae56ff4806f23c289a3838fbc026d956ac05b5c05c985e32f525
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/linktr_ee/2026-07-21T15-28-57-551Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/linktr_ee/2026-07-21T15-28-57-551Z
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.