Tools & Wizards About Us
sites.wustl.edu screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% 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

sites.wustl.edu

Home | WashU Sites | Washington University in St. Louis

Page Load Speed

2.1 sec in total

First Response

131 ms

Resources Loaded

1.8 sec

Page Rendered

182 ms

sites.wustl.edu screenshot

About Website

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

Simple, free self-service web hosting. As a member of the WashU Sites community, you'll have access to tools and resources to share the importan...

Visit sites.wustl.edu

Key Findings

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

Performance Metrics

sites.wustl.edu performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

sites.wustl.edu

131 ms

sites.wustl.edu

461 ms

style.min.css

63 ms

style-ppi-single.css

123 ms

style.min.css

185 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 85% of them (72 requests) were addressed to the original Sites.wustl.edu, 7% (6 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Bpb-us-w2.wpmucdn.com. The less responsive or slowest element that took the longest time to load (733 ms) belongs to the original domain Sites.wustl.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.3 kB (15%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 55.5 kB

  • Original 75.3 kB
  • After minification 74.6 kB
  • After compression 19.8 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 55.5 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 10.8 kB

  • Original 292.2 kB
  • After minification 281.4 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. Sites Wu St L images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 144.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 878.5 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 144.9 kB or 14% of the original size.

CSS Optimization

-17%

Potential reduce by 24.0 kB

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

Requests Breakdown

Number of requests can be reduced by 69 (90%)

Requests Now

77

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sites.wustl.edu

sites.wustl.edu

131 ms

sites.wustl.edu

sites.wustl.edu

461 ms

style.min.css

style.min.css

63 ms

style-ppi-single.css

style-ppi-single.css

123 ms

style.min.css

style.min.css

185 ms

style.min.css

style.min.css

237 ms

style.min.css

style.min.css

246 ms

style.min.css

style.min.css

251 ms

style.min.css

style.min.css

258 ms

style.min.css

style.min.css

265 ms

blocks.style.build.css

blocks.style.build.css

270 ms

style.css

style.css

352 ms

css

css

35 ms

dashicons.min.css

dashicons.min.css

308 ms

lodash.min.js

lodash.min.js

371 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

317 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

328 ms

wp-polyfill.min.js

wp-polyfill.min.js

398 ms

react.min.js

react.min.js

369 ms

react-dom.min.js

react-dom.min.js

500 ms

dom-ready.min.js

dom-ready.min.js

392 ms

hooks.min.js

hooks.min.js

408 ms

i18n.min.js

i18n.min.js

429 ms

a11y.min.js

a11y.min.js

431 ms

url.min.js

url.min.js

455 ms

api-fetch.min.js

api-fetch.min.js

462 ms

blob.min.js

blob.min.js

464 ms

autop.min.js

autop.min.js

489 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

490 ms

deprecated.min.js

deprecated.min.js

519 ms

dom.min.js

dom.min.js

525 ms

escape-html.min.js

escape-html.min.js

520 ms

element.min.js

element.min.js

549 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

550 ms

keycodes.min.js

keycodes.min.js

558 ms

priority-queue.min.js

priority-queue.min.js

582 ms

compose.min.js

compose.min.js

577 ms

private-apis.min.js

private-apis.min.js

589 ms

js

js

73 ms

redux-routine.min.js

redux-routine.min.js

607 ms

data.min.js

data.min.js

557 ms

html-entities.min.js

html-entities.min.js

506 ms

rich-text.min.js

rich-text.min.js

458 ms

shortcode.min.js

shortcode.min.js

419 ms

blocks.min.js

blocks.min.js

481 ms

moment.min.js

moment.min.js

429 ms

date.min.js

date.min.js

487 ms

primitives.min.js

primitives.min.js

422 ms

warning.min.js

warning.min.js

431 ms

components.min.js

components.min.js

733 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

422 ms

commands.min.js

commands.min.js

421 ms

notices.min.js

notices.min.js

392 ms

preferences-persistence.min.js

preferences-persistence.min.js

424 ms

preferences.min.js

preferences.min.js

413 ms

style-engine.min.js

style-engine.min.js

411 ms

token-list.min.js

token-list.min.js

408 ms

wordcount.min.js

wordcount.min.js

406 ms

block-editor.min.js

block-editor.min.js

626 ms

core-data.min.js

core-data.min.js

430 ms

ppi-list.js

ppi-list.js

408 ms

server-side-render.min.js

server-side-render.min.js

407 ms

ppi-single.js

ppi-single.js

406 ms

jquery.min.js

jquery.min.js

435 ms

jquery-migrate.min.js

jquery-migrate.min.js

435 ms

underscore.min.js

underscore.min.js

421 ms

backbone.min.js

backbone.min.js

409 ms

api-request.min.js

api-request.min.js

465 ms

wp-api.min.js

wp-api.min.js

460 ms

frontend.js

frontend.js

437 ms

front.js

front.js

439 ms

scripts.js

scripts.js

488 ms

gtm.js

gtm.js

81 ms

search.svg

search.svg

74 ms

close.svg

close.svg

75 ms

sites-hero-2cwjro1-1sogxwf.jpg

sites-hero-2cwjro1-1sogxwf.jpg

52 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

39 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

49 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

56 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

64 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

63 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

64 ms

rich-functionality-icon-2fg9oxq.png

rich-functionality-icon-2fg9oxq.png

36 ms

tools-icon-2kf1sep.png

tools-icon-2kf1sep.png

38 ms

WordPress-icon-2gd917j.png

WordPress-icon-2gd917j.png

42 ms

Accessibility Review

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

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

sites.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 Sites.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 Sites.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

sites.wustl.edu

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