ucsf.edu website information.
ucsf.edu domain name is registered by .EDU top-level domain registry. See the other sites registred in .EDU domain zone.
No name server records were found.
and probably website ucsf.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 ucsf.edu position was 1105 (in the world). The lowest Alexa rank position was 1202. Now website ucsf.edu ranked in Alexa database as number 1194 (in the world).
Website ucsf.edu Desktop speed measurement score (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.
ucsf.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 ucsf.edu (24/100) is better than the results of 6.28% 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-20-2024 | N/A | N/A |
| Apr-19-2024 | 1,194 | 0 |
| Apr-18-2024 | 1,194 | 4 |
| Apr-17-2024 | 1,198 | -5 |
| Apr-16-2024 | 1,193 | -1 |
| Apr-15-2024 | 1,192 | 1 |
| Apr-14-2024 | 1,193 | -3 |
Advertisement
ucsf.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.
ucsf.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: UCSF.EDU
Registrant:
University of California at San Francisco
Room MUG-14
500 Parnassus Ave.
San Francisco, CA 94143-0225
US
Administrative Contact:
IT Operations
University of California, San Francisco
Suite 601
1855 Folsom
San Francisco, CA 94143-0225
US
+1.4155144100
it.networkteam@ucsf.edu
Technical Contact:
IT Operations
University of California, San Francisco
Suite 601
1855 Folsom St
San Francisco, CA 94143-0225
US
+1.4155144100
it.networkteam@ucsf.edu
Name Servers:
WTC-AC179-ENS1.UCSF.EDU
2408-0C50-ENS1.UCSF.EDU
3002-S251-ENS1.UCSF.EDU
Domain record activated: 21-Feb-1986
Domain record last updated: 18-Dec-2019
Domain expires: 31-Jul-2022
ucsf.edu server information
Servers Location
| IP Address |
|---|
| Country |
|---|
ucsf.edu desktop page speed rank
Last tested: 2019-12-02
ucsf.edu Desktop Speed Test Quick Summary
priority - 10 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 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:
http://ucsf.edu/modules/custom/ckeditor_y3ti_plugi…nents-loader.js?q0l1sp
http://ucsf.edu/modules/custom/ckeditor_y3ti_plugi…ponents-lite.js?q0l1sp
https://calendar.ucsf.edu/widget/view?schools=ucsf…ate=list-2019-redesign
http://ucsf.edu/sites/default/files/js/js_XGay61Kj…GYtgCJSwyzIwrkXoHC4.js
Optimize CSS Delivery of the following:
http://ucsf.edu/sites/default/files/css/css_bX-LgH…5678DpG8PJA.css?q0l1sp
priority - 7 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 69.1KiB (66% reduction).
priority - 2 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.
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-TSHCJ6 (15 minutes)
https://js-agent.newrelic.com/nr-1153.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1 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 9.3KiB (13% reduction).
Minifying http://ucsf.edu/modules/custom/ckeditor_y3ti_plugi…nents-loader.js?q0l1sp could save 763B (55% reduction) after compression.
Minifying http://ucsf.edu/modules/custom/ckeditor_y3ti_plugi…style-interface.min.js could save 286B (23% reduction) after compression.
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 7.8KiB (57% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/cta-arrow-white-left.svg could save 1.2KiB (71% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/magnifier.svg could save 1KiB (64% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/cta-arrow.svg could save 898B (67% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/images/footer-logo.svg could save 766B (48% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/card/directions.svg could save 751B (58% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/logo.svg could save 650B (47% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/card/transit.svg could save 506B (50% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/ext-link-gray.svg could save 280B (42% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/x-large.svg could save 246B (43% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/card/campus.svg could save 245B (40% reduction).
Compressing http://ucsf.edu/themes/custom/ucsf/assets/images/external-link.svg could save 181B (38% reduction).
priority - 0 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.6KiB (52% reduction).
Compressing https://pbs.twimg.com/profile_images/859082365041344512/tODmEcwr_normal.jpg could save 936B (59% reduction).
Compressing http://d3e1o4bcbhmj8g.cloudfront.net/assets/platfo…bout/widget_footer.png could save 726B (42% reduction).
ucsf.edu Desktop Resources
| Total Resources | 60 |
| Number of Hosts | 12 |
| Static Resources | 45 |
| JavaScript Resources | 13 |
| CSS Resources | 2 |
ucsf.edu Desktop Resource Breakdown
ucsf.edu mobile page speed rank
Last tested: 2017-12-02
ucsf.edu Mobile Speed Test Quick Summary
priority - 201 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.9MiB (56% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…rons.jpg?itok=LxIvvUEW could save 185.6KiB (72% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…alth.jpg?itok=0-UG68yq could save 163.1KiB (64% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…r_01.jpg?itok=zDLnb0ba could save 153.3KiB (70% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…_013.jpg?itok=3nY1iznT could save 134.4KiB (62% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…inic.jpg?itok=bJ_RPZJh could save 130.3KiB (61% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…AIDS.jpg?itok=HF53yqcE could save 123.9KiB (63% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…room.jpg?itok=Zok1xe9G could save 123.3KiB (63% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…omo2.jpg?itok=RgYE3jSW could save 112.8KiB (57% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…ting.jpg?itok=yDqKf0Fi could save 110.1KiB (60% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…2018.jpg?itok=GTRCdquS could save 95.9KiB (65% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…ing2.jpg?itok=gJFDHtgE could save 94.4KiB (75% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…West.jpg?itok=WAA2NlL9 could save 83.1KiB (62% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…el_0.jpg?itok=PI1hFMP_ could save 80.4KiB (59% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…y-01.png?itok=M-a9I0pX could save 48.7KiB (18% reduction).
Compressing https://www.ucsf.edu/sites/default/files/field/ima…s/Best-in-the-West.jpg could save 24.9KiB (17% reduction).
Compressing https://www.ucsf.edu/sites/default/files/styles/pa…romo.png?itok=blmmvK5Y could save 11.6KiB (13% reduction).
Compressing https://www.ucsf.edu/sites/default/files/About-Patient-Care-thumb.jpg could save 8.6KiB (20% reduction).
Compressing and resizing https://www.ucsf.edu/sites/all/themes/ucsf_base/logo.png could save 4.4KiB (76% reduction).
Compressing https://d3e1o4bcbhmj8g.cloudfront.net/photos/57725…0844db2f5cda60c4fa.jpg could save 1.4KiB (50% reduction).
Compressing https://d3e1o4bcbhmj8g.cloudfront.net/photos/58238…7d408d2d19c0503907.jpg could save 701B (35% reduction).
priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 10 blocking script resources and 11 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://calendar.ucsf.edu/widget/view?schools=ucsf…m=4&picks=1&hidedesc=1
https://www.ucsf.edu/sites/all/modules/contrib/res…/respond.min.js?p083o2
https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js
https://www.ucsf.edu/sites/all/modules/contrib/lig…lightbox.js?1512253815
https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js
https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js
https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js
https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js
https://cdnjs.cloudflare.com/ajax/libs/modernizr/2.0.6/modernizr.min.js
Optimize CSS Delivery of the following:
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://hello.myfonts.net/count/2c06fd
https://hello.myfonts.net/count/2d0d15
https://hello.myfonts.net/count/2d0d15
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
https://www.ucsf.edu/sites/default/files/advagg_cs…B2rIImtEjwBZpCp-_w.css
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.ucsf.edu/
https://www.ucsf.edu/
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.
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://dpi1c6z6qg9qf.cloudfront.net/client/v3/tutorialize.js.gz (expiration not specified)
https://calendar.ucsf.edu/widget/view?schools=ucsf…m=4&picks=1&hidedesc=1 (10 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 4 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 38.2KiB (33% reduction).
Minifying https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js could save 4.9KiB (13% reduction) after compression.
Minifying https://www.ucsf.edu/sites/all/modules/contrib/lig…lightbox.js?1512253815 could save 3.3KiB (34% reduction) after compression.
Minifying https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js could save 1,002B (53% reduction) after compression.
Minifying https://www.ucsf.edu/sites/default/files/advagg_js…dB2rIImtEjwBZpCp-_w.js could save 753B (47% reduction) after compression.
priority - 2 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 20.2KiB (82% reduction).
Compressing https://d31qbv1cthcecs.cloudfront.net/atrk.js could save 2.2KiB (61% reduction).
ucsf.edu Mobile Resources
| Total Resources | 83 |
| Number of Hosts | 22 |
| Static Resources | 63 |
| JavaScript Resources | 20 |
| CSS Resources | 12 |
ucsf.edu Mobile Resource Breakdown
ucsf.edu mobile page usability
Last tested: 2017-12-02
ucsf.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 href="#main-content" class="element-invisi…kip-to-content">Skip to main content</a> is close to 1 other tap targets.ucsf.edu similar domains
www.ucsf.net
www.ucsf.org
www.ucsf.info
www.ucsf.biz
www.ucsf.us
www.ucsf.mobi
www.csf.edu
www.ucsf.edu
www.ycsf.edu
www.uycsf.edu
www.yucsf.edu
www.hcsf.edu
www.uhcsf.edu
www.hucsf.edu
www.jcsf.edu
www.ujcsf.edu
www.jucsf.edu
www.icsf.edu
www.uicsf.edu
www.iucsf.edu
www.usf.edu
www.uxsf.edu
www.ucxsf.edu
www.uxcsf.edu
www.udsf.edu
www.ucdsf.edu
www.udcsf.edu
www.ufsf.edu
www.ucfsf.edu
www.ufcsf.edu
www.uvsf.edu
www.ucvsf.edu
www.uvcsf.edu
www.ucf.edu
www.ucwf.edu
www.ucswf.edu
www.ucwsf.edu
www.ucef.edu
www.ucsef.edu
www.ucesf.edu
www.ucdf.edu
www.ucsdf.edu
www.uczf.edu
www.ucszf.edu
www.uczsf.edu
www.ucxf.edu
www.ucsxf.edu
www.ucaf.edu
www.ucsaf.edu
www.ucasf.edu
www.ucs.edu
www.ucsc.edu
www.ucsfc.edu
www.ucscf.edu
www.ucsd.edu
www.ucsfd.edu
www.ucsr.edu
www.ucsfr.edu
www.ucsrf.edu
www.ucst.edu
www.ucsft.edu
www.ucstf.edu
www.ucsg.edu
www.ucsfg.edu
www.ucsgf.edu
www.ucsv.edu
www.ucsfv.edu
www.ucsvf.edu
ucsf.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.
ucsf.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.