Tools & Wizards About Us
kayak.no screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

kayak.no

Søk etter billige flybilletter, hoteller og leiebiler | KAYAK

Page Load Speed

1.1 sec in total

First Response

16 ms

Resources Loaded

825 ms

Page Rendered

272 ms

kayak.no screenshot

About Website

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.no

Key Findings

We 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.

Performance Metrics

kayak.no performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value3,790 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

kayak.no

16 ms

www.kayak.no

553 ms

combined.css

19 ms

combined.css

26 ms

polyfillio.js

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 Optimization Overview & Recommendations

Page size can be reduced by 564.4 kB (66%)

Content Size

853.5 kB

After Optimization

289.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Kayak.no main page is 853.5 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.

HTML Optimization

-82%

Potential reduce by 401.1 kB

  • Original 492.1 kB
  • After minification 492.1 kB
  • After compression 90.9 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.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 169 B
  • After minification 169 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.

JavaScript Optimization

-45%

Potential reduce by 163.2 kB

  • Original 361.3 kB
  • After minification 361.2 kB
  • After compression 198.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 163.2 kB or 45% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

kayak.no

kayak.no

16 ms

www.kayak.no

www.kayak.no

553 ms

combined.css

combined.css

19 ms

combined.css

combined.css

26 ms

polyfillio.js

polyfillio.js

120 ms

combined.js

combined.js

173 ms

combined.js

combined.js

198 ms

context

context

118 ms

svg

svg

78 ms

Accessibility Review

kayak.no accessibility score

62

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kayak.no best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kayak.no SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    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.

Social Sharing Optimization

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: