Tools & Wizards About Us
emedicine.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

emedicine.com

Diseases & Conditions - Medscape Reference

Page Load Speed

46.1 sec in total

First Response

396 ms

Resources Loaded

38.8 sec

Page Rendered

6.9 sec

emedicine.com screenshot

About Website

Welcome to emedicine.com homepage info - get ready to check Emedicine best content right away, or after learning these important things about emedicine.com

The eMedicine point-of-care clinical reference features up-to-date, searchable, peer-reviewed medical articles organized in specialty-focused textbooks, and is continuously updated with practice-chang...

Visit emedicine.com

Key Findings

We analyzed Emedicine.com page load time and found that the first response time was 396 ms and then it took 45.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

emedicine.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value5,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.092

92/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

emedicine.medscape.com

396 ms

global-desktop.css

1081 ms

jquery-desktop.js

1465 ms

global-desktop.js

1465 ms

global-lib-bottom.js

1077 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Emedicine.com, 9% (9 requests) were made to Emedicine.medscape.com and 4% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Fw.adsafeprotected.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (73%)

Content Size

3.0 MB

After Optimization

810.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Emedicine.com main page is 3.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 53.0 kB

  • Original 71.2 kB
  • After minification 63.0 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 8.1 kB, which is 11% 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 53.0 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 13.6 kB

  • Original 161.1 kB
  • After minification 147.5 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. Emedicine images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.7 MB

  • Original 2.3 MB
  • After minification 1.8 MB
  • After compression 584.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 1.7 MB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 374.3 kB

  • Original 434.3 kB
  • After minification 339.8 kB
  • After compression 59.9 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. Emedicine.com needs all CSS files to be minified and compressed as it can save up to 374.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (68%)

Requests Now

94

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

emedicine.medscape.com

emedicine.medscape.com

396 ms

global-desktop.css

global-desktop.css

1081 ms

jquery-desktop.js

jquery-desktop.js

1465 ms

global-desktop.js

global-desktop.js

1465 ms

global-lib-bottom.js

global-lib-bottom.js

1077 ms

medscape-library.js

medscape-library.js

1077 ms

mbox-reduction.js

mbox-reduction.js

1453 ms

ref-desktop.css

ref-desktop.css

1626 ms

ref-desktop.js

ref-desktop.js

1599 ms

medscape-core.js

medscape-core.js

1599 ms

profads2.js

profads2.js

1596 ms

conversion_async.js

conversion_async.js

79 ms

medscape-vt.js

medscape-vt.js

1561 ms

build-ad-tag.js

build-ad-tag.js

1563 ms

cp.js

cp.js

1617 ms

medscape-site.js

medscape-site.js

1616 ms

eu-cookie.css

eu-cookie.css

1617 ms

bi_medscape.js

bi_medscape.js

1656 ms

cc.js

cc.js

32 ms

css

css

1068 ms

global-print.css

global-print.css

562 ms

mbox.js

mbox.js

161 ms

standard

standard

189 ms

mscp-logo.png

mscp-logo.png

364 ms

ref-logged-out-all-11182015.png

ref-logged-out-all-11182015.png

427 ms

standard

standard

93 ms

gpt.js

gpt.js

532 ms

text_advertisement_top.gif

text_advertisement_top.gif

60 ms

ProximaNova-Bold-webfont.woff

ProximaNova-Bold-webfont.woff

602 ms

ProximaNova-Light-webfont.woff

ProximaNova-Light-webfont.woff

601 ms

ProximaNova-Reg-webfont.woff

ProximaNova-Reg-webfont.woff

24 ms

pubads_impl_147.js

pubads_impl_147.js

775 ms

bg-header-dots.png

bg-header-dots.png

124 ms

icon-morelink-gt.png

icon-morelink-gt.png

313 ms

icon-arrow-carousel-left.png

icon-arrow-carousel-left.png

296 ms

icon-arrow-carousel-right.png

icon-arrow-carousel-right.png

296 ms

ProximaNova-Sbold-webfont.woff

ProximaNova-Sbold-webfont.woff

226 ms

container.html

container.html

125 ms

fbevents.js

fbevents.js

207 ms

vptrack_iframe.html

vptrack_iframe.html

228 ms

_Incapsula_Resource

_Incapsula_Resource

139 ms

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf

1640 ms

490389451150319

490389451150319

355 ms

rd

rd

196 ms

_Incapsula_Resource

_Incapsula_Resource

319 ms

dest5.html

dest5.html

460 ms

id

id

404 ms

id

id

4247 ms

ibs:dpid=411&dpuuid=Wa8PuQAAAc668IkB

ibs:dpid=411&dpuuid=Wa8PuQAAAc668IkB

4844 ms

_Incapsula_Resource

_Incapsula_Resource

4802 ms

merge-desktop-l.json

merge-desktop-l.json

4364 ms

merge-desktop-r.json

merge-desktop-r.json

4425 ms

us

us

4022 ms

ss-identifying-lesions.jpg

ss-identifying-lesions.jpg

3989 ms

getvisitorcontinent

getvisitorcontinent

3349 ms

ads

ads

1501 ms

profession=Anonymous

profession=Anonymous

2003 ms

1679 ms

measure.min.js

measure.min.js

1657 ms

s87496041751001

s87496041751001

1384 ms

ss-herpes_simplex_viruses.jpg

ss-herpes_simplex_viruses.jpg

1241 ms

ss-school.jpg

ss-school.jpg

1223 ms

ss-vaccinations.jpg

ss-vaccinations.jpg

1719 ms

ss-pediatric-brain-tumors.jpg

ss-pediatric-brain-tumors.jpg

1371 ms

ss-thyroid-cancer.jpg

ss-thyroid-cancer.jpg

1223 ms

ss-backpain.jpg

ss-backpain.jpg

1499 ms

ss-pediatric-sports-injuries.jpg

ss-pediatric-sports-injuries.jpg

1240 ms

ss-scuba-diving-injuries.jpg

ss-scuba-diving-injuries.jpg

1238 ms

ss-cerebrovascular-accident.jpg

ss-cerebrovascular-accident.jpg

1165 ms

ss-drug-approvals-2017-midyear.jpg

ss-drug-approvals-2017-midyear.jpg

1038 ms

ss-ci-pedi.jpg

ss-ci-pedi.jpg

1165 ms

ss-miss-findings-radiographs.jpg

ss-miss-findings-radiographs.jpg

1165 ms

ss-venomous-spiders.jpg

ss-venomous-spiders.jpg

984 ms

ss-gunshot-wounds.jpg

ss-gunshot-wounds.jpg

1112 ms

ss-myopathies.jpg

ss-myopathies.jpg

1113 ms

2467 ms

4151 ms

_Incapsula_Resource

_Incapsula_Resource

1477 ms

collapse-ad.js

collapse-ad.js

1196 ms

osd_listener.js

osd_listener.js

2488 ms

osd.js

osd.js

1865 ms

ad-label-switch.js

ad-label-switch.js

3851 ms

click

click

3476 ms

moatad.js

moatad.js

3476 ms

click

click

5652 ms

textlink-ads.jpg

textlink-ads.jpg

398 ms

textlink-ads.jpg

textlink-ads.jpg

355 ms

a.js

a.js

2084 ms

s82670238302089

s82670238302089

570 ms

sca.17.4.1.js

sca.17.4.1.js

2387 ms

dt

dt

2361 ms

activeview

activeview

1002 ms

dt

dt

1893 ms

activeview

activeview

1701 ms

click

click

3159 ms

click

click

2491 ms

tags

tags

3492 ms

dt

dt

3947 ms

300x250.jpg

300x250.jpg

5093 ms

lidar.js

lidar.js

2010 ms

d5qAyLYU.js

d5qAyLYU.js

1799 ms

pixel.gif

pixel.gif

5014 ms

jload

jload

2267 ms

9im3l02I.html

9im3l02I.html

883 ms

Accessibility Review

emedicine.com accessibility score

91

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

emedicine.com best practices score

62

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

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

emedicine.com SEO score

89

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emedicine.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Emedicine.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

emedicine.com

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