DREW.EDU Home - Drew University

drew.edu Website Information

Daily Unique Visits: 77,543

Daily Page Views: 465,258

Income Per Day: $931

Estimated Value: $670,320

This website is located in United States and is using following IP address 192.107.39.6. See the complete list of popular websites hosted in United States.

drew.edu is registered under .EDU top-level domain. Please check other sites in .EDU zone.

Website drew.edu is using the following name servers:

  • ns1.drew.edu
  • ns5.dnsmadeeasy.com
  • ns6.dnsmadeeasy.com
  • ns7.dnsmadeeasy.com

and is probably hosted by GOOGLE - Google LLC, US. See the full list of other websites hosted by GOOGLE - Google LLC, US.

The highest website drew.edu position in Alexa rank database was 17801 and the lowest rank position was 18579. Current position of drew.edu in Alexa rank database is 18496.

Desktop speed score of drew.edu (61/100) is better than the results of 37.05% of other sites and shows that the page desktop performance can be improved.

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

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

Advertisement

drew.edu Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


drew.edu whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


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

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.

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

Domain Name: DREW.EDU

Registrant:
Drew University
36 Madison Avenue
ACAD-COMP
Madison, NJ 07940
USA

Administrative Contact:
Scott Wood
Drew University
36 Madison Avenue
ACAD-COMP
Madison, NJ 07940
USA
+1.9734083657
swood1@drew.edu

Technical Contact:
Paul Coen
Drew University
36 Madison Avenue
ACAD-COMP
Madison, NJ 07940
USA
+1.9734083035
pcoen@drew.edu

Name Servers:
NS1.DREW.EDU
PNS41.CLOUDNS.NET
PNS42.CLOUDNS.NET
PNS43.CLOUDNS.NET
NS42.CLOUDNS.NET
PNS44.CLOUDNS.NET

Domain record activated: 15-Dec-1989
Domain record last updated: 10-Jun-2024
Domain expires: 31-Jul-2025

drew.edu server information

Servers Location

drew.edu desktop page speed rank

Last tested: 2017-05-27


Desktop Speed Bad
61/100

drew.edu Desktop Speed Test Quick Summary


priority - 52Optimize images

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

Optimize the following images to reduce their size by 503.9KiB (58% reduction).

Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2016/12/taryn-1-1.jpg could save 173.7KiB (77% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2016/12/voorman.jpg could save 122.3KiB (78% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…t_0715_023-335x485.jpg could save 33.4KiB (46% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/02/lesssitting.jpg could save 28.5KiB (56% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…tion_564Ps-280x187.jpg could save 20.2KiB (61% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…/summer_BC-280x158.jpg could save 18.8KiB (63% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…-Joan_0024-280x187.jpg could save 18KiB (66% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…chelle_Kim-300x300.jpg could save 17.3KiB (56% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…ards_184Ps-273x187.jpg could save 17.2KiB (65% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/wallst-280x157.jpg could save 15.2KiB (51% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…rberhoding-335x485.jpg could save 9.5KiB (26% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…shgranted-335x485.jpeg could save 8.7KiB (28% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…cloisters-335x485.jpeg could save 7.5KiB (19% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…/bikemonth-280x157.jpg could save 4KiB (27% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…186_SQ_Web-187x187.jpg could save 3.6KiB (29% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/wolfe-280x187.jpeg could save 3KiB (27% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/walker-335x485.jpg could save 3KiB (11% reduction).

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

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

Remove render-blocking JavaScript:

http://www.drew.edu/1/wp-content/themes/drew-ACFIX/js/modernizr.js
http://www.drew.edu/1/wp-content/themes/drew-ACFIX/js/site.js
http://www.drew.edu/1/wp-includes/js/wp-embed.min.js?ver=4.7

Optimize CSS Delivery of the following:

http://www.drew.edu/1/wp-content/themes/drew-ACFIX/css/site.css
http://www.drew.edu/1/wp-admin/admin-ajax.php?action=frmpro_css&ver=2231247

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://drew.edu/
http://www.drew.edu/
http://www.drew.edu/1/

priority - 2Reduce server response time

priority - 2Prioritize 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 20% of the final above-the-fold content could be rendered with the full HTML response.

priority - 0Leverage 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)

drew.edu Desktop Resource Breakdown

Total Resources38
Number of Hosts4
Static Resources1
JavaScript Resources5
CSS Resources2

drew.edu mobile page speed rank

Last tested: 2017-05-19


Mobile Speed Bad
51/100

drew.edu Mobile Speed Test Quick Summary


priority - 52Optimize images

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

Optimize the following images to reduce their size by 503.9KiB (58% reduction).

Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2016/12/taryn-1-1.jpg could save 173.7KiB (77% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2016/12/voorman.jpg could save 122.3KiB (78% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…t_0715_023-335x485.jpg could save 33.4KiB (46% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/02/lesssitting.jpg could save 28.5KiB (56% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…tion_564Ps-280x187.jpg could save 20.2KiB (61% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…/summer_BC-280x158.jpg could save 18.8KiB (63% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…-Joan_0024-280x187.jpg could save 18KiB (66% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…chelle_Kim-300x300.jpg could save 17.3KiB (56% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…ards_184Ps-273x187.jpg could save 17.2KiB (65% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/wallst-280x157.jpg could save 15.2KiB (51% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…rberhoding-335x485.jpg could save 9.5KiB (26% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…shgranted-335x485.jpeg could save 8.7KiB (28% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…cloisters-335x485.jpeg could save 7.5KiB (19% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…/bikemonth-280x157.jpg could save 4KiB (27% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2…186_SQ_Web-187x187.jpg could save 3.6KiB (29% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/wolfe-280x187.jpeg could save 3KiB (27% reduction).
Compressing http://www.drew.edu/1/wp-content/uploads/sites/7/2017/05/walker-335x485.jpg could save 3KiB (11% reduction).

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

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

Remove render-blocking JavaScript:

http://www.drew.edu/1/wp-content/themes/drew-ACFIX/js/modernizr.js
http://www.drew.edu/1/wp-content/themes/drew-ACFIX/js/site.js
http://www.drew.edu/1/wp-includes/js/wp-embed.min.js?ver=4.7

Optimize CSS Delivery of the following:

http://www.drew.edu/1/wp-content/themes/drew-ACFIX/css/site.css
http://www.drew.edu/1/wp-admin/admin-ajax.php?action=frmpro_css&ver=2231247

priority - 10Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://drew.edu/
http://www.drew.edu/
http://www.drew.edu/1/

priority - 8Prioritize 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 60% of the final above-the-fold content could be rendered with the full HTML response.

priority - 4Reduce server response time

priority - 1Leverage 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)

drew.edu Mobile Resource Breakdown

Total Resources38
Number of Hosts4
Static Resources1
JavaScript Resources5
CSS Resources2

drew.edu mobile page usability

Last tested: 2017-05-19


Mobile Usability Good
96/100

drew.edu Mobile Usability Test Quick Summary


priority - 3Size 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 <button class="cards_trigger"> is close to 2 other tap targets.

The tap target <div class="fs-carousel-ca…-touch-element">Watch The Rev.…read more</div> is close to 1 other tap targets.

The tap target <article class="card theme_bor…rousel-visible">Watch The Rev.…atch the video</article> is close to 1 other tap targets.

The tap target <a href="http://www.drew.edu/directory" class="directory">Directory</a> and 3 others are close to other tap targets.
The tap target <a href="https://www.fa…rewUniversity/" class="facebook">Facebook</a> and 2 others are close to other tap targets.

drew.edu HTML validation

Errors

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 103 Column: 1 - 71
"...='all' /> <link rel='https://api.w.org/' href='http://www.drew.edu/1/wp-json/' /> <link..."

The element “footer” must not appear as a descendant of the “header” element.

Line: 192 Column: 4 - 40
"...</div> <footer class="builder_intro_footer"> <..." Line: 380 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 390 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 401 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 412 Column: 5 - 32
"... </p> <footer class="card_footer"> <a..." Line: 422 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 433 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 448 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 458 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 469 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 480 Column: 5 - 32
"... </p> <footer class="card_footer"> <a..." Line: 490 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 501 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 513 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 523 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 533 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 543 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 556 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 567 Column: 5 - 32
"... </p> <footer class="card_footer"> <a..." Line: 578 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 589 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 602 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 613 Column: 5 - 32
"....</p> <footer class="card_footer"> <a..." Line: 623 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 633 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 643 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..." Line: 653 Column: 5 - 32
"...</h4> <footer class="card_footer"> <a..."

The element “header” must not appear as a descendant of the “header” element.

Line: 209 Column: 4 - 34
"...utton> <header class="builder_header"> <..."

Element “div” not allowed as child of element “button” in this context. (Suppressing further errors from this subtree.)

Line: 216 Column: 6 - 10
"..."5"> <div> ..." Line: 223 Column: 6 - 10
"...33"> <div> ..." Line: 230 Column: 6 - 10
"..."3"> <div> ..." Line: 237 Column: 6 - 10
"..."7"> <div> ..." Line: 244 Column: 6 - 10
"...36"> <div> ..." Line: 251 Column: 6 - 10
"...35"> <div> ..." Line: 258 Column: 6 - 10
"...34"> <div> ..." Line: 265 Column: 6 - 10
"..."8"> <div> ..." Line: 272 Column: 6 - 10
"...32"> <div> ..." Line: 279 Column: 6 - 10
"..."9"> <div> ..." Line: 286 Column: 6 - 10
"...10"> <div> ..." Line: 293 Column: 6 - 10
"...11"> <div> ..." Line: 300 Column: 6 - 10
"...12"> <div> ..." Line: 307 Column: 6 - 10
"...13"> <div> ..." Line: 314 Column: 6 - 10
"...14"> <div> ..." Line: 321 Column: 6 - 10
"...15"> <div> ..." Line: 328 Column: 6 - 10
"...16"> <div> ..." Line: 335 Column: 6 - 10
"...17"> <div> ..." Line: 342 Column: 6 - 10
"...31"> <div> ..." Line: 349 Column: 6 - 10
"...37"> <div> ..." Line: 356 Column: 6 - 10
"...18"> <div> ..."

Warnings

Empty heading.

Line: 164 Column: 7 - 38
"...r"> <h2 class="builder_intro_label"> </h2>..."

drew.edu similar domains

Similar domains:
www.drew.com
www.drew.net
www.drew.org
www.drew.info
www.drew.biz
www.drew.us
www.drew.mobi
www.rew.edu
www.drew.edu
www.xrew.edu
www.dxrew.edu
www.xdrew.edu
www.srew.edu
www.dsrew.edu
www.sdrew.edu
www.erew.edu
www.derew.edu
www.edrew.edu
www.rrew.edu
www.drrew.edu
www.rdrew.edu
www.frew.edu
www.dfrew.edu
www.fdrew.edu
www.crew.edu
www.dcrew.edu
www.cdrew.edu
www.dew.edu
www.deew.edu
www.dreew.edu
www.ddew.edu
www.drdew.edu
www.ddrew.edu
www.dfew.edu
www.drfew.edu
www.dtew.edu
www.drtew.edu
www.dtrew.edu
www.drw.edu
www.drww.edu
www.dreww.edu
www.drwew.edu
www.drsw.edu
www.dresw.edu
www.drsew.edu
www.drdw.edu
www.dredw.edu
www.drrw.edu
www.drerw.edu
www.dre.edu
www.dreq.edu
www.drewq.edu
www.dreqw.edu
www.drea.edu
www.drewa.edu
www.dreaw.edu
www.dres.edu
www.drews.edu
www.dree.edu
www.drewe.edu

drew.edu Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


drew.edu TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.