Tools & Wizards About Us
ecount.in screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ecount.in

Simplified Cloud Accounting Software for Traders, Transporters, CA, MSME and More

Page Load Speed

2.4 sec in total

First Response

34 ms

Resources Loaded

2.1 sec

Page Rendered

243 ms

ecount.in screenshot

About Website

Visit ecount.in now to see the best up-to-date Ecount content for India and also check out these interesting facts you probably never knew about ecount.in

GST Ready, ERP Transport, Logistics & Fleet Management Software (TMS) with Cloud Base Option. Windows, Web and Android App Base Software

Visit ecount.in

Key Findings

We analyzed Ecount.in page load time and found that the first response time was 34 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ecount.in performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

ecount.in

34 ms

www.ecount.in

472 ms

bootstrap.min.css

15 ms

custom.css

28 ms

WebResource.axd

463 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Ecount.in, 2% (1 request) were made to Statcounter.com and 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (659 ms) belongs to the original domain Ecount.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.8 kB (49%)

Content Size

334.8 kB

After Optimization

171.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ecount.in main page is 334.8 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. 30% of websites need less resources to load. HTML takes 131.0 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 120.4 kB

  • Original 131.0 kB
  • After minification 63.7 kB
  • After compression 10.6 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 67.4 kB, which is 51% 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 120.4 kB or 92% of the original size.

Image Optimization

-34%

Potential reduce by 16.6 kB

  • Original 49.6 kB
  • After minification 33.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. Obviously, Ecount needs image optimization as it can save up to 16.6 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 19.1 kB

  • Original 99.8 kB
  • After minification 99.8 kB
  • After compression 80.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 19.1 kB or 19% of the original size.

CSS Optimization

-14%

Potential reduce by 7.6 kB

  • Original 54.4 kB
  • After minification 54.4 kB
  • After compression 46.8 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. Ecount.in needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (10%)

Requests Now

59

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ecount.in

ecount.in

34 ms

www.ecount.in

www.ecount.in

472 ms

bootstrap.min.css

bootstrap.min.css

15 ms

custom.css

custom.css

28 ms

WebResource.axd

WebResource.axd

463 ms

email-decode.min.js

email-decode.min.js

21 ms

jquery.min.js

jquery.min.js

659 ms

modules.js

modules.js

43 ms

slick.js

slick.js

42 ms

theme.js

theme.js

575 ms

counter.js

counter.js

44 ms

helpicon.png

helpicon.png

11 ms

ecount-logo.svg

ecount-logo.svg

12 ms

softwareicon.svg

softwareicon.svg

14 ms

whatsicon.png

whatsicon.png

23 ms

sine2009.webp

sine2009.webp

537 ms

india1st.webp

india1st.webp

537 ms

trusted_icon.webp

trusted_icon.webp

33 ms

onlinetransport.webp

onlinetransport.webp

43 ms

accountsoftware.webp

accountsoftware.webp

58 ms

CRM1.webp

CRM1.webp

71 ms

clients1.webp

clients1.webp

83 ms

c02.webp

c02.webp

101 ms

c01.webp

c01.webp

112 ms

c03.webp

c03.webp

123 ms

c06.webp

c06.webp

141 ms

c11.webp

c11.webp

153 ms

c21.webp

c21.webp

164 ms

c27.webp

c27.webp

173 ms

c30.webp

c30.webp

184 ms

ritalogo.png

ritalogo.png

195 ms

Microsoft-Certified.svg

Microsoft-Certified.svg

207 ms

logo.png

logo.png

218 ms

logo.png

logo.png

242 ms

fbicon.png

fbicon.png

253 ms

youtubeicon.png

youtubeicon.png

265 ms

playstoreicon.png

playstoreicon.png

276 ms

sprite.png

sprite.png

83 ms

trusted_icon.webp

trusted_icon.webp

430 ms

onlinetransport.webp

onlinetransport.webp

83 ms

accountsoftware.webp

accountsoftware.webp

427 ms

CRM1.webp

CRM1.webp

645 ms

clients1.webp

clients1.webp

85 ms

c02.webp

c02.webp

83 ms

c01.webp

c01.webp

85 ms

c03.webp

c03.webp

86 ms

c06.webp

c06.webp

87 ms

c11.webp

c11.webp

87 ms

c21.webp

c21.webp

88 ms

c27.webp

c27.webp

89 ms

c30.webp

c30.webp

89 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

33 ms

t.php

t.php

97 ms

c30.webp

c30.webp

11 ms

c27.webp

c27.webp

10 ms

c21.webp

c21.webp

437 ms

c11.webp

c11.webp

19 ms

c06.webp

c06.webp

22 ms

c03.webp

c03.webp

28 ms

clients1.webp

clients1.webp

37 ms

c02.webp

c02.webp

41 ms

c01.webp

c01.webp

53 ms

Accessibility Review

ecount.in accessibility score

75

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ecount.in best practices score

67

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

Page has valid source maps

SEO Factors

ecount.in SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    CHARSET=UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecount.in 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 Ecount.in main page’s claimed encoding is charset=utf-8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ecount.in

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