Tools & Wizards About Us
stanfordhealthcare.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

stanfordhealthcare.org

Stanford Health Care (SHC) - Stanford Medical Center | Stanford Health Care

Page Load Speed

2.7 sec in total

First Response

52 ms

Resources Loaded

2.3 sec

Page Rendered

365 ms

stanfordhealthcare.org screenshot

About Website

Visit stanfordhealthcare.org now to see the best up-to-date Stanford Health Care content for United States and also check out these interesting facts you probably never knew about stanfordhealthcare.org

Stanford Health Care delivers the highest levels of care and compassion. SHC treats cancer, heart disease, brain disorders, primary care issues, and many more.

Visit stanfordhealthcare.org

Key Findings

We analyzed Stanfordhealthcare.org page load time and found that the first response time was 52 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

stanfordhealthcare.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value3,480 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

stanfordhealthcare.org

52 ms

stanfordhealthcare.org

70 ms

css

124 ms

satelliteLib-b7ed4568546d9bd6ce2b05b772cb152a44e19f76.js

129 ms

main.min.854a479be09ccc83d90f66623857c18c.css

87 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 43% of them (32 requests) were addressed to the original Stanfordhealthcare.org, 14% (10 requests) were made to Sales.liveperson.net and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (618 ms) relates to the external source Smetrics.stanfordhealthcare.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (61%)

Content Size

4.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stanfordhealthcare.org main page is 4.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. 70% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 95.9 kB

  • Original 111.4 kB
  • After minification 69.9 kB
  • After compression 15.5 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 41.6 kB, which is 37% 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 95.9 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 76.9 kB

  • Original 886.4 kB
  • After minification 809.6 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. Stanford Health Care images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.6 MB

  • Original 2.2 MB
  • After minification 2.1 MB
  • After compression 606.1 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.6 MB or 72% of the original size.

CSS Optimization

-84%

Potential reduce by 782.2 kB

  • Original 932.0 kB
  • After minification 922.4 kB
  • After compression 149.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. Stanfordhealthcare.org needs all CSS files to be minified and compressed as it can save up to 782.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stanfordhealthcare.org

stanfordhealthcare.org

52 ms

stanfordhealthcare.org

stanfordhealthcare.org

70 ms

css

css

124 ms

satelliteLib-b7ed4568546d9bd6ce2b05b772cb152a44e19f76.js

satelliteLib-b7ed4568546d9bd6ce2b05b772cb152a44e19f76.js

129 ms

main.min.854a479be09ccc83d90f66623857c18c.css

main.min.854a479be09ccc83d90f66623857c18c.css

87 ms

aggregate.megasearch.min.css

aggregate.megasearch.min.css

65 ms

aggregateapps.min.e0f83a174792e082618fd6717468f8d8.css

aggregateapps.min.e0f83a174792e082618fd6717468f8d8.css

109 ms

aem-optimized.min.5f353cc5ea54882fdb9a4f4aebd1c3f9.js

aem-optimized.min.5f353cc5ea54882fdb9a4f4aebd1c3f9.js

96 ms

js

js

171 ms

main.min.42d636ffbf0cf0a7db452ddab0217308.js

main.min.42d636ffbf0cf0a7db452ddab0217308.js

112 ms

aggregate.megasearch.min.js

aggregate.megasearch.min.js

78 ms

aggregateapps.min.a89aed35010e622f5a533dec5d6d1ce3.js

aggregateapps.min.a89aed35010e622f5a533dec5d6d1ce3.js

103 ms

id

id

26 ms

mbox-contents-9dfad21df2ad9dc47352af0bbd3c855e027f84ad.js

mbox-contents-9dfad21df2ad9dc47352af0bbd3c855e027f84ad.js

89 ms

id

id

44 ms

target.js

target.js

98 ms

ajax

ajax

68 ms

opacity-80-000000.png

opacity-80-000000.png

259 ms

maxresdefault.jpg

maxresdefault.jpg

428 ms

logo-shc.png

logo-shc.png

259 ms

image.png

image.png

268 ms

image.jpg

image.jpg

259 ms

image.jpg

image.jpg

259 ms

image.jpg

image.jpg

259 ms

image.jpg

image.jpg

262 ms

image.jpg

image.jpg

260 ms

image.jpg

image.jpg

258 ms

image.jpg

image.jpg

257 ms

image.png

image.png

261 ms

image.jpg

image.jpg

263 ms

image.jpg

image.jpg

259 ms

image.jpg

image.jpg

263 ms

token.json

token.json

278 ms

chat-2015-40px.png

chat-2015-40px.png

147 ms

spritesheetSHC.png

spritesheetSHC.png

76 ms

masthead-shadow.png

masthead-shadow.png

72 ms

masthead-drawer-shadow-bottom.png

masthead-drawer-shadow-bottom.png

74 ms

opacity-90-f7f7f7.png

opacity-90-f7f7f7.png

74 ms

opacity-70-000000.png

opacity-70-000000.png

73 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

314 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

314 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

445 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

520 ms

s-code-contents-96e481b56652bb075547d08a2d1c93a4fb44d098.js

s-code-contents-96e481b56652bb075547d08a2d1c93a4fb44d098.js

380 ms

gtm.js

gtm.js

595 ms

clinicaltitles.json

clinicaltitles.json

308 ms

api.js

api.js

355 ms

1452554000978.png

1452554000978.png

207 ms

1452554038961.png

1452554038961.png

203 ms

iframe_api

iframe_api

160 ms

s53416850348003

s53416850348003

618 ms

analytics.js

analytics.js

116 ms

gateway.min.js

gateway.min.js

109 ms

le-mtagconfig.js

le-mtagconfig.js

54 ms

recaptcha__en.js

recaptcha__en.js

144 ms

www-widgetapi.js

www-widgetapi.js

128 ms

tag.js

tag.js

85 ms

collect

collect

35 ms

foresee_trigger.js

foresee_trigger.js

42 ms

.jsonp

.jsonp

67 ms

collect

collect

68 ms

mTag.js

mTag.js

47 ms

5 ms

10 ms

transparent.gif

transparent.gif

15 ms

9 ms

8 ms

11 ms

10 ms

9 ms

6 ms

satellite-559d93dd376236057100010c.js

satellite-559d93dd376236057100010c.js

54 ms

frameWorker.html

frameWorker.html

14 ms

foresee_frame_controller.js

foresee_frame_controller.js

14 ms

Accessibility Review

stanfordhealthcare.org accessibility score

86

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

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

stanfordhealthcare.org best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

stanfordhealthcare.org SEO score

99

Search Engine Optimization Advices

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanfordhealthcare.org 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 Stanfordhealthcare.org main page’s claimed encoding is iso-8859-1. 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

stanfordhealthcare.org

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