Tools & Wizards About Us
comm.stanford.edu screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

comm.stanford.edu

Communication Department

Page Load Speed

2.6 sec in total

First Response

340 ms

Resources Loaded

775 ms

Page Rendered

1.4 sec

comm.stanford.edu screenshot

About Website

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.edu

Key Findings

We analyzed Comm.stanford.edu page load time and found that the first response time was 340 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

comm.stanford.edu performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

comm.stanford.edu

340 ms

js

47 ms

css_wrP9CHmWOMhzfDZQjUO4-_iePHAcFrxdfP0aaD_-cXQ.css

162 ms

all.css

34 ms

v4-shims.css

57 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 57% of them (20 requests) were addressed to the original Comm.stanford.edu, 17% (6 requests) were made to Fonts.gstatic.com and 14% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (340 ms) belongs to the original domain Comm.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.8 kB (7%)

Content Size

4.9 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Comm.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 83.3 kB

  • Original 95.8 kB
  • After minification 89.9 kB
  • After compression 12.5 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 83.3 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.4 MB
  • After minification 4.4 MB

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.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 102.8 kB
  • After minification 102.8 kB
  • After compression 102.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. This website has mostly compressed JavaScripts.

CSS Optimization

-79%

Potential reduce by 237.4 kB

  • Original 301.4 kB
  • After minification 300.8 kB
  • After compression 64.0 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 237.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (37%)

Requests Now

27

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 27 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

comm.stanford.edu

comm.stanford.edu

340 ms

js

js

47 ms

css_wrP9CHmWOMhzfDZQjUO4-_iePHAcFrxdfP0aaD_-cXQ.css

css_wrP9CHmWOMhzfDZQjUO4-_iePHAcFrxdfP0aaD_-cXQ.css

162 ms

all.css

all.css

34 ms

v4-shims.css

v4-shims.css

57 ms

css_OFb13-ISKy5dSi-o288vWjHn_RZ40KKxm32xIoQnI_E.css

css_OFb13-ISKy5dSi-o288vWjHn_RZ40KKxm32xIoQnI_E.css

166 ms

css_-lOjFKCCplGljRuVHp02U-mKiNm_xLBiGZ4vZqhm65E.css

css_-lOjFKCCplGljRuVHp02U-mKiNm_xLBiGZ4vZqhm65E.css

82 ms

modernizr.min.js

modernizr.min.js

57 ms

js_xAeqjffksr2iDot1mtaS0ZTb6faap7iGrQC7oO7n1Eo.js

js_xAeqjffksr2iDot1mtaS0ZTb6faap7iGrQC7oO7n1Eo.js

37 ms

css2

css2

29 ms

css2

css2

47 ms

css2

css2

53 ms

css2

css2

52 ms

css2

css2

54 ms

artboard_57lrv_1.jpg

artboard_57lrv_1.jpg

95 ms

a1r_0.jpeg

a1r_0.jpeg

58 ms

screenshot_2023-05-23_at_10.28.55_am_0.png

screenshot_2023-05-23_at_10.28.55_am_0.png

93 ms

misinformation_0.jpeg

misinformation_0.jpeg

91 ms

welfare-autocrats_0.jpeg

welfare-autocrats_0.jpeg

92 ms

conversation_0.jpeg

conversation_0.jpeg

91 ms

metrics-at-work_0.jpeg

metrics-at-work_0.jpeg

150 ms

polarization_0.jpeg

polarization_0.jpeg

96 ms

dry_0.jpeg

dry_0.jpeg

141 ms

walk-phone_0.jpeg

walk-phone_0.jpeg

119 ms

content-switching_0.jpeg

content-switching_0.jpeg

118 ms

democracys-detectives_0.jpeg

democracys-detectives_0.jpeg

120 ms

avatar-interaction_0.jpeg

avatar-interaction_0.jpeg

130 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky461EO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky461EO.woff

18 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm61EO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm61EO.woff

55 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw461EO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw461EO.woff

56 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7FEO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7FEO.woff

58 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7FEO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7FEO.woff

57 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7FEO.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7FEO.woff

57 ms

stanford.woff

stanford.woff

36 ms

css_exH5cq1XGDFla3PCwwGhpQ4TZB8peGfsqrxWX1UTkgU.css

css_exH5cq1XGDFla3PCwwGhpQ4TZB8peGfsqrxWX1UTkgU.css

33 ms

Accessibility Review

comm.stanford.edu accessibility score

100

Accessibility Issues

Best Practices

comm.stanford.edu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

comm.stanford.edu SEO score

90

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: