kiwi.com

kiwi.com is SSL secured

Free website and domain report on kiwi.com

Last Updated: 23rd September, 2020 Update Now
Overview

Snoop Summary for kiwi.com

This is a free and comprehensive report about kiwi.com. Kiwi.com is hosted in United States on a server with an IP address of 13.32.179.37, where USD is the local currency and the local language is English. Our records indicate that kiwi.com is owned/operated by KIWI.COM S.R.O.. Kiwi.com is expected to earn an estimated $463 USD per day from advertising revenue. The sale of kiwi.com would possibly be worth $338,061 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Kiwi.com is insanely popular with an estimated 109,505 daily unique visitors. This report was last updated 23rd September, 2020.

About kiwi.com

Site Preview: kiwi.com kiwi.com
Title:
Description:
Keywords and Tags: travel
Related Terms: kiwi
Fav Icon:
Age: Over 29 years old
Domain Created: 23rd November, 1994
Domain Updated: 26th September, 2017
Domain Expires: 8th January, 2026
Review

Snoop Score

3/5 (Great!)

Valuation

$338,061 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 11,923
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 109,505
Monthly Visitors: 3,332,974
Yearly Visitors: 39,969,169
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $463 USD
Monthly Revenue: $14,095 USD
Yearly Revenue: $169,025 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: kiwi.com 8
Domain Name: kiwi 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.86 seconds
Load Time Comparison: Faster than 13% of sites

PageSpeed Insights

Avg. (All Categories) 80
Performance 90
Accessibility 67
Best Practices 93
SEO 100
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.kiwi.com/us/
Updated: 23rd September, 2020

2.15 seconds
First Contentful Paint (FCP)
24%
63%
13%

0.02 seconds
First Input Delay (FID)
85%
7%
8%

Simulate loading on desktop
90

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for kiwi.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive kiwi.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://kiwi.com/
0
68.476000102237
446
0
301
text/html
https://kiwi.com/
69.009999977425
173.16400003619
424
0
301
https://www.kiwi.com/
173.76999999397
400.62800003216
1027
0
302
text/html
https://www.kiwi.com/us/
401.17700002156
2769.8560000863
18046
102853
200
text/html
Document
https://www.kiwi.com/images/hero/hero-largeDesktop.webp?v=3
2796.2529999204
2927.6789999567
63361
62182
200
application/octet-stream
Image
https://www.kiwi.com/images/hero/icon-refunds.svg
2796.5009999461
2907.865999965
1978
1768
200
image/svg+xml
Image
https://www.kiwi.com/images/hero/icon-self-service.svg
2802.2320000455
2908.9530000929
2541
3285
200
image/svg+xml
Image
https://www.kiwi.com/images/hero/icon-information.svg
2802.4410000071
2863.2600000128
3852
6235
200
image/svg+xml
Image
https://www.kiwi.com/images/illust/AppQRCode.png
2802.6360000949
2834.9029999226
30796
29518
200
image/webp
Image
https://www.kiwi.com/images/qr/download_app.png
2803.0340000987
2936.1219999846
1831
554
200
image/webp
Image
https://skypicker-api.infinario.com/js/infinario.min.js
2803.2150000799
3064.0040000435
87613
283010
200
application/javascript
Script
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
2812.7359999344
2925.978000043
36071
34568
200
application/octet-stream
Font
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
2825.3830000758
2903.578999918
31434
29924
200
application/octet-stream
Font
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
2830.4280000739
2963.2620001212
36588
35084
200
application/octet-stream
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2805.105
10.381
2818.659
5.98
2831.461
31.103
2862.588
68.747
2933.472
13.728
2952.903
12.149
2979.106
17.636
3004.027
41.493
3123.524
64.78
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Kiwi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 16 KiB
Images can slow down the page's load time. Kiwi.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.kiwi.com/images/illust/AppQRCode.png
29518
16399
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Kiwi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Kiwi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Kiwi.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Kiwi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Kiwi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
17217

Diagnostics

Avoids enormous network payloads — Total size was 309 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
87613
https://www.kiwi.com/images/hero/hero-largeDesktop.webp?v=3
63361
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
36588
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
36071
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
31434
https://www.kiwi.com/images/illust/AppQRCode.png
30796
https://www.kiwi.com/us/
18046
https://www.kiwi.com/images/hero/icon-information.svg
3852
https://www.kiwi.com/images/hero/icon-self-service.svg
2541
https://www.kiwi.com/images/hero/icon-refunds.svg
1978
Avoids an excessive DOM size — 248 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
248
Maximum DOM Depth
22
Maximum Child Elements
17
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Kiwi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.kiwi.com/us/
266.355
5.158
1.631
https://skypicker-api.infinario.com/js/infinario.min.js
64.78
36.967
11.078
Unattributable
58.27
1.516
0.227
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
114.501
Style & Layout
113.185
Rendering
92.518
Script Evaluation
43.641
Script Parsing & Compilation
12.936
Parse HTML & CSS
12.624
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 14 requests • 309 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
14
316008
Image
6
104359
Font
3
104093
Script
1
87613
Document
1
18046
Other
3
1897
Stylesheet
0
0
Media
0
0
Third-party
1
87613
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00052196237291202
0.00022564283955595
0.00016596600088927
0.00014529607162474
0.00013715407917178
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://skypicker-api.infinario.com/js/infinario.min.js
1150
65
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.2 s
The time taken for the page contents to be visibly populated.

Other

First Meaningful Paint — 1.0 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused JavaScript — Potential savings of 63 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
87613
64009
Avoid multiple page redirects — Potential savings of 570 ms
Redirects can cause additional delays before the page can begin loading. Kiwi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://kiwi.com/
190
https://kiwi.com/
150
https://www.kiwi.com/
230
https://www.kiwi.com/us/
0

Opportunities

Reduce initial server response time — Root document took 2,370 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.kiwi.com/us/
2369.677

Diagnostics

Serve static assets with an efficient cache policy — 10 resources found
Kiwi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
300000
87613
https://www.kiwi.com/images/hero/hero-largeDesktop.webp?v=3
3600000
63361
https://www.kiwi.com/images/illust/AppQRCode.png
3600000
30796
https://www.kiwi.com/images/hero/icon-information.svg
3600000
3852
https://www.kiwi.com/images/hero/icon-self-service.svg
3600000
2541
https://www.kiwi.com/images/hero/icon-refunds.svg
3600000
1978
https://www.kiwi.com/images/qr/download_app.png
3600000
1831
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
2628000000
36588
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
2628000000
36071
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
2628000000
31434
67

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of kiwi.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Kiwi.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Kiwi.com may provide relevant information that dialogue cannot, by using audio descriptions.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
93

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that kiwi.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
core-js
3.6.4: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://kiwi.com/

Audits

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for kiwi.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of kiwi.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
48

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of kiwi.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of kiwi.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://kiwi.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 76
Performance 73
Accessibility 71
Best Practices 86
SEO 100
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.kiwi.com/us/
Updated: 23rd September, 2020

2.74 seconds
First Contentful Paint (FCP)
13%
67%
20%

0.12 seconds
First Input Delay (FID)
74%
7%
19%

Simulate loading on mobile
73

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for kiwi.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 130 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive kiwi.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://kiwi.com/
0
29.720999998972
431
0
301
text/html
https://kiwi.com/
30.449999962002
83.57299992349
424
0
301
https://www.kiwi.com/
84.24599992577
222.74899994954
1020
0
302
text/html
https://www.kiwi.com/us/
223.3530000085
822.90999998804
29551
255469
200
text/html
Document
https://www.kiwi.com/images/hero/hero-smallMobile@2x.webp?v=3
880.64799993299
928.51799994241
96048
94876
200
application/octet-stream
Image
https://www.kiwi.com/images/hero/icon-refunds.svg
880.97299996298
934.93899994064
1978
1768
200
image/svg+xml
Image
https://www.kiwi.com/images/hero/icon-self-service.svg
890.6989999814
972.46199997608
2541
3285
200
image/svg+xml
Image
https://www.kiwi.com/images/hero/icon-information.svg
890.88799990714
939.01699990965
3852
6235
200
image/svg+xml
Image
https://images.kiwi.com/photos/30x30/los-angeles_ca_us.webp
891.36399992276
929.13299996872
1165
694
200
image/webp
Image
https://images.kiwi.com/photos/30x30/san-francisco_ca_us.webp
891.5149999084
940.36299991421
903
432
200
image/webp
Image
https://images.kiwi.com/photos/30x30/barcelona_es.webp
892.13900000323
923.6319999909
967
496
200
image/webp
Image
https://images.kiwi.com/photos/30x30/cancun_mx.webp
892.35400001053
922.96999995597
897
424
200
image/webp
Image
https://images.kiwi.com/photos/30x30/paris_fr.webp
895.31299995724
934.18199999724
875
404
200
image/webp
Image
https://images.kiwi.com/photos/30x30/berlin_de.webp
895.62500000466
932.78899998404
1047
576
200
image/webp
Image
https://images.kiwi.com/photos/30x30/fort-lauderdale_fl_us.webp
895.75299993157
934.57799998578
901
430
200
image/webp
Image
https://images.kiwi.com/photos/30x30/frankfurt_de.webp
895.90000000317
929.97599998489
1001
530
200
image/webp
Image
https://images.kiwi.com/photos/30x30/miami_fl_us.webp
896.4439999545
964.94699991308
1051
580
200
image/webp
Image
https://images.kiwi.com/photos/30x30/las-vegas_nv_us.webp
898.7049999414
930.384999956
1021
550
200
image/webp
Image
https://images.kiwi.com/photos/30x30/denver_co_us.webp
898.86899990961
933.75500000548
887
416
200
image/webp
Image
https://images.kiwi.com/photos/30x30/orlando_fl_us.webp
899.01399996597
966.24400001019
1021
550
200
image/webp
Image
https://images.kiwi.com/photos/30x30/london_gb.webp
899.17699992657
951.04799990077
1087
614
200
image/webp
Image
https://images.kiwi.com/photos/30x30/san-juan_pr_pr.webp
899.3349999655
929.41699991934
968
498
200
image/webp
Image
https://skypicker-api.infinario.com/js/infinario.min.js
899.51799996197
1268.1759999832
87100
283010
200
application/javascript
Script
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
929.83899998944
1005.4029999301
36071
34568
200
application/octet-stream
Font
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
969.53999996185
1015.5669999076
36588
35084
200
application/octet-stream
Font
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
971.24899993651
1030.5149999913
31434
29924
200
application/octet-stream
Font
https://images.kiwi.com/photos/30x30/mexico-city_mx.webp
1034.5049999887
1050.7089999737
847
376
200
image/webp
Image
https://images.kiwi.com/photos/30x30/atlanta_ga_us.webp
1034.835999948
1050.2589999232
837
366
200
image/webp
Image
https://images.kiwi.com/photos/30x30/houston_tx_us.webp
1035.085999989
1053.2739999471
965
494
200
image/webp
Image
https://images.kiwi.com/photos/30x30/seattle_wa_us.webp
1035.3119999636
1051.1519999709
1136
666
200
image/webp
Image
https://images.kiwi.com/photos/30x30/rome_it.webp
1035.5749999871
1051.8429999938
1017
546
200
image/webp
Image
https://images.kiwi.com/photos/30x30/guadalajara_mx.webp
1035.918999929
1097.468999913
1035
564
200
image/webp
Image
https://images.kiwi.com/photos/30x30/warsaw_pl.webp
1036.4249999402
1052.493999945
947
476
200
image/webp
Image
https://images.kiwi.com/photos/30x30/dallas_tx_us.webp
1036.6719999583
1053.8299999898
979
508
200
image/webp
Image
https://images.kiwi.com/photos/30x30/vienna_at.webp
1036.8719999678
1054.2499999283
1003
530
200
image/webp
Image
https://images.kiwi.com/photos/30x30/boston_ma_us.webp
1037.1569999261
1055.963999941
845
374
200
image/webp
Image
https://images.kiwi.com/photos/30x30/copenhagen_dk.webp
1037.4559999909
1098.5609999625
1147
674
200
image/webp
Image
https://images.kiwi.com/photos/30x30/phoenix_az_us.webp
1037.8879999043
1055.5649999296
929
458
200
image/webp
Image
https://images.kiwi.com/photos/30x30/stockholm_se.webp
1038.0829999922
1097.9999999981
1061
590
200
image/webp
Image
https://images.kiwi.com/photos/30x30/tampa_fl_us.webp
1038.2329999702
1057.1739999577
1153
682
200
image/webp
Image
https://images.kiwi.com/photos/30x30/toronto_on_ca.webp
1039.2780000111
1098.2969999313
951
480
200
image/webp
Image
https://images.kiwi.com/photos/30x30/lima_pe.webp
1040.5610000016
1075.8039999055
947
476
200
image/webp
Image
https://www.kiwi.com/images/map/map.svg
1141.9589999132
1179.8459999263
14573
33131
200
image/svg+xml
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
896.585
18.972
933.625
9.102
942.784
6.602
953.123
14.546
967.705
132.733
1100.566
7.199
1124.697
8.252
1132.981
17.88
1150.916
5.626
1156.568
5.902
1163.291
33.703
1197.425
28.661
1239.451
26.601
1267.289
6.215
1338.248
8.609
1366.92
77.232
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Kiwi.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Kiwi.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Kiwi.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Kiwi.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Kiwi.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Kiwi.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Kiwi.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Diagnostics

Avoids enormous network payloads — Total size was 363 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.kiwi.com/images/hero/hero-smallMobile@2x.webp?v=3
96048
https://skypicker-api.infinario.com/js/infinario.min.js
87100
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
36588
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
36071
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
31434
https://www.kiwi.com/us/
29551
https://www.kiwi.com/images/map/map.svg
14573
https://www.kiwi.com/images/hero/icon-information.svg
3852
https://www.kiwi.com/images/hero/icon-self-service.svg
2541
https://www.kiwi.com/images/hero/icon-refunds.svg
1978
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Kiwi.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.kiwi.com/us/
1069.22
30.868
31.54
Unattributable
461.268
5.508
0.596
https://skypicker-api.infinario.com/js/infinario.min.js
308.928
262.5
25.832
Minimizes main-thread work — 1.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
745.24
Other
518.416
Script Evaluation
298.876
Parse HTML & CSS
118.896
Rendering
100.02
Script Parsing & Compilation
57.968
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 43 requests • 363 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
43
371201
Image
35
148582
Font
3
104093
Script
1
87100
Document
1
29551
Other
3
1875
Stylesheet
0
0
Media
0
0
Third-party
1
87100
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
div
0.00040428797128812
0.00034280701308755
div
0.00033294303517845
0.00018853034489965
div
3.2328174174694E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 8 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://skypicker-api.infinario.com/js/infinario.min.js
5460
309
https://www.kiwi.com/us/
2354
265
https://www.kiwi.com/us/
2758
115
https://www.kiwi.com/us/
2220
76
Unattributable
2619
72
https://www.kiwi.com/us/
2691
67
https://www.kiwi.com/us/
2296
58
https://www.kiwi.com/us/
634
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 5.1 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.5 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.5 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused JavaScript — Potential savings of 62 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
87100
63634
Avoid serving legacy JavaScript to modern browsers — Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
17116

Diagnostics

Avoid an excessive DOM size — 1,042 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1,042
Maximum DOM Depth
21
Maximum Child Elements
30

Metrics

Largest Contentful Paint — 4.5 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 310 ms
Users could experience a delay when interacting with the page.
First Contentful Paint (3G) — 7050 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Reduce initial server response time — Root document took 600 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.kiwi.com/us/
600.554
Avoid multiple page redirects — Potential savings of 1,890 ms
Redirects can cause additional delays before the page can begin loading. Kiwi.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://kiwi.com/
630
https://kiwi.com/
480
https://www.kiwi.com/
780
https://www.kiwi.com/us/
0

Diagnostics

Serve static assets with an efficient cache policy — 39 resources found
Kiwi.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://skypicker-api.infinario.com/js/infinario.min.js
300000
87100
https://www.kiwi.com/images/hero/hero-smallMobile@2x.webp?v=3
3600000
96048
https://www.kiwi.com/images/map/map.svg
3600000
14573
https://www.kiwi.com/images/hero/icon-information.svg
3600000
3852
https://www.kiwi.com/images/hero/icon-self-service.svg
3600000
2541
https://www.kiwi.com/images/hero/icon-refunds.svg
3600000
1978
https://images.kiwi.com/photos/30x30/los-angeles_ca_us.webp
86400000
1165
https://images.kiwi.com/photos/30x30/tampa_fl_us.webp
86400000
1153
https://images.kiwi.com/photos/30x30/seattle_wa_us.webp
86400000
1136
https://images.kiwi.com/photos/30x30/stockholm_se.webp
86400000
1061
https://images.kiwi.com/photos/30x30/miami_fl_us.webp
86400000
1051
https://images.kiwi.com/photos/30x30/berlin_de.webp
86400000
1047
https://images.kiwi.com/photos/30x30/guadalajara_mx.webp
86400000
1035
https://images.kiwi.com/photos/30x30/las-vegas_nv_us.webp
86400000
1021
https://images.kiwi.com/photos/30x30/orlando_fl_us.webp
86400000
1021
https://images.kiwi.com/photos/30x30/rome_it.webp
86400000
1017
https://images.kiwi.com/photos/30x30/frankfurt_de.webp
86400000
1001
https://images.kiwi.com/photos/30x30/dallas_tx_us.webp
86400000
979
https://images.kiwi.com/photos/30x30/san-juan_pr_pr.webp
86400000
968
https://images.kiwi.com/photos/30x30/barcelona_es.webp
86400000
967
https://images.kiwi.com/photos/30x30/houston_tx_us.webp
86400000
965
https://images.kiwi.com/photos/30x30/toronto_on_ca.webp
86400000
951
https://images.kiwi.com/photos/30x30/lima_pe.webp
86400000
947
https://images.kiwi.com/photos/30x30/warsaw_pl.webp
86400000
947
https://images.kiwi.com/photos/30x30/phoenix_az_us.webp
86400000
929
https://images.kiwi.com/photos/30x30/san-francisco_ca_us.webp
86400000
903
https://images.kiwi.com/photos/30x30/fort-lauderdale_fl_us.webp
86400000
901
https://images.kiwi.com/photos/30x30/denver_co_us.webp
86400000
887
https://images.kiwi.com/photos/30x30/paris_fr.webp
86400000
875
https://images.kiwi.com/photos/30x30/mexico-city_mx.webp
86400000
847
https://images.kiwi.com/photos/30x30/boston_ma_us.webp
86400000
845
https://images.kiwi.com/photos/30x30/atlanta_ga_us.webp
86400000
837
https://images.kiwi.com/photos/30x30/copenhagen_dk.webp
604800000
1147
https://images.kiwi.com/photos/30x30/london_gb.webp
604800000
1087
https://images.kiwi.com/photos/30x30/vienna_at.webp
604800000
1003
https://images.kiwi.com/photos/30x30/cancun_mx.webp
604800000
897
https://static-data.kiwi.com/fonts/circular-pro/bold.woff2
2628000000
36588
https://static-data.kiwi.com/fonts/circular-pro/medium.woff2
2628000000
36071
https://static-data.kiwi.com/fonts/circular-pro/book.woff2
2628000000
31434
71

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of kiwi.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Kiwi.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Kiwi.com may provide relevant information that dialogue cannot, by using audio descriptions.

ARIA

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
86

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that kiwi.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
core-js
3.6.4: pure
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://kiwi.com/

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://images.kiwi.com/photos/30x30/los-angeles_ca_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/san-francisco_ca_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/barcelona_es.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/cancun_mx.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/paris_fr.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/berlin_de.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/fort-lauderdale_fl_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/frankfurt_de.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/miami_fl_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/las-vegas_nv_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/denver_co_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/orlando_fl_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/london_gb.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/san-juan_pr_pr.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/mexico-city_mx.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/atlanta_ga_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/houston_tx_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/seattle_wa_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/rome_it.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/guadalajara_mx.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/warsaw_pl.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/dallas_tx_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/vienna_at.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/boston_ma_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/copenhagen_dk.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/phoenix_az_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/stockholm_se.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/tampa_fl_us.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/toronto_on_ca.webp
328 x 238 (1.38)
30 x 30 (1.00)
https://images.kiwi.com/photos/30x30/lima_pe.webp
328 x 238 (1.38)
30 x 30 (1.00)

Audits

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for kiwi.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of kiwi.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of kiwi.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of kiwi.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://kiwi.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 13.32.179.37
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon.com, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization: KIWI.COM S.R.O.
Country: CZ
City:
State: JIHOMORAVSKY KRAJ
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy Online Services Cayman Islands Ltd. 104.20.224.74
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3.5/5 (3 reviews)
WOT Trustworthiness: 70/100
WOT Child Safety: 73/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.kiwi.com
Issued By: Amazon
Valid From: 18th March, 2020
Valid To: 18th April, 2021
Subject: CN = *.kiwi.com
Hash: fffad5ab
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 13788767996546381155549252828767742149
Serial Number (Hex): 0A5F9EC00EE6D1DB7871B402164068C5
Valid From: 18th March, 2024
Valid To: 18th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.2
Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : A4:B9:09:90:B4:18:58:14:87:BB:13:A2:CC:67:70:0A:
3C:35:98:04:F9:1B:DF:B8:E3:77:CD:0E:C8:0D:DC:10
Timestamp : Mar 18 08:27:23.666 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:58:12:A2:26:13:03:78:8E:71:14:E8:B5:
84:04:FF:2F:BD:BF:C0:8E:BE:1E:B7:BB:70:9C:87:88:
D2:DE:16:DB:02:21:00:E9:1D:8D:41:69:6A:5C:87:4A:
57:39:CC:06:A2:91:19:3D:85:AF:AD:E8:F6:29:88:36:
25:AB:5E:CB:B2:1B:0F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Mar 18 08:27:23.733 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C0:A5:18:51:AB:48:FD:6F:32:18:C5:
24:43:4E:1B:B4:A1:B1:33:86:54:B6:EE:AF:E4:E2:E3:
7D:30:A2:3F:81:02:21:00:B0:2F:5D:0E:EC:A0:33:D9:
40:97:A2:C8:3E:AE:E4:F7:4C:07:7F:E5:EB:75:B8:9A:
2E:9B:6B:2C:CF:FA:ED:0C
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:kiwi.com
DNS:*.kiwi.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
kiwi.com. 13.32.179.37 IN 59
kiwi.com. 13.32.179.24 IN 59
kiwi.com. 13.32.179.31 IN 59
kiwi.com. 13.32.179.33 IN 59

NS Records

Host Nameserver Class TTL
kiwi.com. ns-1440.awsdns-52.org. IN 21599
kiwi.com. ns-1968.awsdns-54.co.uk. IN 21599
kiwi.com. ns-534.awsdns-02.net. IN 21599
kiwi.com. ns-71.awsdns-08.com. IN 21599

MX Records

Priority Host Server Class TTL
1 kiwi.com. aspmx.l.google.com. IN 299
10 kiwi.com. alt3.aspmx.l.google.com. IN 299
10 kiwi.com. alt4.aspmx.l.google.com. IN 299
5 kiwi.com. alt1.aspmx.l.google.com. IN 299
5 kiwi.com. alt2.aspmx.l.google.com. IN 299

SOA Records

Domain Name Primary NS Responsible Email TTL
kiwi.com. ns-71.awsdns-08.com. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
kiwi.com. MS=ms94610270 IN 299
kiwi.com. ZOOM_verify_u48SbTWsRz2CiE52wfyhkA IN 299
kiwi.com. ahrefs-site-verification_3e75cb96d8ce9a8a4a91ee88ecee8dd0aeb0b0f97ee552139e2481e8fc4bd1be IN 299
kiwi.com. atlassian-domain-verification=UEW7mLvm33hEJAoaf1cGHkgR9eEVRgp2KLaQeb136/BCueRkvkat56/ghqC1KpwK IN 299
kiwi.com. docusign=18596426-6b5b-4624-8d08-ec81dc1fe2fb IN 299
kiwi.com. facebook-domain-verification=pk4sjaa3xnhejgwe755uyfue1fw2ms IN 299
kiwi.com. google-site-verification=5p5zmxyEHtXX7XyJnkoM7dfuSCHUHVlhmUO-Y8H47lo IN 299
kiwi.com. google-site-verification=8Bt_wzakl1ZxaWs16pELWmHG0C3hO90RNJQvPHwbqx4 IN 299
kiwi.com. google-site-verification=8WuGnhoXGME8b34bkWUqln7IPg9ucU3JpeZFJvi4WVg IN 299
kiwi.com. google-site-verification=IzSR5QFnaUsLb5g84hR30imdyNFyg-FI9sojfYOzeZk IN 299
kiwi.com. google-site-verification=KndsZ-yTeIXjJ-MS5dATh_xBrs3-qNB2fJH0iipYh74 IN 299
kiwi.com. google-site-verification=L6yAc_1czJLHMuZTR2hhQJifVijBmkFYgzM1rJQOpho IN 299
kiwi.com. google-site-verification=QncoGFtxHaTKickQSpdNoBrOnMq5f9WStFxDsCZefoI IN 299
kiwi.com. google-site-verification=hUd_2qpSj5oVrqYCdD7GGjsYXsGx905qPdZLTYlS6zc IN 299
kiwi.com. google-site-verification=jCRNxVC4RxIHftCEoH3W7TFDkJ3a3ULIZLSMGumUkho IN 299
kiwi.com. google-site-verification=kPCx5UW1O7NENsrYJEbqwOjmDi7PvUaE3AUe2jslEuY IN 299
kiwi.com. google-site-verification=x1HSN4n5--mz476P7ugpY2xxgPELOleGzfubYpoI6lk IN 299
kiwi.com. northpass-domain-verification=a67d03b1dcc2e0ea289c709f329549e3 IN 299
kiwi.com. v=spf1 IN 299

HTTP Response Headers

Whois Lookup

Created: 23rd November, 1994
Changed: 26th September, 2017
Expires: 8th January, 2026
Registrar: UNIREGISTRAR CORP
Status: clientTransferProhibited
Nameservers: ns-1440.awsdns-52.org
ns-1968.awsdns-54.co.uk
ns-534.awsdns-02.net
ns-71.awsdns-08.com
Owner Organization: KIWI.COM S.R.O.
Owner State: JIHOMORAVSKY KRAJ
Owner Country: CZ
Owner Email: https://uniregistry.com/whois/contact/kiwi.com?landerid=whois
Full Whois:


Domain Name: KIWI.COM
Registry Domain ID: 902033_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.uniregistrar.net
Registrar URL: http://uniregistry.com
Updated Date: 2017-09-26-T11:13:02Z
Creation Date: 1994-11-23-T05:00:00Z
Registrar Registration Expiration Date: 2026-01-08-T16:13:53Z
Registrar: UNIREGISTRAR CORP
Registrar IANA ID: 1659
Registrar Abuse Contact Email: abuse@uniregistry.com
Registrar Abuse Contact Phone: +1.4426008800
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Registrant Organization: KIWI.COM S.R.O.
Registrant State/Province: JIHOMORAVSKY KRAJ
Registrant Country: CZ
Registrant Email: https://uniregistry.com/whois/contact/kiwi.com?landerid=whois
Name Server: ns-534.awsdns-02.net
Name Server: ns-1440.awsdns-52.org
Name Server: ns-71.awsdns-08.com
Name Server: ns-1968.awsdns-54.co.uk
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/

>>> Last update of WHOIS database: 2020-09-23T18:20:08.076Z <<<

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of high volume automated processes. Access to
the Whois database is provided solely to obtain information about or
related to a domain name registration record, and no warranty is made
as to its accuracy or fitness for any particular purpose.. You agree
that you may use this Data only for lawful purposes and that under no
circumstances will you use this data to allow, enable, or otherwise
support the transmission of mass unsolicited, commercial advertising
or solicitations via e-mail, telephone, or facsimile. Compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of Uniregistrar,
Uniregistry Corp. or Uniregistry Ltd. (CA). Uniregistrar reserves the
right to restrict your access to the Whois database in its sole
discretion to ensure operational stability and police abuse.






Nameservers

Name IP Address
ns-1440.awsdns-52.org 205.251.197.160
ns-1968.awsdns-54.co.uk 205.251.199.176
ns-534.awsdns-02.net 205.251.194.22
ns-71.awsdns-08.com 205.251.192.71
Related

Subdomains

Domain Subdomain
ninja

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
$316 USD 1/5
$757 USD 1/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address