Tools & Wizards About Us
support.makemytrip.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

support.makemytrip.com

Page Load Speed

24.3 sec in total

First Response

3.1 sec

Resources Loaded

21.1 sec

Page Rendered

156 ms

support.makemytrip.com screenshot

About Website

Welcome to support.makemytrip.com homepage info - get ready to check Support Makemytrip best content for India right away, or after learning these important things about support.makemytrip.com

MakeMyTrip provides 24X7 Customer Support for your travel related queries. Signin, View Bookings, Print E-Ticket, Cancel Booking, Check Refund Status or send us your valuable feedback.

Visit support.makemytrip.com

Key Findings

We analyzed Support.makemytrip.com page load time and found that the first response time was 3.1 sec and then it took 21.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

support.makemytrip.com performance score

0

Network Requests Diagram

support.makemytrip.com

3062 ms

header_footer.css

1503 ms

bootstrap.css

2135 ms

forms.css

1236 ms

input_group.css

938 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 38% of them (20 requests) were addressed to the original Support.makemytrip.com, 8% (4 requests) were made to Apis.google.com and 4% (2 requests) were made to Makemytrip.com. The less responsive or slowest element that took the longest time to load (16.3 sec) relates to the external source Makemytrip.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 814.8 kB (57%)

Content Size

1.4 MB

After Optimization

624.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Support.makemytrip.com main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 835.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 95.1 kB

  • Original 123.0 kB
  • After minification 113.3 kB
  • After compression 27.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 95.1 kB or 77% of the original size.

Image Optimization

-16%

Potential reduce by 45.5 kB

  • Original 290.0 kB
  • After minification 244.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Support Makemytrip needs image optimization as it can save up to 45.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 517.8 kB

  • Original 835.7 kB
  • After minification 759.0 kB
  • After compression 317.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 517.8 kB or 62% of the original size.

CSS Optimization

-82%

Potential reduce by 156.4 kB

  • Original 190.4 kB
  • After minification 155.6 kB
  • After compression 33.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Support.makemytrip.com needs all CSS files to be minified and compressed as it can save up to 156.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (69%)

Requests Now

52

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Makemytrip. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

support.makemytrip.com

support.makemytrip.com

3062 ms

header_footer.css

header_footer.css

1503 ms

bootstrap.css

bootstrap.css

2135 ms

forms.css

forms.css

1236 ms

input_group.css

input_group.css

938 ms

glyphicon.css

glyphicon.css

1258 ms

jquery-ui.css

jquery-ui.css

1861 ms

mmt_ma.css

mmt_ma.css

1858 ms

screen_responsive.css

screen_responsive.css

1902 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

2018 ms

bootstrap.min.js

bootstrap.min.js

2085 ms

jquery.custom.js

jquery.custom.js

2147 ms

Login-Scripts.js

Login-Scripts.js

2151 ms

jquery.blockui.js

jquery.blockui.js

16046 ms

md5.js

md5.js

2192 ms

s_code_08072010.js

s_code_08072010.js

16290 ms

ch.css

ch.css

131 ms

common_header_scripts_raw.js

common_header_scripts_raw.js

152 ms

mbox-min.js

mbox-min.js

145 ms

WebResource.axd

WebResource.axd

1364 ms

chf_blackoverlay_3.0.js

chf_blackoverlay_3.0.js

14763 ms

base.css

base.css

888 ms

beacon.js

beacon.js

142 ms

all.js

all.js

483 ms

client:plusone.js

client:plusone.js

191 ms

mmt_logo_strip_new.png

mmt_logo_strip_new.png

343 ms

common_header_footer_sprite_vernacular_05.png

common_header_footer_sprite_vernacular_05.png

47 ms

login.png

login.png

995 ms

common_header_footer_sprite.png

common_header_footer_sprite.png

1524 ms

footer_bg.gif

footer_bg.gif

324 ms

footer_bg_bottom.gif

footer_bg_bottom.gif

335 ms

8470e796519e.js

8470e796519e.js

224 ms

webengage-min-v-4.0.js

webengage-min-v-4.0.js

310 ms

ga.js

ga.js

233 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

223 ms

s76113780508749

s76113780508749

61 ms

postmessageRelay

postmessageRelay

101 ms

gz.js

gz.js

170 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

58 ms

164 ms

xd_arbiter.php

xd_arbiter.php

287 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

94 ms

rpc:shindig_random.js

rpc:shindig_random.js

70 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

v4.js

v4.js

69 ms

auth

auth

92 ms

upf.js

upf.js

60 ms

3618811893-postmessage.js

3618811893-postmessage.js

7 ms

l3.jpg

l3.jpg

45 ms

125 ms

usabilla_black_rightSideImprove.png

usabilla_black_rightSideImprove.png

188 ms

xd_arbiter.php

xd_arbiter.php

143 ms

inspectlet.js

inspectlet.js

142 ms

SEO Factors

support.makemytrip.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.makemytrip.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Support.makemytrip.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

support.makemytrip.com

Open Graph description is not detected on the main page of Support Makemytrip. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: