hollins.edu website information.
hollins.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 hollins.edu domain:
- hoshi.hollins.edu
- hudns.hollins.edu
and probably website hollins.edu is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.
According to Alexa traffic rank the highest website hollins.edu position was 53326 (in the world). The lowest Alexa rank position was 996469. Now website hollins.edu ranked in Alexa database as number 57426 (in the world).
Website hollins.edu Desktop speed measurement score (18/100) is better than the results of 3.49% of other sites shows that the page desktop performance can be improved.
hollins.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 hollins.edu (19/100) is better than the results of 4.1% 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 |
|---|---|---|
| Nov-20-2024 | 57,426 | -999 |
| Nov-19-2024 | 56,427 | 397 |
| Nov-18-2024 | 56,824 | -518 |
| Nov-17-2024 | 56,306 | -1,209 |
| Nov-16-2024 | 55,097 | -577 |
| Nov-15-2024 | 54,520 | -48 |
| Nov-14-2024 | 54,472 | -52 |
Advertisement
hollins.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.
hollins.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: HOLLINS.EDU
Registrant:
Hollins University
Information Technology
8142 E. Campus Drive
Roanoke, VA 24020
USA
Administrative Contact:
Brent C McIntyre
Hollins University
7916 Williamson Road
Dana 237
Roanoke, VA 24019
USA
+1.5403626324
bmcintyre@hollins.edu
Technical Contact:
John Boyd
Hollins University
Information Technology
8003 Fishburn
Roanoke, VA 24019
USA
+1.5403626550
jboyd@hollins.edu
Name Servers:
NS3.DNSMADEEASY.COM
NS1.DNSMADEEASY.COM
NS2.DNSMADEEASY.COM
NS0.DNSMADEEASY.COM
NS4.DNSMADEEASY.COM
Domain record activated: 11-May-1993
Domain record last updated: 05-Jun-2024
Domain expires: 31-Jul-2027
hollins.edu server information
hollins.edu desktop page speed rank
Last tested: 2018-11-26
hollins.edu Desktop Speed Test Quick Summary
priority - 373 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 3.6MiB (91% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/09/achieve.jpg could save 906.1KiB (97% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/09/learn.jpg could save 870KiB (94% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/11/Kantor_0873.jpg could save 146.9KiB (80% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11…endsgiving-600x600.jpg could save 81.6KiB (86% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/swimmer-600x600.jpg could save 64.9KiB (85% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11…endsgiving-600x600.jpg could save 63.2KiB (83% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/riding-600x600.jpg could save 62.6KiB (85% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/EDW-museum-600x600.jpg could save 62.6KiB (87% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11…dent-Paris-600x600.jpg could save 58.8KiB (86% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/11/Midsummer_top.jpg could save 57.8KiB (50% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/mal-600x600.jpg could save 49.8KiB (85% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/riding-1-600x600.jpg could save 48.1KiB (82% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11…t-painting-600x364.jpg could save 41KiB (78% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/accepted-600x600.jpg could save 39.4KiB (84% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/1842-patch-600x600.jpg could save 37.5KiB (87% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/in-600x600.jpg could save 33.4KiB (83% reduction).
priority - 4 Reduce server response time
In our test, your server responded in 0.56 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
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-PKK88ND (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/181621…1375?v=2.8.33&r=stable (20 minutes)
https://mx.technolutions.net/ping?id=85ef25de-ad7f…d7c8-a703-c42a35489bbd (30 minutes)
https://admissions.hollins.edu/ping (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 3 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 32.5KiB (35% reduction).
Minifying https://www.hollins.edu/wp-content/themes/hollins-nc/js/foundation.js could save 7.9KiB (32% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…end/jquery.timeline.js could save 7.7KiB (44% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…CustomScrollbar.min.js could save 2.3KiB (27% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/themes/hollins-nc/js/main.js could save 1.5KiB (34% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…d/jquery.easing.1.3.js could save 1.1KiB (58% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…ery.my_add_function.js could save 293B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/themes/hollins-…brokenborder.jquery.js could save 276B (27% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…uery.mousewheel.min.js could save 226B (32% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-drop.min.js could save 128B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-pulsate.min.js could save 128B (26% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-size.min.js could save 128B (11% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-slide.min.js could save 128B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-blind.min.js could save 127B (20% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-clip.min.js could save 127B (24% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-highlight.min.js could save 126B (28% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-shake.min.js could save 126B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-fade.min.js could save 125B (37% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-fold.min.js could save 125B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-scale.min.js could save 125B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-bounce.min.js could save 124B (18% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-explode.min.js could save 124B (18% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-transfer.min.js could save 124B (25% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/jquery.masonry.min.js could save 119B (17% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/progressbar.min.js could save 116B (13% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/mouse.min.js could save 115B (12% reduction) after compression.
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:
priority - 0 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 2.3KiB (60% 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 1.7KiB (23% reduction).
Minifying https://www.hollins.edu/wp-content/plugins/content…y.mCustomScrollbar.css could save 371B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/circula…/circularCountdown.css could save 187B (28% reduction) after compression.
hollins.edu Desktop Resources
| Total Resources | 114 |
| Number of Hosts | 14 |
| Static Resources | 100 |
| JavaScript Resources | 68 |
| CSS Resources | 13 |
hollins.edu Desktop Resource Breakdown
hollins.edu mobile page speed rank
Last tested: 2018-11-26
hollins.edu Mobile Speed Test Quick Summary
priority - 339 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 3.2MiB (81% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/09/achieve.jpg could save 745.8KiB (80% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/09/learn.jpg could save 713.9KiB (77% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/EDW-museum.jpg could save 156KiB (95% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/11/Kantor_0873.jpg could save 146.9KiB (80% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/riding.jpg could save 146.8KiB (94% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/swimmer.jpg could save 132KiB (94% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/mal.jpg could save 118.4KiB (94% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/riding-1.jpg could save 92.6KiB (91% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/1842-patch.jpg could save 92.2KiB (95% reduction).
Compressing and resizing https://www.hollins.edu/wp-content/uploads/2018/11/accepted.jpg could save 86.1KiB (93% reduction).
Compressing https://www.hollins.edu/wp-content/uploads/2018/11/Midsummer_top.jpg could save 57.8KiB (50% reduction).
priority - 10 Reduce server response time
In our test, your server responded in 0.64 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 8 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:
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.googletagmanager.com/gtm.js?id=GTM-PKK88ND (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/181621…1375?v=2.8.33&r=stable (20 minutes)
https://mx.technolutions.net/ping?id=85ef25de-ad7f…8023-ca23-eaa86b4dab27 (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 3 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 32.5KiB (35% reduction).
Minifying https://www.hollins.edu/wp-content/themes/hollins-nc/js/foundation.js could save 7.9KiB (32% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…end/jquery.timeline.js could save 7.7KiB (44% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…CustomScrollbar.min.js could save 2.3KiB (27% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/themes/hollins-nc/js/main.js could save 1.5KiB (34% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…d/jquery.easing.1.3.js could save 1.1KiB (58% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…ery.my_add_function.js could save 293B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/themes/hollins-…brokenborder.jquery.js could save 276B (27% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/content…uery.mousewheel.min.js could save 226B (32% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-drop.min.js could save 128B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-pulsate.min.js could save 128B (26% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-size.min.js could save 128B (11% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-slide.min.js could save 128B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-blind.min.js could save 127B (20% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-clip.min.js could save 127B (24% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-highlight.min.js could save 126B (28% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-shake.min.js could save 126B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-fade.min.js could save 125B (37% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-fold.min.js could save 125B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-scale.min.js could save 125B (21% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-bounce.min.js could save 124B (18% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-explode.min.js could save 124B (18% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/effect-transfer.min.js could save 124B (25% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/jquery.masonry.min.js could save 119B (17% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/progressbar.min.js could save 116B (13% reduction) after compression.
Minifying https://www.hollins.edu/wp-includes/js/jquery/ui/mouse.min.js could save 115B (12% reduction) after compression.
priority - 0 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 2.3KiB (60% 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 1.7KiB (23% reduction).
Minifying https://www.hollins.edu/wp-content/plugins/content…y.mCustomScrollbar.css could save 371B (23% reduction) after compression.
Minifying https://www.hollins.edu/wp-content/plugins/circula…/circularCountdown.css could save 187B (28% reduction) after compression.
hollins.edu Mobile Resources
| Total Resources | 114 |
| Number of Hosts | 14 |
| Static Resources | 99 |
| JavaScript Resources | 68 |
| CSS Resources | 13 |
hollins.edu Mobile Resource Breakdown
hollins.edu mobile page usability
Last tested: 2018-11-26
hollins.edu Mobile Usability Test Quick Summary
priority - 1 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 href="/on-campus/loc…siting-campus/">Plan a Visit</a> and 10 others are close to other tap targets.hollins.edu similar domains
www.hollins.net
www.hollins.org
www.hollins.info
www.hollins.biz
www.hollins.us
www.hollins.mobi
www.ollins.edu
www.hollins.edu
www.bollins.edu
www.hbollins.edu
www.bhollins.edu
www.gollins.edu
www.hgollins.edu
www.ghollins.edu
www.yollins.edu
www.hyollins.edu
www.yhollins.edu
www.uollins.edu
www.huollins.edu
www.uhollins.edu
www.jollins.edu
www.hjollins.edu
www.jhollins.edu
www.nollins.edu
www.hnollins.edu
www.nhollins.edu
www.hllins.edu
www.hillins.edu
www.hoillins.edu
www.hiollins.edu
www.hkllins.edu
www.hokllins.edu
www.hkollins.edu
www.hlllins.edu
www.holllins.edu
www.hlollins.edu
www.hpllins.edu
www.hopllins.edu
www.hpollins.edu
www.holins.edu
www.hoplins.edu
www.holplins.edu
www.hoolins.edu
www.hololins.edu
www.hoollins.edu
www.hoklins.edu
www.holklins.edu
www.holpins.edu
www.hollpins.edu
www.holoins.edu
www.holloins.edu
www.holkins.edu
www.hollkins.edu
www.hollns.edu
www.holluns.edu
www.holliuns.edu
www.holluins.edu
www.holljns.edu
www.hollijns.edu
www.holljins.edu
www.hollkns.edu
www.hollikns.edu
www.hollons.edu
www.hollions.edu
www.hollis.edu
www.hollibs.edu
www.hollinbs.edu
www.hollibns.edu
www.hollihs.edu
www.hollinhs.edu
www.hollihns.edu
www.hollijs.edu
www.hollinjs.edu
www.hollims.edu
www.hollinms.edu
www.hollimns.edu
www.hollin.edu
www.hollinw.edu
www.hollinsw.edu
www.hollinws.edu
www.holline.edu
www.hollinse.edu
www.hollines.edu
www.hollind.edu
www.hollinsd.edu
www.hollinds.edu
www.hollinz.edu
www.hollinsz.edu
www.hollinzs.edu
www.hollinx.edu
www.hollinsx.edu
www.hollinxs.edu
www.hollina.edu
www.hollinsa.edu
www.hollinas.edu
hollins.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.
hollins.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.