1 sec in total
132 ms
690 ms
190 ms
Click here to check amazing Go WUSTL content for United States. Otherwise, check out these important facts you probably never knew about go.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 go.wustl.eduWe analyzed Go.wustl.edu page load time and found that the first response time was 132 ms and then it took 880 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
go.wustl.edu performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value10.9 s
0/100
25%
Value10.0 s
9/100
10%
Value1,040 ms
25/100
30%
Value0.002
100/100
15%
Value12.5 s
14/100
10%
132 ms
112 ms
112 ms
18 ms
31 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Go.wustl.edu, 94% (82 requests) were made to It.wustl.edu and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (132 ms) belongs to the original domain Go.wustl.edu.
Page size can be reduced by 306.3 kB (22%)
1.4 MB
1.1 MB
In fact, the total size of Go.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.
Potential reduce by 74.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 74.8 kB or 75% of the original size.
Potential reduce by 206.7 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 206.7 kB or 18% of the original size.
Potential reduce by 24.7 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. Go.wustl.edu needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 17% of the original size.
Number of requests can be reduced by 76 (92%)
83
7
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go 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 63 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
go.wustl.edu
132 ms
112 ms
js
112 ms
leaflet.min.css
18 ms
style.min.css
31 ms
style-ppi-single.css
39 ms
style.min.css
39 ms
style.min.css
44 ms
style.min.css
37 ms
style.min.css
42 ms
blocks.style.build.css
48 ms
swipebox.min.css
65 ms
dashicons.min.css
60 ms
fullcalendar.min.css
57 ms
style.css
62 ms
style.css
48 ms
css
65 ms
ytprefs.min.css
54 ms
frontend-gtag.min.js
63 ms
lodash.min.js
69 ms
wp-polyfill-inert.min.js
69 ms
regenerator-runtime.min.js
83 ms
wp-polyfill.min.js
79 ms
react.min.js
80 ms
react-dom.min.js
81 ms
dom-ready.min.js
82 ms
hooks.min.js
80 ms
i18n.min.js
98 ms
a11y.min.js
96 ms
url.min.js
120 ms
api-fetch.min.js
121 ms
blob.min.js
122 ms
autop.min.js
121 ms
block-serialization-default-parser.min.js
123 ms
deprecated.min.js
122 ms
dom.min.js
123 ms
escape-html.min.js
124 ms
element.min.js
125 ms
is-shallow-equal.min.js
124 ms
keycodes.min.js
123 ms
priority-queue.min.js
122 ms
compose.min.js
105 ms
private-apis.min.js
102 ms
redux-routine.min.js
99 ms
data.min.js
101 ms
html-entities.min.js
96 ms
shortcode.min.js
94 ms
blocks.min.js
96 ms
moment.min.js
92 ms
date.min.js
88 ms
primitives.min.js
114 ms
rich-text.min.js
83 ms
warning.min.js
84 ms
components.min.js
95 ms
keyboard-shortcuts.min.js
95 ms
notices.min.js
77 ms
preferences-persistence.min.js
78 ms
preferences.min.js
79 ms
style-engine.min.js
78 ms
token-list.min.js
76 ms
wordcount.min.js
75 ms
block-editor.min.js
64 ms
core-data.min.js
62 ms
ppi-list.js
61 ms
server-side-render.min.js
62 ms
ppi-single.js
40 ms
jquery.min.js
40 ms
jquery-migrate.min.js
40 ms
underscore.min.js
40 ms
jquery.swipebox.min.js
39 ms
infinite-scroll.pkgd.min.js
38 ms
front.js
41 ms
functions.js
38 ms
ytprefs.min.js
38 ms
backbone.min.js
36 ms
api-request.min.js
37 ms
wp-api.min.js
36 ms
frontend.js
35 ms
scripts.js
34 ms
fitvids.min.js
98 ms
26 ms
search.svg
91 ms
close.svg
38 ms
linkedin.svg
40 ms
youtube.svg
38 ms
font
23 ms
font
30 ms
go.wustl.edu accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
go.wustl.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
go.wustl.edu SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Go.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 Go.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.
go.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: