Tools & Wizards About Us
email.wustl.edu screenshot

Report Summary

  • 29

    Performance

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

email.wustl.edu

Email & Calendaring - WUSTL Information Technology

Page Load Speed

975 ms in total

First Response

146 ms

Resources Loaded

661 ms

Page Rendered

168 ms

email.wustl.edu screenshot

About Website

Visit email.wustl.edu now to see the best up-to-date Email WUSTL content for United States and also check out these interesting facts you probably never knew about email.wustl.edu

The Email & Calendaring service, powered by Office 365 provides reliable and cost-effective collaboration services. It is useful for email communication, calendaring, IM/video conferencing and access ...

Visit email.wustl.edu

Key Findings

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

Performance Metrics

email.wustl.edu performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

email.wustl.edu

146 ms

72 ms

js

111 ms

leaflet.min.css

16 ms

style.min.css

19 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Email.wustl.edu, 90% (84 requests) were made to It.wustl.edu and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (146 ms) belongs to the original domain Email.wustl.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.9 kB (24%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Email.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. 80% 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 75.8 kB

  • Original 100.3 kB
  • After minification 99.1 kB
  • After compression 24.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. 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 75.8 kB or 76% of the original size.

JavaScript Optimization

-15%

Potential reduce by 165.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 931.0 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 165.4 kB or 15% of the original size.

CSS Optimization

-43%

Potential reduce by 93.7 kB

  • Original 218.1 kB
  • After minification 217.8 kB
  • After compression 124.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. Email.wustl.edu needs all CSS files to be minified and compressed as it can save up to 93.7 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (92%)

Requests Now

85

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

email.wustl.edu

email.wustl.edu

146 ms

72 ms

js

js

111 ms

leaflet.min.css

leaflet.min.css

16 ms

style.min.css

style.min.css

19 ms

style-ppi-single.css

style-ppi-single.css

27 ms

style.min.css

style.min.css

23 ms

style.min.css

style.min.css

29 ms

style.min.css

style.min.css

27 ms

style.min.css

style.min.css

27 ms

style.min.css

style.min.css

32 ms

blocks.style.build.css

blocks.style.build.css

35 ms

swipebox.min.css

swipebox.min.css

33 ms

dashicons.min.css

dashicons.min.css

35 ms

fullcalendar.min.css

fullcalendar.min.css

37 ms

style.css

style.css

38 ms

style.css

style.css

39 ms

css

css

49 ms

ytprefs.min.css

ytprefs.min.css

45 ms

frontend-gtag.min.js

frontend-gtag.min.js

53 ms

lodash.min.js

lodash.min.js

47 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

46 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

45 ms

wp-polyfill.min.js

wp-polyfill.min.js

64 ms

react.min.js

react.min.js

64 ms

react-dom.min.js

react-dom.min.js

79 ms

dom-ready.min.js

dom-ready.min.js

77 ms

hooks.min.js

hooks.min.js

85 ms

i18n.min.js

i18n.min.js

78 ms

a11y.min.js

a11y.min.js

87 ms

url.min.js

url.min.js

86 ms

api-fetch.min.js

api-fetch.min.js

89 ms

blob.min.js

blob.min.js

89 ms

autop.min.js

autop.min.js

87 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

89 ms

deprecated.min.js

deprecated.min.js

90 ms

dom.min.js

dom.min.js

94 ms

escape-html.min.js

escape-html.min.js

91 ms

element.min.js

element.min.js

92 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

91 ms

keycodes.min.js

keycodes.min.js

82 ms

priority-queue.min.js

priority-queue.min.js

79 ms

compose.min.js

compose.min.js

76 ms

private-apis.min.js

private-apis.min.js

76 ms

redux-routine.min.js

redux-routine.min.js

76 ms

data.min.js

data.min.js

70 ms

html-entities.min.js

html-entities.min.js

72 ms

shortcode.min.js

shortcode.min.js

73 ms

blocks.min.js

blocks.min.js

74 ms

moment.min.js

moment.min.js

73 ms

date.min.js

date.min.js

70 ms

primitives.min.js

primitives.min.js

79 ms

rich-text.min.js

rich-text.min.js

74 ms

warning.min.js

warning.min.js

73 ms

components.min.js

components.min.js

94 ms

keyboard-shortcuts.min.js

keyboard-shortcuts.min.js

72 ms

commands.min.js

commands.min.js

73 ms

notices.min.js

notices.min.js

68 ms

preferences-persistence.min.js

preferences-persistence.min.js

56 ms

preferences.min.js

preferences.min.js

66 ms

style-engine.min.js

style-engine.min.js

41 ms

token-list.min.js

token-list.min.js

64 ms

wordcount.min.js

wordcount.min.js

60 ms

block-editor.min.js

block-editor.min.js

62 ms

core-data.min.js

core-data.min.js

57 ms

ppi-list.js

ppi-list.js

56 ms

server-side-render.min.js

server-side-render.min.js

57 ms

ppi-single.js

ppi-single.js

55 ms

jquery.min.js

jquery.min.js

56 ms

jquery-migrate.min.js

jquery-migrate.min.js

68 ms

underscore.min.js

underscore.min.js

71 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

74 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

73 ms

front.js

front.js

74 ms

functions.js

functions.js

76 ms

ytprefs.min.js

ytprefs.min.js

74 ms

backbone.min.js

backbone.min.js

86 ms

api-request.min.js

api-request.min.js

87 ms

wp-api.min.js

wp-api.min.js

87 ms

frontend.js

frontend.js

92 ms

scripts.js

scripts.js

90 ms

fitvids.min.js

fitvids.min.js

89 ms

search.svg

search.svg

29 ms

close.svg

close.svg

30 ms

linkedin.svg

linkedin.svg

29 ms

youtube.svg

youtube.svg

27 ms

81 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

18 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

23 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

39 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

44 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

45 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

58 ms

Accessibility Review

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

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

email.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 Email.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 Email.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

email.wustl.edu

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: