4.4 sec in total
516 ms
3.7 sec
186 ms
Welcome to sites.stanford.edu homepage info - get ready to check Sites Stanford best content for United States right away, or after learning these important things about sites.stanford.edu
Stanford Sites is a free, self-service tool for building and managing websites for university work. It offers design flexibility, integration with Stanford systems, and substantial functionality throu...
Visit sites.stanford.eduWe analyzed Sites.stanford.edu page load time and found that the first response time was 516 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sites.stanford.edu performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.2 s
2/100
25%
Value5.5 s
54/100
10%
Value30 ms
100/100
30%
Value0.157
74/100
15%
Value6.9 s
54/100
10%
516 ms
449 ms
676 ms
489 ms
400 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Sites.stanford.edu, 60% (31 requests) were made to Uit.stanford.edu and 15% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (676 ms) relates to the external source Itservices.stanford.edu.
Page size can be reduced by 476.3 kB (74%)
643.9 kB
167.6 kB
In fact, the total size of Sites.stanford.edu main page is 643.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. CSS take 354.0 kB which makes up the majority of the site volume.
Potential reduce by 32.2 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 32.2 kB or 77% of the original size.
Potential reduce by 5.8 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. Obviously, Sites Stanford needs image optimization as it can save up to 5.8 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 145.6 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 145.6 kB or 64% of the original size.
Potential reduce by 292.8 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. Sites.stanford.edu needs all CSS files to be minified and compressed as it can save up to 292.8 kB or 83% of the original size.
Number of requests can be reduced by 31 (74%)
42
11
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sites 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 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
sites.stanford.edu
516 ms
sites.stanford.edu
449 ms
stanfordsites
676 ms
stanfordsites
489 ms
stanfordsites
400 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
89 ms
css_8WsBE51ZLaFfp0zwBAlE3X3LwLPjbG0g87gpHZu-DlA.css
175 ms
css_b_V5rf2qKXfXoVMOGEx89EWxe3ycPAaCUJ73t5anm1o.css
344 ms
css_ZkUqnHCHG4qW55MrylMtK30A9SRgVPWYXgIOQgJDQ4M.css
358 ms
stanford_itservices_custom.css
258 ms
css_KCjy3HSviVu-ALy_O4cIbhr92oAg52WQk2vqw-wGcss.css
261 ms
jquery-1.9.1.min.js
438 ms
jquery-migrate-1.2.1.min.js
271 ms
jquery.once.js
355 ms
drupal.js
356 ms
google_cse.js
372 ms
googleanalytics.js
427 ms
bootstrap.min.js
435 ms
open_framework.js
433 ms
jquery.placeholder.min.js
434 ms
stanford-framework.js
510 ms
stanford_itservices.js
512 ms
footable.js
517 ms
jquery.fancybox.pack.js
520 ms
js_injector_10.js
525 ms
js_injector_11.js
527 ms
js_injector_12.js
593 ms
js_injector_15.js
593 ms
css
57 ms
css
72 ms
cse.js
72 ms
analytics.js
29 ms
collect
23 ms
jsapi
53 ms
default+en.css
4 ms
default.css
46 ms
default+en.I.js
16 ms
css_nTr55mbZYlMSsBXnLjRgu7jXCLkPIwg_iGLiIvrYokQ.css
177 ms
default.css
15 ms
header-stanford-logo@2x.png
120 ms
logo.png
118 ms
bullet.gif
119 ms
footer-stanford-logo@2x.png
119 ms
async-ads.js
68 ms
google_custom_search_watermark.gif
53 ms
small-logo.png
24 ms
search_box_icon.png
85 ms
clear.png
83 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
27 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
32 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
81 ms
fontawesome-webfont.woff
350 ms
sites.stanford.edu accessibility score
sites.stanford.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
sites.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 Sites.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 Sites.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.
sites.stanford.edu
Open Graph description is not detected on the main page of Sites 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: