2.1 sec in total
227 ms
1.2 sec
636 ms
Welcome to kontiki2.com homepage info - get ready to check Kon Tiki2 best content for Norway right away, or after learning these important things about kontiki2.com
Kon-Tiki2 expedition to Easter Island, and back again, starting November 2015
Visit kontiki2.comWe analyzed Kontiki2.com page load time and found that the first response time was 227 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
kontiki2.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value3.2 s
73/100
25%
Value5.3 s
58/100
10%
Value320 ms
76/100
30%
Value0.058
98/100
15%
Value15.4 s
7/100
10%
227 ms
69 ms
30 ms
136 ms
22 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 53% of them (57 requests) were addressed to the original Kontiki2.com, 13% (14 requests) were made to Maps.google.com and 9% (10 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (556 ms) belongs to the original domain Kontiki2.com.
Page size can be reduced by 489.1 kB (29%)
1.7 MB
1.2 MB
In fact, the total size of Kontiki2.com main page is 1.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 30.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 30.1 kB or 74% of the original size.
Potential reduce by 46.9 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. Kon Tiki2 images are well optimized though.
Potential reduce by 380.1 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 380.1 kB or 69% of the original size.
Potential reduce by 31.9 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. Kontiki2.com needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 83% of the original size.
Number of requests can be reduced by 35 (33%)
107
72
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kon Tiki2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
kontiki2.com
227 ms
style.css
69 ms
jquery.min.js
30 ms
jquery.vscroll.js
136 ms
js
22 ms
track.js
223 ms
css
23 ms
css
36 ms
css
46 ms
widgets.js
206 ms
newbg.jpg
302 ms
kontiki-s.png
139 ms
fb.png
147 ms
russia.png
147 ms
image1.jpg
205 ms
image5.jpg
205 ms
image2.jpg
148 ms
image3.jpg
300 ms
image4.jpg
299 ms
12-Torgeir-279A9418-s.jpg
205 ms
12-Torgeir-FILE0078-1-s.jpg
299 ms
12-Tupak-279A9269-1-s.jpg
301 ms
12-Tupak-279A9272-1-s.jpg
300 ms
12-Tupak-279A9289-s.jpg
331 ms
12-Tupak-279A9308-s.jpg
337 ms
1-s.jpg
337 ms
3-s.jpg
338 ms
2-s.jpg
356 ms
image2-s.jpg
356 ms
image3-s.jpg
408 ms
image5-s.jpg
409 ms
image4-s.jpg
409 ms
image6-s.jpg
410 ms
image7-s.jpg
433 ms
2-s.jpg
433 ms
1-s.jpg
476 ms
1-s.jpg
476 ms
2-s.jpg
476 ms
2.jpg
475 ms
3.jpg
554 ms
1.jpg
490 ms
4.jpg
529 ms
5.jpg
533 ms
1-s.jpg
531 ms
2-s.jpg
530 ms
3-s.jpg
556 ms
common.js
56 ms
map.js
57 ms
util.js
57 ms
marker.js
55 ms
StaticMapService.GetMapImage
69 ms
4-s.jpg
467 ms
image1-s.jpg
462 ms
image2-s.jpg
463 ms
onion.js
28 ms
openhand_8_8.cur
21 ms
1-s.jpg
408 ms
2-s.jpg
431 ms
3-s.jpg
437 ms
4-s.jpg
477 ms
stats.js
43 ms
controls.js
38 ms
infowindow.js
36 ms
StaticMapService.GetMapImage
87 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
173 ms
ViewportInfoService.GetViewportInfo
67 ms
transparent.png
33 ms
css
29 ms
5-s.jpg
384 ms
thi.png
384 ms
3A-logo-350.png
451 ms
logo-opera.png
425 ms
logo-kongsberg.png
522 ms
logo-sima-350.png
524 ms
rahiti-3.png
68 ms
tupaq-3.png
141 ms
flag-16.png
141 ms
google4.png
18 ms
mapcnt6.png
17 ms
sv5.png
25 ms
tmapctrl.png
19 ms
tmapctrl4.png
19 ms
logo-mgp-200.jpg
490 ms
vt
7 ms
vt
5 ms
vt
7 ms
vt
5 ms
vt
5 ms
AuthenticationService.Authenticate
49 ms
syndication
182 ms
594882037619777539
184 ms
proxy.jpg
29 ms
proxy.jpg
31 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
39 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
86 ms
Dt-5TmXB_normal.jpeg
83 ms
default_profile_1_normal.png
77 ms
Cd5EByYXEAA1tsT.jpg
83 ms
Cd0vQebWAAAvXQE.jpg:large
99 ms
Cd0YKjmWAAAWvT_.jpg
84 ms
CdyM8ttW0AA3Y82.jpg:large
134 ms
Cd6ySSXW0AAWuR4.jpg:small
131 ms
Cd6ySZOXIAAewfT.jpg:small
133 ms
Cd6ySZZWAAAWz4K.jpg:small
135 ms
Cd0Oj25WwAEkhX4.jpg:small
137 ms
Cd0Oj46W0AAMwF-.jpg:small
135 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
80 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
92 ms
kontiki2.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
kontiki2.com 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kontiki2.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kontiki2.com 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 Kontiki2.com 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.
kontiki2.com
Open Graph description is not detected on the main page of Kon Tiki2. 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: