2.4 sec in total
153 ms
2 sec
274 ms
Click here to check amazing KAYAK content for Norway. Otherwise, check out these important facts you probably never knew about kayak.no
Bruk reisesøkemotoren KAYAK til å søke og sammenligne priser for flyreiser, hotell, leiebiler og pakkereiser. Finn de beste prisene for turen din her.
Visit kayak.noWe analyzed Kayak.no page load time and found that the first response time was 153 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
kayak.no performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.0 s
0/100
25%
Value8.0 s
21/100
10%
Value4,550 ms
0/100
30%
Value0.03
100/100
15%
Value12.7 s
13/100
10%
153 ms
162 ms
166 ms
168 ms
219 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Kayak.no, 22% (20 requests) were made to A3.r9cdn.net and 16% (15 requests) were made to A2.r9cdn.net. The less responsive or slowest element that took the longest time to load (387 ms) relates to the external source D2s3bizpgknsvz.cloudfront.net.
Page size can be reduced by 371.3 kB (62%)
596.0 kB
224.8 kB
In fact, the total size of Kayak.no main page is 596.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. 55% of websites need less resources to load. Javascripts take 411.3 kB which makes up the majority of the site volume.
Potential reduce by 148.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 148.6 kB or 80% of the original size.
Potential reduce by 0 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. KAYAK images are well optimized though.
Potential reduce by 222.7 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 222.7 kB or 54% of the original size.
Number of requests can be reduced by 51 (58%)
88
37
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KAYAK. 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 7 to 1 for CSS and as a result speed up the page load time.
www.kayak.no
153 ms
horizon.less
162 ms
legacy.less
166 ms
keel.less
168 ms
common.less
219 ms
hotels.less
192 ms
seo.less
165 ms
base.less
171 ms
hwt-logo-for-white.png
155 ms
globalalien.js
264 ms
horizon.js
174 ms
legacy.js
264 ms
common.js
263 ms
hotels.js
162 ms
base.js
152 ms
seo.js
151 ms
js
337 ms
a-small-flag-sprite.png
109 ms
kayak-logo.png
104 ms
19x23-offset-30-menu-icon-header.png
106 ms
calendar-close-x.png
107 ms
downtip-white.png
109 ms
21x24-21-offset-datepicker-icons.png
104 ms
15x15-15-offset-x.png
104 ms
gpt.js
122 ms
d6a12f84-city-29309-547c81b4.jpg
110 ms
bd933a9c-city-28501-1525fa5d266.jpg
108 ms
857b1b61-city-32760-554a6f99.jpg
104 ms
async-ads.js
143 ms
gtm.js
209 ms
NavMenuContent
107 ms
c3b36d21-City-16078-53d0006d.jpg
32 ms
543b7731-city-9739-146cf1b2972.jpg
31 ms
704be28f-city-24840-5506d98e.jpg
33 ms
0efcd7ef-city-9880-55409779.jpg
81 ms
8533.jpg
80 ms
10x10-offset-20-close-x-sprite.png
78 ms
f18625cf-city-22567-15254a656c3.jpg
30 ms
ee4b0ac7-city-15830-1525fbbd3e1.jpg
36 ms
a2a99d53-city-14057-54e213d9.jpg
31 ms
d174a19f-city-17898-146cf169e9c.jpg
30 ms
282d16f1-city-9109-556de5b4.jpg
34 ms
4035ecda-city-1669-54fd74eb.jpg
79 ms
9c8ac24c-city-3472-1525fdf36ef.jpg
78 ms
45x45-45-offset-lightbox-nav.png
78 ms
analytics.js
153 ms
pubads_impl_81.js
100 ms
ads
267 ms
container.html
178 ms
platform.js
246 ms
sdk.js
188 ms
ecommerce.js
81 ms
conversion_async.js
289 ms
bat.js
308 ms
fbevents.js
207 ms
379 ms
d2s3bizpgknsvz.cloudfront.net
387 ms
ytc.js
270 ms
bk-coretag.js
282 ms
activityi;src=5142311;type=visit0;cat=front0;u9=NOK;u12=rJU1KewSEVZEdrA0NjC-_sthi5U;u14=frontdoor;u15=main;u16=no_NO;u19=false;ord=1126631649025;~oref=https%3A%2F%2Fwww.kayak.no%2F
356 ms
collect
122 ms
collect
246 ms
collect
185 ms
collect
213 ms
collect
186 ms
collect
212 ms
collect
212 ms
collect
212 ms
collect
234 ms
297 ms
xd_arbiter.php
231 ms
1
190 ms
ads
208 ms
cb=gapi.loaded_0
60 ms
osd.js
168 ms
249 ms
285 ms
199 ms
ga-audiences
146 ms
iframe
119 ms
price-alert_ad_v1.jpg
50 ms
1
97 ms
ads
152 ms
19 ms
js
33 ms
1233565733-idpiframe.js
104 ms
explore_ad_v1.jpg
57 ms
i.js
202 ms
1
47 ms
iframerpc
29 ms
my-trips_ad_v1.jpg
10 ms
kayak.no accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role] values are not valid
[aria-*] attributes are not valid or misspelled
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
kayak.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
kayak.no SEO score
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
NO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kayak.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian 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 Kayak.no 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.
kayak.no
Open Graph data is detected on the main page of KAYAK. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: