Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

dokken.no

Riving | Veidekke

Page Load Speed

2.4 sec in total

First Response

295 ms

Resources Loaded

1.6 sec

Page Rendered

425 ms

dokken.no screenshot

About Website

Visit dokken.no now to see the best up-to-date Dokken content and also check out these interesting facts you probably never knew about dokken.no

Vi utfører alle typer riveoppdrag og har godt utvalg av maskiner og spesialutstyr for denne typen arbeid. Vi er spesielt godt rustet for tunge betongbygg og høye konstruksjoner samt knusing og sorteri...

Visit dokken.no

Key Findings

We analyzed Dokken.no page load time and found that the first response time was 295 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

dokken.no performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

dokken.no

295 ms

article8260.ece

360 ms

base.css

211 ms

cookie-notice.css

196 ms

norge-variant.css

196 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Dokken.no, 63% (22 requests) were made to Veidekke.no and 11% (4 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (509 ms) relates to the external source Veidekke.no.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

490.3 kB

In fact, the total size of Dokken.no 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. 35% of websites need less resources to load. Images take 369.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.4 kB

  • Original 30.6 kB
  • After minification 30.5 kB
  • After compression 8.2 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 22.4 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 369.9 kB
  • After minification 368.0 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. Dokken images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 203.0 kB

  • Original 286.5 kB
  • After minification 257.2 kB
  • After compression 83.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 203.0 kB or 71% of the original size.

CSS Optimization

-91%

Potential reduce by 304.2 kB

  • Original 334.8 kB
  • After minification 205.4 kB
  • After compression 30.6 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. Dokken.no needs all CSS files to be minified and compressed as it can save up to 304.2 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (69%)

Requests Now

29

After Optimization

9

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

Accessibility Review

dokken.no accessibility score

100

Accessibility Issues

Best Practices

dokken.no 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

dokken.no SEO score

98

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

    NO

  • Language Claimed

    EN

  • Encoding

    UTF-8

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