Manifest position 719 · CrUX rank bucket 1000
https://www.capcut.com
Coverage complete
Coverage-complete representative audit of public marketing, tool, content, template, localisation, authentication-entry and failure-state archetypes.
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 default capture, computed color-scheme is normal, and the CSS probe found no prefers-color-scheme rules. F001 medium: The public site is hard-coded to a light theme. |
respect-user-preferencesrespects-reduced-motion | issues | high | Under prefers-reduced-motion: reduce, the CSS probe found no reduced-motion rule and a scroll animation remained active; the platform probe found 11 autoplaying videos without controls. F002 high: Motion-heavy media does not adapt to reduced-motion preferences. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse accessibility scored 1.0, the high-contrast screenshot retained readable controls/text, and the CSS includes two prefers-contrast rules. |
implement-natural-interactionsview-transitions | issues | high | The CSS/source probe found zero view-transition declarations across the loaded public landing surface. F003 low: Page and state changes do not use View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | CSS inspection found animation-timeline: scroll(root) on the shrinking header, with a non-support transition fallback. |
implement-natural-interactionsphysical-gestures | pass | medium | The audited public templates use native scrolling and clickable controls without custom pointer-role divs; no gesture surface fought platform scrolling. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The fixed header uses a declarative scroll(root) animation to change chrome through the first 40 px of scrolling. |
provide-guided-navigationanchored-positioning | issues | high | The online-editor screenshot shows a floating welcome-bonus card overlapping the hero; the CSS probe found no anchor-name, position-anchor, or position-try usage. F004 low: Floating promotional UI is manually positioned rather than anchored with resilient fallbacks. |
provide-guided-navigationdirects-attention | pass | medium | Breadcrumbs, selected template chips, prominent headings, and clear route labels orient users across tool, article and template archetypes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, mobile, editor, AI-tool, resource, and sign-in screenshots show a cookie banner covering a large portion of the first viewport; several content pages also show a welcome-bonus popup. F005 high: Load-time consent and promotional overlays obscure primary content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The loaded page contained no dialog or popover elements and no ARIA dialog, despite presenting modal-like cookie and promotional overlays. F006 medium: Overlay UI does not use native dialog or popover primitives. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Outside overlays, the homepage and template listing devote the viewport to content with restrained header chrome and clear section hierarchy. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The mobile layout primitive measured 376 px content against a 360 px visual viewport, producing 16 px horizontal overflow on both English and Arabic homepages. F007 medium: The page overflows horizontally at a 360 px viewport. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The computed/source probes found zero @container rules and zero elements with a non-normal container-type. F008 low: Reusable components rely on viewport styling rather than container queries. |
adapt-to-the-form-factorinput-modality-aware | issues | high | An active-focus probe successfully focused links and buttons but consistently reported outline: none and no focus box-shadow; the menu control measured only 24 by 24 px and many nav targets were 32 px high. F009 high: Keyboard focus is invisible and several controls are undersized. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Home and tool first viewports provide descriptive H1s and prominent Try online, Generate AI Video, or Upload actions. |
support-core-task-successprimary-flow-completion | issues | high | “Try online for free” and tool CTAs route to a sign-in page whose main message is “Sign up to unlock all features”; no editing surface is available without authentication. F010 high: The advertised free online editor journey requires account creation before the task can begin. |
support-core-task-successclear-system-state-and-recovery | issues | high | The deliberate missing-route probe produced a bare infrastructure 404 with no recovery action. F022 high: Unknown routes dead-end on an infrastructure error page. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 12.3 s, FCP 5.0 s, CLS 0.261, and a performance score of 0.47. A separate trace on a warm desktop-like run was much faster, so the mobile throttled result is the risk signal. F011 high: Lab Core Web Vitals are poor on mobile. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse measured CLS 0.261 and identified the templates section plus cookie banner fonts as major shift sources; all 34 audited img elements lacked width and height attributes. F012 high: Late content and unreserved images cause visible layout shift. |
be-fast-and-stableefficient-main-thread | pass | high | The DevTools trace found two short long tasks, longest 61.34 ms, and only 14.03 ms total blocking time; Lighthouse TBT was 120 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR recorded 105 requests and 11.63 MB transferred, including 9.17 MB of media; 98 requests and 11.53 MB came from origins other than www.capcut.com. One synchronous parser-inserted head script was confirmed without async/defer. F013 high: Initial delivery is dominated by eager third-party media. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | medium | The HAR shipped 29 scripts / 1.31 MB and Lighthouse reported legacy/deprecated behavior; multiple login, monitoring, analytics and polyfill bundles load on the public landing page. F013 high: Initial delivery is dominated by eager third-party media. F017 medium: Deprecated markup and unload handlers reduce platform resilience. |
be-inclusivenames-roles-labels | issues | high | After opening “Continue with email”, the only email input had no associated label and no aria-label, relying solely on placeholder="Enter email". F014 medium: The email sign-in field has no accessible label. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 1.0 and the default/high-contrast screenshots preserve readable foreground/background contrast. |
be-inclusivestructure-and-focus | issues | high | The focus probe focused dozens of controls while computed outline remained none and box-shadow remained none, making keyboard location imperceptible. F015 high: Focus indication is removed across the navigation and primary controls. |
be-inclusivelegible-text | pass | high | Screenshots across home, tools, resources, templates and sign-in show readable type, clear alignment, and no text clipping at the tested viewports. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360 px reflow had 16 px horizontal overflow, several targets were below 44 px, and 11 autoplay videos had no controls. F007 medium: The page overflows horizontally at a 360 px viewport. F009 high: Keyboard focus is invisible and several controls are undersized. F002 high: Motion-heavy media does not adapt to reduced-motion preferences. |
follow-best-practicesno-console-errors | issues | high | Lighthouse failed the console-errors audit due to TikTok monitoring CORS failures; the HAR also recorded monitoring failures and a malformed image 404. F016 medium: The homepage logs network and CORS errors. |
follow-best-practicessound-document-and-assets | issues | high | The document has valid HTML doctype/UTF-8, but every audited image lacks intrinsic dimensions and Lighthouse found invalid picture/source markup. F012 high: Late content and unreserved images cause visible layout shift. F017 medium: Deprecated markup and unload handlers reduce platform resilience. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reported unload event listeners, invalid picture/source markup, and BFCache prevention from unload and no-store behavior. F017 medium: Deprecated markup and unload handlers reduce platform resilience. |
be-discoverabletitle-and-description | pass | high | Homepage and all representative tool, listing and article routes expose unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse found four links named only “More” and marked robots.txt invalid because of the unknown LLM-Content directive. F018 low: Generic link text and a non-standard robots directive reduce crawler clarity. |
be-discoverablecanonical-and-indexing-signals | pass | high | Homepage returned 200, has a canonical URL, 28 hreflang links, an indexable robots policy for major crawlers, and sitemap indexes. |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage includes aligned WebSite JSON-LD plus Open Graph title, description, image, dimensions, URL, type and locale. |
be-private-and-securesecure-transport-and-headers | issues | high | Eight cookies were flagged as insecure by the cookie primitive, all used SameSite=None, two fingerprint cookies last 400 days, and CSP permits unsafe-eval/unsafe-inline. F019 high: Cookie and CSP settings weaken browser-enforced protection. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Before any consent action, the tracker primitive observed 13 third-party origins including Microsoft Clarity and TikTok monitoring; the HAR counted 98 third-party requests. F020 medium: Tracking and third-party activity begins before consent. |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No permission prompt appeared on load; sign-in offers federated providers and the environment supports WebAuthn, though passkey enrolment was not visible in the unauthenticated state. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive confirmed HSTS, nosniff and frame protection but found no Referrer-Policy or Permissions-Policy. F021 medium: Referrer-Policy and Permissions-Policy are absent. |
be-resilientprogressive-enhancement | pass | high | Discoverability captures found 92% homepage and 91% article rendered-word coverage in raw HTML; neither route is a JS shell and article H1/content survives no-JS. |
be-resilientresilient-runtime-behaviour | issues | medium | The floating welcome-bonus card overlaps hero/content while the implementation has no anchor positioning or position fallback rules. F004 low: Floating promotional UI is manually positioned rather than anchored with resilient fallbacks. |
be-resilientoffline-and-installable | pass | medium | The app-like product links a valid standalone web manifest with icons/start_url and navigator.serviceWorker is present. |
be-resilientnetwork-and-http-failure-states | issues | high | A representative missing route returned a bare “404 Not Found / Guru Meditation / Goofy Deploy Page Server” page with no navigation, explanation, search, or recovery link. F022 high: Unknown routes dead-end on an infrastructure error page. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The Arabic resource page rendered Arabic content while html.lang and html.dir were both empty. Its cookie banner remained English, and the page carries substantial physical left/right CSS alongside logical rules. F023 high: Arabic pages omit document language and direction metadata. |
be-internationalisedlocale-aware-data | pass | medium | Arabic resource dates render with Arabic digits and month names; the site exposes 28 locale alternates. |
be-internationalisedtime-zone-correctness | not-applicable | high | No event scheduling, local-time entry, recurring interval, or time-zone-sensitive user flow appears in the representative public/editor-entry surfaces. |
be-trustworthyno-dark-patterns | pass | medium | Consent presents equally prominent Accept all and Decline all controls, and terms/privacy links are visible in sign-in. |
be-trustworthyhumane-error-handling | issues | high | Submitting the empty email state showed “Enter a valid email address”, but the field remained validity.valid=true and had no aria-invalid or aria-describedby association. F024 medium: Email validation errors are not programmatically associated with the field. |
be-trustworthytrustworthy-input-assistance | pass | high | The email field uses type=email, inputmode=email, and autocomplete=username. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The free-editor promise is followed by mandatory sign-up before editing; the commitment is not disclosed at the CTA. F010 high: The advertised free online editor journey requires account creation before the task can begin. |
be-sustainableoptimised-assets | issues | high | The image primitive found all 34 images missing dimensions, 24 without srcset, six oversized beyond twice display width, and one below-fold image eagerly loaded. F026 medium: Images are not responsively sized or dimensioned. |
be-sustainableno-wasteful-work | issues | high | Before interaction the page starts 11 autoplay videos and 98 third-party requests, including analytics/monitoring. F020 medium: Tracking and third-party activity begins before consent. F025 high: Autoplay media and third-party bytes are disproportionate for a landing page. |
be-sustainablethird-party-and-media-budget | issues | high | The load transferred 11.63 MB, 9.17 MB as media and 11.53 MB from third-party origins; 11 video elements autoplayed muted without controls. F025 high: Autoplay media and third-party bytes are disproportionate for a landing page. |
be-agent-readystructured-agent-capabilities | issues | high | The site publishes a useful llms.txt and server-rendered content, but loaded source exposed no WebMCP or agentic tool registration for its editing/generation capabilities. F027 low: Agent discovery is documented, but product capabilities are not exposed as safe structured tools. |
be-agent-readyon-device-inference | not-applicable | medium | The audited public marketing, content, sign-in and editor-entry surfaces do not expose a bounded inference task that can be verified as appropriate for built-in on-device AI. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten real menu open/close cycles, DOM nodes returned to 1,169; separate heap summaries differed by only 0.4% nodes and 0.6% retained size, with no top detached constructor signal. |
be-memory-efficientbounded-footprint | pass | medium | The loaded media-rich landing page retained about 28.1 MB across 455k snapshot nodes, proportionate to its React, video and login integrations despite network-weight concerns. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Ten menu cycles left live DOM count unchanged and the post snapshot did not surface Detached constructors among top retained constructor groups. |
Provenance
Canonical report: results/atomic/reports/0719-www_capcut_com.json
Report SHA-256: 1b8241cd3d12a7b4cc9391029aeeaf0c95f8179ddb5b1c09dc0e8d229ea6fea9
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_capcut_com/2026-07-22T15-12-27-075Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_capcut_com/2026-07-22T15-12-27-075Z
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.