UPS.EDU University of Puget Sound


ups.edu website information.

ups.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 ups.edu domain:

  • dns2.pugetsound.edu
  • dns3.pugetsound.edu
  • dns1.pugetsound.edu

and probably website ups.edu is hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US hosting company.

According to Alexa traffic rank the highest website ups.edu position was 24379 (in the world). The lowest Alexa rank position was 976166. Now website ups.edu ranked in Alexa database as number 55523 (in the world).

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

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

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

Weekly Rank Report

DateRankChange
Nov-20-2024 55,523-78
Nov-19-2024 55,445434
Nov-18-2024 55,879437
Nov-17-2024 56,316-394
Nov-16-2024 55,92252
Nov-15-2024 55,974-96
Nov-14-2024 55,878-916

Advertisement

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



ups.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: UPS.EDU

Registrant:
University of Puget Sound
1500 North Warner
Tacoma, WA 98416
USA

Administrative Contact:
Jared Hoover
University of Puget Sound
1500 North Warner
Tacoma, WA 98416
USA
+1.2538793185
jhoover@ups.edu

Technical Contact:
Henry Lee
University of Puget Sound
1500 North Warner
Tacoma, WA 98416
USA
+1.2538792873
henrylee@pugetsound.edu

Name Servers:
DNS2.PUGETSOUND.EDU
DNS1.PUGETSOUND.EDU

Domain record activated: 11-Apr-1989
Domain record last updated: 08-Jul-2024
Domain expires: 31-Jul-2027

ups.edu server information

Servers Location

IP Address
207.207.127.174
Region
Washington
City
University Place

ups.edu desktop page speed rank

Last tested: 2017-05-27


Desktop Speed Bad
17/100

ups.edu Desktop Speed Test Quick Summary


priority - 362 Optimize images

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

Optimize the following images to reduce their size by 3.5MiB (82% reduction).

Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-22-at-53833-pm.png could save 707.6KiB (88% reduction).
Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-25-at-121130-pm.png could save 635.7KiB (87% reduction).
Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-25-at-115824-am.png could save 622KiB (86% reduction).
Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-25-at-115949-am.png could save 531KiB (86% reduction).
Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-25-at-120841-pm.png could save 524.5KiB (86% reduction).
Compressing and resizing https://www.pugetsound.edu/files/screen-shot-2017-05-22-at-53717-pm.png could save 471.2KiB (83% reduction).
Compressing https://www.pugetsound.edu/files/homepage/pugetsound_60014977.jpg could save 10.2KiB (20% reduction).
Compressing https://www.pugetsound.edu/files/homepage/2020.jpg could save 7.6KiB (18% reduction).
Compressing https://www.pugetsound.edu/files/homepage/lrg_nic-…m-his-berlin-hot-2.jpg could save 7.2KiB (17% reduction).
Compressing https://www.pugetsound.edu/files/homepage/watsons17.jpg could save 6KiB (18% reduction).
Compressing https://www.pugetsound.edu/images/icons.png could save 5.8KiB (15% reduction).
Compressing https://www.pugetsound.edu/files/homepage/wwd_art-600x400.jpg could save 5.6KiB (24% reduction).

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

Your page has 2 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://www.pugetsound.edu/js/lib/modernizr.js
https://www.pugetsound.edu/js/site.js?1495819090

Optimize CSS Delivery of the following:

https://www.pugetsound.edu/css/site.css?1495819090
https://www.pugetsound.edu/css/fonts.css
https://fast.fonts.net/t/1.css?apiType=css&project…4a0d-8fec-4e1138962a70

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://ups.edu/
http://www.pugetsound.edu/
https://www.pugetsound.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://www.googletagmanager.com/gtm.js?id=GTM-NK6K8K9 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1894008857500690?v=2.7.11 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

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 4.4KiB (16% reduction).

Minifying https://www.pugetsound.edu/css/site.css?1495819090 could save 4.4KiB (16% reduction) after compression.

ups.edu Desktop Resources

Total Resources42
Number of Hosts7
Static Resources30
JavaScript Resources6
CSS Resources4

ups.edu Desktop Resource Breakdown

ups.edu mobile page speed rank

Last tested: 2017-05-27


Mobile Speed Bad
49/100

ups.edu Mobile Speed Test Quick Summary


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

Your page has 2 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://www.pugetsound.edu/js/lib/modernizr.js
https://www.pugetsound.edu/js/site.js?1495819090

Optimize CSS Delivery of the following:

https://www.pugetsound.edu/css/site.css?1495819090
https://www.pugetsound.edu/css/fonts.css
https://fast.fonts.net/t/1.css?apiType=css&project…4a0d-8fec-4e1138962a70

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://ups.edu/
http://www.pugetsound.edu/
https://www.pugetsound.edu/

priority - 5 Optimize images

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

Optimize the following images to reduce their size by 50.4KiB (20% reduction).

Compressing https://www.pugetsound.edu/files/homepage/pugetsound_60014977.jpg could save 10.2KiB (20% reduction).
Compressing https://www.pugetsound.edu/files/homepage/2020.jpg could save 7.6KiB (18% reduction).
Compressing https://www.pugetsound.edu/files/homepage/lrg_nic-…m-his-berlin-hot-2.jpg could save 7.2KiB (17% reduction).
Compressing https://www.pugetsound.edu/files/homepage/watsons17.jpg could save 6KiB (18% reduction).
Compressing https://www.pugetsound.edu/images/icons.png could save 5.8KiB (15% reduction).
Compressing https://www.pugetsound.edu/files/homepage/wwd_art-600x400.jpg could save 5.6KiB (24% reduction).
Compressing https://www.pugetsound.edu/images/voices/psa2017-soandinnerphoto.jpg could save 4.9KiB (20% reduction).
Compressing https://www.pugetsound.edu/images/voices/SOAN.jpg could save 3.1KiB (64% reduction).

priority - 3 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.googletagmanager.com/gtm.js?id=GTM-NK6K8K9 (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1894008857500690?v=2.7.11 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

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 4.4KiB (16% reduction).

Minifying https://www.pugetsound.edu/css/site.css?1495819090 could save 4.4KiB (16% reduction) after compression.

ups.edu Mobile Resources

Total Resources43
Number of Hosts7
Static Resources32
JavaScript Resources6
CSS Resources4

ups.edu Mobile Resource Breakdown

ups.edu mobile page usability

Last tested: 2017-05-27


Mobile Usability Good
100/100

ups.edu similar domains

Similar domains:
www.ups.com
www.ups.net
www.ups.org
www.ups.info
www.ups.biz
www.ups.us
www.ups.mobi
www.ps.edu
www.ups.edu
www.yps.edu
www.uyps.edu
www.yups.edu
www.hps.edu
www.uhps.edu
www.hups.edu
www.jps.edu
www.ujps.edu
www.jups.edu
www.ips.edu
www.uips.edu
www.iups.edu
www.us.edu
www.uos.edu
www.upos.edu
www.uops.edu
www.uls.edu
www.upls.edu
www.ulps.edu
www.up.edu
www.upw.edu
www.upsw.edu
www.upws.edu
www.upe.edu
www.upse.edu
www.upes.edu
www.upd.edu
www.upsd.edu
www.upds.edu
www.upz.edu
www.upsz.edu
www.upzs.edu
www.upx.edu
www.upsx.edu
www.upxs.edu
www.upa.edu
www.upsa.edu
www.upas.edu

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


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