Tools & Wizards About Us
docchecker.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

docchecker.com

DocChecker - Find Doctors - Make Appointments Instantly For Free!

Page Load Speed

2.5 sec in total

First Response

250 ms

Resources Loaded

1.9 sec

Page Rendered

351 ms

docchecker.com screenshot

About Website

Click here to check amazing Doc Checker content for United States. Otherwise, check out these important facts you probably never knew about docchecker.com

DocChecker, Find Doctors Online And Make Appointments Instantly For Free! Search By Insurances, Zip And Specialty.

Visit docchecker.com

Key Findings

We analyzed Docchecker.com page load time and found that the first response time was 250 ms and then it took 2.3 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

docchecker.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

docchecker.com

250 ms

docchecker.com

847 ms

js

83 ms

js

116 ms

css

57 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 73% of them (37 requests) were addressed to the original Docchecker.com, 12% (6 requests) were made to Use.typekit.net and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Docchecker.com.

Page Optimization Overview & Recommendations

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

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docchecker.com main page is 1.8 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.2 kB

  • Original 50.3 kB
  • After minification 38.7 kB
  • After compression 9.1 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 11.6 kB, which is 23% 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 41.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 72.9 kB

  • Original 1.3 MB
  • After minification 1.2 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. Doc Checker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.6 kB

  • Original 412.0 kB
  • After minification 412.0 kB
  • After compression 410.5 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.

CSS Optimization

-9%

Potential reduce by 5.5 kB

  • Original 64.2 kB
  • After minification 64.2 kB
  • After compression 58.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. Docchecker.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (50%)

Requests Now

38

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

docchecker.com

docchecker.com

250 ms

docchecker.com

docchecker.com

847 ms

js

js

83 ms

js

js

116 ms

css

css

57 ms

font-awesome.min.css

font-awesome.min.css

102 ms

ionicons.min.css

ionicons.min.css

169 ms

bootstrap.min.css

bootstrap.min.css

274 ms

jquery.min.js

jquery.min.js

282 ms

bootstrap.min.js

bootstrap.min.js

214 ms

crousel-doc.js

crousel-doc.js

215 ms

jquery.js

jquery.js

294 ms

jquery.maskedinput-1.3.js

jquery.maskedinput-1.3.js

247 ms

rating.js

rating.js

299 ms

custon-style.css

custon-style.css

374 ms

js

js

79 ms

api.js

api.js

61 ms

font-awesome.css

font-awesome.css

50 ms

326 ms

351 ms

logo-doc.png

logo-doc.png

465 ms

mwe5hxs.css

mwe5hxs.css

101 ms

jqueryss.min.js

jqueryss.min.js

399 ms

jqueryss.inputmask.bundle.js

jqueryss.inputmask.bundle.js

466 ms

L_669791_166979_IMG_6524.JPG

L_669791_166979_IMG_6524.JPG

464 ms

L_c7010370103_25_edouard-m-belotte.png

L_c7010370103_25_edouard-m-belotte.png

498 ms

L_c7011070110_596_william1.jpg

L_c7011070110_596_william1.jpg

465 ms

L_c7004970049_98_MARINA%20IMAGE.png

L_c7004970049_98_MARINA%20IMAGE.png

558 ms

L_c7024070240_412_Dr.-Michael-Samandarov.jpg

L_c7024070240_412_Dr.-Michael-Samandarov.jpg

498 ms

L_667691_166769_Dr_Dwayne_ROLLINS.jpg

L_667691_166769_Dr_Dwayne_ROLLINS.jpg

559 ms

L_c141141_262_image%20(13).png

L_c141141_262_image%20(13).png

620 ms

L_c6576265762_394_dr-marie-belotte.jpg

L_c6576265762_394_dr-marie-belotte.jpg

558 ms

L_c7010770107_974_Malakov_BW.jpeg

L_c7010770107_974_Malakov_BW.jpeg

565 ms

L_c6933269332_622_richardswift.jpg

L_c6933269332_622_richardswift.jpg

576 ms

swift.JPG

swift.JPG

703 ms

kohani.jpg

kohani.jpg

703 ms

voskin.jpg

voskin.jpg

767 ms

patient.jpg

patient.jpg

643 ms

captcha.php

captcha.php

648 ms

cropped-casa-4.png

cropped-casa-4.png

691 ms

336 ms

353 ms

recaptcha__en.js

recaptcha__en.js

27 ms

FuturaPTLight.otf

FuturaPTLight.otf

429 ms

PlayfairDisplay-Regular.ttf

PlayfairDisplay-Regular.ttf

385 ms

p.css

p.css

63 ms

d

d

60 ms

d

d

68 ms

d

d

77 ms

d

d

68 ms

d

d

85 ms

Accessibility Review

docchecker.com accessibility score

66

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

docchecker.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

docchecker.com SEO score

62

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

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

docchecker.com

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