Manifest position 624 · CrUX rank bucket 1000
https://imgsrc.ru
Coverage complete
Atomic coverage complete across five representative public templates; no local source was provided and no fixes were applied.
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 | pass | high | Explicit light and dark screenshots show complete surface retinting; :root declares color-scheme: light dark and shared colors use light-dark(). |
respect-user-preferencesrespects-reduced-motion | pass | high | Under emulated reduce, the probe found zero active animations; audited interactions and pages contain no auto-advance or non-essential motion. |
respect-user-preferencesrespects-contrast | issues | high | The preference probe found no forced-colors or prefers-contrast rules. Lighthouse found four homepage and two registration links distinguishable only by low-contrast colour, including a 1.41:1 link-versus-surrounding-text contrast. F01 medium: High-contrast support and link differentiation are incomplete. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across the MPA templates found no @view-transition or view-transition-name use; screenshots show separate routes with no continuity mechanism. F02 low: Cross-document navigation swaps abruptly with no View Transition or attention cue. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation exists on the audited templates, so there is no implementation to move off the main thread. |
implement-natural-interactionsphysical-gestures | pass | high | No custom pointermove/gesture handlers fight native scrolling; galleries and pages use ordinary browser scroll and link behavior. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The long homepage and FAQ screenshots show static chrome; CSS inspection contains no scroll-state container queries, progress indicator, or scroll-position-aware treatment. F03 low: Long pages provide no scroll-state feedback or progress affordance. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, contextual popover, or anchored menu is present on the audited public templates. |
provide-guided-navigationdirects-attention | issues | high | DOM/CSS inspection across the MPA templates found no @view-transition or view-transition-name use; screenshots show separate routes with no continuity mechanism. F02 low: Cross-document navigation swaps abruptly with no View Transition or attention cue. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Every route screenshot begins with a full-width red “FREE MEGA links” promotion before the site header, with no dismiss control. F04 low: A bright promotional banner precedes the core content on every audited template. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM uses a clickable div with inline onclick to toggle another div; it has no button semantics, expanded state, or native popover/details light-dismiss behavior. F05 medium: The mobile navigation is a pointer-only custom div instead of a semantic disclosure/popover. |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots show a content-first, border-light layout with the photo/gallery taking most available space. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Mobile layout measured scrollWidth=clientWidth=360 with zero horizontal overflow on homepage and registration. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The shared CSS has a single max-width media query and no @container/container-type, while the same .recot/.reco gallery component is reused in multiple layout contexts. F06 low: Reusable galleries adapt only through viewport media queries, not their containers. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The keyboard/target probe measured many links at 13px high and registration fields at about 18px high; mobile screenshots confirm tightly packed icon and text targets. F07 high: Touch targets and controls are substantially smaller than accessible target sizes. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage heading, image-hosting proposition, Search, Join, and Upload paths are visible in the first viewport. |
support-core-task-successprimary-flow-completion | pass | high | A city search completed to a populated results page; registration reaches an actionable validation state without a dead end. |
support-core-task-successclear-system-state-and-recovery | issues | high | Submitting an empty registration shows “username should only contain 4 to 16 aphanumeric latin symbols” beside the login field, but the DOM has no required, aria-invalid, aria-describedby, or live error announcement. F08 medium: Registration errors are cryptic and are not programmatically connected to their fields. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 2.9s and the independent trace measured 3.906s; good LCP is 2.5s or less. CLS was only 0.016 and TBT effectively zero. F09 medium: The homepage LCP misses the good Core Web Vitals threshold. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observed CLS 0.0167 on home and 0.00045 on registration, both comfortably good. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout observers found no long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR transferred 12.64MB across 67 requests; Lighthouse measured 14,547KiB. A single Material Symbols font was 3.74MB, and cache analysis estimated 6,592KiB savings across 64 resources. F10 high: Resource delivery is extremely heavy and poorly cached for a thumbnail-led homepage. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 52–53KiB of unused JavaScript from Yandex Metrika on both homepage and registration templates. F11 low: Analytics JavaScript is mostly unused on initial load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse failed both login and email inputs for missing labels; the DOM probe confirmed labels=null and aria-label=null for each field. F12 high: Registration fields have no programmatic labels. |
be-inclusivesufficient-contrast | issues | high | The preference probe found no forced-colors or prefers-contrast rules. Lighthouse found four homepage and two registration links distinguishable only by low-contrast colour, including a 1.41:1 link-versus-surrounding-text contrast. F01 medium: High-contrast support and link differentiation are incomplete. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark on homepage and registration; the registration probe found no main, nav, header, footer, aside, or explicit role landmarks. F13 medium: Pages lack semantic landmarks and navigation structure. |
be-inclusivelegible-text | issues | high | Mobile CSS sets body text to 3vw, about 10.8px at 360px, while screenshots show a clipped registration title and heavily truncated gallery labels. F14 medium: Mobile typography is cramped and truncates important context. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The keyboard/target probe measured many links at 13px high and registration fields at about 18px high; mobile screenshots confirm tightly packed icon and text targets. F07 high: Touch targets and controls are substantially smaller than accessible target sizes. |
follow-best-practicesno-console-errors | pass | high | Neither Lighthouse run reported console-errors or runtime exception audit failures. |
follow-best-practicessound-document-and-assets | issues | high | The image audit found all 61 rendered images missing complete width/height dimensions and all 61 lacking img srcset; 49 were more than twice their rendered width. F15 medium: Images lack intrinsic dimensions and responsive source sizing. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found DevTools Inspector issues on both templates and five BFCache failure reasons on registration. F16 medium: Chrome reports platform hygiene problems, including BFCache blockers. |
be-discoverabletitle-and-description | pass | high | All representative templates have unique descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links use real hrefs, viewport meta is present, robots permits public pages, and Lighthouse SEO scored 1.0. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage has a canonical and valid hreflang, but search and registration heads have no canonical. /sitemap.xml returns 410 while robots.txt points to two .txt sitemap resources. F17 medium: Canonical and sitemap indexing signals are inconsistent across public templates. |
be-discoverablestructured-and-shareable-metadata | issues | high | Homepage and public content DOM contain descriptive title/meta but no Open Graph metadata or JSON-LD for the organization, image gallery, or photo entity. F18 low: Rich entity and share-preview metadata is absent. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers confirm HTTPS, HSTS, nosniff, and X-Frame-Options DENY, but Content-Security-Policy and Permissions-Policy are missing; Referrer-Policy is the permissive legacy no-referrer-when-downgrade. F19 high: Browser-enforced security policy is incomplete. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Network evidence shows Yandex Metrika starts immediately, makes redirecting cookie-sync/watch requests, and Lighthouse found 15–16 third-party cookies. The cookie audit also found three SameSite=None analytics cookies. F20 high: Yandex analytics tracks users on load without an observed consent gate. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The registration copy states “We will send your password to this email”; audited auth/account surfaces expose no WebAuthn/passkey path. F21 high: Account creation relies on emailed passwords rather than modern authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Headers confirm HTTPS, HSTS, nosniff, and X-Frame-Options DENY, but Content-Security-Policy and Permissions-Policy are missing; Referrer-Policy is the permissive legacy no-referrer-when-downgrade. F19 high: Browser-enforced security policy is incomplete. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% content coverage without JavaScript and confirmed a server-rendered MPA, not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Search, registration, custom mobile menu, and photo viewer rendered without clipping or runtime failure at 360px. |
be-resilientoffline-and-installable | not-applicable | high | This server-rendered public image host is content/commerce-like rather than an installable app; offline upload/search is intrinsically network-dependent. |
be-resilientnetwork-and-http-failure-states | pass | high | The 410 sitemap response rendered a clear not-found page with links back to the homepage and search. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Pages correctly expose lang=en and en/ru/x-default hreflang, but shared CSS is dominated by left/right, width/height, margin-left and padding-right with no logical-property strategy. F22 medium: Bilingual templates use physical CSS properties rather than writing-mode-safe logical properties. |
be-internationalisedlocale-aware-data | not-applicable | high | Audited public templates contain no currency, absolute dates, or locale-sensitive numeric input requiring client-side formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduled events, cross-zone times, or DST-sensitive concepts appear in the representative paths. |
be-trustworthyno-dark-patterns | pass | high | Audited public flows show no preselected purchase, confirmshaming, forced continuity, or blocked cancellation state. |
be-trustworthyhumane-error-handling | issues | high | Submitting an empty registration shows “username should only contain 4 to 16 aphanumeric latin symbols” beside the login field, but the DOM has no required, aria-invalid, aria-describedby, or live error announcement. F08 medium: Registration errors are cryptic and are not programmatically connected to their fields. |
be-trustworthytrustworthy-input-assistance | issues | high | The login and email inputs have no autocomplete tokens; email is type=text and neither field supplies required or inputmode hints. F23 medium: Registration inputs do not provide browser input assistance. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The registration copy states “We will send your password to this email”; audited auth/account surfaces expose no WebAuthn/passkey path. F21 high: Account creation relies on emailed passwords rather than modern authentication. |
be-sustainableoptimised-assets | issues | high | 49 of 61 images were over 2x rendered width; homepage transfers 8.76MB of images plus a 3.74MB icon font, while most cards display at only about 129px. F24 high: Oversized media and font payloads are disproportionate to the rendered thumbnail grid. |
be-sustainableno-wasteful-work | issues | high | Network evidence shows Yandex Metrika starts immediately, makes redirecting cookie-sync/watch requests, and Lighthouse found 15–16 third-party cookies. The cookie audit also found three SameSite=None analytics cookies. F20 high: Yandex analytics tracks users on load without an observed consent gate. |
be-sustainablethird-party-and-media-budget | issues | high | 49 of 61 images were over 2x rendered width; homepage transfers 8.76MB of images plus a 3.74MB icon font, while most cards display at only about 129px. Network evidence shows Yandex Metrika starts immediately, makes redirecting cookie-sync/watch requests, and Lighthouse found 15–16 third-party cookies. The cookie audit also found three SameSite=None analytics cookies. F24 high: Oversized media and font payloads are disproportionate to the rendered thumbnail grid. F20 high: Yandex analytics tracks users on load without an observed consent gate. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The site explicitly publishes Content-Signal ai-input=no and exposes no intended agent-facing transaction surface; structured agent tools are out of scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation, generation, or language-processing task is offered where on-device inference would improve the audited experience. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After 10 open/close menu cycles, retained heap decreased from 3,591,843 to 3,544,225 bytes and node count from 73,175 to 72,652. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was proportionate for the server-rendered page at 3.59MB self size and 73,175 snapshot nodes. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Repeated menu interaction did not grow native nodes, closures, arrays, or object counts; no Detached* constructor appeared among retained leaders. |
Provenance
Canonical report: results/atomic/reports/0624-imgsrc_ru.json
Report SHA-256: 391905d2cfa4698ae1d09d08972745c5f431577a4300d13b3f343ad22dfd8146
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/imgsrc_ru/2026-07-22T00-17-18-782Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/imgsrc_ru/2026-07-22T00-17-18-782Z
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.