Tools & Wizards About Us
gwbweb.wustl.edu screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

gwbweb.wustl.edu

Brown School | Brown School at Washington University in St. Louis

Page Load Speed

2.3 sec in total

First Response

107 ms

Resources Loaded

2 sec

Page Rendered

193 ms

gwbweb.wustl.edu screenshot

About Website

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

The Brown School at Washington University in St. Louis. Advancing social work and public health.

Visit gwbweb.wustl.edu

Key Findings

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

gwbweb.wustl.edu performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.827

4/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

gwbweb.wustl.edu

107 ms

brownschool.wustl.edu

110 ms

Home.aspx

270 ms

css

40 ms

css

55 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gwbweb.wustl.edu, 83% (49 requests) were made to Brownschool.wustl.edu and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (625 ms) relates to the external source Brownschool.wustl.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 696.0 kB (28%)

Content Size

2.5 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gwbweb.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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 79.5 kB

  • Original 101.1 kB
  • After minification 97.0 kB
  • After compression 21.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 79.5 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 56.1 kB

  • Original 1.7 MB
  • After minification 1.6 MB

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. Gwbweb Wu St L images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 324.8 kB

  • Original 436.1 kB
  • After minification 416.3 kB
  • After compression 111.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 324.8 kB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 235.6 kB

  • Original 270.4 kB
  • After minification 191.0 kB
  • After compression 34.8 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. Gwbweb.wustl.edu needs all CSS files to be minified and compressed as it can save up to 235.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (36%)

Requests Now

53

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gwbweb.wustl.edu

gwbweb.wustl.edu

107 ms

brownschool.wustl.edu

brownschool.wustl.edu

110 ms

Home.aspx

Home.aspx

270 ms

css

css

40 ms

css

css

55 ms

controls.css

controls.css

114 ms

htmleditorstyles.css

htmleditorstyles.css

99 ms

corev4.css

corev4.css

373 ms

general.css

general.css

120 ms

newsprint.css

newsprint.css

95 ms

homepage.css

homepage.css

123 ms

home_slideshow.css

home_slideshow.css

134 ms

css

css

60 ms

jquery.min.js

jquery.min.js

84 ms

jquery.SPServices-0.7.1a.min.js

jquery.SPServices-0.7.1a.min.js

200 ms

jquery.color.js

jquery.color.js

150 ms

slideshow.js

slideshow.js

158 ms

WebResource.axd

WebResource.axd

106 ms

ScriptResource.axd

ScriptResource.axd

116 ms

blank.js

blank.js

132 ms

init.js

init.js

206 ms

ScriptResource.axd

ScriptResource.axd

72 ms

ScriptResource.axd

ScriptResource.axd

41 ms

fgimg.png

fgimg.png

71 ms

washULogo.gif

washULogo.gif

65 ms

go.jpg

go.jpg

68 ms

WebResource.axd

WebResource.axd

69 ms

WebResource.axd

WebResource.axd

66 ms

logo-brown-school-slideshow.gif

logo-brown-school-slideshow.gif

70 ms

proctor_100.jpg

proctor_100.jpg

618 ms

Thompson_rollup.jpg

Thompson_rollup.jpg

625 ms

Kreuter_rollup.jpg

Kreuter_rollup.jpg

618 ms

smidt_rollup.jpg

smidt_rollup.jpg

622 ms

KatieCox_rollup.jpg

KatieCox_rollup.jpg

619 ms

DAA2016_rollup.jpg

DAA2016_rollup.jpg

619 ms

fabbre_rollup_2.jpg

fabbre_rollup_2.jpg

620 ms

grow-lead-change_banner.jpg

grow-lead-change_banner.jpg

624 ms

footer-facebook.png

footer-facebook.png

621 ms

footer-twitter.png

footer-twitter.png

621 ms

footer-linkedin.png

footer-linkedin.png

625 ms

footer-google.png

footer-google.png

624 ms

bgximg.png

bgximg.png

605 ms

background-html.jpg

background-html.jpg

599 ms

background-body.jpg

background-body.jpg

598 ms

background-sideCol.jpg

background-sideCol.jpg

599 ms

background-sideCol-gradient.jpg

background-sideCol-gradient.jpg

600 ms

ajax-loader.gif

ajax-loader.gif

601 ms

arrow-more.gif

arrow-more.gif

601 ms

background-global.gif

background-global.gif

602 ms

background-footer.jpg

background-footer.jpg

602 ms

MViwy4K6e56oHcyeMzjbCQ.ttf

MViwy4K6e56oHcyeMzjbCQ.ttf

551 ms

F-uvpIj1hF17IDyvQvI50Q.ttf

F-uvpIj1hF17IDyvQvI50Q.ttf

552 ms

analytics.js

analytics.js

547 ms

slide%20c.jpg

slide%20c.jpg

266 ms

slide%20d.jpg

slide%20d.jpg

345 ms

slide-f.jpg

slide-f.jpg

285 ms

icon-arrows.png

icon-arrows.png

58 ms

collect

collect

24 ms

collect

collect

74 ms

Accessibility Review

gwbweb.wustl.edu accessibility score

80

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

[aria-hidden="true"] elements contain focusable descendents

High

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

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

gwbweb.wustl.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gwbweb.wustl.edu SEO score

87

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

High

Tap targets are not sized appropriately

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

gwbweb.wustl.edu

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