Tools & Wizards About Us
summercollege.stanford.edu screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

summercollege.stanford.edu

Stanford Summer Session The Fourth Academic Quarter

Page Load Speed

806 ms in total

First Response

18 ms

Resources Loaded

580 ms

Page Rendered

208 ms

summercollege.stanford.edu screenshot

About Website

Welcome to summercollege.stanford.edu homepage info - get ready to check Summer College Stanford best content for United States right away, or after learning these important things about summercollege.stanford.edu

Be a visiting Stanford student this summer. Study alongside a dynamic student body from more than 40 countries and engage in community building programming that meets you on your own terms. Earn credi...

Visit summercollege.stanford.edu

Key Findings

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

Performance Metrics

summercollege.stanford.edu performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value2,280 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

summercollege.stanford.edu

18 ms

summer.stanford.edu

161 ms

js

58 ms

google_tag.script.js

15 ms

ajax-progress.module.css

21 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Summercollege.stanford.edu, 88% (91 requests) were made to Summer.stanford.edu and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Cdn.jsdelivr.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.0 kB (43%)

Content Size

326.5 kB

After Optimization

186.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Summercollege.stanford.edu main page is 326.5 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. 55% of websites need less resources to load. HTML takes 125.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 100.8 kB

  • Original 125.4 kB
  • After minification 89.7 kB
  • After compression 24.6 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 35.7 kB, which is 28% 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 100.8 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 780 B

  • Original 23.2 kB
  • After minification 22.5 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. Summer College Stanford images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 15.8 kB

  • Original 124.0 kB
  • After minification 124.0 kB
  • After compression 108.3 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 15.8 kB or 13% of the original size.

CSS Optimization

-42%

Potential reduce by 22.7 kB

  • Original 53.8 kB
  • After minification 46.1 kB
  • After compression 31.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. Summercollege.stanford.edu needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 93 (92%)

Requests Now

101

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Summer College 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 34 to 1 for JavaScripts and from 61 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

summercollege.stanford.edu

summercollege.stanford.edu

18 ms

summer.stanford.edu

summer.stanford.edu

161 ms

js

js

58 ms

google_tag.script.js

google_tag.script.js

15 ms

ajax-progress.module.css

ajax-progress.module.css

21 ms

align.module.css

align.module.css

41 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

40 ms

fieldgroup.module.css

fieldgroup.module.css

39 ms

container-inline.module.css

container-inline.module.css

40 ms

clearfix.module.css

clearfix.module.css

40 ms

details.module.css

details.module.css

41 ms

hidden.module.css

hidden.module.css

51 ms

item-list.module.css

item-list.module.css

50 ms

js.module.css

js.module.css

50 ms

nowrap.module.css

nowrap.module.css

50 ms

position-container.module.css

position-container.module.css

49 ms

progress.module.css

progress.module.css

48 ms

reset-appearance.module.css

reset-appearance.module.css

69 ms

resize.module.css

resize.module.css

72 ms

sticky-header.module.css

sticky-header.module.css

70 ms

system-status-counter.css

system-status-counter.css

71 ms

system-status-report-counters.css

system-status-report-counters.css

73 ms

system-status-report-general-info.css

system-status-report-general-info.css

67 ms

tabledrag.module.css

tabledrag.module.css

74 ms

tablesort.module.css

tablesort.module.css

76 ms

tree-child.module.css

tree-child.module.css

80 ms

additional-admin.css

additional-admin.css

78 ms

extlink.css

extlink.css

76 ms

color.css

color.css

79 ms

font.css

font.css

82 ms

size.css

size.css

83 ms

space.css

space.css

83 ms

document.css

document.css

83 ms

forms.css

forms.css

84 ms

lists.css

lists.css

85 ms

media.css

media.css

88 ms

tables.css

tables.css

85 ms

text.css

text.css

86 ms

css

css

78 ms

js

js

96 ms

analytics.js

analytics.js

68 ms

js

js

89 ms

snippet.js

snippet.js

85 ms

vue.runtime.min.js

vue.runtime.min.js

94 ms

vuex.min.js

vuex.min.js

275 ms

reset.css

reset.css

86 ms

base.css

base.css

83 ms

utilities.css

utilities.css

78 ms

layouts.css

layouts.css

62 ms

align.css

align.css

62 ms

cluster.css

cluster.css

63 ms

constrained.css

constrained.css

64 ms

grid.css

grid.css

67 ms

stack.css

stack.css

65 ms

main-nav.css

main-nav.css

55 ms

mobile-nav.css

mobile-nav.css

58 ms

footer-nav.css

footer-nav.css

59 ms

footer.css

footer.css

58 ms

site-logo.css

site-logo.css

60 ms

social-nav.css

social-nav.css

61 ms

contact-nav.css

contact-nav.css

42 ms

quicklink-nav.css

quicklink-nav.css

38 ms

pre-footer.css

pre-footer.css

39 ms

testimonial.css

testimonial.css

40 ms

hero.css

hero.css

41 ms

masthead.css

masthead.css

39 ms

notification-message.css

notification-message.css

37 ms

pre-header.css

pre-header.css

37 ms

masthead-mobile.css

masthead-mobile.css

38 ms

search-bar.css

search-bar.css

35 ms

reverse.css

reverse.css

36 ms

jquery.min.js

jquery.min.js

189 ms

once.min.js

once.min.js

187 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

196 ms

drupal.js

drupal.js

196 ms

drupal.init.js

drupal.init.js

197 ms

index.umd.min.js

index.umd.min.js

196 ms

google_analytics.js

google_analytics.js

196 ms

breakpoint.js

breakpoint.js

198 ms

device.js

device.js

196 ms

jquery.form.min.js

jquery.form.min.js

197 ms

progress.js

progress.js

196 ms

loadjs.min.js

loadjs.min.js

196 ms

debounce.js

debounce.js

195 ms

announce.js

announce.js

193 ms

message.js

message.js

193 ms

ajax.js

ajax.js

194 ms

base.js

base.js

193 ms

ajax_view.js

ajax_view.js

191 ms

views-flag-refresh.js

views-flag-refresh.js

192 ms

flag-refresh.js

flag-refresh.js

192 ms

extlink.js

extlink.js

192 ms

main-nav.js

main-nav.js

190 ms

mobile-nav.js

mobile-nav.js

191 ms

build-pager-common.js

build-pager-common.js

198 ms

build-hero.js

build-hero.js

197 ms

logo.svg

logo.svg

173 ms

sss_062418_0049sm.jpg

sss_062418_0049sm.jpg

175 ms

D16A0157.jpg

D16A0157.jpg

175 ms

logo-stacked.svg

logo-stacked.svg

173 ms

font

font

175 ms

collect

collect

77 ms

gtm.js

gtm.js

59 ms

Accessibility Review

summercollege.stanford.edu accessibility score

84

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

Best Practices

summercollege.stanford.edu best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

summercollege.stanford.edu SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

summercollege.stanford.edu

Open Graph description is not detected on the main page of Summer College 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: