Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

api.eazydiner.com

Best restaurants in Delhi NCR | Delhi NCR restaurants, 2023- EazyDiner

Page Load Speed

7.1 sec in total

First Response

404 ms

Resources Loaded

4.3 sec

Page Rendered

2.4 sec

api.eazydiner.com screenshot

About Website

Visit api.eazydiner.com now to see the best up-to-date Api Eazy Diner content for India and also check out these interesting facts you probably never knew about api.eazydiner.com

Best restaurants in Delhi NCR: Book online restaurant reservation with a guaranteed deal. Check &#10004 deals &#10004 menu &#10004 reviews of the best restaurants in Delhi NCR.

Visit api.eazydiner.com

Key Findings

We analyzed Api.eazydiner.com page load time and found that the first response time was 404 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

api.eazydiner.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

api.eazydiner.com

404 ms

api.eazydiner.com

2178 ms

js

79 ms

gtm.js

127 ms

fbevents.js

30 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 33% of them (34 requests) were addressed to the original Api.eazydiner.com, 61% (63 requests) were made to D4t7t8y8xqo0t.cloudfront.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Api.eazydiner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 687.6 kB (7%)

Content Size

9.6 MB

After Optimization

8.9 MB

In fact, the total size of Api.eazydiner.com main page is 9.6 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. Only a small number of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 321.9 kB

  • Original 358.3 kB
  • After minification 221.2 kB
  • After compression 36.4 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 137.1 kB, which is 38% 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 321.9 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 226.1 kB

  • Original 8.8 MB
  • After minification 8.6 MB

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 Eazy Diner images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 136.2 kB

  • Original 381.2 kB
  • After minification 381.2 kB
  • After compression 245.0 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 136.2 kB or 36% of the original size.

CSS Optimization

-13%

Potential reduce by 3.4 kB

  • Original 25.5 kB
  • After minification 25.5 kB
  • After compression 22.1 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. Api.eazydiner.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (18%)

Requests Now

85

After Optimization

70

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

Accessibility Review

api.eazydiner.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

api.eazydiner.com best practices score

42

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

api.eazydiner.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Open Graph description is not detected on the main page of Api Eazy Diner. 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: