Skip to content
Audit Complete

Results for https://sverigesradio.se

Visit site
SE · SEK (kr) · Estimated Applicable regulations: GDPR · ePrivacy Directive · EAA Dev cost: SEK 850/hr How jurisdiction is detected
Singapore Singapore · Singapore Completed: Apr 22, 2026 22:10 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C74

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 3543 peers
You 74
·
Avg 73
At average
0 50 100
Better than 56% of Google Search Console sites See full Google Search Console benchmark →
Microsoft · 2293 peers
You 74
·
Avg 72
At average
0 50 100
Better than 61% of Microsoft sites See full Microsoft benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

98 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fsverigesradio.se)](https://beavercheck.com/results/0057a7e6-5123-4502-b2a9-063fbf7798f1)
<a href="https://beavercheck.com/results/0057a7e6-5123-4502-b2a9-063fbf7798f1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsverigesradio.se" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsverigesradio.se

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 12.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 12.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~32%.

Speed (2)

Page takes 12.7s to load

+12% bounce

Users abandon at ~3s — you're 10.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

121 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

SEK 3,400 investment → SEK 16,667/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +5782%

Investment

SEK 3,400

4h · 5 findings

Monthly returns

SEK 16,667 /mo

~SEK 199,998 / year

  • Conversions recovered SEK 16,659
  • Bandwidth savings SEK 7.09

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • GDPR EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

SEK 1,700 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

kr3,400

4.0 developer hours at kr850/hr

Based on Sweden rates (kr850/hr)

Quick wins
kr1,700 4 fixes in ~120 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
kr /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

SEK 10,041,674 / month at risk

~SEK 120,500,085 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA
  • No privacy policy link detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    GDPR: EUR 10,000 – EUR 20,000,000

+6 more

Bandwidth Waste

SEK 7.09 /mo

8415.1 MB/mo × 0.842 SEK/GB

  • Optimize transfer: save ~842 KB per page load
    Saves SEK 7.09/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

27
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.98 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

12.66 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.12 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.175

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

7.46 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

18.70 s

Detailed Report

Audit breakdown by category with detailed findings.

27

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.17497] map[node:map[boundingRect:map[bottom:26639 height:26375 left:0 right:412 top:264 width:412] lhId:page-15-DIV nodeLabel:Nyheter Just nu: Hockey på Gotland NYHETER FRÅN EKOT Lyssna på nyheter Slut på … path:1,HTML,1,BODY,6,DIV selector:body#root > div.relative snippet:<div class="relative" data-aria-hidden="true" aria-hidden="true"> type:node] score:0.17497]]

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:95.39 source:map[column:56959 line:20 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/07n-9ddzh-ma-.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:10.326 source:map[column:15269 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/172slz~3~k_v8.js urlProvider:network]] map[reflowTime:0.234 source:map[column:12862 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/050vfryjddk_~.js urlProvider:network]] map[reflowTime:47.387 source:map[column:18977 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/04ebm-pjddm86.js urlProvider:network]] map[reflowTime:37.443 source:map[column:7403 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/050vfryjddk_~.js urlProvider:network]]]

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
Melania Trump, Donald Trump och en kanin div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/EIag/706658dd-68bf-4eba-a4ee-0b92ee5c59b3?w=750&h=750&q=7587.9 KiB83.1 KiB
En ishockeyspelare i Björklövens vita och gröna matchtröja står på isen med en … div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/De4rvYT_tg/93b09b52-cd02-498f-a958-cb434dc32b63?w=750...85.9 KiB81.2 KiB
Konvolut för Dagens Eko div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/static/AA/5526/b88ec273-4f1a-4693-a4e1-7e27f7b4e59d.j...66.1 KiB62.5 KiB
En närbild på Daniel Alling, SR:s internationella korrespondent. div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/D-s89RsrfDN4/d3c9a121-392b-40d3-a949-0a7f1234226b?w=7...47.2 KiB44.6 KiB
Björklövens Anton Malmström firar tillsammans med lagkamrater efter att ha gjor… div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/AA/c060ce8b-5d44-4546-b045-6e60b801a793?w=750&h=422&q=7589.7 KiB38.1 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/8d95e31e-8e07-4a1a-9b87-20c599b27f72.jpg...50.3 KiB33.6 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/f8052638-fc1f-4e54-9ea9-f9ae38eeead8.png...38.5 KiB25.7 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/46923ee0-b7b7-407f-be5a-b9a764b39e68.jpg...33.4 KiB22.3 KiB
hormuz div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/P5YduElCm9mi6lzHgA/7e623e11-8148-4eb5-8a76-a40ba153bd...22.8 KiB21.6 KiB
Daniella Afram och Jonathan Saglund, bilbyggare på Volvo. div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/e1ddff10-84d2-422a-9eef-5953048d4e09.jpg...30.9 KiB20.6 KiB
Johan Garpenlöv div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/AA/a04eaf82-a237-495f-92ef-9378a14d8f34?w=750&h=750&q=7522.7 KiB18.9 KiB
Snabbgående iranska patrullbåtar i Hormuzsundet div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/AA/17753a04-e819-46f2-9a47-b091d16afcfc?w=750&h=422&q=7569.2 KiB17.7 KiB
Det är oklart om avtalet med företaget Oracle kan brytas. div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/68a87440-8895-4923-bdf9-f9c24ab2a233.png...22.0 KiB14.7 KiB
Till vänster: Målningen Andy Warhols Scandinavian Beauty II. Till höger: Andy W… div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/7d5ed154-a5a1-4026-92ea-b53cca941e96.jpg...21.9 KiB14.6 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:2058.934 label:Time to first byte subpart:timeToFirstByte] map[duration:29.511 label:Resource load delay subpart:resourceLoadDelay] map[duration:679.07 label:Resource load duration subpart:resourceLoadDuration] map[duration:70.35 label:Element render delay subpart:elementRenderDelay]]
lhId: page-14-IMG
nodeLabel: Arkivbild – snötyngda påskliljor vid en vägkant i Malmö 2021.
path: 1,HTML,1,BODY,6,DIV,0,MAIN,0,DIV,0,DIV,2,SECTION,0,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,IMG
selector: div.click-target-container > div.relative > div.text-fg > img.absolute
snippet: <img alt="Arkivbild – snötyngda påskliljor vid en vägkant i Malmö 2021." class="absolute top-0 left-0 h-full w-full object-cover" loading="eager" fetchpriority="high" sizes="(min-width: 1024px) 1024px, 100vw" style="object-fit: cover; max-width: 1024px; max-height: 576px;" srcset="https://image-api.sr.se/v1/static/AA/83/8adcf635-2e29-4656-9a36-ce1e661fb2…" src="https://image-api.sr.se/v1/static/AA/83/8adcf635-2e29-4656-9a36-ce1e661fb2…">

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
value: no origins were preconnected
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

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.

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.3 s

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 858 ms
URLTime Spent
www.sverigesradio.se/958 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Nyheter Just nu: Hockey på Gotland NYHETER FRÅN EKOT Lyssna på nyheter Slut på … body#root > div.relative
0.175

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 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

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 Evaluation4.6 s
Other1.5 s
Style & Layout1.4 s
Script Parsing & Compilation535 ms
Rendering414 ms
Parse HTML & CSS269 ms
Garbage Collection66 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.Not actionable

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

Optimize DOM size
Font display
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 1 user timing
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 1 animated element found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 190 ms
Server Backend Latencies 220 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
INP breakdown
96

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DIREKT div.click-target-container > div.relative > div.gap-05 > span.font-sans

These are opportunities to improve the legibility of your content.

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
`[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
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
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
ARIA IDs are unique
`[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
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
Elements with visible text labels have matching accessible names.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Authorization will not be covered by the wildcard symbol (*) in CORS Access-Control-Allow-Headers handling.
Uses HTTPS
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 browser errors logged to the console
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
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
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

74
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.05 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.61 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

157 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.040

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.56 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.60 s

Detailed Report

Audit breakdown by category with detailed findings.

74

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:98.331 source:map[column:56959 line:20 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/07n-9ddzh-ma-.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:35.497 source:map[type:text value:[unattributed]]] map[reflowTime:2.521 source:map[column:10743 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/12btysqzj855j.js urlProvider:network]] map[reflowTime:5.094 source:map[column:12862 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/050vfryjddk_~.js urlProvider:network]] map[reflowTime:1.39 source:map[column:13128 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/050vfryjddk_~.js urlProvider:network]] map[reflowTime:48.909 source:map[column:18977 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/04ebm-pjddm86.js urlProvider:network]] map[reflowTime:40.417 source:map[column:7403 line:1 type:source-location url:https://www.sverigesradio.se/_next/static/chunks/050vfryjddk_~.js urlProvider:network]]]

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
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/8d95e31e-8e07-4a1a-9b87-20c599b27f72.jpg...89.5 KiB83.4 KiB
Snabbgående iranska patrullbåtar i Hormuzsundet div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/AA/17753a04-e819-46f2-9a47-b091d16afcfc?w=1024&h=576&q=75122.4 KiB69.1 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/f8052638-fc1f-4e54-9ea9-f9ae38eeead8.png...61.9 KiB57.7 KiB
Melania Trump, Donald Trump och en kanin div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/EIag/706658dd-68bf-4eba-a4ee-0b92ee5c59b3?w=512&h=512&q=7549.6 KiB46.4 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/46923ee0-b7b7-407f-be5a-b9a764b39e68.jpg...48.1 KiB44.8 KiB
Daniella Afram och Jonathan Saglund, bilbyggare på Volvo. div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/e1ddff10-84d2-422a-9eef-5953048d4e09.jpg...45.7 KiB42.6 KiB
En närbild på Daniel Alling, SR:s internationella korrespondent. div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/D-s89RsrfDN4/d3c9a121-392b-40d3-a949-0a7f1234226b?w=5...34.6 KiB32.0 KiB
En man i kostym sitter vid ett bord med papper och en kaffekopp framför sig. Ba… div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/MABHDVA/3c5f4acc-9731-4109-a900-726e046981e6?w=1024&h...70.1 KiB31.2 KiB
Det är oklart om avtalet med företaget Oracle kan brytas. div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/68a87440-8895-4923-bdf9-f9c24ab2a233.png...33.4 KiB31.2 KiB
Till vänster: Målningen Andy Warhols Scandinavian Beauty II. Till höger: Andy W… div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/7d5ed154-a5a1-4026-92ea-b53cca941e96.jpg...32.3 KiB30.1 KiB
Konvolut för Dagens Eko div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/static/AA/5526/b88ec273-4f1a-4693-a4e1-7e27f7b4e59d.j...31.1 KiB28.7 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/14d0a253-b395-4d58-9d37-0d3789c06ab2.jpg...27.4 KiB25.6 KiB
Arkivbild – snötyngda påskliljor vid en vägkant i Malmö 2021. div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/8adcf635-2e29-4656-9a36-ce1e661fb2b5.jpg...42.4 KiB18.9 KiB
div.flex > div.relative > div.text-fg > img.absolute div.flex > div.relative > div.text-fg > img.absolute
/v1/static/AA/83/bab359a9-5a70-4100-bd90-a137678aaeb6.png...19.4 KiB18.0 KiB
hormuz div.click-target-container > div.relative > div.text-fg > img.absolute
/v1/P5YduElCm9mi6lzHgA/7e623e11-8148-4eb5-8a76-a40ba153bd...18.4 KiB17.0 KiB
En manlig och kvinnlig programledare tittar in i kameran, kvinnan skrattar. div.click-target-container > div.relative > div.text-fg > img.absolute
image-api.sr.se/v1/AA/98c9d74d-dd49-4e22-9d89-79431ad1eceb?w=1024&h=576&q=7527.5 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
value: no origins were preconnected
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

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.

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: 598 ms
URLTime Spent
sverigesradio.se/598 ms
www.sverigesradio.se/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 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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 Evaluation1.2 s
Other561 ms
Style & Layout425 ms
Rendering144 ms
Script Parsing & Compilation144 ms
Parse HTML & CSS70 ms
Garbage Collection31 ms

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 CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 1 user timing
JavaScript execution time 1.3 s
Avoid long main-thread tasks 9 long tasks found
Avoid non-composited animations 1 animated element found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
96

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DIREKT div.click-target-container > div.relative > div.gap-05 > span.font-sans

These are opportunities to improve the legibility of your content.

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
`[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
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
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
ARIA IDs are unique
`[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
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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.
Image elements have `[alt]` attributes
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
Elements with visible text labels have matching accessible names.
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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Authorization will not be covered by the wildcard symbol (*) in CORS Access-Control-Allow-Headers handling.
Uses HTTPS
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 browser errors logged to the console
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
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
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Send Feedback