2.9 sec in total
345 ms
2.3 sec
184 ms
Click here to check amazing EFN content. Otherwise, check out these important facts you probably never knew about efn.no
EFN
Visit efn.noWe analyzed Efn.no page load time and found that the first response time was 345 ms and then it took 2.5 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.
efn.no performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.6 s
35/100
25%
Value5.6 s
52/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.6 s
81/100
10%
345 ms
491 ms
229 ms
354 ms
466 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 78% of them (25 requests) were addressed to the original Efn.no, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (875 ms) relates to the external source Analytics.efn.no.
Page size can be reduced by 39.1 kB (67%)
58.8 kB
19.6 kB
In fact, the total size of Efn.no main page is 58.8 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 44.1 kB which makes up the majority of the site volume.
Potential reduce by 10.3 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 10.3 kB or 70% of the original size.
Potential reduce by 28.8 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 28.8 kB or 65% of the original size.
Number of requests can be reduced by 13 (48%)
27
14
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
efn.no
345 ms
efn.no
491 ms
jquery-1.4.2.min.js
229 ms
jquery.validate.min.js
354 ms
jquery-ui-1.7.2.custom.min.js
466 ms
jquery.tooltip.min.js
344 ms
jquery.cookie.js
344 ms
common-all.js
342 ms
common-pc.js
358 ms
all.css
475 ms
pc.css
459 ms
jquery-ui-1.7.2.custom.css
473 ms
all.css
470 ms
pc.css
471 ms
css
62 ms
css
74 ms
logo-screen.png
443 ms
logo-print.gif
231 ms
flag-no-active.png
227 ms
flag-en.png
226 ms
icon-rss-large.png
228 ms
linuxpowered.png
231 ms
valid-xhtml10.png
340 ms
anybrowser02.gif
344 ms
blueribbon.gif
343 ms
icon-mobile-dark.png
341 ms
piwik.js
875 ms
bodybg.png
211 ms
vRvZYZlUaogOuHbBTT1SNevvDin1pK8aKteLpeZ5c0A.woff
18 ms
0ihfXUL2emPh0ROJezvraLO3LdcAZYWl9Si6vvxL-qU.woff
21 ms
DBCt-NXN57MTAFjitYxdrNxB8OB85xaNTJvVSB9YUjQ.woff
26 ms
piwik.php
112 ms
efn.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
efn.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
efn.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 Efn.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 Efn.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.
efn.no
Open Graph description is not detected on the main page of EFN. 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: