10.8 sec in total
2.1 sec
8.4 sec
262 ms
Click here to check amazing Comm Stanford content for United States. Otherwise, check out these important facts you probably never knew about comm.stanford.edu
Visit comm.stanford.eduWe analyzed Comm.stanford.edu page load time and found that the first response time was 2.1 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
comm.stanford.edu performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value4.5 s
37/100
25%
Value3.2 s
92/100
10%
Value140 ms
95/100
30%
Value0.131
81/100
15%
Value5.0 s
76/100
10%
2087 ms
304 ms
279 ms
194 ms
199 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 92% of them (57 requests) were addressed to the original Comm.stanford.edu, 3% (2 requests) were made to Stanford.edu and 2% (1 request) were made to P.jwpcdn.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Comm.stanford.edu.
Page size can be reduced by 508.9 kB (9%)
5.6 MB
5.1 MB
In fact, the total size of Comm.stanford.edu main page is 5.6 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 33.3 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 4.5 kB, which is 11% 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 33.3 kB or 80% of the original size.
Potential reduce by 138.0 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. Comm Stanford images are well optimized though.
Potential reduce by 228.0 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 228.0 kB or 71% of the original size.
Potential reduce by 109.6 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. Comm.stanford.edu needs all CSS files to be minified and compressed as it can save up to 109.6 kB or 84% of the original size.
Number of requests can be reduced by 29 (48%)
60
31
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comm 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 15 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
comm.stanford.edu
2087 ms
su-identity.css
304 ms
base.css
279 ms
skeleton.css
194 ms
comments.css
199 ms
buttons.css
286 ms
superfish.css
207 ms
prettyPhoto.css
502 ms
flexslider.css
251 ms
styles.css
442 ms
styles.css
326 ms
youtube-playlist-thumbs.css
341 ms
wp-paginate.css
342 ms
jquery.js
957 ms
jquery-migrate.min.js
417 ms
jwplayer.js
83 ms
ajaxhandlergplwt.js
444 ms
typography-sans.css
423 ms
skin-dark.css
567 ms
style.css
613 ms
comm.css
617 ms
wp-emoji-release.min.js
427 ms
jquery.flexslider.js
598 ms
jquery.isotope.js
545 ms
jquery.prettyPhoto.js
508 ms
jquery.hoverIntent.js
517 ms
superfish.js
521 ms
supersubs.js
599 ms
chosen.jquery.js
608 ms
skeleton-key.js
612 ms
jquery.form.min.js
914 ms
scripts.js
692 ms
ga.js
6 ms
__utm.gif
29 ms
brandbar-stanford-logo@2x.png
72 ms
noise-grey.jpg
99 ms
pattern_diagonal_medium.png
100 ms
comm-banner.png
269 ms
uparrow.png
108 ms
slide-shadow.png
113 ms
pan-slide.png
4152 ms
hancock-slide.jpg
2736 ms
africa-dp-slide.jpg
1251 ms
newsroom-slide.jpg
4104 ms
political-confrontation.png
2122 ms
comp-journalism-slide.png
1348 ms
democratic-surround-slide.png
5614 ms
coral-world-slide.jpg
1771 ms
surveys-slide.png
4528 ms
hbr-games.png
5298 ms
temp-anomolies.jpg
3237 ms
img-bg-pat.png
3578 ms
pop_link.png
3670 ms
post_link.png
3761 ms
turner-chicago.jpg
4349 ms
liautaud-thumbnail.jpg
4837 ms
linen-black.jpg
4618 ms
pattern_diagonal_dark.png
4441 ms
SourceSansPro-Regular-webfont.woff
4660 ms
aller_rg-webfont.svg
5112 ms
flexslider_direction_nav.png
4468 ms
dropdown_right.png
4548 ms
comm.stanford.edu accessibility score
comm.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
comm.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 Comm.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 Comm.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.
comm.stanford.edu
Open Graph description is not detected on the main page of Comm 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: