Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

kavli.dk

Erikssaser - Eriks Saser

Page Load Speed

21.7 sec in total

First Response

6.2 sec

Resources Loaded

15.2 sec

Page Rendered

250 ms

kavli.dk screenshot

About Website

Visit kavli.dk now to see the best up-to-date Kavli content and also check out these interesting facts you probably never knew about kavli.dk

Q-Meieriene ble opprettet i 2000. Siden 2002 har vi vært en del av Kavli Norge. Vi foredler i dag (2010) melk fra ca 530 gårder – 210.000 liter daglig.

Visit kavli.dk

Key Findings

We analyzed Kavli.dk page load time and found that the first response time was 6.2 sec and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

kavli.dk performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.383

27/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

kavli.dk

6243 ms

www.kavli.dk

5611 ms

kavlinorge_head.css

366 ms

kavlinorge_footer.js

881 ms

v.gif

161 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 44% of them (18 requests) were addressed to the original Kavli.dk, 41% (17 requests) were made to Kavli.cdn.keymedia.no and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Kavli.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.2 kB (7%)

Content Size

1.0 MB

After Optimization

944.8 kB

In fact, the total size of Kavli.dk main page is 1.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 917.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 41.2 kB

  • Original 47.6 kB
  • After minification 28.9 kB
  • After compression 6.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 18.7 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 74 B

  • Original 917.5 kB
  • After minification 917.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Kavli images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (12%)

Requests Now

33

After Optimization

29

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kavli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

kavli.dk accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kavli.dk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kavli.dk SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    DA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kavli.dk can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it does not match the claimed Danish language. Our system also found out that Kavli.dk main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Kavli. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: