Tools & Wizards About Us
api.zomato.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

api.zomato.com

API Home | Zomato

Page Load Speed

1.6 sec in total

First Response

358 ms

Resources Loaded

1.2 sec

Page Rendered

108 ms

api.zomato.com screenshot

About Website

Visit api.zomato.com now to see the best up-to-date API Zomato content for India and also check out these interesting facts you probably never knew about api.zomato.com

Build rich location based web and mobile applications using restaurants and events data using Zomato API

Visit api.zomato.com

Key Findings

We analyzed Api.zomato.com page load time and found that the first response time was 358 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster. This domain responded with an error, which can significantly jeopardize Api.zomato.com rating and web reputation

Performance Metrics

api.zomato.com performance score

0

Network Requests Diagram

api.zomato.com

358 ms

api

303 ms

h-1f51f025bc7e8f953a83c4dca9269ae1

90 ms

h-1f51f025bc7e8f953a83c4dca9269ae1

64 ms

conversion.js

44 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Api.zomato.com, 32% (7 requests) were made to B.zmtcdn.com and 23% (5 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (358 ms) belongs to the original domain Api.zomato.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.0 kB (29%)

Content Size

134.4 kB

After Optimization

95.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-78%

Potential reduce by 38.9 kB

  • Original 49.9 kB
  • After minification 37.6 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 12.3 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 25.4 kB
  • After minification 25.4 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. API Zomato images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 100 B

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 59.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 9 (53%)

Requests Now

17

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

api.zomato.com

api.zomato.com

358 ms

api

api

303 ms

h-1f51f025bc7e8f953a83c4dca9269ae1

h-1f51f025bc7e8f953a83c4dca9269ae1

90 ms

h-1f51f025bc7e8f953a83c4dca9269ae1

h-1f51f025bc7e8f953a83c4dca9269ae1

64 ms

conversion.js

conversion.js

44 ms

dc.js

dc.js

91 ms

jumbo_call_handler.php

jumbo_call_handler.php

87 ms

gtm.js

gtm.js

57 ms

75 ms

zlogo-us-en3_2x.png

zlogo-us-en3_2x.png

19 ms

ajax-loader.gif

ajax-loader.gif

20 ms

loading-transparent.gif

loading-transparent.gif

31 ms

api_overview.png

api_overview.png

76 ms

zwhite5r.png

zwhite5r.png

73 ms

analytics.js

analytics.js

73 ms

126 ms

inpage_linkid.js

inpage_linkid.js

70 ms

zombatsregular-webfont-web.woff

zombatsregular-webfont-web.woff

9 ms

__utm.gif

__utm.gif

20 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

23 ms

__utm.gif

__utm.gif

33 ms

SEO Factors

api.zomato.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.zomato.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Api.zomato.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

api.zomato.com

Open Graph data is detected on the main page of API Zomato. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: