Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

kontent.dk

Digital Asset Management, PIM & Image bank

Page Load Speed

6.4 sec in total

First Response

342 ms

Resources Loaded

5 sec

Page Rendered

1 sec

About Website

Welcome to kontent.dk homepage info - get ready to check Kontent best content right away, or after learning these important things about kontent.dk

User-friendly DAM & PIM for companies to organize all digital assets like product data, images, videos, or size guides in a professional way.

Visit kontent.dk

Key Findings

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

Performance Metrics

kontent.dk performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

kontent.dk

342 ms

www.konform.com

1364 ms

screen-1457022034801.css

230 ms

css

25 ms

flog-1457022034801.js

215 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kontent.dk, 95% (95 requests) were made to Konform.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Konform.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 490.7 kB (5%)

Content Size

9.7 MB

After Optimization

9.2 MB

In fact, the total size of Kontent.dk main page is 9.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 109.2 kB

  • Original 126.8 kB
  • After minification 117.3 kB
  • After compression 17.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 109.2 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 142.1 kB

  • Original 9.2 MB
  • After minification 9.1 MB

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. Kontent images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 132.3 kB

  • Original 218.8 kB
  • After minification 218.8 kB
  • After compression 86.5 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 132.3 kB or 60% of the original size.

CSS Optimization

-90%

Potential reduce by 107.1 kB

  • Original 119.5 kB
  • After minification 96.7 kB
  • After compression 12.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kontent.dk needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

93

After Optimization

93

The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kontent. According to our analytics all requests are already optimized.

Accessibility Review

kontent.dk accessibility score

96

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.

Best Practices

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

SEO Factors

kontent.dk SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kontent.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Kontent.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 Kontent. 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: