Skip to content
https://vg.no

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

40

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/player/extras/latest/player-plugin-skin-vgtv2-latest.js3600.0 s265.8 KiB
cmp.vg.no/Notice.8f529.js3600.0 s91.3 KiB
/player/extras/latest/player.next.min.bundled-latest.js3600.0 s73.5 KiB
vgc.no/player/player-plugin-skin-vgtv2-latest.js3600.0 s73.1 KiB
vgc.no/player/player.next.min.bundled-latest.js3600.0 s67.9 KiB
cmp.vg.no/unified/wrapperMessagingWithoutDetection.js3600.0 s40.3 KiB
log.medietall.no/analytics.v2.js3600.0 s24.9 KiB
cdn.stream.schibsted.media/jw/jwplayer-8.34.5/jwplayer.core.js86400.0 s43.0 KiB
cdn.stream.schibsted.media/jw/jwplayer-8.34.5/jwplayer.js86400.0 s42.3 KiB
ssl.p.jwpcdn.com/player/v/8.34.5/jwpsrv.js900.0 s18.1 KiB
cdn.stream.schibsted.media/player/extras/latest/player-plugin-adn-latest.js3600.0 s19.4 KiB
ssl.p.jwpcdn.com/player/v/8.34.5/vast.js86400.0 s30.3 KiB
/player/extras/latest/player-plugin-chromecast-latest.js3600.0 s11.2 KiB
cdn.stream.schibsted.media/jw/jwplayer-8.34.5/provider.html5.js86400.0 s14.9 KiB
cogwheel.inventory.schibsted.io/prod/latest/gdpr-bundle.js3600.0 s7.4 KiB
cmp.vg.no/Notice.30929.css3600.0 s6.7 KiB
www.gstatic.com/eureka/clank/146/cast_sender.js86400.0 s13.4 KiB
/player/extras/latest/player-plugin-sponsor-overlay-lates...3600.0 s5.0 KiB
cdn.stream.schibsted.media/player/extras/latest/player-dna-vg-latest.css3600.0 s4.3 KiB
static.privacy.schibsted.com/cmp/schibsted_logo_primary_20231017.svg0.0 ms3.2 KiB
/player/extras/latest/player-plugin-topic-subscriber-late...3600.0 s3.1 KiB
esm.schibsted.tech/node/events.mjs86400.0 s5.0 KiB
cmp.vg.no/polyfills.01516.js3600.0 s2.3 KiB
esm.schibsted.tech/node/process.mjs86400.0 s3.8 KiB
vgc.no/player/player-skin-vgtv2-latest.css3600.0 s1.4 KiB
static.privacy.schibsted.com/cmp/chevron_down_20231017.svg0.0 ms1.0 KiB
static.privacy.schibsted.com/cmp/brands/VG.svg0.0 ms848 B
cdn.stream.schibsted.media/player/extras/latest/player-skin-vgtv2-latest.css3600.0 s1002 B
platform.iteratehq.com/loader.js1800.0 s919 B
/player/extras/latest/player-plugin-media-session-latest.js3600.0 s935 B
esm.schibsted.tech/node/async_hooks.mjs86400.0 s1.8 KiB
ads.inventory.schibsted.io/ad-service/ad-banner-sponsor-advertisement/ad.js0.0 ms641 B
esm.schibsted.tech/@schibsted/nanostores-account600.0 s606 B
esm.schibsted.tech/@schibsted/account-sdk-browser@%5E5.2.6?target=es2022600.0 s589 B
static.privacy.schibsted.com/cmp/brands/none.svg0.0 ms498 B
esm.schibsted.tech/@schibsted/dark-mode600.0 s533 B
esm.schibsted.tech/tiny-emitter@%5E2.1.0?target=es2022600.0 s530 B
esm.schibsted.tech/scheduler@%5E0.27.0?target=es2020600.0 s528 B
esm.schibsted.tech/@vgno/components-loader?external=react,react-dom600.0 s511 B
esm.schibsted.tech/nanostores@%5E1.0.1?target=es2022600.0 s511 B
esm.schibsted.tech/node/tty.mjs86400.0 s703 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:6.495 source:map[column:20 line:73 type:source-location url:https://www.vg.no/ urlProvider:network]] map[reflowTime:0.274 source:map[column:18 line:94 type:source-location url:https://www.vg.no/ urlProvider:network]] map[reflowTime:71.524 source:map[type:text value:[unattributed]]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
article._teaser_1tmv8_4 > a.color-text-primary > div._figure_1tmv8_31 > img._image_1tmv8_71 article._teaser_1tmv8_4 > a.color-text-primary > div._figure_1tmv8_31 > img._image_1tmv8_71
/v2/images/89e59f7a-2071-3dbd-8c5c-38097897595c?fit=crop&...176.8 KiB122.9 KiB
article._teaser_1tmv8_4 > a.color-text-primary > div._figure_1tmv8_31 > img._image_1tmv8_71 article._teaser_1tmv8_4 > a.color-text-primary > div._figure_1tmv8_31 > img._image_1tmv8_71
/v2/images/0cc1ba2c-5323-3c45-b1f5-4401bfbf5836?fit=crop&...25.6 KiB12.3 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s
URLTime Spent
vg.no/1.0 s
www.vg.no/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation3.2 s
Other2.1 s
Style & Layout1.0 s
Script Parsing & Compilation438 ms
Rendering308 ms
Parse HTML & CSS278 ms
Garbage Collection53 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 16.2 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Font display
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
User Timing marks and measures 1 user timing
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 130 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 210 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
Avoid non-composited animations
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Torsdag Rask Tradisjonell blomkålsuppe Tilberedningstid: 30 min. Lagret av 2.4K ol._dishList_1chga_83 > li._listItemWrapper_1chga_118 > track-element > a._listItem_1chga_118
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 400 (Bad Request)
Failed to load resource: the server responded with a status of 400 (Bad Request)
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 404 ()
SDKError: HasSession failed at https://esm.schibsted.tech/@schibsted/account-sdk-browser@5.2.6/es2022/account-sdk-browser.mjs:5:1183 at async ee (https://cdn.stream.schibsted.media/player/extras/latest/player.next.min.bundled-latest.js:1:61153)
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback