Manifest position 259 · CrUX rank bucket 1000
https://www.ninisite.com
Coverage complete
Coverage-complete audit of four representative templates plus an error-recovery path.
Attempts
2 / 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 remains the same white surface as the default screenshot; computed html/body color-scheme is normal and CSS inspection found no prefers-color-scheme rule. F-respect-user-preferences-respects-color-scheme medium: The site does not adapt to the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The emulated preference was active and document.getAnimations() returned no running page animations. |
respect-user-preferencesrespects-contrast | issues | high | Lighthouse found 107 color-contrast failures, and the stylesheet has no prefers-contrast treatment while many controls use pale grey text. F-respect-user-preferences-respects-contrast medium: High-contrast resilience is weak. |
implement-natural-interactionsview-transitions | issues | high | Representative routes are conventional full navigations; DOM/CSS inspection found no authored transition rules beyond third-party reset declarations. F-implement-natural-interactions-view-transitions low: Route changes do not use meaningful View Transitions. |
implement-natural-interactionsscroll-driven-animations | pass | high | No authored parallax, scrollytelling, or scroll-linked effects were present, so there is no main-thread scroll-animation anti-pattern to replace. |
implement-natural-interactionsphysical-gestures | pass | high | Primary browsing uses native document scrolling and standard links; no custom pointer-driven gesture surface was found. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The homepage is 14,852 px tall at mobile width, yet screenshots and inspected CSS show static chrome with no progress indicator or authored scroll-state behavior. F-provide-guided-navigation-scroll-state-aware-chrome low: Long pages provide no scroll-position-aware navigation cue. |
provide-guided-navigationanchored-positioning | pass | high | No site-owned tooltip, popover, or edge-positioned transient menu requiring anchor positioning was present. |
provide-guided-navigationdirects-attention | pass | high | The active section is visibly highlighted and breadcrumb/list headings orient users on article and forum routes. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Mobile screenshots show fixed bottom ads covering article cards, forum content, signup fields, and the 404 recovery surface; desktop also shows a large floating ad over the hero. F-maximize-content-reduce-noise-no-intrusive-interruptions high: Advertising repeatedly obscures primary content and controls. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection found no dialog, popover, or details primitives while injected Yektanet styles create fixed overlays up to z-index 99,999,999 with custom close controls. F-maximize-content-reduce-noise-semantic-dismissible-primitives medium: Injected promotional overlays use custom high-z-index div/iframe chrome. |
maximize-content-reduce-noisereduced-chrome | issues | high | Every representative mobile screenshot gives substantial first-viewport area to banner and floating advertising, including overlapping stacked promotions on discussion and signup. F-maximize-content-reduce-noise-reduced-chrome high: Commercial chrome competes with the editorial experience. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | The 360x800 layout probe reported scrollWidth 366 against a 360 px visual viewport, for 6 px overflow. F-adapt-to-the-form-factor-responsive-no-horizontal-scroll low: The mobile layout has measurable horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection across home, article, forum, and signup templates found no authored @container rules; many ad and card rules use fixed pixel widths and global media queries. F-adapt-to-the-form-factor-component-level-responsiveness medium: Components rely on viewport styling rather than container-level adaptation. |
adapt-to-the-form-factorinput-modality-aware | issues | high | A focused signup navigation link computed to outline:none and box-shadow:none; Lighthouse also reported 9 insufficiently sized or spaced targets. F-adapt-to-the-form-factor-input-modality-aware high: Keyboard focus is not visibly indicated and several targets are too small. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Each route communicates its purpose with recognizable navigation and prominent editorial, forum, or registration content. |
support-core-task-successprimary-flow-completion | issues | high | The signup mobile screenshot shows a large floating video promotion covering password/captcha fields in the primary registration form. F-support-core-task-success-primary-flow-completion high: The signup journey is obstructed by advertising. |
support-core-task-successclear-system-state-and-recovery | pass | high | The unknown route renders a branded 404 explanation and suggested recent content rather than a blank or broken shell. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured FCP 5.5 s, LCP 10.6 s, Speed Index 6.3 s, and Time to Interactive 11.9 s (performance 0.59); a separate trace measured LCP 2.67 s, showing material run variance. F-be-fast-and-stable-good-core-web-vitals high: Mobile load performance misses the LCP quality bar. |
be-fast-and-stablevisual-stability | pass | high | The layout observer recorded CLS 0 and Lighthouse measured CLS 0.004, both within the good range. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded one 92 ms long task and 42 ms TBT; Lighthouse measured 80 ms TBT, indicating limited blocking despite slow visual load. |
be-fast-and-stableefficient-resource-delivery | issues | high | The images primitive found 89 below-fold images without lazy loading, 73 without srcset, 91 legacy-format images, and 16 oversized images. F-be-fast-and-stable-efficient-resource-delivery high: Images and noncritical resources are delivered inefficiently. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 174 KiB unused JavaScript and 38 KiB unused CSS; the main CSS bundle was 93% unused in the sampled load. F-be-fast-and-stable-trim-unused-and-duplicate-code medium: The page ships substantial unused JavaScript and CSS. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found 7 unnamed buttons, 4 unnamed links, one required-children ARIA failure, and two presentation-role conflicts. F-be-inclusive-names-roles-labels high: Several interactive controls lack accessible names or valid ARIA structure. |
be-inclusivesufficient-contrast | issues | high | Lighthouse found 107 elements with insufficient foreground/background contrast. F-be-inclusive-sufficient-contrast high: Text and controls fail contrast requirements at scale. |
be-inclusivestructure-and-focus | issues | high | All four inspected templates had zero h1 and zero main elements; Lighthouse found seven heading-order failures and no main landmark, while the focus probe showed no visible focus ring. F-be-inclusive-structure-and-focus high: Document structure and keyboard focus are not robust. |
be-inclusivelegible-text | pass | high | Persian body and heading text is generally large, line-spaced, and readable in the sampled article and forum views, aside from separately reported contrast issues. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse found 9 target-size failures and the 360 px layout had 6 px horizontal overflow; the viewport meta itself permits scaling. F-be-inclusive-zoom-reflow-targets-and-media medium: Small targets and slight overflow undermine reflow usability. |
follow-best-practicesno-console-errors | issues | high | Lighthouse’s errors-in-console audit failed because a resource returned HTTP 404. F-follow-best-practices-no-console-errors medium: The homepage logs a failed network request. |
follow-best-practicessound-document-and-assets | issues | high | The images primitive found 3 images without dimensions, 16 oversized images, and 73 without responsive sources; Lighthouse also reported a low-resolution mobile logo. F-follow-best-practices-sound-document-and-assets medium: Asset markup and responsive image delivery need cleanup. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse found no deprecated APIs, BFCache blocker, invalid source maps, paste prevention, or geolocation/notification prompt on load. |
be-discoverabletitle-and-description | pass | high | The homepage and representative routes have descriptive unique titles; the homepage has a matching meta description in raw and rendered HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse SEO reported “Allow /sitemap” on line 4 as syntax not understood; links and viewport otherwise passed. F-be-discoverable-crawlable-and-mobile-friendly low: robots.txt contains an invalid directive. |
be-discoverablecanonical-and-indexing-signals | pass | high | The public homepage returned 200, Lighthouse found a valid canonical, and no accidental noindex was observed; robots syntax is reported separately. |
be-discoverablestructured-and-shareable-metadata | pass | high | Canonical, Open Graph, and JSON-LD markup are present across all four inspected templates. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, HSTS, nosniff, and X-Frame-Options are present, but CSP is missing; all 6 observed first-party cookies lacked Secure and used SameSite=None. F-be-private-and-secure-secure-transport-and-headers high: Security headers and cookie attributes are incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker probe saw 19 third-party origins and known Clarity, Google Tag Manager, and DoubleClick endpoints; Lighthouse found third-party cookies and the screenshots show multiple ad formats. F-be-private-and-secure-data-minimisation-and-third-parties high: The page has a broad tracking and advertising footprint. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse confirmed no permission prompts on load, but signup/sign-in DOM exposes password fields and no WebAuthn/passkey affordance. F-be-private-and-secure-in-context-permissions-and-modern-auth medium: Authentication is password-only and lacks modern phishing-resistant options. |
be-private-and-securedefensive-browser-policies | issues | high | The headers probe found no CSP, Referrer-Policy, or Permissions-Policy; HSTS and X-Frame-Options are present. F-be-private-and-secure-defensive-browser-policies medium: Several browser-enforced defensive policies are absent. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 100% rendered-content coverage, title and description present, and no empty JS shell. |
be-resilientresilient-runtime-behaviour | issues | high | Fixed Yektanet containers use extreme z-index values and overlap form and error-recovery content at mobile sizes. F-be-resilient-resilient-runtime-behaviour medium: Third-party overlays create fragile, obstructed runtime states. |
be-resilientoffline-and-installable | not-applicable | high | This is a content/community website rather than an installed app; offline/PWA behavior is contextual and no installability intent was declared. |
be-resilientnetwork-and-http-failure-states | pass | high | A nonexistent route renders a useful 404 state with explanation and links to recent content. |
be-internationalisedlang-dir-and-logical-properties | issues | high | All inspected templates set lang="fa" but neither html nor body declares dir="rtl"; CSS includes many physical left/right declarations despite some logical properties. F-be-internationalised-lang-dir-and-logical-properties medium: Persian pages do not declare document direction. |
be-internationalisedlocale-aware-data | pass | high | Rendered timestamps and numeric content use Persian locale presentation consistently in article and forum views. |
be-internationalisedtime-zone-correctness | not-applicable | high | The sampled public templates expose relative editorial/forum timestamps but no cross-time-zone scheduling or event-coordination task. |
be-trustworthyno-dark-patterns | issues | high | Floating promotions cover editorial, forum, registration, and 404 surfaces; some include only tiny branding/close affordances and resemble in-page content. F-be-trustworthy-no-dark-patterns high: Advertisements are visually intrusive and insufficiently separated from key tasks. |
be-trustworthyhumane-error-handling | issues | high | Signup markup contains required validation messages but no aria-live or aria-invalid, and several fields lack associated labels. F-be-trustworthy-humane-error-handling medium: Form errors are not exposed with modern accessible state semantics. |
be-trustworthytrustworthy-input-assistance | issues | high | The telephone field has autocomplete="off" and no associated label; confirm-password and captcha fields also lack associated labels, while password has new-password. F-be-trustworthy-trustworthy-input-assistance medium: Registration input assistance is incomplete. |
be-trustworthysafe-commercial-and-account-flows | issues | high | A floating advertisement covers registration fields, and the authentication surface offers passwords without a passkey option. F-be-trustworthy-safe-commercial-and-account-flows high: The account flow is neither distraction-free nor proportionate. |
be-sustainableoptimised-assets | issues | high | Of 93 images, 91 are legacy formats, 73 lack srcset, 89 below-fold images are not lazy, and 16 are oversized. F-be-sustainable-optimised-assets high: The image strategy wastes bandwidth and decoding work. |
be-sustainableno-wasteful-work | issues | high | The tracker probe recorded 19 third-party origins; Lighthouse attributes the largest unused-JS savings to GTM/gtag and measured 174 KiB unused JavaScript overall. F-be-sustainable-no-wasteful-work medium: Background advertising and analytics work is disproportionate. |
be-sustainablethird-party-and-media-budget | issues | high | Lighthouse transferred 1,535 KiB and two Google tag scripts were among the four largest resources; tracker evidence found 19 third-party origins and multiple simultaneous ad formats. F-be-sustainable-third-party-and-media-budget high: Third-party code consumes a large share of the page budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No agent-facing intent or transactional agent surface was declared; this emerging capability is an opportunity, not a requirement for this editorial/community audit. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or generative feature is offered in the sampled experience, so on-device inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten full-page down/up scroll cycles, heap self size rose from 28.1 MB to 30.9 MB and nodes from 500,439 to 532,899; this bounded single-run increase does not establish unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap self size was 28.1 MB. Although the DOM/ad footprint is large, the sampled heap remained proportionate and did not approach instability. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | No Detached* constructor population appeared among the retained-size leaders before or after the repeated scroll exercise. |
Provenance
Canonical report: results/atomic/reports/0259-www_ninisite_com.json
Report SHA-256: 283d1e5900d3be934cb6dd81eaea0a89caa3b665e92186a67923dab01f329f81
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ninisite_com/2026-07-26T01-36-36-565Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ninisite_com/2026-07-26T01-36-36-565Z
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.