Tools & Wizards About Us
hematology.im.wustl.edu screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hematology.im.wustl.edu

Division of Hematology | Washington University in St. Louis

Page Load Speed

1.9 sec in total

First Response

140 ms

Resources Loaded

1.4 sec

Page Rendered

401 ms

hematology.im.wustl.edu screenshot

About Website

Welcome to hematology.im.wustl.edu homepage info - get ready to check Hematology Im Wu St L best content for United States right away, or after learning these important things about hematology.im.wustl.edu

Visit hematology.im.wustl.edu

Key Findings

We analyzed Hematology.im.wustl.edu page load time and found that the first response time was 140 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

hematology.im.wustl.edu performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

hematology.im.wustl.edu

140 ms

hematology.wustl.edu

269 ms

js

92 ms

style.min.css

76 ms

style-ppi-single.css

121 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hematology.im.wustl.edu, 89% (79 requests) were made to Hematology.wustl.edu and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (389 ms) relates to the external source Hematology.wustl.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 488.2 kB (19%)

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hematology.im.wustl.edu main page is 2.5 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 70.2 kB

  • Original 92.9 kB
  • After minification 92.0 kB
  • After compression 22.7 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 70.2 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 10.5 kB

  • Original 986.1 kB
  • After minification 975.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. Hematology Im Wu St L images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 355.4 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 910.3 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 355.4 kB or 28% of the original size.

CSS Optimization

-32%

Potential reduce by 52.2 kB

  • Original 164.6 kB
  • After minification 164.6 kB
  • After compression 112.4 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. Hematology.im.wustl.edu needs all CSS files to be minified and compressed as it can save up to 52.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (83%)

Requests Now

81

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hematology.im.wustl.edu

hematology.im.wustl.edu

140 ms

hematology.wustl.edu

hematology.wustl.edu

269 ms

js

js

92 ms

style.min.css

style.min.css

76 ms

style-ppi-single.css

style-ppi-single.css

121 ms

style.min.css

style.min.css

131 ms

style.min.css

style.min.css

142 ms

style.min.css

style.min.css

121 ms

style.min.css

style.min.css

121 ms

style.min.css

style.min.css

123 ms

blocks.style.build.css

blocks.style.build.css

136 ms

style.css

style.css

168 ms

css

css

55 ms

dashicons.min.css

dashicons.min.css

202 ms

frontend-gtag.js

frontend-gtag.js

146 ms

lodash.min.js

lodash.min.js

190 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

159 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

163 ms

wp-polyfill.min.js

wp-polyfill.min.js

231 ms

react.min.js

react.min.js

189 ms

react-dom.min.js

react-dom.min.js

261 ms

dom-ready.min.js

dom-ready.min.js

229 ms

hooks.min.js

hooks.min.js

252 ms

i18n.min.js

i18n.min.js

253 ms

a11y.min.js

a11y.min.js

255 ms

url.min.js

url.min.js

254 ms

api-fetch.min.js

api-fetch.min.js

256 ms

blob.min.js

blob.min.js

256 ms

autop.min.js

autop.min.js

257 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

273 ms

deprecated.min.js

deprecated.min.js

274 ms

dom.min.js

dom.min.js

279 ms

escape-html.min.js

escape-html.min.js

278 ms

element.min.js

element.min.js

281 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

284 ms

keycodes.min.js

keycodes.min.js

299 ms

priority-queue.min.js

priority-queue.min.js

301 ms

compose.min.js

compose.min.js

307 ms

private-apis.min.js

private-apis.min.js

311 ms

redux-routine.min.js

redux-routine.min.js

285 ms

data.min.js

data.min.js

246 ms

html-entities.min.js

html-entities.min.js

220 ms

shortcode.min.js

shortcode.min.js

223 ms

blocks.min.js

blocks.min.js

251 ms

moment.min.js

moment.min.js

228 ms

date.min.js

date.min.js

285 ms

primitives.min.js

primitives.min.js

212 ms

rich-text.min.js

rich-text.min.js

227 ms

warning.min.js

warning.min.js

234 ms

components.min.js

components.min.js

389 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

225 ms

commands.min.js

commands.min.js

228 ms

notices.min.js

notices.min.js

214 ms

preferences-persistence.min.js

preferences-persistence.min.js

222 ms

preferences.min.js

preferences.min.js

194 ms

style-engine.min.js

style-engine.min.js

180 ms

token-list.min.js

token-list.min.js

187 ms

wordcount.min.js

wordcount.min.js

192 ms

block-editor.min.js

block-editor.min.js

360 ms

core-data.min.js

core-data.min.js

198 ms

ppi-list.js

ppi-list.js

205 ms

server-side-render.min.js

server-side-render.min.js

215 ms

ppi-single.js

ppi-single.js

222 ms

jquery.min.js

jquery.min.js

230 ms

jquery-migrate.min.js

jquery-migrate.min.js

218 ms

underscore.min.js

underscore.min.js

230 ms

backbone.min.js

backbone.min.js

239 ms

api-request.min.js

api-request.min.js

239 ms

wp-api.min.js

wp-api.min.js

242 ms

frontend.js

frontend.js

256 ms

scripts.js

scripts.js

265 ms

twitter-logo-white.png

twitter-logo-white.png

232 ms

search.svg

search.svg

94 ms

close.svg

close.svg

95 ms

Home-1440x550.png

Home-1440x550.png

243 ms

Patient-Care-icon.png

Patient-Care-icon.png

93 ms

Research-icon.png

Research-icon.png

96 ms

Education-icon.png

Education-icon.png

95 ms

amy-zhou-1.jfif

amy-zhou-1.jfif

99 ms

Evan-Garber-e1715889291536-edited-1.jpg

Evan-Garber-e1715889291536-edited-1.jpg

99 ms

Sickle-Cell-Treatment-Center.jpg

Sickle-Cell-Treatment-Center.jpg

129 ms

twitter.svg

twitter.svg

96 ms

SCCWUPBJC_Horiz_REV-RGB_22-1024x105.png

SCCWUPBJC_Horiz_REV-RGB_22-1024x105.png

99 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

35 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

44 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

55 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

63 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

63 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

84 ms

Accessibility Review

hematology.im.wustl.edu accessibility score

92

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

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hematology.im.wustl.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

hematology.im.wustl.edu SEO score

93

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

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 Hematology.im.wustl.edu 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 Hematology.im.wustl.edu 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

hematology.im.wustl.edu

Open Graph description is not detected on the main page of Hematology Im Wu St L. 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: