Tools & Wizards About Us
ezeebank.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ezeebank.com

EzeeBank - Internet Banking, Mobile Banking, Mobile Wallets

Page Load Speed

3.3 sec in total

First Response

118 ms

Resources Loaded

3 sec

Page Rendered

231 ms

ezeebank.com screenshot

About Website

Visit ezeebank.com now to see the best up-to-date Ezee Bank content for India and also check out these interesting facts you probably never knew about ezeebank.com

Net banking and mobile banking registration process, BHIM UPI, USSD *99# Mobile Banking.

Visit ezeebank.com

Key Findings

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

Performance Metrics

ezeebank.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

satishsingh.godaddysites.com

118 ms

css

69 ms

css

84 ms

site.css

23 ms

duel.js

328 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ezeebank.com, 12% (6 requests) were made to Platform.twitter.com and 8% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.9 kB (48%)

Content Size

260.6 kB

After Optimization

134.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ezeebank.com main page is 260.6 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. 40% of websites need less resources to load. Javascripts take 162.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.6 kB

  • Original 39.1 kB
  • After minification 39.0 kB
  • After compression 9.5 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 29.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 129 B

  • Original 12.1 kB
  • After minification 12.0 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. Ezee Bank images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 58.0 kB

  • Original 162.7 kB
  • After minification 162.5 kB
  • After compression 104.7 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 58.0 kB or 36% of the original size.

CSS Optimization

-82%

Potential reduce by 38.1 kB

  • Original 46.7 kB
  • After minification 46.7 kB
  • After compression 8.6 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. Ezeebank.com needs all CSS files to be minified and compressed as it can save up to 38.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (47%)

Requests Now

45

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

satishsingh.godaddysites.com

satishsingh.godaddysites.com

118 ms

css

css

69 ms

css

css

84 ms

site.css

site.css

23 ms

duel.js

duel.js

328 ms

adsbygoogle.js

adsbygoogle.js

52 ms

getSeal

getSeal

685 ms

tcc_l.combined.1.0.5.min.js

tcc_l.combined.1.0.5.min.js

406 ms

jq.js

jq.js

73 ms

analytics.js

analytics.js

169 ms

1f8f7e24a41a3f59737053e10dc0a385

1f8f7e24a41a3f59737053e10dc0a385

433 ms

integrator.js

integrator.js

306 ms

ca-pub-1046410915412130.js

ca-pub-1046410915412130.js

19 ms

zrt_lookup.html

zrt_lookup.html

254 ms

show_ads_impl.js

show_ads_impl.js

153 ms

linkid.js

linkid.js

125 ms

media.gallery.js

media.gallery.js

132 ms

twitter-icn.png

twitter-icn.png

130 ms

social.twitter.js

social.twitter.js

130 ms

ads

ads

98 ms

osd.js

osd.js

92 ms

cookiemanager.js

cookiemanager.js

110 ms

iebackground.js

iebackground.js

110 ms

collect

collect

100 ms

ads

ads

60 ms

util.instances.js

util.instances.js

71 ms

util.model.js

util.model.js

70 ms

documentHelper.js

documentHelper.js

56 ms

helper.js

helper.js

103 ms

ads

ads

73 ms

collect

collect

67 ms

util.window.js

util.window.js

50 ms

25e177f7a5080d331f2285a7832eaef9

25e177f7a5080d331f2285a7832eaef9

1363 ms

browser.js

browser.js

32 ms

ga-audiences

ga-audiences

38 ms

widgets.js

widgets.js

23 ms

index.php

index.php

198 ms

widget_iframe.32d6c6b4cb1ed84df04e7f9705a90c47.html

widget_iframe.32d6c6b4cb1ed84df04e7f9705a90c47.html

16 ms

settings

settings

81 ms

jot

jot

67 ms

ut3Ltniq_normal.jpg

ut3Ltniq_normal.jpg

286 ms

retweet-icn.png

retweet-icn.png

42 ms

button.460b6e50c797f0f03177332228ca7d20.js

button.460b6e50c797f0f03177332228ca7d20.js

2 ms

ypY1GPCQ_normal.jpg

ypY1GPCQ_normal.jpg

245 ms

DlgF2XnUwAAN_c8.jpg:thumb

DlgF2XnUwAAN_c8.jpg:thumb

316 ms

nO-ChMdc_normal.jpg

nO-ChMdc_normal.jpg

258 ms

follow_button.32d6c6b4cb1ed84df04e7f9705a90c47.en.html

follow_button.32d6c6b4cb1ed84df04e7f9705a90c47.en.html

39 ms

tweet_button.32d6c6b4cb1ed84df04e7f9705a90c47.en.html

tweet_button.32d6c6b4cb1ed84df04e7f9705a90c47.en.html

61 ms

jot.html

jot.html

3 ms

d95155f228751e863ca40d996a76fcae

d95155f228751e863ca40d996a76fcae

160 ms

538d8fb36afb529a9a27aced46ef30f9

538d8fb36afb529a9a27aced46ef30f9

105 ms

event

event

272 ms

Accessibility Review

ezeebank.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

Best Practices

ezeebank.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ezeebank.com SEO score

92

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

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

ezeebank.com

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