Tools & Wizards About Us
vascularsurg.wustl.edu screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

vascularsurg.wustl.edu

Home | Section of Vascular Surgery | Washington University in St. Louis

Page Load Speed

2.8 sec in total

First Response

136 ms

Resources Loaded

2.5 sec

Page Rendered

160 ms

vascularsurg.wustl.edu screenshot

About Website

Visit vascularsurg.wustl.edu now to see the best up-to-date Vascular Surg Wu St L content for United States and also check out these interesting facts you probably never knew about vascularsurg.wustl.edu

Washington University Vascular Surgery The Vascular Surgery Service at Washington University was started in 1983 – the first year that the Americ...

Visit vascularsurg.wustl.edu

Key Findings

We analyzed Vascularsurg.wustl.edu page load time and found that the first response time was 136 ms and then it took 2.6 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

vascularsurg.wustl.edu performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

vascularsurg.wustl.edu

136 ms

vascularsurgery.wustl.edu

420 ms

style.min.css

67 ms

style-ppi-single.css

147 ms

mediaelementplayer-legacy.min.css

212 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vascularsurg.wustl.edu, 88% (73 requests) were made to Vascularsurgery.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 (658 ms) relates to the external source Vascularsurgery.wustl.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.5 kB (17%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vascularsurg.wustl.edu main page is 1.4 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 65.8 kB

  • Original 87.4 kB
  • After minification 86.8 kB
  • After compression 21.6 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 65.8 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.5 kB

  • Original 144.3 kB
  • After minification 142.8 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. Vascular Surg Wu St L images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 149.6 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 907.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 149.6 kB or 14% of the original size.

CSS Optimization

-17%

Potential reduce by 23.6 kB

  • Original 139.7 kB
  • After minification 139.7 kB
  • After compression 116.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. Vascularsurg.wustl.edu needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vascular Surg 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 57 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vascularsurg.wustl.edu

vascularsurg.wustl.edu

136 ms

vascularsurgery.wustl.edu

vascularsurgery.wustl.edu

420 ms

style.min.css

style.min.css

67 ms

style-ppi-single.css

style-ppi-single.css

147 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

212 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

255 ms

style.min.css

style.min.css

337 ms

style.min.css

style.min.css

278 ms

style.min.css

style.min.css

285 ms

style.min.css

style.min.css

288 ms

style.min.css

style.min.css

286 ms

blocks.style.build.css

blocks.style.build.css

314 ms

style.css

style.css

343 ms

css

css

35 ms

dashicons.min.css

dashicons.min.css

408 ms

lodash.min.js

lodash.min.js

417 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

353 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

374 ms

wp-polyfill.min.js

wp-polyfill.min.js

459 ms

react.min.js

react.min.js

406 ms

react-dom.min.js

react-dom.min.js

539 ms

dom-ready.min.js

dom-ready.min.js

434 ms

hooks.min.js

hooks.min.js

474 ms

i18n.min.js

i18n.min.js

474 ms

a11y.min.js

a11y.min.js

474 ms

url.min.js

url.min.js

494 ms

api-fetch.min.js

api-fetch.min.js

521 ms

blob.min.js

blob.min.js

533 ms

autop.min.js

autop.min.js

535 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

537 ms

deprecated.min.js

deprecated.min.js

555 ms

dom.min.js

dom.min.js

582 ms

escape-html.min.js

escape-html.min.js

596 ms

element.min.js

element.min.js

599 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

600 ms

keycodes.min.js

keycodes.min.js

601 ms

priority-queue.min.js

priority-queue.min.js

613 ms

compose.min.js

compose.min.js

644 ms

private-apis.min.js

private-apis.min.js

658 ms

redux-routine.min.js

redux-routine.min.js

600 ms

data.min.js

data.min.js

525 ms

html-entities.min.js

html-entities.min.js

461 ms

shortcode.min.js

shortcode.min.js

426 ms

blocks.min.js

blocks.min.js

494 ms

moment.min.js

moment.min.js

446 ms

date.min.js

date.min.js

515 ms

primitives.min.js

primitives.min.js

451 ms

rich-text.min.js

rich-text.min.js

423 ms

warning.min.js

warning.min.js

401 ms

components.min.js

components.min.js

644 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

456 ms

commands.min.js

commands.min.js

435 ms

notices.min.js

notices.min.js

393 ms

preferences-persistence.min.js

preferences-persistence.min.js

424 ms

preferences.min.js

preferences.min.js

437 ms

style-engine.min.js

style-engine.min.js

429 ms

token-list.min.js

token-list.min.js

394 ms

wordcount.min.js

wordcount.min.js

395 ms

block-editor.min.js

block-editor.min.js

615 ms

core-data.min.js

core-data.min.js

509 ms

ppi-list.js

ppi-list.js

438 ms

server-side-render.min.js

server-side-render.min.js

410 ms

ppi-single.js

ppi-single.js

400 ms

jquery.min.js

jquery.min.js

526 ms

jquery-migrate.min.js

jquery-migrate.min.js

460 ms

underscore.min.js

underscore.min.js

455 ms

backbone.min.js

backbone.min.js

490 ms

api-request.min.js

api-request.min.js

474 ms

wp-api.min.js

wp-api.min.js

463 ms

frontend.js

frontend.js

465 ms

front.js

front.js

574 ms

scripts.js

scripts.js

575 ms

search.svg

search.svg

80 ms

close.svg

close.svg

81 ms

135 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

24 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

30 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

50 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

57 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

75 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

57 ms

Vascular-home-page-photo-1a4ins2-350x233.jpg

Vascular-home-page-photo-1a4ins2-350x233.jpg

465 ms

Sanchez-2c3pp5u-1440x400.jpg

Sanchez-2c3pp5u-1440x400.jpg

489 ms

Accessibility Review

vascularsurg.wustl.edu accessibility score

93

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.

Best Practices

vascularsurg.wustl.edu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

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

vascularsurg.wustl.edu SEO score

100

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

vascularsurg.wustl.edu

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