WUSTL.EDU Washington University in St. Louis


wustl.edu website information.

wustl.edu website servers are located in United States and are responding from following IP address 128.252.114.30. Check the full list of most visited websites located in United States.

wustl.edu domain name is registered by .EDU top-level domain registry. See the other sites registred in .EDU domain zone.

Following name servers are specified for wustl.edu domain:

  • ns01.ip.wustl.edu
  • ns00.ip.wustl.edu
  • ns03.ip.wustl.edu
  • ns02.ip.wustl.edu
  • alpha.louisiana.edu

and probably website wustl.edu is hosted by wustl.edu web hosting company. Check the complete list of other most popular websites hosted by wustl.edu hosting company.

According to Alexa traffic rank the highest website wustl.edu position was 3385 (in the world). The lowest Alexa rank position was 19205. Now website wustl.edu ranked in Alexa database as number 5680 (in the world).

Website wustl.edu Desktop speed measurement score (57/100) is better than the results of 29.1% of other sites shows that the page desktop performance can be improved.

wustl.edu Mobile usability score (99/100) is better than the results of 87.11% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of wustl.edu (34/100) is better than the results of 9.3% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-14-2019 5,6801,122
Nov-13-2019 6,8021,524
Nov-12-2019 8,3263,226
Nov-11-2019 11,552-3,173
Nov-10-2019 8,379-384
Nov-09-2019 7,995-874
Nov-08-2019 7,121-3,126

Advertisement

wustl.edu Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


wustl.edu whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


This Registry database contains ONLY .EDU domains.
The data in the EDUCAUSE Whois database is provided
by EDUCAUSE for information purposes in order to
assist in the process of obtaining information about
or related to .edu domain registration records.

The EDUCAUSE Whois database is authoritative for the
.EDU domain.

A Web interface for the .EDU EDUCAUSE Whois Server is
available at: http://whois.educause.net

By submitting a Whois query, you agree that this information
will not be used to allow, enable, or otherwise support
the transmission of unsolicited commercial advertising or
solicitations via e-mail. The use of electronic processes to
harvest information from this server is generally prohibited
except as reasonably necessary to register or modify .edu
domain names.

You may use "%" as a wildcard in your search. For further
information regarding the use of this WHOIS server, please
type: help

--------------------------

Domain Name: WUSTL.EDU

Registrant:
Washington University in St. Louis
Network Technology Services
One Brookings Drive Campus Box 1048
St. Louis, MO 63130-4899
UNITED STATES

Administrative Contact:
Network Technology Services
Washington University
1 Brookings Dr, Campus Box 1048
St. Louis, MO 63130-4899
UNITED STATES
(314) 935-7048
nts-admin@wustl.edu

Technical Contact:
Network Technology Services
Washington University
1 Brookings Dr Campus Box 1048
St. Louis, MO 63130-4899
UNITED STATES
(314) 935-7048
noc@wustl.edu

Name Servers:
NS00.IP.WUSTL.EDU 128.252.0.1
NS01.IP.WUSTL.EDU 128.252.0.9
NS02.IP.WUSTL.EDU 128.252.0.17
NS03.IP.WUSTL.EDU 128.252.0.25
ALPHA.LOUISIANA.EDU

Domain record activated: 07-Dec-1987
Domain record last updated: 22-Feb-2013
Domain expires: 31-Jul-2018

wustl.edu server information

Servers Location

wustl.edu desktop page speed rank

Last tested: 2016-06-13


Desktop Speed Bad
57/100

wustl.edu Desktop Speed Test Quick Summary


priority - 66 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 648.3KiB (57% reduction).

Compressing and resizing https://wustl.edu/wp-content/uploads/2016/06/athletics-Lagieski.jpg could save 229.2KiB (94% reduction).
Compressing and resizing https://wustl.edu/wp-content/uploads/2016/06/social-ArtHill.jpg could save 188.9KiB (93% reduction).
Compressing and resizing https://wustl.edu/wp-content/uploads/2016/06/event-STEMFIT.jpg could save 60.3KiB (88% reduction).
Compressing and resizing https://wustl.edu/wp-content/themes/wustl_edu/_ass…/18-nobel-laureats.png could save 54.8KiB (75% reduction).
Losslessly compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…c/bg-campaign-wide.png could save 50.9KiB (20% reduction).
Losslessly compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…static/bg-cta-wide.png could save 39.9KiB (19% reduction).
Compressing and resizing https://wustl.edu/wp-content/themes/wustl_edu/_ass…rz_white_solid_rev.png could save 12.1KiB (39% reduction).
Compressing and resizing https://wustl.edu/wp-content/themes/wustl_edu/_ass…tn/40-study-abroad.png could save 4.6KiB (31% reduction).
Losslessly compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…mg/campaign-footer.png could save 2.2KiB (37% reduction).
Compressing and resizing https://wustl.edu/wp-content/themes/wustl_edu/_ass…btn/142-inventions.png could save 2.2KiB (28% reduction).
Compressing and resizing https://wustl.edu/wp-content/themes/wustl_edu/_ass…/386K-bottle-saved.png could save 2KiB (36% reduction).
Losslessly compressing https://wustl.edu/wp-content/themes/wustl_edu/_assets/img/pull-down.png could save 1.1KiB (52% reduction).

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://wustl.edu/wp-includes/js/jquery/jquery.js?ver=1.12.3
https://wustl.edu/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.0

Optimize CSS Delivery of the following:

https://wustl.edu/wp-content/uploads/formidable/cs…blepro.css?ver=5271420
https://wustl.edu/wp-content/plugins/washu-emergen…ss/style.css?ver=4.5.2
https://wustl.edu/wp-content/plugins/wustl-settings/user.css?ver=4.5.2
https://wustl.edu/wp-content/themes/wustl_edu/style.css?ver=4.5.2
https://fonts.googleapis.com/css?family=Source+San…%2C400italic&ver=4.5.2

priority - 4 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-analytics.com/analytics.js (2 hours)
https://wustl.edu/wp-content/plugins/washu-emergen…ss/style.css?ver=4.5.2 (3 days)
https://wustl.edu/wp-content/plugins/wustl-settings/user.css?ver=4.5.2 (3 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…nu-aim.js?ver=20150507 (3 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…ernizr.js?ver=20150507 (3 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…cripts.js?ver=20150507 (3 days)
https://wustl.edu/wp-content/themes/wustl_edu/style.css?ver=4.5.2 (3 days)
https://wustl.edu/wp-content/uploads/formidable/cs…blepro.css?ver=5271420 (3 days)
https://wustl.edu/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.0 (3 days)
https://wustl.edu/wp-includes/js/jquery/jquery.js?ver=1.12.3 (3 days)
https://wustl.edu/wp-includes/js/wp-embed.min.js?ver=4.5.2 (3 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…cturefill.3.0.2.min.js (3 days)
https://wustl.edu/wp-includes/js/wp-emoji-release.min.js?ver=4.5.2 (3 days)

priority - 1 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 12.1KiB (66% reduction).

Compressing https://wustl.edu/wp-content/themes/wustl_edu/_assets/img/washu-logo.svg could save 10.5KiB (66% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…ons/icon-instagram.svg could save 949B (66% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…icons/icon-twitter.svg could save 670B (63% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4KiB (24% reduction).

Minifying https://wustl.edu/wp-content/themes/wustl_edu/style.css?ver=4.5.2 could save 4KiB (24% reduction) after compression.

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.3KiB (71% reduction).

Minifying https://wustl.edu/wp-content/themes/wustl_edu/_ass…nu-aim.js?ver=20150507 could save 2.3KiB (71% reduction) after compression.

wustl.edu Desktop Resources

Total Resources58
Number of Hosts4
Static Resources44
JavaScript Resources9
CSS Resources5

wustl.edu Desktop Resource Breakdown

wustl.edu mobile page speed rank

Last tested: 2017-05-03


Mobile Speed Bad
34/100

wustl.edu Mobile Speed Test Quick Summary


priority - 158 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.5MiB (66% reduction).

Compressing https://wustl.edu/wp-content/uploads/2017/05/athle…17-softball-champs.jpg could save 376.1KiB (75% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/11/15111…rnational_law_011.jpeg could save 221.1KiB (81% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/04/social-Brookings1904.jpg could save 184.1KiB (71% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/11/12012…unar_new_year_106.jpeg could save 140.8KiB (81% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/04/event-French-eat-dinner.jpg could save 133.2KiB (70% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/11/initiatives-ees-cities.jpeg could save 123.2KiB (64% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/11/initi…-ahh-BurskyCenter.jpeg could save 72.3KiB (62% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/05/story-BabaBadji.jpg could save 62KiB (45% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/11/initiatives-ie-Carter.jpeg could save 54.5KiB (64% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/04/experts-Dlugosz.jpeg could save 53.8KiB (50% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/04/expert-GrahamColditz.jpeg could save 53.6KiB (51% reduction).
Compressing https://wustl.edu/wp-content/uploads/2017/05/story-3Dbrain.jpg could save 47KiB (45% reduction).
Compressing https://wustl.edu/wp-content/uploads/2016/07/18-nobel-laureats.png could save 16.1KiB (23% reduction).
Compressing https://wustl.edu/wp-content/uploads/2014/10/icon-sustainability.png could save 1.1KiB (15% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…img/transparent6x4.gif could save 1KiB (93% reduction).

priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://wustl.edu/wp-includes/js/jquery/jquery.js?ver=1.12.4
https://wustl.edu/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
https://wustl.edu/wp-content/themes/wustl_edu/_ass…cripts.js?ver=20150507
https://wustl.edu/wp-content/themes/wustl_edu/_ass…nu-aim.js?ver=20150507
https://wustl.edu/wp-content/themes/wustl_edu/_ass…ernizr.js?ver=20150507
https://wustl.edu/wp-includes/js/wp-embed.min.js?ver=4.7.4

Optimize CSS Delivery of the following:

https://wustl.edu/wp-content/plugins/washu-emergen…ss/style.css?ver=4.7.4
https://wustl.edu/wp-content/themes/wustl_edu/style.css?ver=1.8.7
https://fonts.googleapis.com/css?family=Source+San…%2C400italic&ver=4.7.4

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 64% of the final above-the-fold content could be rendered with the full HTML response.

priority - 5 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.google-analytics.com/analytics.js (2 hours)
https://wustl.edu/wp-includes/js/jquery/jquery.js?ver=1.12.4 (2.5 days)
https://wustl.edu/wp-content/plugins/washu-emergen…ss/style.css?ver=4.7.4 (2.5 days)
https://wustl.edu/wp-content/themes/wustl_edu/style.css?ver=1.8.7 (2.5 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…ernizr.js?ver=20150507 (2.5 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…cturefill.3.0.2.min.js (2.5 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…cripts.js?ver=20150507 (2.5 days)
https://wustl.edu/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 (2.5 days)
https://wustl.edu/wp-includes/js/wp-embed.min.js?ver=4.7.4 (2.5 days)
https://wustl.edu/wp-content/themes/wustl_edu/_ass…nu-aim.js?ver=20150507 (2.5 days)
https://wustl.edu/wp-includes/js/wp-emoji-release.min.js?ver=4.7.4 (2.5 days)

priority - 4 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 38KiB (64% reduction).

Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…g/leading-together.svg could save 13.8KiB (63% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…ng-together-footer.svg could save 12.1KiB (64% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_assets/img/washu-logo.svg could save 10.5KiB (66% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…ons/icon-instagram.svg could save 949B (66% reduction).
Compressing https://wustl.edu/wp-content/themes/wustl_edu/_ass…icons/icon-twitter.svg could save 670B (63% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.3KiB (71% reduction).

Minifying https://wustl.edu/wp-content/themes/wustl_edu/_ass…nu-aim.js?ver=20150507 could save 2.3KiB (71% reduction) after compression.

wustl.edu Mobile Resources

Total Resources60
Number of Hosts4
Static Resources46
JavaScript Resources9
CSS Resources3

wustl.edu Mobile Resource Breakdown

wustl.edu mobile page usability

Last tested: 2017-05-03


Mobile Usability Good
99/100

wustl.edu Mobile Usability Test Quick Summary


priority - 0 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://source.wustl.edu" class="explore hover-underline">Explore the source</a> is close to 1 other tap targets.

The tap target <a href="https://www.fa…type=3&amp;theater">View of the 19…kings archway.</a> and 1 others are close to other tap targets.
The tap target <a href="https://source…revent-cancer/">Graham A. Colditz</a> is close to 1 other tap targets.

wustl.edu Mobile Resources

Total Resources60
Number of Hosts4
Static Resources46
JavaScript Resources9
CSS Resources3

wustl.edu Mobile Resource Breakdown

wustl.edu similar domains

Similar domains:
www.wustl.com
www.wustl.net
www.wustl.org
www.wustl.info
www.wustl.biz
www.wustl.us
www.wustl.mobi
www.ustl.edu
www.wustl.edu
www.qustl.edu
www.wqustl.edu
www.qwustl.edu
www.austl.edu
www.waustl.edu
www.awustl.edu
www.sustl.edu
www.wsustl.edu
www.swustl.edu
www.eustl.edu
www.weustl.edu
www.ewustl.edu
www.wstl.edu
www.wystl.edu
www.wuystl.edu
www.wyustl.edu
www.whstl.edu
www.wuhstl.edu
www.whustl.edu
www.wjstl.edu
www.wujstl.edu
www.wjustl.edu
www.wistl.edu
www.wuistl.edu
www.wiustl.edu
www.wutl.edu
www.wuwtl.edu
www.wuswtl.edu
www.wuwstl.edu
www.wuetl.edu
www.wusetl.edu
www.wuestl.edu
www.wudtl.edu
www.wusdtl.edu
www.wudstl.edu
www.wuztl.edu
www.wusztl.edu
www.wuzstl.edu
www.wuxtl.edu
www.wusxtl.edu
www.wuxstl.edu
www.wuatl.edu
www.wusatl.edu
www.wuastl.edu
www.wusl.edu
www.wusrl.edu
www.wustrl.edu
www.wusrtl.edu
www.wusfl.edu
www.wustfl.edu
www.wusftl.edu
www.wusgl.edu
www.wustgl.edu
www.wusgtl.edu
www.wusyl.edu
www.wustyl.edu
www.wusytl.edu
www.wust.edu
www.wustp.edu
www.wustlp.edu
www.wustpl.edu
www.wusto.edu
www.wustlo.edu
www.wustol.edu
www.wustk.edu
www.wustlk.edu
www.wustkl.edu

wustl.edu Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


wustl.edu TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.