Tools & Wizards About Us
docdoc.sg screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

docdoc.sg

Transforming healthcare | Empowering lives | Docdoc

Page Load Speed

4.3 sec in total

First Response

22 ms

Resources Loaded

4.1 sec

Page Rendered

178 ms

docdoc.sg screenshot

About Website

Visit docdoc.sg now to see the best up-to-date Docdoc content for Singapore and also check out these interesting facts you probably never knew about docdoc.sg

DocDoc is Asia’s leading patient empowerment company. We are the patients’ trusted medical advisor. With a network of more than 23,000 doctors under contract and extensive proprietary data on outcome,...

Visit docdoc.sg

Key Findings

We analyzed Docdoc.sg page load time and found that the first response time was 22 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

docdoc.sg performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

docdoc.sg

22 ms

www.docdoc.sg

35 ms

www.docdoc.sg

163 ms

head-9e0fc78c24e414b24c25be33b236e51c.js

69 ms

140809765.js

285 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Docdoc.sg, 23% (25 requests) were made to 4731993def70233880c2-85120bc1c06d179469037673b27322a2.ssl.cf1.rackcdn.com and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source 4731993def70233880c2-85120bc1c06d179469037673b27322a2.ssl.cf1.rackcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (66%)

Content Size

3.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Docdoc.sg main page is 3.1 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. 60% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.1 kB

  • Original 82.3 kB
  • After minification 82.2 kB
  • After compression 19.2 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 63.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 267.0 kB
  • After minification 267.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. Docdoc images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.4 MB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 649.2 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 1.4 MB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 577.0 kB

  • Original 689.0 kB
  • After minification 684.4 kB
  • After compression 112.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. Docdoc.sg needs all CSS files to be minified and compressed as it can save up to 577.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (72%)

Requests Now

87

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

docdoc.sg

docdoc.sg

22 ms

www.docdoc.sg

www.docdoc.sg

35 ms

www.docdoc.sg

www.docdoc.sg

163 ms

head-9e0fc78c24e414b24c25be33b236e51c.js

head-9e0fc78c24e414b24c25be33b236e51c.js

69 ms

140809765.js

140809765.js

285 ms

tracking.js

tracking.js

342 ms

gtm.js

gtm.js

94 ms

docdoc-logo-3d89d34827ad2084d67669e6a216a385.svg

docdoc-logo-3d89d34827ad2084d67669e6a216a385.svg

67 ms

qiuqiu-avatar-9a9642c5c923fe0194887e69ffb20293.png

qiuqiu-avatar-9a9642c5c923fe0194887e69ffb20293.png

369 ms

application_part1-0f76ad1b32bfcb2ca51012ccf4adbef7.css

application_part1-0f76ad1b32bfcb2ca51012ccf4adbef7.css

3012 ms

application_preload-cbc0588e35160147a29057f34b0a24ca.js

application_preload-cbc0588e35160147a29057f34b0a24ca.js

61 ms

i18n.en-0fe4302e5aca2e6ff64f9708dd8a1506.js

i18n.en-0fe4302e5aca2e6ff64f9708dd8a1506.js

21 ms

mixpanel_production-57b933f75783426c6d4366b94d08e3bc.js

mixpanel_production-57b933f75783426c6d4366b94d08e3bc.js

184 ms

application_desktop-444676bb514413314ce3cfc9f0298efd.js

application_desktop-444676bb514413314ce3cfc9f0298efd.js

375 ms

application_part2-7f120af69f22fb75a392ecb6a96d8ad9.css

application_part2-7f120af69f22fb75a392ecb6a96d8ad9.css

298 ms

application_part3-8a1a43c8555367f590806786cceedd42.css

application_part3-8a1a43c8555367f590806786cceedd42.css

483 ms

application_part4-e80599aa7ced7c433a40b739150002c6.css

application_part4-e80599aa7ced7c433a40b739150002c6.css

444 ms

application_part5-00a662769e1ab8abc06c744e938681db.css

application_part5-00a662769e1ab8abc06c744e938681db.css

567 ms

font-awesome.min.css

font-awesome.min.css

156 ms

phonenum.jsp

phonenum.jsp

1608 ms

conversion_async.js

conversion_async.js

227 ms

dc.js

dc.js

275 ms

roundtrip.js

roundtrip.js

254 ms

4257.js

4257.js

318 ms

widgets.js

widgets.js

153 ms

platform.js

platform.js

174 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

149 ms

event

event

114 ms

script_data.js

script_data.js

251 ms

107 ms

155 ms

171 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

47 ms

__utm.gif

__utm.gif

104 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

97 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

110 ms

fastbutton

fastbutton

156 ms

129 ms

s

s

94 ms

u

u

127 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

53 ms

120 ms

KSGHIV5WLJENPPWAA37AE6.js

KSGHIV5WLJENPPWAA37AE6.js

186 ms

75 ms

59 ms

postmessageRelay

postmessageRelay

88 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

66 ms

localization.en.1.3632191afe35222a6b78c04d457adc0d_c3d00ca7f7111f5fc858d9e2f338cbad.js

localization.en.1.3632191afe35222a6b78c04d457adc0d_c3d00ca7f7111f5fc858d9e2f338cbad.js

69 ms

ping

ping

157 ms

open_chat.cgi

open_chat.cgi

156 ms

api.js

api.js

54 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

58 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

52 ms

jot

jot

146 ms

livechat-classic_f726105e9a.ttf

livechat-classic_f726105e9a.ttf

69 ms

tr

tr

80 ms

out

out

39 ms

out

out

31 ms

out

out

38 ms

out

out

39 ms

out

out

71 ms

out

out

70 ms

48 ms

u.php

u.php

80 ms

adsct

adsct

196 ms

pixel

pixel

80 ms

embedded.20160229163048.js

embedded.20160229163048.js

106 ms

tap.php

tap.php

16 ms

sync

sync

16 ms

377928.gif

377928.gif

11 ms

in

in

5 ms

sd

sd

9 ms

_Incapsula_Resource

_Incapsula_Resource

28 ms

_Incapsula_Resource

_Incapsula_Resource

28 ms

sdk.js

sdk.js

237 ms

21 ms

xd_arbiter.php

xd_arbiter.php

241 ms

xd_arbiter.php

xd_arbiter.php

300 ms

phnumint_md_gp.jsp

phnumint_md_gp.jsp

300 ms

specialty-select-icon-88a5a4cddb45b807848482730c3f9ab4.png

specialty-select-icon-88a5a4cddb45b807848482730c3f9ab4.png

82 ms

select-arrow-down-85f6580dc59c2a88e8931649c74c9a28.png

select-arrow-down-85f6580dc59c2a88e8931649c74c9a28.png

80 ms

location-icon-cb838655b94b1a984a90c6d4ce14eb56.png

location-icon-cb838655b94b1a984a90c6d4ce14eb56.png

79 ms

speciality-icon-eb0bf2f1ae83b420f36875859e814bfd.png

speciality-icon-eb0bf2f1ae83b420f36875859e814bfd.png

133 ms

smiley-icon-859d37ca80588ac78fbfe19dc42f771a.png

smiley-icon-859d37ca80588ac78fbfe19dc42f771a.png

143 ms

lock-icon-23bba43d61b195ce4079271f7211ad44.png

lock-icon-23bba43d61b195ce4079271f7211ad44.png

168 ms

devices-new-4eb5e0fbe99fb99b56e05130d78ae49f.png

devices-new-4eb5e0fbe99fb99b56e05130d78ae49f.png

155 ms

hong_kong-af339d23a5ecdda214d745ec947765d0.png

hong_kong-af339d23a5ecdda214d745ec947765d0.png

235 ms

korea-bcddf727b66d70e7495f92cd3ba5c49b.png

korea-bcddf727b66d70e7495f92cd3ba5c49b.png

191 ms

malaysia-7522830ede86532c4842df551c6faeb9.png

malaysia-7522830ede86532c4842df551c6faeb9.png

251 ms

singapore-fa11f8bf75d7d896c29f8403edbbdd81.png

singapore-fa11f8bf75d7d896c29f8403edbbdd81.png

312 ms

strait-logo-65c95c22f5f0e75bc29ed3a39a20a12f.png

strait-logo-65c95c22f5f0e75bc29ed3a39a20a12f.png

161 ms

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

4 ms

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

19 ms

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

19 ms

xjAJXh38I15wypJXxuGMBrrIa-7acMAeDBVuclsi6Gc.woff

xjAJXh38I15wypJXxuGMBrrIa-7acMAeDBVuclsi6Gc.woff

19 ms

PRmiXeptR36kaC0GEAetxhbnBKKEOwRKgsHDreGcocg.woff

PRmiXeptR36kaC0GEAetxhbnBKKEOwRKgsHDreGcocg.woff

17 ms

72 ms

footer

footer

121 ms

rum.js

rum.js

47 ms

mag-glass-28f9fbe44976f6e147a8197df79deae0.png

mag-glass-28f9fbe44976f6e147a8197df79deae0.png

341 ms

21 ms

like.php

like.php

47 ms

f99c11d602

f99c11d602

130 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

286 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

300 ms

Accessibility Review

docdoc.sg accessibility score

77

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.

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

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

docdoc.sg 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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

docdoc.sg SEO score

85

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

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 Docdoc.sg 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 Docdoc.sg 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

docdoc.sg

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