6.2 sec in total
226 ms
4 sec
2 sec
Visit 62n.fo now to see the best up-to-date 62 N content and also check out these interesting facts you probably never knew about 62n.fo
Discover the Faroe Islands and let 62N plan your stay | 62N has more than 50 years experience arranging trips to the Faroe Islands. Have a look at the variety of exciting package holidays
Visit 62n.foWe analyzed 62n.fo page load time and found that the first response time was 226 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
62n.fo performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value3.0 s
78/100
25%
Value6.4 s
41/100
10%
Value4,030 ms
1/100
30%
Value0.019
100/100
15%
Value7.5 s
47/100
10%
226 ms
370 ms
132 ms
181 ms
253 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 13% of them (9 requests) were addressed to the original 62n.fo, 57% (39 requests) were made to D1gqok3qfmv025.cloudfront.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Siteimproveanalytics.com.
Page size can be reduced by 180.0 kB (17%)
1.1 MB
908.2 kB
In fact, the total size of 62n.fo main page is 1.1 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. 70% of websites need less resources to load. Images take 724.3 kB which makes up the majority of the site volume.
Potential reduce by 163.7 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 163.7 kB or 87% of the original size.
Potential reduce by 12.6 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. 62 N images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.3 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. 62n.fo has all CSS files already compressed.
Number of requests can be reduced by 32 (52%)
61
29
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 62 N. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
62n.fo
226 ms
en
370 ms
datepicker.min.css
132 ms
custom.css
181 ms
Modal.css
253 ms
logo.svg
46 ms
g%C3%A1sadalur-waterfall.jpg
38 ms
bosdalafoss-dama.jpg
10 ms
tindholmur-gongufolk.jpg
9 ms
risin-og-kellingin-kvold.jpg
38 ms
services_kuffert.png
37 ms
services_bil.png
46 ms
services_bed.png
80 ms
DependencyHandler.axd
584 ms
DependencyHandler.axd
503 ms
DependencyHandler.axd
588 ms
DependencyHandler.axd
424 ms
datepicker.min.js
321 ms
custom.js
330 ms
Modal.js
330 ms
js
136 ms
2793154.js
137 ms
safetovisit.png
498 ms
logo_thefaroeislands.png
71 ms
header_gradient.png
114 ms
DD_menuSymbol.png
115 ms
saksun-1.jpg
130 ms
arrow-down-bg_33.png
130 ms
shutterstock_1655438104.jpg
140 ms
bicycling-in-the-faroe-islands.jpg
140 ms
puffin.jpg
141 ms
mykines-2.jpg
143 ms
mykines-1.jpg
153 ms
11_fullwidthlink_1.png
152 ms
socialmedia_instagram.png
169 ms
socialmedia_skype.png
169 ms
socialmedia_facebook.png
171 ms
socialmedia_linkedin3.png
170 ms
css
62 ms
xwb0nux.css
97 ms
DependencyHandler.axd
443 ms
DependencyHandler.axd
448 ms
DependencyHandler.axd
207 ms
p.css
39 ms
close.svg
410 ms
d
409 ms
ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CA.ttf
673 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-33mZGCQYag.ttf
786 ms
ieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYag.ttf
762 ms
fbevents.js
860 ms
ls.js
1397 ms
siteanalyze_6150121.js
1401 ms
saksun-1.jpg
470 ms
shutterstock_1655438104.jpg
268 ms
bicycling-in-the-faroe-islands.jpg
267 ms
puffin.jpg
269 ms
mykines-2.jpg
270 ms
mykines-1.jpg
571 ms
arrowleft.png
389 ms
dd_itemClosed_dark.png
388 ms
collectedforms.js
598 ms
leadflows.js
584 ms
2793154.js
602 ms
2793154.js
595 ms
analytics.js
337 ms
2045968865629838
151 ms
collect
366 ms
collect
336 ms
62n.fo 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
62n.fo 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
Page has valid source maps
62n.fo 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 62n.fo can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 62n.fo 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.
62n.fo
Open Graph description is not detected on the main page of 62 N. 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: