2.9 sec in total
324 ms
2.4 sec
211 ms
Click here to check amazing FN content for Norway. Otherwise, check out these important facts you probably never knew about fn.no
FN-sambandet
Visit fn.noWe analyzed Fn.no page load time and found that the first response time was 324 ms and then it took 2.6 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.
fn.no performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value6.4 s
10/100
25%
Value5.4 s
57/100
10%
Value980 ms
28/100
30%
Value0.017
100/100
15%
Value8.1 s
42/100
10%
324 ms
516 ms
18 ms
194 ms
25 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 76% of them (39 requests) were addressed to the original Fn.no, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (744 ms) belongs to the original domain Fn.no.
Page size can be reduced by 385.0 kB (37%)
1.0 MB
664.3 kB
In fact, the total size of Fn.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. 40% of websites need less resources to load. Images take 587.5 kB which makes up the majority of the site volume.
Potential reduce by 27.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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 11% 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 27.2 kB or 76% of the original size.
Potential reduce by 33.1 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. FN images are well optimized though.
Potential reduce by 114.7 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 114.7 kB or 64% of the original size.
Potential reduce by 210.0 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. Fn.no needs all CSS files to be minified and compressed as it can save up to 210.0 kB or 85% of the original size.
Number of requests can be reduced by 22 (49%)
45
23
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
fn.no
324 ms
www.fn.no
516 ms
wurfl.js
18 ms
mobile_redirect.js
194 ms
css
25 ms
bootstrap.css
610 ms
global_styles.css
200 ms
core_hb.css
203 ms
core_sd.css
322 ms
core_bg.css
382 ms
millennium.css
292 ms
anythingslider.css
300 ms
ezie_jcrop_bootstrap_issue_fix.css
302 ms
core_pa.css
485 ms
dynamic.css
399 ms
jquery.js
706 ms
tinysort.js
428 ms
jquery.sticky.js
477 ms
core.js
499 ms
jquery.anythingslider.min.js
536 ms
init.js
571 ms
shop.js
582 ms
countdown.js
699 ms
ga.js
40 ms
__utm.gif
12 ms
logo_reduced.png
105 ms
facebook-ikon.png
102 ms
twitter-ikon.png
97 ms
rss-ikon.png
99 ms
UNDP-er-50-Et-kritisk-tidspunkt-for-verden_span6.jpg
410 ms
Noedhjelp_span3.png
224 ms
frontapgearticle_arrow.png
221 ms
Globalis_span3.png
390 ms
frontpage_flap.png
222 ms
Internasjonal-kvinnedag_span4.jpg
223 ms
calendarFnDayEmblem.png
287 ms
calendarDateImage.png
306 ms
Kvinner-noekkelen-til-en-baerekraftig-verden_span4.png
507 ms
UNHCR-Stadig-flere-kvinner-og-barn-flykter-over-Middelhavet_span4.jpg
308 ms
Skole-plugg.png
572 ms
Ungdomspanelet-plugg.jpg
744 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
49 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
62 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
62 ms
all.js
158 ms
icon_arrow_brown.png
363 ms
198 ms
xd_arbiter.php
133 ms
xd_arbiter.php
257 ms
print.css
104 ms
fn.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fn.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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fn.no SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fn.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 Fn.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.
fn.no
Open Graph description is not detected on the main page of FN. 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: