Manifest position 672 · CrUX rank bucket 1000
https://www.vg.no
Coverage complete
Coverage-complete atomic audit of six representative public paths. Authenticated account management, paid checkout completion and destructive form submission were intentionally not performed; their public entry states and applicable template checks were inspected.
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 emulation leaves color-scheme normal and light body colors unchanged. F04 medium: The site does not honor the system dark-color preference |
respect-user-preferencesrespects-reduced-motion | issues | high | 409 animations remain running under reduce, close to the default 420. F05 medium: Reduced-motion preference leaves hundreds of animations running |
respect-user-preferencesrespects-contrast | pass | high | High-contrast screenshot preserves visible text, controls and focus; Lighthouse contrast checks pass. |
implement-natural-interactionsview-transitions | issues | high | No view-transition signal is present across linked MPA templates. F06 low: Cross-page navigation has no View Transition treatment |
implement-natural-interactionsscroll-driven-animations | pass | high | Stylesheet probe found animation-timeline/scroll-timeline use, avoiding a solely scroll-event-driven implementation. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile drawer opens from a labelled button, fits the viewport, and uses native scrolling/expand controls without observed custom pointer friction. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | Long homepage/article surfaces retain static fixed chrome without progress or changed scroll state. F07 low: Sticky site chrome does not communicate scroll state |
provide-guided-navigationanchored-positioning | pass | high | Live CSS inspection finds anchor positioning and the inspected mobile menu remains attached and fully visible. |
provide-guided-navigationdirects-attention | pass | high | Expanded mobile navigation clearly groups content, shows disclosure state, and keeps the underlying selected content spatially understandable. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Cookie consent obscures nearly all initial desktop and mobile content. F01 high: Cookie consent blocks the entire initial experience |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The consent surface is a role=dialog div around a cross-origin iframe rather than native dialog, unlike account dialogs on the page. F02 low: The consent overlay is an ad-hoc iframe dialog rather than a native dialog |
maximize-content-reduce-noisereduced-chrome | pass | high | After consent, the main viewport is dominated by news cards and headlines; chrome is compact and the mobile menu is only shown on request. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | 360x800 layout reports scrollWidth 360, horizontal overflow 0 and a viewport meta tag on homepage and article. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Homepage CSS exposes nine container rules and cards/menu visibly recompose at mobile width. |
adapt-to-the-form-factorinput-modality-aware | pass | high | Focus probes show a visible browser outline on controls; Lighthouse accessibility is 1.0 and mobile controls are usable in the opened menu. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage, section, article and tips templates expose clear headlines/purpose and labelled next actions. |
support-core-task-successprimary-flow-completion | pass | high | The public tips journey reaches a labelled POST form with required content and optional contact/file fields without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | Invalid required content triggers native validation and a real HTTP 404 presents explanation, feedback and homepage recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse mobile LCP is 8.0 s and CLS 0.054; unthrottled trace LCP is 1.89 s, showing slow-condition risk. F08 high: Mobile lab LCP is slow despite a fast unthrottled trace |
be-fast-and-stablevisual-stability | pass | high | Observed CLS is 0 on the homepage consent state and 0.052 on article mobile, both within the good threshold. |
be-fast-and-stableefficient-main-thread | pass | high | Trace reports zero >50 ms long tasks and 0 ms TBT; Lighthouse TBT is 70 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | Five confirmed head stylesheets are render-blocking with about 170 ms potential savings. F09 medium: Critical delivery includes avoidable render-blocking CSS |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 464 KiB unused JS, 32 KiB unused CSS, 17 KiB duplicated JS and 40 KiB legacy JS. F10 medium: The homepage ships substantial unused and duplicated code |
be-inclusivenames-roles-labels | pass | high | Lighthouse accessibility scores 1.0; form fields are labelled or aria-labelled and meaningful article imagery has descriptive alt text. |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility and visual checks found no contrast failure, including high-contrast emulation. |
be-inclusivestructure-and-focus | issues | high | Homepage has no h1 and begins with repeated h2 teaser headings, although landmarks and focus outlines exist. F11 medium: The homepage has no level-one heading |
be-inclusivelegible-text | pass | high | Article body has a comfortable narrow measure and clear typographic hierarchy; mobile headlines reflow without clipping. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Mobile layouts reflow with zero horizontal overflow, scaling is not prevented, Lighthouse accessibility is 1.0, and article audio has a labelled control. |
follow-best-practicesno-console-errors | issues | high | Lighthouse and HAR record repeated 400/403/404 failures plus an Account SDK console.error. F12 medium: Routine account and media checks log browser errors |
follow-best-practicessound-document-and-assets | issues | high | Doctype/charset pass, but image probes find incomplete dimensions/oversizing and Lighthouse estimates 326 KiB savings. F13 low: Several article and homepage images lack complete intrinsic sizing or are oversized |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse reports BFCache, deprecations and inspector issues passing; no permission prompt appears on load. |
be-discoverabletitle-and-description | pass | high | All four templates have descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Real hrefs, viewport metadata, crawlable robots policy and Lighthouse SEO 1.0 are present. |
be-discoverablecanonical-and-indexing-signals | issues | high | Homepage, section and article have canonicals and sitemap is 200, but the public tips page has no canonical. F14 low: The public tips page omits a canonical URL |
be-discoverablestructured-and-shareable-metadata | pass | high | Homepage/section/article expose JSON-LD and Open Graph; article OG title/image match its visible story. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS, CSP and HSTS are strong, but __mbl is a 365-day cookie without Secure and _sp_su uses SameSite=None. F16 low: A long-lived first-party cookie is set without Secure |
be-private-and-securedata-minimisation-and-third-parties | issues | high | 82 requests and 2.04 MB transfer are third-party across 26 origins, including a known tracker. F15 high: The initial page has a large third-party and tracking footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt fires on load; authentication is delegated to Schibsted and no password/auth data is collected by the audited VG templates. |
be-private-and-securedefensive-browser-policies | pass | high | CSP frame-ancestors, HSTS, nosniff, DENY framing, strict-origin referrer policy and restrictive permissions policy are all present. |
be-resilientprogressive-enhancement | pass | high | Raw HTML retains 96% homepage and 97% article rendered vocabulary; neither page is a JS shell. |
be-resilientresilient-runtime-behaviour | pass | high | Opened mobile menu fits the viewport and remains usable; 404 and template navigation stabilize without blank shells. |
be-resilientoffline-and-installable | issues | high | A standalone manifest and shortcuts are present but no service-worker registrations exist. F17 low: The app-like manifest is not backed by an offline service worker |
be-resilientnetwork-and-http-failure-states | pass | high | A real 404 status renders an explanatory state with feedback and homepage recovery actions rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All templates declare lang=no and preserve natural Norwegian reading order across desktop/mobile; no bidi-sensitive flow is present. |
be-internationalisedlocale-aware-data | pass | high | News timestamps are rendered in Norwegian relative forms such as “I dag”, “i går”, minutes and hours, consistently across templates. |
be-internationalisedtime-zone-correctness | not-applicable | high | No user-entered, scheduled, recurring or cross-zone time flow exists in the representative public news, article, tips or offers templates. |
be-trustworthyno-dark-patterns | issues | high | Consent UI makes acceptance prominent while personalized-ad rejection is labelled as a paid service and no equal reject-all action appears. F03 high: Consent choices are visually asymmetric and decline is framed as paid |
be-trustworthyhumane-error-handling | pass | high | Required tips content uses native post-interaction validity with a specific “Please fill in this field” message; fields are labelled. |
be-trustworthytrustworthy-input-assistance | issues | high | Tips contact fields for name, email and telephone have no autocomplete tokens. F18 medium: The tips form omits autocomplete assistance for contact fields |
be-trustworthysafe-commercial-and-account-flows | pass | high | Commercial offers are explicitly labelled ANNONSE and show merchant/discount; account and subscription actions are clearly named and leave VG for their dedicated provider. |
be-sustainableoptimised-assets | issues | high | Lighthouse estimates 326 KiB image savings and probes identify oversized/missing-dimension assets. F19 medium: Responsive image delivery leaves avoidable bytes on the table |
be-sustainableno-wasteful-work | issues | high | Initial view initiates 152 requests, 94 scripts and 23 fetches, including repeated failed anonymous account calls. F20 medium: Initial background work is disproportionate to the news view |
be-sustainablethird-party-and-media-budget | issues | high | Initial transfer is 2.80 MB, with an 829 KB preview MP4 and 2.04 MB third-party bytes before playback intent. F21 medium: Autoloaded media and third-party code dominate the initial budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No WebMCP capability is exposed and robots explicitly disallows AI training crawlers while allowing OAI SearchBot. |
be-agent-readyon-device-inference | not-applicable | high | The covered news, article and tips surfaces do not present a user task that requires site-authored on-device inference. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten bottom-to-top scroll cycles, total self size rose only 6,736 bytes (0.03%) and nodes 0.4%, with no Detached constructor in the top summaries. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap is 25.29 MB self size and 398,725 nodes for a very long, media-rich homepage; footprint remained stable after exercise. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither heap summary lists Detached constructors among top retained constructors and repeated scroll did not produce material total growth. |
Provenance
Canonical report: results/atomic/reports/0672-www_vg_no.json
Report SHA-256: 019e1829adc5343ed4f9271dc1bb33dd5b22f3ccdb360093635f4dd56fd83935
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_vg_no/2026-07-22T07-27-35-983Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_vg_no/2026-07-22T07-27-35-983Z
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.