3.2 sec in total
360 ms
2.6 sec
232 ms
Visit nkom.no now to see the best up-to-date Nkom content for Norway and also check out these interesting facts you probably never knew about nkom.no
Nkom - Nasjonal kommunikasjonsmyndighet
Visit nkom.noWe analyzed Nkom.no page load time and found that the first response time was 360 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nkom.no performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value4.0 s
49/100
25%
Value5.9 s
49/100
10%
Value20 ms
100/100
30%
Value0.033
100/100
15%
Value4.1 s
87/100
10%
360 ms
900 ms
380 ms
263 ms
259 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 86% of them (48 requests) were addressed to the original Nkom.no, 4% (2 requests) were made to S7.addthis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Nkom.no.
Page size can be reduced by 333.9 kB (67%)
500.9 kB
167.1 kB
In fact, the total size of Nkom.no main page is 500.9 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. 35% of websites need less resources to load. Javascripts take 400.2 kB which makes up the majority of the site volume.
Potential reduce by 78.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 78.2 kB or 78% of the original size.
Potential reduce by 255.6 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 255.6 kB or 64% of the original size.
Number of requests can be reduced by 38 (72%)
53
15
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nkom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
nkom.no
360 ms
www.nkom.no
900 ms
npt.desktop.css
380 ms
jquery.cookiebar.css
263 ms
npt.level1.css
259 ms
npt.theme.css
376 ms
jquery-1.7.2.min.js
628 ms
jquery.cookiebar.js
359 ms
jquery.ui.core.min.js
385 ms
jquery.ui.widget.min.js
385 ms
jquery.ui.datepicker.min.js
484 ms
jquery.ui.datepicker-no.js
504 ms
jquery.tools.min.js
504 ms
jquery.validate.min.js
629 ms
jquery.cookie.js
510 ms
npt.main.js
608 ms
npt.desktop.js
633 ms
npt.datepicker.js
633 ms
mac.js
629 ms
html5shiv-printshiv.js
729 ms
js
61 ms
addthis_widget.js
15 ms
npt.main.css
375 ms
logo02.png
175 ms
2.png
176 ms
4.png
174 ms
3.png
176 ms
5.png
174 ms
small.jpeg
193 ms
small.jpeg
304 ms
12.jpeg
288 ms
14.jpeg
295 ms
logo01.png
288 ms
gtm.js
95 ms
300lo.json
44 ms
bg02.png
197 ms
bg03.png
204 ms
ico01.png
315 ms
ico02.png
314 ms
ico03.png
319 ms
ico04.png
320 ms
blt01.png
325 ms
bg06.png
326 ms
ico05.png
438 ms
blt02.png
436 ms
mobile.png
442 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
440 ms
ui-bg_flat_55_4c7093_40x100.png
445 ms
ui-icons_ffffff_256x240.png
447 ms
ui-bg_highlight-soft_85_f7f7f7_1x100.png
560 ms
bg08.png
559 ms
bg07.png
562 ms
sh.7c7179124ea24ac6ba46caac.html
46 ms
analytics.js
45 ms
collect
15 ms
collect
65 ms
nkom.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
nkom.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
nkom.no SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nkom.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 Nkom.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.
nkom.no
Open Graph description is not detected on the main page of Nkom. 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: