Skip to content
https://yle.fi

Lighthouse Desktop

· 0 checks — Desktop 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.

96

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
analytics-sdk.yle.fi/yle-analytics.min.js600.0 s139.4 KiB
player-v2.yle.fi/embed.js60.0 s77.3 KiB
design-system.cdn.yle.fi/fonts/yle-next/1.0.0/YleNextVar.woff23600.0 s66.8 KiB
design-system.cdn.yle.fi/fonts/yle-next/1.0.0/YleNextVar-Italic.woff23600.0 s47.2 KiB
/yleisradiooy/launcher.js?iab_consent=BOv_CmhOv_CmhAAABBE...7200.0 s23.8 KiB
tag-manager.yle.fi/ylefi-production.js0.0 ms856 B

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:42.591 source:map[column:217404 line:2 type:source-location url:https://yle.fi/ukko/assets/build/936.6d2bbdb591d6ec74301c.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:15.251 source:map[type:text value:[unattributed]]] map[reflowTime:28.614 source:map[column:25276 line:1 type:source-location url:https://yle.fi/ukko/assets/build/sp-3c733c89e9dc72c7431d.js urlProvider:network]] map[reflowTime:13.817 source:map[column:77161 line:0 type:source-location url:https://yle.fi/ukko/assets/build/966.0b5a955341ae4f687d47.js urlProvider:network]] map[reflowTime:25.741 source:map[column:14645 line:0 type:source-location url:https://yle.fi/ukko/assets/build/966.0b5a955341ae4f687d47.js urlProvider:network]] map[reflowTime:3.033 source:map[column:10567 line:0 type:source-location url:https://yle.fi/ukko/assets/build/693.ac98aa35b5d9a8ffff4a.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: Ihmiset kävelevät ohi banderollin, jossa on Yhdysvaltain presidentti Donald Tru…
path: 1,HTML,1,BODY,0,DIV,3,DIV,0,DIV,0,MAIN,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,PICTURE,4,IMG
selector: div.GridSystem__GridCell-sc-886966b2-0 > div.ResponsiveImage__ImageWrapper-sc-d5704480-1 > picture > img.ResponsiveImage__Img-sc-d5704480-0
snippet: <img alt="Ihmiset kävelevät ohi banderollin, jossa on Yhdysvaltain presidentti Donal…" src="https://images.cdn.yle.fi/image/upload/c_crop,x_0,y_0,w_6130,h_3448/w_636,…" class="ResponsiveImage__Img-sc-d5704480-0 gYcoSK" loading="lazy">

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

Diagnostics

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.

Estimated savings: 90 ms 569.5 KiB
URLTransfer SizeEst Savings
player-v2.yle.fi/143.8548a9a1553a1277bd33.js306.1 KiB251.4 KiB
analytics-sdk.yle.fi/yle-analytics.min.js138.9 KiB107.2 KiB
yle.fi/ukko/assets/build/936.6d2bbdb591d6ec74301c.js204.5 KiB87.2 KiB
player-v2.yle.fi/761.77dd3ec144e0d2e580a9.js81.9 KiB52.8 KiB
yle.fi/ukko/assets/build/32.99c1de605179bf9a3116.js41.6 KiB36.5 KiB
player-v2.yle.fi/embed.js76.8 KiB34.3 KiB

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

●Time to Interactive 2.5 s
●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,432 KiB
●JavaScript execution time 0.6 s
●Minimizes main-thread work 1.6 s
●Avoid long main-thread tasks 3 long tasks found
●Avoid non-composited animations 120 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 80 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 40 ms
○INP breakdown
○User Timing marks and measures
○Avoid large layout shifts
97

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Suomeksi aside.ycd-banner > div.ycd-content > div.ycd-language-selector > button#ycd-language-selector__menu-button
Lue lisää evästeistämme div.ycd-content > div.ycd-banner__info > p#ycd-banner__info-body > a.ycd-banner__read-more-link
Vain välttämättömät aside.ycd-banner > div.ycd-consent-buttons > div.ycd-consent-buttons__row > button.ycd-consent-buttons__button
Hyväksy kaikki aside.ycd-banner > div.ycd-consent-buttons > div.ycd-consent-buttons__row > button.ycd-consent-buttons__button
Muokkaa evästeasetuksia div.ycd-background > aside.ycd-banner > div.ycd-consent-buttons > button.ycd-consent-buttons__button

These are opportunities to improve keyboard navigation in your application.

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
Suomeksi aside.ycd-banner > div.ycd-content > div.ycd-language-selector > button#ycd-language-selector__menu-button
○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
●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
●`[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
●Form elements have associated labels
●`[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
●Document has a `<title>` element
●`<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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○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
/v1/user/login?app_id=tunnus-sdk&app_key=dtYmXC2V3DYKhJG1...
Failed to load resource: the server responded with a status of 401 ()
/v1/user/login?app_id=yle-consent-sdk&app_key=9diylCAglIh...
Failed to load resource: the server responded with a status of 401 ()
/v1/user/login?app_id=tunnus-sdk&app_key=dtYmXC2V3DYKhJG1...
Failed to load resource: the server responded with a status of 401 ()
/v1/user/login?app_id=tunnus-sdk&app_key=dtYmXC2V3DYKhJG1...
Failed to load resource: the server responded with a status of 401 ()

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
yle.fi/ukko/assets/build/936.6d2bbdb591d6ec74301c.js
player-v2.yle.fi/embed.jsplayer-v2.yle.fi/embed.js.map
player-v2.yle.fi/761.77dd3ec144e0d2e580a9.jsplayer-v2.yle.fi/761.77dd3ec144e0d2e580a9.js.map
player-v2.yle.fi/143.8548a9a1553a1277bd33.jsplayer-v2.yle.fi/143.8548a9a1553a1277bd33.js.map
●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
○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