2.9 sec in total
294 ms
2.4 sec
257 ms
Click here to check amazing Me Stanford content for United States. Otherwise, check out these important facts you probably never knew about me.stanford.edu
Visit me.stanford.eduWe analyzed Me.stanford.edu page load time and found that the first response time was 294 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
me.stanford.edu performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value6.1 s
12/100
25%
Value3.6 s
86/100
10%
Value80 ms
99/100
30%
Value0.026
100/100
15%
Value5.9 s
66/100
10%
294 ms
95 ms
168 ms
174 ms
539 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 76% of them (47 requests) were addressed to the original Me.stanford.edu, 16% (10 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Me.stanford.edu.
Page size can be reduced by 595.2 kB (51%)
1.2 MB
581.7 kB
In fact, the total size of Me.stanford.edu main page is 1.2 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. 45% of websites need less resources to load. Images take 433.9 kB which makes up the majority of the site volume.
Potential reduce by 63.4 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 63.4 kB or 83% of the original size.
Potential reduce by 19.9 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. Me Stanford images are well optimized though.
Potential reduce by 274.8 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 274.8 kB or 73% of the original size.
Potential reduce by 237.1 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. Me.stanford.edu needs all CSS files to be minified and compressed as it can save up to 237.1 kB or 82% of the original size.
Number of requests can be reduced by 19 (37%)
51
32
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Me 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 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
me.stanford.edu
294 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
95 ms
css_JsNupfpWENtZl3PsbtMoRvOBlo9YKAdVhAdHLPsR8FE.css
168 ms
css_ikO0Dxm7cLx8sij8aCz93A0aaPm7Vn5LlfEi4H4knHY.css
174 ms
css_515M-xmuI5BfL3_0WJ0WUJIhjq0JRA7EycVOU7KVncI.css
539 ms
css_DEcSjCp-53I4R68YkbYpVCB5xAVMeyp8BxdCfaoMuT8.css
172 ms
css_CxPbaFg3cM3FxG3ej086r7TdSDMr9iNmYpKiQireSWI.css
339 ms
css_uzop0G6Q3_XDucBFoRXKpEGkYcXZ1VBftlFJPKlgXUA.css
187 ms
js_ZDOaep6HA5A0eriyiN-YaNv7MHsjd-FIuFyilZ2o5cw.js
413 ms
js_g98Ekqvuj1mMaUqTkLdcrMmJymw4aFC5YyzBQBviahY.js
264 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
260 ms
js_-cetIfXDXXJJq0AucmmhPBg5VxxsP7eFUYHwSmiDlEw.js
457 ms
js_LxKCaoSyzyisxaz6qBZBjJozp09Oh6fhKjbYBvTyHrA.js
351 ms
js_K49aIUKzfLNeWGtWtukLf9cDppj8EXc7ykLu2aTJx4A.js
352 ms
js_mMIgUqMwfpz7hXoU459Fiu6lZKZp2hydclUjuup1Rfc.js
424 ms
js_Sv8uJlue17zb2YFPCC_BM7KfY-1RosuFAA3ztby-e3U.js
431 ms
js_6lEiBKPgYd0J4j7bMPiKzKQR5ow6mo0LR6Gtg_UkEpo.js
433 ms
css
63 ms
css
14 ms
css
25 ms
analytics.js
144 ms
header-stanford-logo@2x.png
193 ms
logo.png
127 ms
searchbutton.png
127 ms
me.jpg
1281 ms
nanotube_cai.jpg
333 ms
birds1_680x320.jpg
252 ms
dsc_7438_870x330.jpg
460 ms
hair_cells_mems_device_pruitt_0.jpg
415 ms
sheppard_prof_of_the_year.jpg
447 ms
btn-arrow-left.png
336 ms
btn-arrow-right.png
416 ms
bullet.gif
418 ms
dsc_0502-68.jpg
664 ms
3d-680x320-follmer_0.jpg
501 ms
hedgehog-slider-0216_0_0.jpg
504 ms
muscle_teaser.jpg
536 ms
design-group_280x145.jpg
739 ms
flow-physics_280x145.jpg
665 ms
mechanics-and-computation_280x145.jpg
585 ms
thermosciences_280x145.jpg
626 ms
forme.jpg
669 ms
design-research-280x145.jpg
803 ms
turbulence_280x145.jpg
827 ms
predictive-science_280x145.jpg
830 ms
facebook.png
752 ms
twitter.png
820 ms
google.png
836 ms
linkedin.png
893 ms
footer-stanford-logo@2x.png
901 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
68 ms
toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff
120 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
169 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
184 ms
M2Jd71oPJhLKp0zdtTvoMzNrcjQuD0pTu1za2FULaMs.woff
241 ms
fpTVHK8qsXbIeTHTrnQH6GGomRtBD2u8FwSY4jjlmeA.woff
241 ms
a5QZnvmn5amyNI-t2BMkWHpumDtkw9GHrrDfd7ZnWpU.woff
241 ms
4j4TR-EfnvCt43InYpUNDKxza3rXaV_G32gF04a66fI.woff
242 ms
3IFMwfRa07i-auYR-B-zNXhCUOGz7vYGh680lGh-uXM.woff
184 ms
rEy5tGc5HdXy56Xvd4f3I9Od4RnLmtUrdSQkDmC5b8k.woff
241 ms
collect
16 ms
css_nTr55mbZYlMSsBXnLjRgu7jXCLkPIwg_iGLiIvrYokQ.css
105 ms
me.stanford.edu accessibility score
me.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
me.stanford.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Me.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 Me.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.
me.stanford.edu
Open Graph description is not detected on the main page of Me 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: