Tools & Wizards About Us
kongehuset.no screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

kongehuset.no

Forsiden på Kongehusets nettsted - Det norske kongehus

Page Load Speed

4.7 sec in total

First Response

328 ms

Resources Loaded

4 sec

Page Rendered

379 ms

kongehuset.no screenshot

About Website

Visit kongehuset.no now to see the best up-to-date Kongehus Et content for Norway and also check out these interesting facts you probably never knew about kongehuset.no

Her finnes informasjon om den norske kongefamilien, samt nyheter om deres offisielle virke og program. Finn også stoff om Slottet, Slottsparken, kongelige ordener og mye annet.

Visit kongehuset.no

Key Findings

We analyzed Kongehuset.no page load time and found that the first response time was 328 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

kongehuset.no performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

kongehuset.no

328 ms

www.kongehuset.no

134 ms

www.kongehuset.no

62 ms

nettsted.css

310 ms

responsive.css

484 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Kongehuset.no, 5% (2 requests) were made to Youtube.com and 3% (1 request) were made to Plausible.io. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kongehuset.no.

Page Optimization Overview & Recommendations

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

Content Size

447.7 kB

After Optimization

424.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kongehuset.no main page is 447.7 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. 20% of websites need less resources to load. Javascripts take 298.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.9 kB

  • Original 21.0 kB
  • After minification 16.5 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 22% 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 15.9 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 3.9 kB

  • Original 104.1 kB
  • After minification 100.2 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. Kongehus Et images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 298.6 kB
  • After minification 298.6 kB
  • After compression 295.4 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.

CSS Optimization

-0%

Potential reduce by 31 B

  • Original 23.9 kB
  • After minification 23.9 kB
  • After compression 23.9 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. Kongehuset.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (50%)

Requests Now

36

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kongehuset.no

kongehuset.no

328 ms

www.kongehuset.no

www.kongehuset.no

134 ms

www.kongehuset.no

www.kongehuset.no

62 ms

nettsted.css

nettsted.css

310 ms

responsive.css

responsive.css

484 ms

retina.css

retina.css

311 ms

video-js.min.css

video-js.min.css

305 ms

script.manual.js

script.manual.js

29 ms

i18n-js.php

i18n-js.php

320 ms

common.js

common.js

310 ms

submenu.js

submenu.js

650 ms

Tween.js

Tween.js

602 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

321 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

661 ms

jqtouch-jquery.js

jqtouch-jquery.js

622 ms

jquery.tools-scrollable.min.js

jquery.tools-scrollable.min.js

626 ms

video.min.js

video.min.js

1500 ms

Youtube.min.js

Youtube.min.js

897 ms

karusell.js

karusell.js

649 ms

nettsted.js

nettsted.js

643 ms

iframe_api

iframe_api

62 ms

logo_norsk.png

logo_norsk.png

345 ms

Scale

Scale

1109 ms

Crop

Crop

1044 ms

Crop

Crop

1102 ms

Crop

Crop

866 ms

Scale

Scale

835 ms

Scale

Scale

653 ms

Scale

Scale

1002 ms

Scale

Scale

1859 ms

Scale

Scale

1879 ms

Scale

Scale

1301 ms

blank.gif

blank.gif

1339 ms

social_fb@2x.png

social_fb@2x.png

1367 ms

social_in@2x.png

social_in@2x.png

1094 ms

social_tw@2x.png

social_tw@2x.png

1109 ms

social_yt@2x.png

social_yt@2x.png

1156 ms

www-widgetapi.js

www-widgetapi.js

7 ms

print.css

print.css

18 ms

Accessibility Review

kongehuset.no accessibility score

93

Accessibility Issues

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

Form elements do not have associated labels

Best Practices

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

kongehuset.no SEO score

90

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

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

    NO

  • Encoding

    UTF-8

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

kongehuset.no

Open Graph data is detected on the main page of Kongehus Et. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: