5.7 sec in total
511 ms
4.7 sec
571 ms
Click here to check amazing Hurtigruten content for Norway. Otherwise, check out these important facts you probably never knew about hurtigruten.no
Bli med på en spektakulær reise i Norge på reiseruten som forandret norskekysten for alltid. Opplev de vakreste fjordene, midnattssolen eller det magiske nordlyset.
Visit hurtigruten.noWe analyzed Hurtigruten.no page load time and found that the first response time was 511 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hurtigruten.no performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value4.3 s
42/100
25%
Value4.8 s
67/100
10%
Value340 ms
74/100
30%
Value0.023
100/100
15%
Value7.7 s
45/100
10%
511 ms
1199 ms
67 ms
653 ms
780 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Hurtigruten.no, 29% (15 requests) were made to Hurtigruten.global.ssl.fastly.net and 10% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Hurtigruten.global.ssl.fastly.net.
Page size can be reduced by 289.8 kB (10%)
2.8 MB
2.5 MB
In fact, the total size of Hurtigruten.no main page is 2.8 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. 65% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 108.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. 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 108.0 kB or 80% of the original size.
Potential reduce by 29.7 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. Hurtigruten images are well optimized though.
Potential reduce by 150.9 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 150.9 kB or 51% of the original size.
Potential reduce by 1.2 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. Hurtigruten.no needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 74% of the original size.
Number of requests can be reduced by 25 (60%)
42
17
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hurtigruten. 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 as a result speed up the page load time.
hurtigruten.no
511 ms
www.hurtigruten.no
1199 ms
css
67 ms
vendor
653 ms
main
780 ms
modernizr
560 ms
all
1537 ms
j.php
103 ms
logo-optimized.png
46 ms
logo-horizontal-optimized.png
45 ms
logo-vertical-optimized.png
100 ms
logo-horizontal-black.png
100 ms
gtm.js
261 ms
flag-norway-small.svg
57 ms
magnus-elander_greenland-com_frontpage.jpg
516 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
158 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
204 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
254 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
253 ms
hurtigruten-icons.woff
28 ms
v.gif
24 ms
footer-water.jpg
103 ms
conversion_async.js
112 ms
hotjar-88340.js
183 ms
fbevents.js
83 ms
nas.v1.min.js
906 ms
cx.js
160 ms
analytics.js
127 ms
activityi;src=4717608;type=remar0;cat=hurti0;ord=1689581735432;~oref=https%3A%2F%2Fwww.hurtigruten.no%2F
99 ms
157 ms
67 ms
linkid.js
35 ms
ec.js
66 ms
59 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
50 ms
sp1.html
30 ms
collect
25 ms
collect
70 ms
p1.js
44 ms
rep.gif
29 ms
ga-audiences
25 ms
no
367 ms
467 ms
pn10franz-gingele.jpg
177 ms
2500x1250_vg-fram-2015-173_mads-pihl.jpg
51 ms
2500x1250_shutterstock_212048782frazao-production.jpg
69 ms
119 ms
track
100 ms
allocate
91 ms
nr-852.min.js
131 ms
collect
22 ms
hurtigruten.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
hurtigruten.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
Page has valid source maps
hurtigruten.no SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Hurtigruten.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 Hurtigruten.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.
hurtigruten.no
Open Graph description is not detected on the main page of Hurtigruten. 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: