7.3 sec in total
254 ms
5.3 sec
1.7 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 254 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
62n.fo performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.1 s
1/100
25%
Value10.1 s
9/100
10%
Value550 ms
54/100
30%
Value0.001
100/100
15%
Value9.1 s
33/100
10%
254 ms
1028 ms
484 ms
106 ms
43 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 75% of them (54 requests) were addressed to the original 62n.fo, 7% (5 requests) were made to Cdn.jsdelivr.net and 6% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain 62n.fo.
Page size can be reduced by 117.3 kB (2%)
4.7 MB
4.6 MB
In fact, the total size of 62n.fo main page is 4.7 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 4.6 MB which makes up the majority of the site volume.
Potential reduce by 107.1 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 107.1 kB or 82% of the original size.
Potential reduce by 929 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. 62 N images are well optimized though.
Potential reduce by 9.3 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 9.3 kB or 26% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 40 (62%)
65
25
The browser has sent 65 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 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
62n.fo
254 ms
www.62n.fo
1028 ms
autoptimize_c2b1af1e9573d853e2b28bfe58873f44.css
484 ms
snx5pfl.css
106 ms
uc.js
43 ms
aos.css
318 ms
swiper-bundle.min.css
38 ms
magnific-popup.min.css
54 ms
autoptimize_single_c6a55456af4776c733018888483aba22.js
336 ms
autoptimize_single_5d29e36ce241a2ef5ec8ec84254d9542.js
322 ms
react.min.js
314 ms
react-dom.min.js
511 ms
jquery.min.js
419 ms
jquery-migrate.min.js
623 ms
autoptimize_single_36d6cfaa5389c16efa9c73c43ed22a7a.js
716 ms
script.js
49 ms
autoptimize_single_825465e05ada08960a91a81237766a83.js
648 ms
autoptimize_single_6964facb3fd0c9e0f0fa16a477c8cf1b.js
742 ms
autoptimize_single_dd84a5188be74ad45b6a50562716d2d9.js
822 ms
autoptimize_single_f4048ee0d4651ac030ba176b391c9213.js
816 ms
autoptimize_single_5c15ace4aa6bde440bc0d4dc5f08cb8b.js
920 ms
autoptimize_single_73173ad8e497df3149a8847abb7999ca.js
946 ms
autoptimize_single_ced805e103c618a34b34d9055b3542b9.js
1032 ms
autoptimize_single_e476967bd5c75220d425abe253678a0c.js
1027 ms
jquery.lazy.min.js
1127 ms
lunnar-focal-crop.min.js
1135 ms
aos.js
65 ms
axios.min.js
37 ms
swiper-bundle.min.js
39 ms
lazyload.min.js
39 ms
jquery.magnific-popup.min.js
60 ms
vue@2.6.14
40 ms
svg-inject.min.js
1216 ms
autoptimize_single_2732a86f2aa37dd31d4b76707fe29cd0.js
1256 ms
autoptimize_single_7d2f9445d4e2d93d648e5d736ee19a70.js
1320 ms
sbi-scripts.min.js
1538 ms
aos.js
11 ms
p.css
22 ms
aos.css
13 ms
64.png
527 ms
64.png
848 ms
sbi-sprite.png
715 ms
logo.svg
538 ms
caret.svg
626 ms
icon-menu.svg
851 ms
icon-close.svg
839 ms
icon-arrow.svg
907 ms
Andrei-Antal-canon-R6-044-scaled-1-1600x1021.jpg
1274 ms
Sol-Gran-Canaria-1600x935.jpg
1360 ms
NYC-1600x500.jpg
1392 ms
shutterstock_1203033751-1-1600x543.jpg
1395 ms
shutterstock_2375164481-1600x660.jpg
1405 ms
shutterstock_644740471.jpg
1641 ms
icon-circle-chevron.svg
1581 ms
shutterstock_345504362.jpg
1993 ms
shutterstock_376302562.jpg
2210 ms
shutterstock_2288863295.jpg
1956 ms
5-Background-img.jpg
1868 ms
kuffert_flugvari.jpg
2246 ms
square-image.jpg
2191 ms
1POOL-B-2-800x533.jpg
2172 ms
50477803606_51501c4d80_k-800x534.jpg
2497 ms
Social-icon.png
2296 ms
placeholder.png
2445 ms
icon-chevron.svg
2442 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
0 ms
icon-facebook.svg
2412 ms
icon-instagram.svg
2454 ms
icon-linkedin.svg
2212 ms
safe-to-visit.svg
2309 ms
visit-fo.svg
2540 ms
logo-lunnar.svg
2488 ms
62n.fo accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
62n.fo SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
FO
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 does not match the claimed Faeroese 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 data is detected on the main page of 62 N. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: