Tools & Wizards About Us
hurtigruten.dk screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

hurtigruten.dk

Hurtigruten - Norske fjorde og nordlys | Hurtigruten

Page Load Speed

2.6 sec in total

First Response

489 ms

Resources Loaded

1.3 sec

Page Rendered

865 ms

hurtigruten.dk screenshot

About Website

Visit hurtigruten.dk now to see the best up-to-date Hurtigruten content for Denmark and also check out these interesting facts you probably never knew about hurtigruten.dk

Hurtigruten er kendt for at sejle langs Norges kyst, men har også spændende rejser til Antarktis, Sydamerika og Grønland.

Visit hurtigruten.dk

Key Findings

We analyzed Hurtigruten.dk page load time and found that the first response time was 489 ms and then it took 2.1 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.

Performance Metrics

hurtigruten.dk performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value4,200 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

hurtigruten.dk

489 ms

www.hurtigruten.dk

60 ms

da-dk

99 ms

1455a5d4ea5a280c.css

44 ms

df9702dd2a785c08.css

87 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Hurtigruten.dk, 64% (32 requests) were made to Hurtigruten.com and 30% (15 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Hurtigruten.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.0 kB (85%)

Content Size

321.7 kB

After Optimization

48.7 kB

  • HTML
  • JavaScript

In fact, the total size of Hurtigruten.dk main page is 321.7 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. 70% of websites need less resources to load. HTML takes 321.0 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 273.0 kB

  • Original 321.0 kB
  • After minification 320.7 kB
  • After compression 48.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 273.0 kB or 85% of the original size.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 14 (42%)

Requests Now

33

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 33 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 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

hurtigruten.dk

hurtigruten.dk

489 ms

www.hurtigruten.dk

www.hurtigruten.dk

60 ms

da-dk

da-dk

99 ms

1455a5d4ea5a280c.css

1455a5d4ea5a280c.css

44 ms

df9702dd2a785c08.css

df9702dd2a785c08.css

87 ms

d1a030a5e5521dcd.css

d1a030a5e5521dcd.css

63 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

139 ms

webpack-634d034efec4d2bc.js

webpack-634d034efec4d2bc.js

66 ms

framework-37c52c0baa33abeb.js

framework-37c52c0baa33abeb.js

53 ms

main-8812cee787a2db4b.js

main-8812cee787a2db4b.js

72 ms

_app-081f717386f7abf4.js

_app-081f717386f7abf4.js

134 ms

3053-c955789bada6eef8.js

3053-c955789bada6eef8.js

132 ms

534-657df6651bd26c7c.js

534-657df6651bd26c7c.js

131 ms

7965-724b2f8cde3feaef.js

7965-724b2f8cde3feaef.js

134 ms

6009-9e0995185135c025.js

6009-9e0995185135c025.js

174 ms

2254-2a0dc6f41e916248.js

2254-2a0dc6f41e916248.js

175 ms

index-5e171243fdc6c8c7.js

index-5e171243fdc6c8c7.js

178 ms

_buildManifest.js

_buildManifest.js

172 ms

_ssgManifest.js

_ssgManifest.js

176 ms

Reine_GettyImages-1175555240.jpg

Reine_GettyImages-1175555240.jpg

53 ms

email-decode.min.js

email-decode.min.js

129 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

123 ms

Signature_Voyages_wordmark_NEG_RGB.svg

Signature_Voyages_wordmark_NEG_RGB.svg

49 ms

Norway_Tromso_HGR_163200_Photo_Getty_Images.JPG

Norway_Tromso_HGR_163200_Photo_Getty_Images.JPG

53 ms

Original_Voyages_wordmark_NEG_RGB.svg

Original_Voyages_wordmark_NEG_RGB.svg

55 ms

crop_fe5_u8L0_a64d8993-1acf-41f2-a1b8-1f305adc989e.jpg

crop_fe5_u8L0_a64d8993-1acf-41f2-a1b8-1f305adc989e.jpg

62 ms

Discovery_Voyages_wordmark_NEG_RGB__1_.svg

Discovery_Voyages_wordmark_NEG_RGB__1_.svg

53 ms

ship_in_raftsundet_norway_hgr_130573_1920_photo_trym_ivar_bergsmo.jpg

ship_in_raftsundet_norway_hgr_130573_1920_photo_trym_ivar_bergsmo.jpg

55 ms

MS_Nordkapp_Norway_HGR_90853_Photo_Photo_Competition-_1_.jpg

MS_Nordkapp_Norway_HGR_90853_Photo_Photo_Competition-_1_.jpg

57 ms

svalbard_product_hero-image_1-original.jpg

svalbard_product_hero-image_1-original.jpg

64 ms

midnight-sun2_norway_2500x1250.jpg

midnight-sun2_norway_2500x1250.jpg

61 ms

coastal_solo_ebd_hero.jpg

coastal_solo_ebd_hero.jpg

67 ms

lofoten-norway-hgr-143507-photo_shutterstock.jpg

lofoten-norway-hgr-143507-photo_shutterstock.jpg

122 ms

kangaamiut-a-typical-view-of-kangaamiut-a-village-in-greenland.jpg

kangaamiut-a-typical-view-of-kangaamiut-a-village-in-greenland.jpg

124 ms

Norway_Trondheim_Summer_HGR_163741_Visit_Norway.jpg

Norway_Trondheim_Summer_HGR_163741_Visit_Norway.jpg

119 ms

US_GOLD_LIST_2024_SEAL_OUTLINE_1.svg

US_GOLD_LIST_2024_SEAL_OUTLINE_1.svg

110 ms

AtlasGrotesk-Regular-Web.woff

AtlasGrotesk-Regular-Web.woff

67 ms

AtlasGrotesk-Regular-Web.woff

AtlasGrotesk-Regular-Web.woff

67 ms

AtlasGrotesk-Regular-Web.b4bcca64.woff

AtlasGrotesk-Regular-Web.b4bcca64.woff

69 ms

AtlasGrotesk-Medium-Web.woff

AtlasGrotesk-Medium-Web.woff

68 ms

AtlasGrotesk-Medium-Web.woff

AtlasGrotesk-Medium-Web.woff

97 ms

AtlasGrotesk-Medium-Web.b6adab02.woff

AtlasGrotesk-Medium-Web.b6adab02.woff

98 ms

Austin-Bold-Web.woff

Austin-Bold-Web.woff

40 ms

Austin-Bold-Web.woff

Austin-Bold-Web.woff

66 ms

Austin-Semibold-Web.woff

Austin-Semibold-Web.woff

41 ms

Austin-Semibold-Web.woff

Austin-Semibold-Web.woff

67 ms

Austin-Semibold-Web.416556ec.woff

Austin-Semibold-Web.416556ec.woff

41 ms

Austin-Regular-Web.woff

Austin-Regular-Web.woff

25 ms

Austin-Regular-Web.woff

Austin-Regular-Web.woff

67 ms

remixicon.26f18b51.woff

remixicon.26f18b51.woff

97 ms

Accessibility Review

hurtigruten.dk accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

hurtigruten.dk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

hurtigruten.dk SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hurtigruten.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it does not match the claimed English language. Our system also found out that Hurtigruten.dk 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.

Social Sharing Optimization

hurtigruten.dk

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: