6.8 sec in total
1.4 sec
4.8 sec
585 ms
Click here to check amazing 66 North content for United States. Otherwise, check out these important facts you probably never knew about 66north.us
Keeping Iceland warm since 1926.
Visit 66north.usWe analyzed 66north.us page load time and found that the first response time was 1.4 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
66north.us performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value11.8 s
0/100
25%
Value9.6 s
11/100
10%
Value4,460 ms
0/100
30%
Value0.066
97/100
15%
Value18.3 s
3/100
10%
1353 ms
354 ms
620 ms
493 ms
34 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 64% of them (35 requests) were addressed to the original 66north.us, 18% (10 requests) were made to Scontent.cdninstagram.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 66north.us.
Page size can be reduced by 686.6 kB (28%)
2.5 MB
1.8 MB
In fact, the total size of 66north.us main page is 2.5 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 90.6 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 34.1 kB, which is 31% 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 90.6 kB or 84% of the original size.
Potential reduce by 21.5 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. 66 North images are well optimized though.
Potential reduce by 371.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 371.4 kB or 64% of the original size.
Potential reduce by 203.0 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. 66north.us needs all CSS files to be minified and compressed as it can save up to 203.0 kB or 85% of the original size.
Number of requests can be reduced by 6 (13%)
47
41
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 66 North. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
www.66north.us
1353 ms
app.min.css
354 ms
modernizr.js
620 ms
spinnach.js
493 ms
conversion.js
34 ms
app.min.js
1202 ms
analytics.js
175 ms
186 ms
bordi-2320x800-9.jpg
298 ms
bordi-2320x800-18.jpg
951 ms
bordi-2320x800-26.jpg
948 ms
66north-logo-small@2x.jpg
949 ms
a6c91dda-d4ae-4d51-be05-1da4055b3900.woff
287 ms
FranklinGothicMed.woff
791 ms
ca49688c-50e1-4f26-bbf1-84ef6401353f.woff
789 ms
ss-social-regular.woff
789 ms
ss-standard.woff
789 ms
linkid.js
11 ms
74 ms
collect
9 ms
collect
64 ms
ga-audiences
17 ms
inspectlet.js
443 ms
feed
938 ms
vefkubbur-staersti-2.jpg
318 ms
or-kubbur-2.jpg
378 ms
asdis-kubbur-3.jpg
318 ms
w11130-665.jpg
318 ms
l81220-839.jpg
454 ms
w11230-900-11.jpg
312 ms
q01159-840.jpg
455 ms
e11451-830-grimsey-3.jpg
453 ms
w11333-415.jpg
455 ms
_a9t9337.jpg
454 ms
dokkbla-duskhufa.jpg
593 ms
q01149-847-spoitop.jpg
811 ms
q81149-840.png
663 ms
vef-2.jpg
660 ms
andrea-kubbur-3.jpg
669 ms
kubbur-2.jpg
687 ms
vefkubbur-2.jpg
760 ms
sjomadur02at2x.jpg
840 ms
66north_phaseone108883.jpg
840 ms
tota-2.jpg
840 ms
1950808726
218 ms
11253930_493972200786670_963895713_n.jpg
354 ms
12446063_227670927579084_594397345_n.jpg
480 ms
12725066_1262660087095403_287992862_n.jpg
749 ms
12717035_161522440897247_1241767708_n.jpg
752 ms
12728639_448292092048027_1069581469_n.jpg
681 ms
12677323_1712605769023293_40383292_n.jpg
682 ms
12501470_186017765091817_992431326_n.jpg
686 ms
12568243_1065819160151768_807624912_n.jpg
760 ms
12424346_489112964605546_1005946676_n.jpg
817 ms
12534361_589021421251571_244140616_n.jpg
817 ms
66north.us accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
66north.us 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
Page has valid source maps
66north.us 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 66north.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 66north.us 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.
66north.us
Open Graph description is not detected on the main page of 66 North. 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: