princeton.edu website information.
princeton.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 princeton.edu domain:
- a24-66.akam.net
- a7-65.akam.net
- auth1.dns.cogentco.com
- a6-64.akam.net
- a20-65.akam.net
- a1-158.akam.net
- a3-67.akam.net
- auth2.dns.cogentco.com
and probably website princeton.edu is hosted by AMAZON-AES - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-AES - Amazon.com, Inc., US hosting company.
According to Alexa traffic rank the highest website princeton.edu position was 212 (in the world). The lowest Alexa rank position was 228. Now website princeton.edu ranked in Alexa database as number 226 (in the world).
Website princeton.edu Desktop speed measurement score (57/100) is better than the results of 31.79% of other sites shows that the page desktop performance can be improved.
princeton.edu Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of princeton.edu (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Apr-26-2024 | 226 | -1 |
| Apr-25-2024 | 225 | 0 |
| Apr-24-2024 | 225 | 0 |
| Apr-23-2024 | 225 | -1 |
| Apr-22-2024 | 224 | 1 |
| Apr-21-2024 | 225 | -1 |
| Apr-20-2024 | 224 | 0 |
Advertisement
princeton.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.
princeton.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.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: PRINCETON.EDU
Registrant:
Princeton University
Office of Information Technology
701 Carnegie Center, Suite 301
Princeton, NJ 08540
US
Administrative Contact:
Princeton University
Princeton University
87 Prospect Ave #106
Office of Information Technology
Networking & Monitoring Services
Princeton, NJ 08540
US
+1.6092582774
netipam@princeton.edu
Technical Contact:
Princeton University
Princeton University
87 Prospect Ave #106
Office of Information Technology
Networking & Monitoring Services
Princeton, NJ 08540
US
+1.6092582774
netipam@princeton.edu
Name Servers:
A7-65.AKAM.NET
A24-66.AKAM.NET
NS6.DNSMADEEASY.COM
A1-158.AKAM.NET
A6-64.AKAM.NET
NS7.DNSMADEEASY.COM
A3-67.AKAM.NET
A20-65.AKAM.NET
NS5.DNSMADEEASY.COM
Domain record activated: 03-Apr-1987
Domain record last updated: 25-Mar-2021
Domain expires: 31-Jul-2021
princeton.edu server information
princeton.edu desktop page speed rank
Last tested: 2018-07-02
princeton.edu Desktop Speed Test Quick Summary
priority - 51 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 499.8KiB (76% reduction).
Compressing https://www.princeton.edu/themes/custom/tony/logo.svg could save 21.9KiB (64% reduction).
Compressing https://www.princeton.edu/themes/custom/tony/images/logo-white.svg could save 21.5KiB (65% reduction).
priority - 19 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 182.2KiB (73% reduction).
Compressing and resizing https://www.princeton.edu/sites/default/files/styl…41_d.jpg?itok=hFEQL7UI could save 55.5KiB (72% reduction).
Compressing and resizing https://www.princeton.edu/sites/default/files/styl…ria1.jpg?itok=o5peWf1o could save 39.2KiB (68% reduction).
priority - 7 Avoid 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://www.princeton.edu/
https://www.princeton.edu/
priority - 2 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://assets.juicer.io/embed.js (expiration not specified)
https://assets.juicer.io/fontawesome-webfont-adbc4…8e9791f457623ac2c.woff (expiration not specified)
https://assets.juicer.io/fontawesome-webfont-ae19e…e0c409046608b38912.ttf (expiration not specified)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
priority - 2 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 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.
Optimize CSS Delivery of the following:
princeton.edu Desktop Resources
| Total Resources | 34 |
| Number of Hosts | 5 |
| Static Resources | 24 |
| JavaScript Resources | 8 |
| CSS Resources | 2 |
princeton.edu Desktop Resource Breakdown
princeton.edu mobile page speed rank
Last tested: 2018-05-26
princeton.edu Mobile Speed Test Quick Summary
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 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:
Optimize CSS Delivery of the following:
https://www.princeton.edu/sites/default/files/css/…syAeLGYvJ-o.css?p95sx2
priority - 26 Avoid 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://www.princeton.edu/
https://www.princeton.edu/
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 43.4KiB (64% reduction).
Compressing https://www.princeton.edu/themes/custom/tony/images/logo-white.svg could save 21.5KiB (65% reduction).
priority - 1 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:
princeton.edu Mobile Resources
| Total Resources | 30 |
| Number of Hosts | 5 |
| Static Resources | 20 |
| JavaScript Resources | 8 |
| CSS Resources | 2 |
princeton.edu Mobile Resource Breakdown
princeton.edu mobile page usability
Last tested: 2018-05-26
princeton.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.
<a id="skip-link" href="#main-content" class="visually-hidde…tton skip-link">Skip to main content</a> is close to 1 other tap targets.<button class="toggle-main-menu">Toggle subitems</button> is close to 1 other tap targets.<input id="header-search" type="search" name="search" class="form-search placeholder"> is close to 1 other tap targets.<input id="header-edit-submit" type="submit" class="button js-form…it placeholder"> is close to 2 other tap targets.princeton.edu similar domains
www.princeton.net
www.princeton.org
www.princeton.info
www.princeton.biz
www.princeton.us
www.princeton.mobi
www.rinceton.edu
www.princeton.edu
www.orinceton.edu
www.porinceton.edu
www.oprinceton.edu
www.lrinceton.edu
www.plrinceton.edu
www.lprinceton.edu
www.pinceton.edu
www.peinceton.edu
www.preinceton.edu
www.perinceton.edu
www.pdinceton.edu
www.prdinceton.edu
www.pdrinceton.edu
www.pfinceton.edu
www.prfinceton.edu
www.pfrinceton.edu
www.ptinceton.edu
www.prtinceton.edu
www.ptrinceton.edu
www.prnceton.edu
www.prunceton.edu
www.priunceton.edu
www.pruinceton.edu
www.prjnceton.edu
www.prijnceton.edu
www.prjinceton.edu
www.prknceton.edu
www.priknceton.edu
www.prkinceton.edu
www.pronceton.edu
www.prionceton.edu
www.proinceton.edu
www.priceton.edu
www.pribceton.edu
www.prinbceton.edu
www.pribnceton.edu
www.prihceton.edu
www.prinhceton.edu
www.prihnceton.edu
www.prijceton.edu
www.prinjceton.edu
www.primceton.edu
www.prinmceton.edu
www.primnceton.edu
www.prineton.edu
www.prinxeton.edu
www.princxeton.edu
www.prinxceton.edu
www.prindeton.edu
www.princdeton.edu
www.prindceton.edu
www.prinfeton.edu
www.princfeton.edu
www.prinfceton.edu
www.prinveton.edu
www.princveton.edu
www.prinvceton.edu
www.princton.edu
www.princwton.edu
www.princewton.edu
www.princweton.edu
www.princston.edu
www.princeston.edu
www.princseton.edu
www.princdton.edu
www.princedton.edu
www.princrton.edu
www.princerton.edu
www.princreton.edu
www.princeon.edu
www.princeron.edu
www.princetron.edu
www.princefon.edu
www.princetfon.edu
www.princefton.edu
www.princegon.edu
www.princetgon.edu
www.princegton.edu
www.princeyon.edu
www.princetyon.edu
www.princeyton.edu
www.princetn.edu
www.princetin.edu
www.princetoin.edu
www.princetion.edu
www.princetkn.edu
www.princetokn.edu
www.princetkon.edu
www.princetln.edu
www.princetoln.edu
www.princetlon.edu
www.princetpn.edu
www.princetopn.edu
www.princetpon.edu
www.princeto.edu
www.princetob.edu
www.princetonb.edu
www.princetobn.edu
www.princetoh.edu
www.princetonh.edu
www.princetohn.edu
www.princetoj.edu
www.princetonj.edu
www.princetojn.edu
www.princetom.edu
www.princetonm.edu
www.princetomn.edu
princeton.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.
princeton.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.