1.3 sec in total
184 ms
915 ms
222 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 184 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
kontiki2.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value3.5 s
63/100
25%
Value4.6 s
70/100
10%
Value460 ms
61/100
30%
Value0.045
99/100
15%
Value9.6 s
29/100
10%
184 ms
76 ms
8 ms
150 ms
38 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 55% of them (34 requests) were addressed to the original Kontiki2.com, 29% (18 requests) were made to Platform.twitter.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (575 ms) belongs to the original domain Kontiki2.com.
Page size can be reduced by 32.1 kB (6%)
574.0 kB
541.9 kB
In fact, the total size of Kontiki2.com main page is 574.0 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. 65% of websites need less resources to load. Images take 425.6 kB which makes up the majority of the site volume.
Potential reduce by 11.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. 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 11.6 kB or 64% of the original size.
Potential reduce by 19.7 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 329 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.
Potential reduce by 441 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. Kontiki2.com needs all CSS files to be minified and compressed as it can save up to 441 B or 21% of the original size.
Number of requests can be reduced by 23 (40%)
58
35
The browser has sent 58 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 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
kontiki2.com
184 ms
style.css
76 ms
jquery.min.js
8 ms
jquery.vscroll.js
150 ms
js
38 ms
track.js
158 ms
css
20 ms
css
40 ms
css
40 ms
widgets.js
51 ms
newbg.jpg
218 ms
kontiki-s.png
77 ms
plot.jpg
384 ms
IMG_6690-s.JPG
147 ms
IMG_6788-s.JPG
148 ms
IMG_6830-s.JPG
151 ms
IMG_6840-s.JPG
153 ms
IMG_6851-s.JPG
219 ms
IMG_6854-s.JPG
220 ms
IMG_6826-s.JPG
226 ms
IMG_6894-s.JPG
227 ms
IMG_6897-s.JPG
291 ms
IMG_6881-s.JPG
290 ms
IMG_6936-s.JPG
292 ms
IMG_6927-s.JPG
301 ms
12-Torgeir-279A9418-s.jpg
303 ms
12-Torgeir-FILE0078-1-s.jpg
383 ms
12-Tupak-279A9269-1-s.jpg
385 ms
12-Tupak-279A9272-1-s.jpg
384 ms
12-Tupak-279A9289-s.jpg
386 ms
12-Tupak-279A9308-s.jpg
387 ms
1-s.jpg
437 ms
3-s.jpg
436 ms
2-s.jpg
437 ms
thi.png
440 ms
3A-logo-350.png
519 ms
logo-opera.png
452 ms
logo-kongsberg.png
573 ms
logo-sima-350.png
508 ms
logo-mgp-200.jpg
575 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
16 ms
Yq6R-LCAWCX3-6Ky7FAFrOF6lw.ttf
17 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
18 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
33 ms
settings
73 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
4 ms
kontiki2
118 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
4 ms
runtime-b1c52fd0a13ead5fcf6b.js
25 ms
modules-96ebc7ac3ad66d681a3d.js
30 ms
main-babd9234dc048fb47339.js
28 ms
_app-a9c9f1a99e4414675fb1.js
28 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
29 ms
_buildManifest.js
64 ms
_ssgManifest.js
64 ms
8526.0c32a8f0cfc5749221a3.js
14 ms
1755.07a49c40b12af4f75780.js
15 ms
8283.f3e5048cca7cef5eed7f.js
5 ms
3077.44bfeb00af01bc4020f6.js
10 ms
1362.42d432e02f7980bca032.js
9 ms
4956.c4e51ef593974b9db0bb.js
22 ms
5893.d500bd2a89ded806aa73.js
6 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
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: