Tools & Wizards About Us
e-doc.in screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

e-doc.in

eDoc.in | Patient Appointment & Tele-Consultation Solution

Page Load Speed

3.2 sec in total

First Response

145 ms

Resources Loaded

2.2 sec

Page Rendered

861 ms

e-doc.in screenshot

About Website

Welcome to e-doc.in homepage info - get ready to check EDoc best content right away, or after learning these important things about e-doc.in

E-Doc.in is a personalised patient booking & telemedicine solution for the medical practitioners. EDOC.IN offers the practitioners to monetise their practise by providing remote diagnosis and consulta...

Visit e-doc.in

Key Findings

We analyzed E-doc.in page load time and found that the first response time was 145 ms and then it took 3 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

e-doc.in performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

e-doc.in

145 ms

e-doc.in

535 ms

bootstrap.min.css

396 ms

font-awesome.min.css

262 ms

owl.carousel.css

201 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 67% of them (29 requests) were addressed to the original E-doc.in, 7% (3 requests) were made to Gstatic.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (838 ms) belongs to the original domain E-doc.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.0 kB (45%)

Content Size

967.6 kB

After Optimization

527.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-doc.in main page is 967.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. 60% of websites need less resources to load. Images take 434.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.5 kB

  • Original 73.4 kB
  • After minification 58.9 kB
  • After compression 12.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 14.5 kB, which is 20% 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 60.5 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 47.4 kB

  • Original 434.1 kB
  • After minification 386.7 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, EDoc needs image optimization as it can save up to 47.4 kB or 11% 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 152.5 kB

  • Original 247.2 kB
  • After minification 245.6 kB
  • After compression 94.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 152.5 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 179.6 kB

  • Original 212.9 kB
  • After minification 172.3 kB
  • After compression 33.3 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. E-doc.in needs all CSS files to be minified and compressed as it can save up to 179.6 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EDoc. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

e-doc.in

e-doc.in

145 ms

e-doc.in

e-doc.in

535 ms

bootstrap.min.css

bootstrap.min.css

396 ms

font-awesome.min.css

font-awesome.min.css

262 ms

owl.carousel.css

owl.carousel.css

201 ms

owl.theme.default.min.css

owl.theme.default.min.css

200 ms

bootstrap-clockpicker.min.css

bootstrap-clockpicker.min.css

209 ms

jquery.timepicker.min.css

jquery.timepicker.min.css

210 ms

templatemo-style.css

templatemo-style.css

323 ms

js

js

66 ms

api.js

api.js

49 ms

jquery.js

jquery.js

261 ms

jquery.timepicker.min.js

jquery.timepicker.min.js

148 ms

bootstrap.min.js

bootstrap.min.js

215 ms

owl.carousel.min.js

owl.carousel.min.js

199 ms

smoothscroll.js

smoothscroll.js

214 ms

custom.js

custom.js

259 ms

bootstrap-clockpicker.min.js

bootstrap-clockpicker.min.js

261 ms

highlight.min.js

highlight.min.js

677 ms

css

css

40 ms

recaptcha__en.js

recaptcha__en.js

382 ms

analytics.js

analytics.js

664 ms

edoclogo.png

edoclogo.png

769 ms

b6.png

b6.png

813 ms

logo-kos-512-x-512-jpeg.jpg

logo-kos-512-x-512-jpeg.jpg

769 ms

Shekar_App_logo.jpg

Shekar_App_logo.jpg

767 ms

divakars_d.png

divakars_d.png

758 ms

KSOGA---LOGO-512-x-512.png

KSOGA---LOGO-512-x-512.png

801 ms

NN_logo_520x520.png

NN_logo_520x520.png

801 ms

Rajasheakear.png

Rajasheakear.png

801 ms

Santasaq.png

Santasaq.png

800 ms

SSM-hospital-1-png-512-x-512.png

SSM-hospital-1-png-512-x-512.png

800 ms

chkdin-white.png

chkdin-white.png

838 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

582 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf

607 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf

660 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

717 ms

se2337t5bwyp.js

se2337t5bwyp.js

564 ms

fallback

fallback

129 ms

collect

collect

88 ms

fallback__ltr.css

fallback__ltr.css

45 ms

css

css

22 ms

logo_48.png

logo_48.png

11 ms

Accessibility Review

e-doc.in accessibility score

57

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

e-doc.in best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

e-doc.in SEO score

92

Search Engine Optimization Advices

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

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 E-doc.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 E-doc.in 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

e-doc.in

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