6.8 sec in total
1.6 sec
4.9 sec
268 ms
Welcome to uhr.stanford.edu homepage info - get ready to check Uhr Stanford best content for United States right away, or after learning these important things about uhr.stanford.edu
Visit uhr.stanford.eduWe analyzed Uhr.stanford.edu page load time and found that the first response time was 1.6 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
uhr.stanford.edu performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value10.7 s
0/100
25%
Value6.1 s
45/100
10%
Value780 ms
37/100
30%
Value0.154
75/100
15%
Value11.0 s
21/100
10%
1575 ms
540 ms
133 ms
351 ms
297 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Uhr.stanford.edu, 46% (38 requests) were made to Cardinalatwork.stanford.edu and 29% (24 requests) were made to Files-cardinalatwork-stanford-edu.s3-us-west-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Files-cardinalatwork-stanford-edu.s3-us-west-2.amazonaws.com.
Page size can be reduced by 1.1 MB (22%)
4.9 MB
3.8 MB
In fact, the total size of Uhr.stanford.edu main page is 4.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 65.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 65.0 kB or 80% of the original size.
Potential reduce by 57.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Uhr Stanford images are well optimized though.
Potential reduce by 432.5 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 432.5 kB or 69% of the original size.
Potential reduce by 556.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Uhr.stanford.edu needs all CSS files to be minified and compressed as it can save up to 556.9 kB or 83% of the original size.
Number of requests can be reduced by 29 (40%)
73
44
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uhr Stanford. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
uhr.stanford.edu
1575 ms
cardinalatwork.stanford.edu
540 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
133 ms
css_JsNupfpWENtZl3PsbtMoRvOBlo9YKAdVhAdHLPsR8FE.css
351 ms
css_9tSZ0nPz-1H4xvY-ur8aWaAgaF4oAzsrLDvWf6KvPSU.css
297 ms
css_0XDvGz6L0_pNKyQ2eMu1kJ98Y14D_J2G7R_xXR3a0ec.css
350 ms
css_N7sR9xJhpUrqJMLbLfAalK-7CB-vByTDk9tzB2C4uSA.css
281 ms
css_WLwgzL11aFJS2a8kmXNeG555gPx1kMUk_pwjOtoZ3w4.css
506 ms
css_QQ79-K-C0Ut1cyKkT-VO9XqyTXLZYNFy139_1rADe8A.css
651 ms
css_ukJ6Vz1RUXTotmv2PV7a95JGA5MsUGoQMXWK4XfI73Y.css
532 ms
stanford-light.css
438 ms
styles-plain.css
509 ms
fonts-sans.css
426 ms
css_2auMbUiSsPOfSNv8FwdJmEWQnJjfoEDONFQir0yRAz8.css
668 ms
js_ZDOaep6HA5A0eriyiN-YaNv7MHsjd-FIuFyilZ2o5cw.js
758 ms
js_g98Ekqvuj1mMaUqTkLdcrMmJymw4aFC5YyzBQBviahY.js
631 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
590 ms
js_lKHOOLVBVf9l38oVBXDCFyFWqnj9Bwel6crRsPRJNQ0.js
898 ms
js_LUVYSmougkvHVdirkHbKGZ6JZwZSbvL88WnHqF5fvbY.js
696 ms
js_OSJgJBUodI4V-kqY0Yv4c0hmKk-yc07xnwK3S_ktKfo.js
803 ms
js_QJHvRlN9zNXiPD6q_Sth7RO3pfCW16yNcvTGnMJfaxg.js
743 ms
js_OQpsMDZ1OlvhINiXqh-1AOoZBOIYOEKtgmpmnN_J43s.js
778 ms
js_6lEiBKPgYd0J4j7bMPiKzKQR5ow6mo0LR6Gtg_UkEpo.js
787 ms
css
55 ms
prum.min.js
22 ms
analytics.js
237 ms
caw-logo.png
682 ms
c4gKTN2IZRU
301 ms
header-stanford-logo@2x.png
300 ms
searchbutton.png
305 ms
searchbutton.png
304 ms
caw-btn-arrow-right.png
304 ms
footer-stanford-logo@2x.png
299 ms
0058_zhenanbao_670px_2.png
1513 ms
priscillafiden_670px_3coloradjust_0.png
1631 ms
0501_daudhaidari_670x670_2.png
1792 ms
staff-survey-news2.png
1153 ms
caw-shadow_0.png
709 ms
stanfordsweetener_460px_cawred.png
826 ms
ticketsvintage_admitone_870x441.png
1098 ms
baseball_040316-096_870x354.png
1064 ms
content.jpg
1159 ms
steppingstonessuccessprogram_080208-033_870x330.png
1400 ms
brownbaglunchwithapplevintage_870x398.png
1344 ms
continuingstudies_maturefemalestudent_61323167_1200x740_0.png
1314 ms
diningyummycafeteria_72210010_870x370.png
1477 ms
colormgmtprinting_dpc_13283418_860x438.png
1522 ms
appleproducts_variety_white_860x370_2_0.png
1587 ms
stanfordhr2014391-bicycles_860x498.png
1717 ms
takingnotes_8670x361.png
1615 ms
hoovertower_ianterpin_idt_0559b_870x330_0.png
1710 ms
asianmantalkingtocolleagues_870x330.png
1784 ms
conference_workshopstables_60093231_860x370_crop.png
1719 ms
techbusinessthinking_870x443.jpg
1781 ms
caw-logo-horizontal.png
1832 ms
125_graphicmark.png
1857 ms
sdk.js
322 ms
caw-bkg-short.jpg
267 ms
facebook.png
246 ms
youtube.png
206 ms
social-facebook.png
223 ms
social-youtube.png
224 ms
ext-link-icon_1.png
223 ms
caw-arrow-left.png
263 ms
caw-arrow-right.png
393 ms
ajax-loader.gif
397 ms
ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf
35 ms
toadOcfmlt9b38dHJxOBGPS42wKzre0cxmO5m5GyTsY.ttf
52 ms
toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf
77 ms
toadOcfmlt9b38dHJxOBGLlcMrNrsnL9dgADnXgYJjs.ttf
78 ms
slick.woff
395 ms
collect
30 ms
www-embed-player-vflQrT_sR.css
88 ms
www-embed-player.js
119 ms
base.js
189 ms
86 ms
xd_arbiter.php
252 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
43 ms
ad_status.js
70 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
21 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
21 ms
css_nTr55mbZYlMSsBXnLjRgu7jXCLkPIwg_iGLiIvrYokQ.css
112 ms
uhr.stanford.edu accessibility score
uhr.stanford.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
uhr.stanford.edu SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uhr.stanford.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Uhr.stanford.edu main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
uhr.stanford.edu
Open Graph description is not detected on the main page of Uhr Stanford. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: