Manifest position 462 · CrUX rank bucket 1000
https://linkmake.in
Coverage complete
Coverage-complete agentic audit of four representative public templates plus a failure route.
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-emulated screenshot is pixel-identical to the default capture; the inline CSS hard-codes light surfaces and declares neither color-scheme nor a dark media query. F01 medium: The public pages ignore the user’s dark theme preference. |
respect-user-preferencesrespects-reduced-motion | pass | medium | Reduced-motion emulation matched and getAnimations() returned an empty list; no non-essential motion or auto-advance exists. |
respect-user-preferencesrespects-contrast | pass | medium | The high-contrast capture remains readable and controls remain visible; contrast defects in the ordinary palette are recorded separately under be-inclusive. |
implement-natural-interactionsview-transitions | issues | medium | The DOM/CSS probe found no view-transition rules, while login, policy, and contact are distinct same-origin documents that switch abruptly. F02 low: Navigation and state changes have no transition treatment. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or scrollytelling component exists on the representative pages. |
implement-natural-interactionsphysical-gestures | not-applicable | high | No gesture-driven, swipe, carousel, or scroll-snap interaction exists to assess. |
provide-guided-navigationscroll-state-aware-chrome | not-applicable | high | No sticky or affixed chrome exists; there is no scroll-reactive component to assess. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or anchored menu exists on the sampled pages. |
provide-guided-navigationdirects-attention | issues | high | Login, policy, and contact DOM snapshots contain no nav landmark or home link; the login screenshot is an isolated panel. F03 medium: Standalone pages provide no orientation or route back to the service. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | medium | Initial desktop and mobile captures show the primary content immediately with no modal, interstitial, consent wall, or obscuring banner. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlays, disclosures, dialogs, or rich custom controls are present. |
maximize-content-reduce-noisereduced-chrome | pass | medium | The initial viewport is dominated by the link fields and supporting copy; header/footer chrome is compact and no ad panels are present. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive measured scrollWidth 390 versus clientWidth 360 (30 px overflow), and the screenshot clips the card at the right edge. F04 high: The homepage overflows horizontally on a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | medium | The platform probe found no container queries; CSS uses one global max-width breakpoint while the same card/form pattern appears at multiple widths. F05 low: Reusable cards and controls only react to the viewport, not their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe reports outline none and no box shadow for all three homepage inputs; footer links are only 16–17 px high. F06 high: Keyboard focus is removed from the primary inputs. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The first viewport clearly states “Protect your link in just one click” and places the URL fields prominently; the missing completion action is recorded separately. |
support-core-task-successprimary-flow-completion | issues | high | The homepage presents URL, title, and size inputs but the rendered DOM contains zero forms and no submit button or action; the screenshot ends the card with an empty rule. F07 critical: The advertised link-protection task cannot be completed. |
support-core-task-successclear-system-state-and-recovery | issues | high | The login flow always invokes a blocking alert saying only “This username and password not found”; the primary homepage has no submission state, and the 404 page offers no recovery action. F08 high: Failure and recovery states are absent or non-actionable. |
be-fast-and-stablegood-core-web-vitals | pass | medium | Trace measured LCP 576 ms, zero long tasks/TBT, and layout measured CLS 0; Lighthouse corroborated LCP 0.8 s, CLS 0, and TBT 10 ms. |
be-fast-and-stablevisual-stability | pass | medium | Desktop and mobile layout observers recorded CLS 0 and no shifts; the page contains no images. |
be-fast-and-stableefficient-main-thread | pass | medium | Trace recorded zero long tasks and 0 ms TBT; Lighthouse measured 10 ms TBT. |
be-fast-and-stableefficient-resource-delivery | issues | high | Lighthouse reports inefficient cache lifetimes (about 7 KiB potential savings); the HAR records a redirected Cloudflare script request. F09 low: Delivery is fast but cache and dependency hygiene can improve. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | The HAR attributes 166,815 of 184,990 transferred bytes to Google Tag Manager, while Lighthouse estimates 68 KiB of unused JavaScript. F10 medium: Third-party JavaScript dominates this tiny page and is mostly unused. |
be-inclusivenames-roles-labels | issues | high | The probe reports empty labels for the textarea and both inputs; visible text is implemented with center/b tags rather than label elements. F11 high: The primary inputs have no programmatic labels and the page lacks semantic landmarks. |
be-inclusivesufficient-contrast | issues | high | Lighthouse scored the color-contrast audit 0; the visual captures show light secondary text and blue links on light surfaces. F12 high: Text contrast fails automated accessibility testing. |
be-inclusivestructure-and-focus | issues | high | The homepage has no h1–h3 and starts all sections at h4, has no landmarks, and removes focus outlines from form controls. F13 high: Heading and focus structure is not logical. |
be-inclusivelegible-text | pass | medium | Screenshots show generally readable 16 px body copy and policy text with comfortable line-height; specific contrast and mobile clipping failures are recorded separately. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport meta sets maximum-scale=1 and user-scalable=no; Lighthouse failed meta-viewport and the mobile layout has 30 px overflow. F14 high: The homepage prevents user scaling and fails narrow reflow. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse did not report browser console errors or uncaught exceptions during the audited load. |
follow-best-practicessound-document-and-assets | pass | medium | DOM evidence confirms an HTML doctype and UTF-8 charset; the images primitive found zero images, so aspect-ratio defects are absent. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports three deprecation warnings; DOM inspection also shows obsolete center and font elements. F15 medium: Deprecated platform usage remains on the page. |
be-discoverabletitle-and-description | issues | high | The homepage title is only “Linkmake”; login and contact DOM snapshots have no meta description, so titles/descriptions do not uniquely describe each surface. F16 medium: Metadata is generic or missing across representative pages. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | All sampled navigation uses real href anchors; robots allows indexing and a viewport meta exists. The scaling restriction is tracked as an accessibility issue. |
be-discoverablecanonical-and-indexing-signals | issues | high | The platform probe found no canonical link and /sitemap.xml returned 404, despite robots allowing indexing. F17 medium: Canonical and sitemap signals are missing. |
be-discoverablestructured-and-shareable-metadata | issues | high | The metadata probe found zero Open Graph tags and zero JSON-LD blocks on the homepage. F18 low: The public service has no social-preview or structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, or nosniff header; analytics cookies are not Secure and use SameSite=None for 400 days. F19 high: HTTPS is present, but transport/header and cookie defaults are unsafe. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence identifies Google Tag Manager and Google Analytics; 90% of transferred bytes are third-party and two 400-day analytics cookies are set on load. F20 high: Analytics runs immediately without an evident consent or minimisation mechanism. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Both Login and Signup links target login.html; submitting any credentials always triggers the same client-side alert, with no passkey or actual authentication path. F21 high: The authentication surface is a non-functional password-only dead end. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence reports no clickjacking control, Referrer-Policy, Permissions-Policy, CSP, or HSTS. F22 high: Browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | medium | Discoverability measured 100% raw/rendered content coverage and isJsShell=false; core text and links remain visible without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | The sampled pages are server-rendered with no custom overlays or async dependencies; no clipping of menus or fragile runtime state was observed. |
be-resilientoffline-and-installable | not-applicable | high | This small public URL service is intrinsically network-dependent and does not claim an installable/offline app experience. |
be-resilientnetwork-and-http-failure-states | issues | high | A representative missing route returns the default nginx 404 with no site identity, search, home link, retry, or support route. F23 medium: HTTP failures do not preserve context or support recovery. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | All sampled pages use lang=en, but the CSS probe found no logical properties and source uses physical padding-left/alignment patterns. F24 low: The English language is declared, but layout CSS is not writing-mode resilient. |
be-internationalisedlocale-aware-data | issues | medium | Visible content hard-codes “$20”, “$4”, “2024”, and “2025”; no locale-aware formatting or locale selector is exposed. F25 low: Commercial values and dates are hard-coded rather than locale-aware. |
be-internationalisedtime-zone-correctness | not-applicable | high | No events, schedules, timestamps, or time-zone-sensitive user data appear in the representative surfaces. |
be-trustworthyno-dark-patterns | issues | high | “Signup” routes to the same login page as “Login”, and every login submission is rejected client-side regardless of credentials. F26 high: Navigation labels promise capabilities that are not delivered. |
be-trustworthyhumane-error-handling | issues | high | The login error is a generic blocking alert; homepage instructions warn of errors but provide no form submission or inline validation. F27 high: Form errors are not humane or accessible. |
be-trustworthytrustworthy-input-assistance | issues | high | The login probe reports empty autocomplete on username/password; homepage and contact inputs likewise expose no autocomplete tokens. F28 medium: Inputs omit autocomplete assistance. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The homepage promotes earnings, referral bonuses, payout, signup, and login, but signup is not distinct and login never authenticates; no account-management or cancellation path was discoverable. F29 high: Account and earning claims lack a usable, reversible account journey. |
be-sustainableoptimised-assets | not-applicable | high | The images primitive found zero images; there are no image/decorative raster assets to optimize. |
be-sustainableno-wasteful-work | issues | high | The page itself is a few kilobytes, but automatic analytics and challenge scripts create six additional requests and most transferred bytes without aiding the broken core task. F30 low: Background analytics work is disproportionate to the page’s functionality. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR reports 166,815 third-party bytes out of 184,990 total, almost entirely Google Tag Manager; there are no image or media assets. F31 medium: The third-party budget is disproportionate for a static form page. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent exists; emerging WebMCP exposure is an opportunity, not an obligation for this simple service. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or inference use case appears in this link service, so on-device inference is not applicable. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten representative focus/type/clear cycles, heap nodes decreased from 118,165 to 117,972 and self size from 5,014,929 to 5,012,665 bytes; no retained growth signal appeared. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries show about 118k nodes and 5.0 MB self size, proportionate to this small page and stable across the repeated interaction. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Total heap node and edge counts did not grow after ten cycles (nodes -193, edges -100), providing no accumulation signal in this interaction window. |
Provenance
Canonical report: results/atomic/reports/0462-linkmake_in.json
Report SHA-256: 9dc91f3ac88c28653ad801ffc69e74048b15d2d7fba19663ade9be4ddcc0142f
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/linkmake_in/2026-07-20T23-38-12-807Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/linkmake_in/2026-07-20T23-38-12-807Z
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.