Mobile 375 × 812

Desktop 1440 × 900

Score: 78 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
Mostly accessible, but some users still face barriers.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
'unsafe-eval' found in script source
Security gaps expose your site and users to attacks, eroding trust.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
Cookie 'TS01b184ef' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
1 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
3 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/14b4f348-317f-4469-bfe5-01a2704c1032)<a href="https://beavercheck.com/results/14b4f348-317f-4469-bfe5-01a2704c1032"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fki.se" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fki.seThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~29%.
Page takes 11.8s to load
+12% bounceUsers abandon at ~3s — you're 9.3s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 738ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
4 broken link(s) on the page
+5% bounceClicks 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.
SEK 3,825 investment → SEK 28,858/month returns + EUR 120,500,000 risk avoided
SEK 3,825
4h · 5 findings
SEK 28,858 /mo
~SEK 346,291 / year
EUR 120,500,000
if kept compliant
SEK 1,275 — 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.
4.5 developer hours at kr850/hr
Based on Sweden rates (kr850/hr)
Start here for the best return on investment
SEK 10,041,674 / month at risk
~SEK 120,500,087 / year if left unfixed
€120,500,000
+4 more
SEK 7.24 /mo
8598.9 MB/mo × 0.842 SEK/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
3.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
11.76 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
738 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.22 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.
12.30 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img | /sites/kise/files/styles/front_page_hero_mobile_2x/public... | 377.0 KiB | 290.2 KiB |
Studenter på campus div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_mobile_2x/public... | 149.1 KiB | 135.8 KiB |
Blodets proteiner förändras kraftigt från barndom till vuxen ålder div.second > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 120.4 KiB | 103.5 KiB |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 111.2 KiB | 96.4 KiB |
Välkomstdagen VT2026 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_mobile_2x/public... | 101.4 KiB | 80.1 KiB |
Nobelmedaljen div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 73.4 KiB | 58.2 KiB |
Studenter som pluggar på campus Solna. div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_mobile_2x/public... | 68.7 KiB | 53.9 KiB |
Välkomstdagen VT2026 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_mobile_2x/public... | 68.4 KiB | 53.2 KiB |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 67.8 KiB | 53.0 KiB |
Collage med bilder av tidskriftsomslag: NEJM, Cell Stem Cell, BMJ, Nature och S… div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 61.4 KiB | 49.6 KiB |
Decorativt montage av flera bilder som visar olika aspekter av forskningsinfras… div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 53.4 KiB | 37.7 KiB |
Annika Östman Wernerson div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile_2x/public/... | 44.4 KiB | 31.0 KiB |
Promotionshögtid 1 november 2024. div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_mobile_2x/public... | 34.6 KiB | 26.5 KiB |
Nu enklare att hitta rätt innovationsstöd vid KI div.second > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 29.4 KiB | 12.5 KiB |
Framsteg för stamcellsterapi vid typ 1-diabetes div.third > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 21.6 KiB | 5.1 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/kise/files/css/css_Ny2PCBf1gytD60mvlwY5z08mwnOv6Kx... | 79.3 KiB | 59.1 KiB |
| /sites/kise/files/css/css_jIbaGCsFO0UBR0nvf34VTWncqs7L2uy... | 37.6 KiB | 27.0 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/kise/files/js/js_Icjwe3JDndpDiMT-08w2mBWT0nZGrhLIt... | 429.9 KiB | 238.7 KiB |
| /sites/kise/files/js/js_rcIe6PKHFpXKQdU4B51E7RWIyBCWWhgYe... | 69.4 KiB | 60.1 KiB |
| www.googletagmanager.com/gtag/js?id=G-VZD17KHKE3&cx=c>m=4e64k1 | 157.0 KiB | 59.9 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-T8BVXM | 137.4 KiB | 57.5 KiB |
| cdn.jsdelivr.net/npm/addsearch-search-ui@0.9/dist/addsearch-search-ui.min.js | 68.9 KiB | 48.6 KiB |
| cdn.jsdelivr.net/npm/addsearch-js-client@1.1.1/dist/addsearch-js-client.min.js | 34.6 KiB | 26.2 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| Unattributable | 481 ms | 8.1 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-T8BVXM | 436 ms | 357 ms | 54 ms |
| /sites/kise/files/js/js_B2e9-xkCsS8xlPL80EWp_Nf84NegRYCT6... | 400 ms | 242 ms | 1.6 ms |
| /sites/kise/files/js/js_Icjwe3JDndpDiMT-08w2mBWT0nZGrhLIt... | 381 ms | 279 ms | 74 ms |
| www.googletagmanager.com/gtag/js?id=G-VZD17KHKE3&cx=c>m=4e64k1 | 346 ms | 286 ms | 58 ms |
| ki.se/ | 283 ms | 12 ms | 1.1 ms |
| cdn.jsdelivr.net/npm/addsearch-search-ui@0.9/dist/addsearch-search-ui.min.js | 94 ms | 61 ms | 33 ms |
| cdn.jsdelivr.net/npm/addsearch-js-client@1.1.1/dist/addsearch-js-client.min.js | 55 ms | 41 ms | 14 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.3 s |
| Other | 519 ms |
| Style & Layout | 314 ms |
| Script Parsing & Compilation | 262 ms |
| Parse HTML & CSS | 67 ms |
| Rendering | 55 ms |
| Garbage Collection | 26 ms |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Meny div > div.container > div.utilities > div#main-menu_toggle |
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Anpassa dina kakor div.wrapper > div.footer__col > p > a.js-cookie-settings-link |
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img |
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.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Mer information om våra kakor div.popup-content > div#popup-text > p > a |
Read this information in English div.popup-content > div#popup-text > p > a |
These items highlight common accessibility best practices.
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.27 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.91 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
44 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.93 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.
3.10 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img | /sites/kise/files/styles/front_page_hero_wide/public/qban... | 513.7 KiB | 272.9 KiB |
Studenter på campus div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_wide/public/qban... | 152.0 KiB | 133.9 KiB |
Blodets proteiner förändras kraftigt från barndom till vuxen ålder div.second > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 120.4 KiB | 99.8 KiB |
Välkomstdagen VT2026 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_wide/public/qban... | 102.2 KiB | 76.4 KiB |
Välkomstdagen VT2026 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_wide/public/qban... | 74.1 KiB | 57.2 KiB |
Studenter som pluggar på campus Solna. div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_wide/public/qban... | 68.8 KiB | 53.4 KiB |
Linnea, digital ambassador in the student area at ANA 8 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 36.9 KiB | 27.1 KiB |
Promotionshögtid 1 november 2024. div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_quintuple_wide/public/qban... | 34.7 KiB | 26.5 KiB |
Nu enklare att hitta rätt innovationsstöd vid KI div.second > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 29.4 KiB | 19.4 KiB |
Sustainable Development Agenda 2030 div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 27.5 KiB | 19.1 KiB |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 33.2 KiB | 17.4 KiB |
Framsteg för stamcellsterapi vid typ 1-diabetes div.third > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 21.6 KiB | 14.2 KiB |
Decorativt montage av flera bilder som visar olika aspekter av forskningsinfras… div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 21.6 KiB | 13.6 KiB |
Tryggare uppväxt gav bättre liv – även för nästa generation div.first > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 13.3 KiB | 8.6 KiB |
KI inviger nytt centrum – ska lyfta AI från projekt till praktik div.third > a.with-image > figure.front-news-block__image > img | /sites/nyheter/files/styles/promo_focalpoint_general/publ... | 11.4 KiB | 7.5 KiB |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 23.1 KiB | 7.3 KiB |
Collage med bilder av tidskriftsomslag: NEJM, Cell Stem Cell, BMJ, Nature och S… div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/qba... | 22.5 KiB | 6.7 KiB |
Nobelmedaljen div.item__media > div.flex-fix > picture > img | /sites/kise/files/styles/promo_carousel_mobile/public/201... | 21.8 KiB | 6.0 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
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.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/kise/files/css/css_Ny2PCBf1gytD60mvlwY5z08mwnOv6Kx... | 79.3 KiB | 60.9 KiB |
| /sites/kise/files/css/css_jIbaGCsFO0UBR0nvf34VTWncqs7L2uy... | 37.6 KiB | 28.7 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/kise/files/js/js_Icjwe3JDndpDiMT-08w2mBWT0nZGrhLIt... | 429.9 KiB | 239.5 KiB |
| www.googletagmanager.com/gtag/js?id=G-VZD17KHKE3&cx=c>m=4e64k1 | 157.0 KiB | 60.3 KiB |
| /sites/kise/files/js/js_rcIe6PKHFpXKQdU4B51E7RWIyBCWWhgYe... | 69.4 KiB | 60.1 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-T8BVXM | 137.4 KiB | 57.4 KiB |
| cdn.jsdelivr.net/npm/addsearch-search-ui@0.9/dist/addsearch-search-ui.min.js | 68.9 KiB | 48.6 KiB |
| cdn.jsdelivr.net/npm/addsearch-js-client@1.1.1/dist/addsearch-js-client.min.js | 34.6 KiB | 26.2 KiB |
| /sites/kise/files/js/js_fg3cHbSILPVTvkWKeyrG9bKeJ5bTQXr5R... | 49.7 KiB | 23.9 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Meny div > div.container > div.utilities > div#main-menu_toggle |
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Anpassa dina kakor div.wrapper > div.footer__col > p > a.js-cookie-settings-link |
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img |
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.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Previous section#P25449 > div.container > div.promo-margin-container > button.slick-prev |
Mer information om våra kakor div.popup-content > div#popup-text > p > a |
Read this information in English div.popup-content > div#popup-text > p > a |
These items highlight common accessibility best practices.
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div > div.hero-frontpage > picture > img div > div.hero-frontpage > picture > img |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img |
div.item__media > div.flex-fix > picture > img div.item__media > div.flex-fix > picture > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback