1.1 sec in total
16 ms
825 ms
272 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 16 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.
kayak.no performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value11.4 s
0/100
25%
Value7.7 s
24/100
10%
Value3,790 ms
1/100
30%
Value0.009
100/100
15%
Value12.9 s
13/100
10%
16 ms
553 ms
19 ms
26 ms
120 ms
Our browser made a total of 9 requests to load all elements on the main page. We found that 44% of them (4 requests) were addressed to the original Kayak.no, 56% (5 requests) were made to Content.r9cdn.net. The less responsive or slowest element that took the longest time to load (553 ms) belongs to the original domain Kayak.no.
Page size can be reduced by 564.4 kB (66%)
852.9 kB
288.5 kB
In fact, the total size of Kayak.no main page is 852.9 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. HTML takes 492.1 kB which makes up the majority of the site volume.
Potential reduce by 401.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 401.1 kB or 82% 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 163.2 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 163.2 kB or 45% of the original size.
We found no issues to fix!
7
7
The browser has sent 7 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KAYAK. According to our analytics all requests are already optimized.
kayak.no
16 ms
www.kayak.no
553 ms
combined.css
19 ms
combined.css
26 ms
polyfillio.js
120 ms
combined.js
173 ms
combined.js
198 ms
context
118 ms
svg
78 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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
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
NO
NO
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 it matches the claimed language. 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: