Tools & Wizards About Us
opendi.dk screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

opendi.dk

Branchebog og vurderingsportal - Opendi

Page Load Speed

2.5 sec in total

First Response

279 ms

Resources Loaded

2 sec

Page Rendered

175 ms

opendi.dk screenshot

About Website

Click here to check amazing Opendi content for Denmark. Otherwise, check out these important facts you probably never knew about opendi.dk

Branchebog og vurderingsportal med 366000 firmaer og 30000 vurderinger. Over 1000 firmaer med detaljerede beskrivelser og bykort.

Visit opendi.dk

Key Findings

We analyzed Opendi.dk page load time and found that the first response time was 279 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

opendi.dk performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

opendi.dk

279 ms

www.opendi.dk

427 ms

bg-texture.jpg

49 ms

map_de.png

40 ms

logo_small.png

39 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Opendi.dk, 38% (6 requests) were made to Static.opendi.com and 25% (4 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (665 ms) relates to the external source Etracker.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.3 kB (52%)

Content Size

315.5 kB

After Optimization

152.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Opendi.dk main page is 315.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. HTML takes 213.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 162.8 kB

  • Original 213.8 kB
  • After minification 197.8 kB
  • After compression 51.1 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 162.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 12.9 kB
  • After minification 12.9 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. Opendi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 481 B

  • Original 88.8 kB
  • After minification 88.7 kB
  • After compression 88.3 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

  • Images
  • JavaScript

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

Network Requests Diagram

opendi.dk

opendi.dk

279 ms

www.opendi.dk

www.opendi.dk

427 ms

bg-texture.jpg

bg-texture.jpg

49 ms

map_de.png

map_de.png

40 ms

logo_small.png

logo_small.png

39 ms

357 ms

swiss_roman-webfont.woff

swiss_roman-webfont.woff

49 ms

swiss_bold-webfont.woff

swiss_bold-webfont.woff

41 ms

e.js

e.js

406 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

665 ms

523 ms

t.js

t.js

548 ms

analytics.js

analytics.js

57 ms

collect

collect

25 ms

cnt_js.php

cnt_js.php

149 ms

cntcc

cntcc

139 ms

Accessibility Review

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

Low

No form fields have multiple labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

opendi.dk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

opendi.dk SEO score

94

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opendi.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Opendi.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

opendi.dk

Open Graph description is not detected on the main page of Opendi. 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: