Yle.fi Yle.fi - oivalla jotain uutta
yle.fi - oivalla jotain uutta. Uutisia, päivän puheenaiheita ja muut Ylen parhaat verkkosisällöt.
yle.fi Desktop Performance
59/100
These metrics represent real-world Chrome users experience viewing yle.fi web page. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Largest Contentful Paint
First Contentful Paint
First Input Delay
Cumulative Layout Shift
Metrics
Total Blocking Time12/100 770 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Speed Index59/100 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint64/100 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive74/100 3.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint98/100 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Cumulative Layout Shift100/100 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Should Fix (11)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce initial server response time
Root document took 2,000 ms
1,405 ms
Remove unused JavaScript
Potential savings of 515 KiB
600 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Serve static assets with an efficient cache policy
7 resources found
Avoid an excessive DOM size
1,464 elements
Minimize main-thread work
2.7 s
Reduce JavaScript execution time
1.7 s
Avoid long main-thread tasks
7 long tasks found
Keep request counts low and transfer sizes small
53 requests • 1,998 KiB
Largest Contentful Paint element
1 element found
Avoid chaining critical requests
7 chains found
Passed Audits (17)
Preload key requests
Minify CSS
Potential savings of 3 KiB
Avoids `document.write()`
Enable text compression
Preconnect to required origins
Uses passive listeners to improve scrolling performance
Avoid multiple page redirects
Potential savings of 190 ms
Minify JavaScript
Efficiently encode images
Minimize third-party usage
Third-party code blocked the main thread for 140 ms
Use video formats for animated content
Avoids enormous network payloads
Total size was 1,998 KiB
Defer offscreen images
Potential savings of 46 KiB
Serve images in next-gen formats
Remove unused CSS
Potential savings of 36 KiB
Eliminate render-blocking resources
Potential savings of 0 ms
Properly size images
Potential savings of 22 KiB
yle.fi Desktop SEO
92/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (1)
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Passed Audits (11)
Document avoids plugins
Document has a meta description
Page has successful HTTP status code
Page isn’t blocked from indexing
robots.txt is valid
Document has a valid `hreflang`
Links have descriptive text
Document has a `<title>` element
Links are crawlable
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Document has a valid `rel=canonical`
yle.fi Desktop Best Practices
77/100
These checks highlight opportunities to improve the overall code health of yle.fi page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (3)
Trust and Safety
Does not use HTTPS
1 insecure request found
General
Browser errors were logged to the console
User Experience
Displays images with incorrect aspect ratio
Passed Audits (11)
Links to cross-origin destinations are safe
Avoids deprecated APIs
Avoids front-end JavaScript libraries with known security vulnerabilities
Avoids Application Cache
Avoids requesting the notification permission on page load
Page has the HTML doctype
Allows users to paste into password fields
Avoids requesting the geolocation permission on page load
Serves images with appropriate resolution
Detected JavaScript libraries
Properly defines charset
yle.fi Desktop Progressive Web App
22/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
PWA Optimized
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Manifest doesn't have a maskable icon
Fast and reliable
`start_url` does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 15.6 s
Current page does not respond with a 200 when offline
Installable
Does not use HTTPS
1 insecure request found
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Passed Audits (4)
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Provides a valid `apple-touch-icon`
yle.fi Desktop Accessibility
88/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (4)
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-hidden="true"]` elements contain focusable descendents
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Image elements do not have `[alt]` attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (21)
`<html>` element has a valid value for its `[lang]` attribute
`[role]`s are contained by their required parent element
`[role]`s have all required `[aria-*]` attributes
`<html>` element has a `[lang]` attribute
The page contains a heading, skip link, or landmark region
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-*]` attributes are valid and not misspelled
Heading elements appear in a sequentially-descending order
Form elements have associated labels
`[role]` values are valid
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[aria-*]` attributes have valid values
Document has a `<title>` element
Links have a discernible name
Buttons have an accessible name
ARIA IDs are unique
`[aria-*]` attributes match their roles
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
No element has a `[tabindex]` value greater than 0
`[aria-hidden="true"]` is not present on the document `<body>`
Desktop Speed
87/100
These checks analyze the performance of yle.fi on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (3)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Optimize images
Passed Audits (7)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify CSS
Minify HTML
Minify JavaScript
Prioritize visible content
www.yle.com
www.yle.net
www.yle.org
www.yle.info
www.yle.biz
www.yle.us
www.yle.mobi
www.le.fi
www.yle.fi
www.tle.fi
www.ytle.fi
www.tyle.fi
www.gle.fi
www.ygle.fi
www.gyle.fi
www.hle.fi
www.yhle.fi
www.hyle.fi
www.ule.fi
www.yule.fi
www.uyle.fi
www.ye.fi
www.ype.fi
www.ylpe.fi
www.yple.fi
www.yoe.fi
www.yloe.fi
www.yole.fi
www.yke.fi
www.ylke.fi
www.ykle.fi
www.yl.fi
www.ylw.fi
www.ylew.fi
www.ylwe.fi
www.yls.fi
www.yles.fi
www.ylse.fi
www.yld.fi
www.yled.fi
www.ylde.fi
www.ylr.fi
www.yler.fi
www.ylre.fi
www.yle.net
www.yle.org
www.yle.info
www.yle.biz
www.yle.us
www.yle.mobi
www.le.fi
www.yle.fi
www.tle.fi
www.ytle.fi
www.tyle.fi
www.gle.fi
www.ygle.fi
www.gyle.fi
www.hle.fi
www.yhle.fi
www.hyle.fi
www.ule.fi
www.yule.fi
www.uyle.fi
www.ye.fi
www.ype.fi
www.ylpe.fi
www.yple.fi
www.yoe.fi
www.yloe.fi
www.yole.fi
www.yke.fi
www.ylke.fi
www.ykle.fi
www.yl.fi
www.ylw.fi
www.ylew.fi
www.ylwe.fi
www.yls.fi
www.yles.fi
www.ylse.fi
www.yld.fi
www.yled.fi
www.ylde.fi
www.ylr.fi
www.yler.fi
www.ylre.fi