5.6 sec in total
126 ms
5.2 sec
321 ms
Visit canvas.stanford.edu now to see the best up-to-date Canvas Stanford content for United States and also check out these interesting facts you probably never knew about canvas.stanford.edu
Log in here to Stanford's main Canvas instance
Visit canvas.stanford.eduWe analyzed Canvas.stanford.edu page load time and found that the first response time was 126 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
canvas.stanford.edu performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value6.1 s
12/100
25%
Value4.5 s
73/100
10%
Value60 ms
100/100
30%
Value0
100/100
15%
Value5.5 s
71/100
10%
126 ms
129 ms
33 ms
520 ms
309 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original Canvas.stanford.edu, 54% (19 requests) were made to Web.stanford.edu and 14% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Web.stanford.edu.
Page size can be reduced by 259.4 kB (15%)
1.7 MB
1.5 MB
In fact, the total size of Canvas.stanford.edu main page is 1.7 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 6.2 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.2 kB or 85% of the original size.
Potential reduce by 77.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. Canvas Stanford images are well optimized though.
Potential reduce by 32.9 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 32.9 kB or 32% of the original size.
Potential reduce by 131.4 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. Canvas.stanford.edu needs all CSS files to be minified and compressed as it can save up to 131.4 kB or 81% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Canvas 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 5 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
canvas.stanford.edu
126 ms
canvas.stanford.edu
129 ms
login
33 ms
discovery
520 ms
309 ms
bootstrap.min.css
820 ms
font-awesome.min.css
102 ms
base.min.css
518 ms
custom_A.css
362 ms
analytics.js
144 ms
jquery.min.js
152 ms
modernizr.custom.17475.js
366 ms
bootstrap.min.js
609 ms
base.js
305 ms
custom.js
391 ms
su-identity.css
399 ms
css
162 ms
css
17 ms
collect
97 ms
brandbar-stanford-logo@2x.png
97 ms
Canvas_color_web.png
88 ms
campusBG_A_lg.jpg
1660 ms
GSB_noGutter.png
577 ms
CS_noGutter.png
338 ms
SU_NoGutter.png
3159 ms
campusBG_A_md.jpg
1078 ms
campusBG_A_sm.jpg
1917 ms
comp.jpg
1067 ms
newsusage.jpg
941 ms
footer-stanford-logo@2x.png
1028 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
28 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
39 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
57 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
57 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
57 ms
canvas.stanford.edu accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
canvas.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
canvas.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 Canvas.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 Canvas.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.
canvas.stanford.edu
Open Graph data is detected on the main page of Canvas Stanford. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: