VAYAMA.COM Vayama™ Official Site - Cheap International Flights


vayama.com website information.

vayama.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

No name server records were found.

According to Alexa traffic rank the highest website vayama.com position was 11269 (in the world). The lowest Alexa rank position was 700867. Current position of vayama.com in Alexa rank database is below 1 million.

Website vayama.com Desktop speed measurement score (68/100) is better than the results of 47.59% of other sites shows that the page desktop performance can be improved.

vayama.com Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of vayama.com (39/100) is better than the results of 17.83% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Oct-18-2021 N/AN/A
Oct-17-2021 N/AN/A
Oct-16-2021 285,720N/A
Oct-15-2021 N/AN/A
Oct-14-2021 93,423N/A
Oct-13-2021 N/AN/A
Oct-12-2021 N/AN/A

Advertisement

vayama.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



vayama.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: VAYAMA.COM
Registry Domain ID: 162365447_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2021-01-13T12:20:38Z
Creation Date: 2005-05-27T22:08:02Z
Registry Expiry Date: 2022-05-27T22:08:02Z
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ADAM.NS.CLOUDFLARE.COM
Name Server: NORA.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
DNSSEC DS Data: 2371 13 2 9428C059E83917884531462DAE6138A074EF89619C82A3DAF84584639D12CDF9
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-25T14:06:59Z

vayama.com server information

Servers Location

IP Address
Country
Region
City

vayama.com desktop page speed rank

Last tested: 2016-08-14


Desktop Speed Medium
68/100

vayama.com Desktop Speed Test Quick Summary


priority - 21 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://bat.bing.com/bat.js (expiration not specified)
http://cdn.optimizely.com/js/997449157.js (2.1 minutes)
http://d3cxv97fi8q177.cloudfront.net/foundation-A4…-baf3-de38602a69ec1.js (5 minutes)
http://d3cxv97fi8q177.cloudfront.net/foundation-ta…-88a0-74a02404d7b51.js (5 minutes)
http://d3cxv97fi8q177.cloudfront.net/mediasource-A…-baf3-de38602a69ec1.js (5 minutes)
http://a.cdn.intentmedia.net/javascripts/intent_media_vayama_ads.js (10 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-5XRSC2 (15 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
http://static.vayama.com/content/banners/KE/2015/728x90KE-Feb.jpg (4 hours)
http://static.vayama.com/content/banners/LA/2016/956x327_banner1_vayama.jpg (4 hours)
http://static.vayama.com/content/banners/vayama/430x100/regions/asia.jpg (4 hours)
http://static.vayama.com/content/banners/vayama/430x100/regions/europe.jpg (4 hours)
http://static.vayama.com/content/banners/vayama/43…gions/southAmerica.jpg (4 hours)
http://static.vayama.com/content/banners/vayama/95…gions/956x327_Asia.jpg (4 hours)
http://static.vayama.com/content/banners/vayama/95…ons/956x327_Europe.jpg (4 hours)
http://static.vayama.com/content/images/icon/newsletterEnvelope.gif (4 hours)
http://static.vayama.com/content/images/socialMedia/facebook.png (4 hours)
http://static.vayama.com/content/images/socialMedia/twitter.png (4 hours)
http://static.vayama.com/content/images/thumbnails/africa.png (4 hours)
http://static.vayama.com/content/images/thumbnails/asia.png (4 hours)
http://static.vayama.com/content/images/thumbnails/caribbean.png (4 hours)
http://static.vayama.com/content/images/thumbnails/centralAmerica.png (4 hours)
http://static.vayama.com/content/images/thumbnails/europe.png (4 hours)
http://static.vayama.com/content/images/thumbnails/middleEast.png (4 hours)
http://static.vayama.com/content/images/thumbnails/pacific.png (4 hours)
http://static.vayama.com/content/images/thumbnails/southAmerica.png (4 hours)
http://static.vayama.com/content/logos/trustLogos/BBB.gif (4 hours)
http://static.vayama.com/content/logos/vayama/155x66VAY.jpg (4 hours)
http://www.vayama.com/css/siteWideFooter.css (11.8 hours)
http://cdn-ca.vayama.com//images/countryFlags/us_75.gif (11.8 hours)
http://cdn-us.vayama.com//images/credentials/iatan.gif (11.8 hours)
http://cdn-us.vayama.com/images/countryFlags/ca_75.gif (11.8 hours)
http://cdn-us.vayama.com/images/countryFlags/hk_75.gif (11.8 hours)
http://cdn-us.vayama.com/images/countryFlags/sg_75.gif (11.8 hours)
http://cdn-us.vayama.com/images/countryFlags/th_75.gif (11.8 hours)
http://www.vayama.com/css/head.css (11.8 hours)
http://www.vayama.com/css/emailVisionPopup.css (12 hours)
http://www.vayama.com/css/home.css (12 hours)
http://www.vayama.com/images/frontpage/vayamaImgs.png (12 hours)

priority - 10 Reduce server response time

In our test, your server responded in 0.32 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://cdn.optimizely.com/js/997449157.js
http://www.vayama.com/js/libs/head.min.js

Optimize CSS Delivery of the following:

http://www.vayama.com/css/home.css
http://www.vayama.com/css/emailVisionPopup.css
http://www.vayama.com/css/siteWideFooter.css
http://www.vayama.com/css/head.css

priority - 5 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 42.5KiB (24% reduction).

Losslessly compressing http://static.vayama.com/content/banners/vayama/95…ons/956x327_Europe.jpg could save 17.8KiB (29% reduction).
Losslessly compressing http://static.vayama.com/content/banners/vayama/95…gions/956x327_Asia.jpg could save 17.1KiB (28% reduction).
Losslessly compressing http://static.vayama.com/content/logos/trustLogos/BBB.gif could save 1.3KiB (32% reduction).
Losslessly compressing http://static.vayama.com/content/logos/vayama/155x66VAY.jpg could save 1,014B (23% reduction).
Losslessly compressing http://static.vayama.com/content/images/thumbnails/africa.png could save 923B (11% reduction).
Losslessly compressing http://static.vayama.com/content/images/thumbnails/europe.png could save 923B (12% reduction).
Losslessly compressing http://static.vayama.com/content/images/thumbnails/middleEast.png could save 921B (11% reduction).
Losslessly compressing http://static.vayama.com/content/images/thumbnails/asia.png could save 920B (11% reduction).
Losslessly compressing http://static.vayama.com/content/images/thumbnails/pacific.png could save 919B (11% reduction).
Losslessly compressing http://www.vayama.com/images/frontpage/vayamaImgs.png could save 835B (40% reduction).

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 6.2KiB (31% reduction).

Minifying http://www.vayama.com/js/home.js could save 3.5KiB (32% reduction) after compression.
Minifying http://www.vayama.com/js/airportCompletor.js could save 1.5KiB (42% reduction) after compression.
Minifying http://www.vayama.com/js/libs/spine.min.js could save 594B (18% reduction) after compression.
Minifying http://www.vayama.com/js/common.js could save 581B (31% reduction) after compression.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2KiB (19% reduction).

Minifying http://www.vayama.com/ could save 2KiB (19% reduction) after compression.

vayama.com Desktop Resources

Total Resources81
Number of Hosts25
Static Resources45
JavaScript Resources29
CSS Resources4

vayama.com Desktop Resource Breakdown

vayama.com mobile page speed rank

Last tested: 2018-02-14


Mobile Speed Bad
39/100

vayama.com Mobile Speed Test Quick Summary


priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://www.vayama.com/assets/js/travix/old-browsers-redirect.js
https://www.google-analytics.com/gtm/js?id=GTM-TPQNL2&l=dataLayer&m=sync&
https://www.vayama.com/assets/js/labels/en-US.js?b…4f26fc9d9f8ec3e9474875
https://www.vayama.com/assets/js/config.4b17d0f13f…73298f898ec2e7d164c.js
https://www.vayama.com/assets/js/settings.eb9289f8…ef445522793e92fddf1.js
https://www.vayama.com/assets/js/fireball/vendors.…0d94719813b336761a6a0b

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Khand:400,…bset=latin,latin,latin
https://www.vayama.com/assets/css/normalize.min.css
https://www.vayama.com/assets/css/ui-bundle.css?25…0d94719813b336761a6a0b
https://www.vayama.com/assets/css/bundle.css?b66d8…4f26fc9d9f8ec3e9474875
https://www.vayama.com/assets/css/theme.css?257513…0d94719813b336761a6a0b

priority - 47 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 460.3KiB (36% reduction).

Compressing https://s1.travix.com/as/asia-japan-tokyo-shinjuku-park-blossom-small.jpg could save 137KiB (48% reduction).
Compressing https://s1.travix.com/mo/mobile-homepage-image-small.jpg could save 51KiB (41% reduction).
Compressing https://s1.travix.com/as/asia-india-agra-taj-mahal-small.jpg could save 48.8KiB (37% reduction).
Compressing https://s1.travix.com/pa/partner-aig-father-son-vususeonly-small.jpg could save 48.2KiB (38% reduction).
Compressing https://s1.travix.com/ge/generic-hearts-beach-valentine-small.jpg could save 37.3KiB (40% reduction).
Compressing https://s1.travix.com/mi/middle-east-jeddah-mosque…aters-darker-small.jpg could save 28.3KiB (35% reduction).
Compressing https://s1.travix.com/ge/general-pick-up-driver-small.jpg could save 27.2KiB (34% reduction).
Compressing https://s1.travix.com/as/asia-united-arabic-emirat…twilight-new-small.jpg could save 25.4KiB (36% reduction).
Compressing https://s1.travix.com/ca/cars-website-red-car-small.jpg could save 21.7KiB (29% reduction).
Compressing https://s1.travix.com/global/assets/images/sprites…2366738-payment@2x.png could save 21.1KiB (18% reduction).
Compressing https://s1.travix.com/global/assets/images/sprites…162366738-trust@2x.png could save 9.9KiB (17% reduction).
Compressing https://s1.travix.com/vayama/US/assets/campaignLogos/vus_tg_aig_S@2x.png could save 1.7KiB (26% reduction).
Compressing https://s1.travix.com/global/assets/airlineLogos/SV@2x.png could save 1.7KiB (22% reduction).
Compressing https://s1.travix.com/global/assets/airlineLogos/EK@2x.png could save 1KiB (18% reduction).

priority - 34 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://vayama.com/
https://vayama.com/
https://www.vayama.com/

priority - 18 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://frontend-tripolis.travix.com/user/ip (expiration not specified)
https://api.farecache.travix.com/fare?lang=en&ac=&…D,IAD&limit=1&format=1 (5 minutes)
https://api.farecache.travix.com/fare?lang=en&ac=&…it=1&Ow=false&format=1 (5 minutes)
https://api.farecache.travix.com/fare?lang=en&ac=&…it=1&Ow=false&format=1 (5 minutes)
https://api.farecache.travix.com/fare?lang=en&ac=&…it=1&Ow=false&format=1 (5 minutes)
https://api.farecache.travix.com/fare?lang=en&ac=&…it=1&Ow=false&format=1 (5 minutes)
https://api.farecache.travix.com/fare?lang=en&ac=&…it=1&Ow=false&format=1 (5 minutes)
https://www.google-analytics.com/gtm/js?id=GTM-TPQNL2&l=dataLayer&m=sync& (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-5XRSC2 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/494839…0424?v=2.8.11&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://api.us.vayama.com/fares/cid-13f6cdb5-b38e-…9e344697/searchoptions (50 minutes)
https://deploy.mopinion.com/js/pastease.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pastease.mopinion.com/config/qyontuewonybvm4pkpt5lvfeqeobemqh8o1 (60 minutes)
https://pastease.mopinion.com/global/mopinion/version (60 minutes)
https://pastease.mopinion.com/status (60 minutes)
https://www.google-analytics.com/plugins/ua/ec.js (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://tdn.r42tag.com/lib/1148-v1.js (4 hours)
https://www.vayama.com/assets/css/normalize.min.css (4 hours)
https://www.vayama.com/assets/js/layout/masonry.layout.js?v2 (4 hours)
https://www.vayama.com/assets/js/vendor/picturefill.min.js?v=3.0.2 (4 hours)

priority - 4 Reduce server response time

In our test, your server responded in 0.45 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 2 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 23KiB (71% reduction).

Compressing https://deploy.mopinion.com/js/pastease.js could save 21KiB (71% reduction).
Compressing https://fonts.mopinion.com/css?family=Open+Sans could save 1.9KiB (78% reduction).
Compressing https://pastease.mopinion.com/config/qyontuewonybvm4pkpt5lvfeqeobemqh8o1 could save 188B (35% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.5KiB (24% reduction).

Minifying https://travix.mopinion.com/survey/travix/setup2018/js/travix_setup.js?v=2 could save 1.1KiB (20% reduction) after compression.
Minifying https://www.vayama.com/assets/js/layout/masonry.layout.js?v2 could save 997B (48% reduction) after compression.
Minifying https://travix.mopinion.com/customerscript/travix/travix.datalayer.js could save 328B (16% reduction) after compression.
Minifying https://travix.mopinion.com/customerscript/travix/custom_btn_pos.js could save 131B (18% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 663B (16% reduction).

Minifying https://travix.mopinion.com/assets/css/surveys/themes/survey-default.css could save 401B (23% reduction) after compression.
Minifying https://fonts.mopinion.com/css?family=Open+Sans could save 262B (11% reduction).

vayama.com Mobile Resources

Total Resources158
Number of Hosts39
Static Resources72
JavaScript Resources49
CSS Resources9

vayama.com Mobile Resource Breakdown

vayama.com mobile page usability

Last tested: 2018-02-14


Mobile Usability Good
99/100

vayama.com Mobile Usability Test Quick Summary


priority - 1 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <div class="date-picker sh…-picker-return">Returning</div> is close to 1 other tap targets.

The tap target <a href="https://www.va…om/city-breaks" class="icon icon-100 icon-Seo_region">City breaks</a> and 17 others are close to other tap targets.

vayama.com similar domains

Similar domains:
www.vayama.com
www.vayama.net
www.vayama.org
www.vayama.info
www.vayama.biz
www.vayama.us
www.vayama.mobi
www.ayama.com
www.vayama.com
www.cayama.com
www.vcayama.com
www.cvayama.com
www.fayama.com
www.vfayama.com
www.fvayama.com
www.gayama.com
www.vgayama.com
www.gvayama.com
www.bayama.com
www.vbayama.com
www.bvayama.com
www.vyama.com
www.vqyama.com
www.vaqyama.com
www.vqayama.com
www.vwyama.com
www.vawyama.com
www.vwayama.com
www.vsyama.com
www.vasyama.com
www.vsayama.com
www.vzyama.com
www.vazyama.com
www.vzayama.com
www.vaama.com
www.vatama.com
www.vaytama.com
www.vatyama.com
www.vagama.com
www.vaygama.com
www.vagyama.com
www.vahama.com
www.vayhama.com
www.vahyama.com
www.vauama.com
www.vayuama.com
www.vauyama.com
www.vayma.com
www.vayqma.com
www.vayaqma.com
www.vayqama.com
www.vaywma.com
www.vayawma.com
www.vaywama.com
www.vaysma.com
www.vayasma.com
www.vaysama.com
www.vayzma.com
www.vayazma.com
www.vayzama.com
www.vayaa.com
www.vayana.com
www.vayamna.com
www.vayanma.com
www.vayaja.com
www.vayamja.com
www.vayajma.com
www.vayaka.com
www.vayamka.com
www.vayakma.com
www.vayam.com
www.vayamq.com
www.vayamaq.com
www.vayamqa.com
www.vayamw.com
www.vayamaw.com
www.vayamwa.com
www.vayams.com
www.vayamas.com
www.vayamsa.com
www.vayamz.com
www.vayamaz.com
www.vayamza.com
www.vayama.con

vayama.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


vayama.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.