Tools & Wizards About Us
stanford-il.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

stanford-il.org

Stanford, IL - Official Website - Home

Page Load Speed

2.3 sec in total

First Response

172 ms

Resources Loaded

1.8 sec

Page Rendered

275 ms

stanford-il.org screenshot

About Website

Visit stanford-il.org now to see the best up-to-date Stanford IL content and also check out these interesting facts you probably never knew about stanford-il.org

Village of Stanford, Illinois in McLean County

Visit stanford-il.org

Key Findings

We analyzed Stanford-il.org page load time and found that the first response time was 172 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

stanford-il.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value3,520 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.19

64/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

stanford-il.org

172 ms

www.stanford-il.org

192 ms

www.stanford-il.org

377 ms

sites.css

24 ms

fancybox.css

22 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 12% of them (10 requests) were addressed to the original Stanford-il.org, 25% (21 requests) were made to Cdn2.editmysite.com and 19% (16 requests) were made to Herowelcomebar.appspot.com. The less responsive or slowest element that took the longest time to load (536 ms) relates to the external source Weebly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.8 kB (15%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stanford-il.org main page is 1.5 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 58.3 kB

  • Original 72.3 kB
  • After minification 70.9 kB
  • After compression 14.0 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 58.3 kB or 81% of the original size.

Image Optimization

-26%

Potential reduce by 59.7 kB

  • Original 229.6 kB
  • After minification 169.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. Obviously, Stanford IL needs image optimization as it can save up to 59.7 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 105.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.0 MB

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

-12%

Potential reduce by 9.3 kB

  • Original 78.9 kB
  • After minification 78.0 kB
  • After compression 69.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. Stanford-il.org needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (62%)

Requests Now

69

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stanford IL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stanford-il.org

stanford-il.org

172 ms

www.stanford-il.org

www.stanford-il.org

192 ms

www.stanford-il.org

www.stanford-il.org

377 ms

sites.css

sites.css

24 ms

fancybox.css

fancybox.css

22 ms

social-icons.css

social-icons.css

33 ms

main_style.css

main_style.css

97 ms

font.css

font.css

23 ms

font.css

font.css

23 ms

font.css

font.css

33 ms

templateArtifacts.js

templateArtifacts.js

171 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

31 ms

stl.js

stl.js

31 ms

main.js

main.js

32 ms

voslogolandscape.png

voslogolandscape.png

329 ms

pdf.png

pdf.png

536 ms

plugins.js

plugins.js

344 ms

custom.js

custom.js

420 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

31 ms

rtf.png

rtf.png

534 ms

weebly-widget.html

weebly-widget.html

120 ms

weebly-widget.html

weebly-widget.html

142 ms

1326946639.jpg

1326946639.jpg

514 ms

bold.woff

bold.woff

33 ms

regular.woff

regular.woff

9 ms

bold.woff

bold.woff

10 ms

regular.woff

regular.woff

9 ms

light.woff

light.woff

9 ms

regular.woff

regular.woff

5 ms

bold.woff

bold.woff

30 ms

italic.woff

italic.woff

30 ms

bolditalic.woff

bolditalic.woff

30 ms

wsocial.woff

wsocial.woff

8 ms

css

css

39 ms

ui-lib.min.css

ui-lib.min.css

21 ms

jquery.min.js

jquery.min.js

31 ms

jquery-ui.min.js

jquery-ui.min.js

38 ms

angular.js

angular.js

268 ms

jquery.jrumble.1.3.js

jquery.jrumble.1.3.js

20 ms

inffuse.js

inffuse.js

29 ms

weebly-widget.js

weebly-widget.js

73 ms

notify.js

notify.js

24 ms

jquery.fontselector.js

jquery.fontselector.js

24 ms

fontselector.css

fontselector.css

24 ms

widget.css

widget.css

72 ms

animate.css

animate.css

27 ms

jquery.fittext.js

jquery.fittext.js

72 ms

jquery.lettering.js

jquery.lettering.js

26 ms

jquery.textillate.js

jquery.textillate.js

28 ms

jquery.marquee.min.js

jquery.marquee.min.js

72 ms

generateMap.php

generateMap.php

433 ms

ga.js

ga.js

59 ms

snowday262.js

snowday262.js

41 ms

api.js

api.js

98 ms

225 ms

widgets.js

widgets.js

168 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

90 ms

7477793.js

7477793.js

84 ms

white_logo2.png

white_logo2.png

36 ms

close.png

close.png

13 ms

sdk.js

sdk.js

34 ms

data

data

288 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff

74 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff

95 ms

data

data

297 ms

recaptcha__en.js

recaptcha__en.js

96 ms

sdk.js

sdk.js

19 ms

92 ms

159 ms

157 ms

169 ms

146 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

69 ms

settings

settings

92 ms

settings

settings

112 ms

n73m7muf

n73m7muf

79 ms

tp2

tp2

150 ms

js

js

79 ms

frame.883650f7.js

frame.883650f7.js

48 ms

vendor.6fdbc794.js

vendor.6fdbc794.js

75 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

25 ms

embeds

embeds

50 ms

embeds

embeds

35 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

47 ms

Accessibility Review

stanford-il.org accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

stanford-il.org best practices score

75

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

Browser errors were logged to the console

SEO Factors

stanford-il.org SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanford-il.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Stanford-il.org 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

stanford-il.org

Open Graph data is detected on the main page of Stanford IL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: