8.2 sec in total
431 ms
7.1 sec
666 ms
Click here to check amazing Nssr content for Norway. Otherwise, check out these important facts you probably never knew about nssr.no
Som medlem i RS får du fri assistanse fra våre 52 redningsskøyter - uten egenandel. Samtidig er du med på å opprettholde en trygg og god kystberedskap.
Visit nssr.noWe analyzed Nssr.no page load time and found that the first response time was 431 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nssr.no performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value10.4 s
0/100
25%
Value10.2 s
8/100
10%
Value2,590 ms
4/100
30%
Value0.068
96/100
15%
Value29.6 s
0/100
10%
431 ms
684 ms
608 ms
1096 ms
473 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nssr.no, 80% (39 requests) were made to Redningsselskapet.no and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Redningsselskapet.no.
Page size can be reduced by 522.9 kB (26%)
2.0 MB
1.5 MB
In fact, the total size of Nssr.no main page is 2.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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 27.0 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 9.8 kB, which is 30% 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.0 kB or 83% of the original size.
Potential reduce by 0 B
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. Nssr images are well optimized though.
Potential reduce by 388.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 388.4 kB or 66% of the original size.
Potential reduce by 107.5 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. Nssr.no needs all CSS files to be minified and compressed as it can save up to 107.5 kB or 85% of the original size.
Number of requests can be reduced by 10 (26%)
38
28
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nssr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
nssr.no
431 ms
www.redningsselskapet.no
684 ms
style.css
608 ms
plugins.min.js
1096 ms
main.min.js
473 ms
wp-embed.min.js
459 ms
css
66 ms
gtm.js
153 ms
rs-logo-header-jubileum.png
612 ms
rs-logo-header.svg
607 ms
badge-google-play.svg
619 ms
badge-app-store.svg
617 ms
ik.svg
613 ms
social-facebook.svg
849 ms
social-twitter.svg
912 ms
social-flickr.svg
915 ms
social-vimeo.svg
926 ms
social-youtube.svg
946 ms
social-instagram.svg
933 ms
social-snapchat.svg
1256 ms
rs-logo-footer.svg
1320 ms
flag_en.svg
1318 ms
Forside_knut_1920x1200px_15865968921_61f85b76f3_o1-1024x640.jpg
1779 ms
arrow.svg
1340 ms
reddet_300x300.jpg
1505 ms
redning_small_statistikk-copy.jpg
1874 ms
rs-ungdom-s-w640-h640-q75-m14419729101.jpg
1966 ms
Nokkeltall_frivillige_V2_21494403751_7cd31d28b4_o.jpg
2081 ms
Kursjenter.jpg
2460 ms
Bj%C3%B8rn_Bendiksen_reddet_2014-1024x480.jpg
2352 ms
Kristiane-og-Ask-1024x480.jpg
2675 ms
Redning_Dagfinn_og_arne_magnus-1024x383.jpg
2785 ms
Idar_ulstein_1920x900.jpg
3003 ms
device-android.png
2694 ms
Odin_samarbeidspartnere.jpg
3438 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
26 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
56 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
57 ms
gretaregular.woff
2806 ms
open-iconic.woff
3018 ms
analytics.js
51 ms
collect
10 ms
collect
55 ms
ga-audiences
41 ms
Forside_knut_1920x1200px_15865968921_61f85b76f3_o1.jpg
3231 ms
gretaregular.ttf
297 ms
open-iconic.ttf
193 ms
gretaregular.svg
1231 ms
open-iconic.otf
586 ms
nssr.no accessibility score
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
nssr.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
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
nssr.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
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nssr.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 language. Our system also found out that Nssr.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.
nssr.no
Open Graph description is not detected on the main page of Nssr. 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: