Tools & Wizards About Us
washtenawhistory.org screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

washtenawhistory.org

Washtenaw County Michigan | Washtenawhistory.org | United States

Page Load Speed

2.2 sec in total

First Response

155 ms

Resources Loaded

2 sec

Page Rendered

55 ms

washtenawhistory.org screenshot

About Website

Click here to check amazing Washtenawhistory content. Otherwise, check out these important facts you probably never knew about washtenawhistory.org

Washtenaw County Historical Society. washtenawhistory.org. Dedicated to preserving and sharing our local history.

Visit washtenawhistory.org

Key Findings

We analyzed Washtenawhistory.org page load time and found that the first response time was 155 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

washtenawhistory.org performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

www.washtenawhistory.org

155 ms

minified.js

30 ms

focus-within-polyfill.js

29 ms

polyfill.min.js

1106 ms

thunderbolt-commons.09398ec1.bundle.min.js

47 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Washtenawhistory.org, 37% (16 requests) were made to Static.parastorage.com and 28% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 921.7 kB (66%)

Content Size

1.4 MB

After Optimization

468.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Washtenawhistory.org main page is 1.4 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. 25% of websites need less resources to load. HTML takes 866.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 693.1 kB

  • Original 866.3 kB
  • After minification 864.7 kB
  • After compression 173.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. 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 693.1 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 1.8 kB

  • Original 38.1 kB
  • After minification 36.3 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. Washtenawhistory images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 226.8 kB

  • Original 485.8 kB
  • After minification 485.8 kB
  • After compression 259.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 226.8 kB or 47% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washtenawhistory. 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 JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.washtenawhistory.org

www.washtenawhistory.org

155 ms

minified.js

minified.js

30 ms

focus-within-polyfill.js

focus-within-polyfill.js

29 ms

polyfill.min.js

polyfill.min.js

1106 ms

thunderbolt-commons.09398ec1.bundle.min.js

thunderbolt-commons.09398ec1.bundle.min.js

47 ms

main.e5a43201.bundle.min.js

main.e5a43201.bundle.min.js

47 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

43 ms

lodash.min.js

lodash.min.js

47 ms

react.production.min.js

react.production.min.js

46 ms

react-dom.production.min.js

react-dom.production.min.js

48 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

48 ms

708faa_e0c4dc7c194245f6b48a4171335064fa~mv2.jpg

708faa_e0c4dc7c194245f6b48a4171335064fa~mv2.jpg

235 ms

708faa_84e654257be5484b84c45b7f2790e8d4~mv2.jpg

708faa_84e654257be5484b84c45b7f2790e8d4~mv2.jpg

428 ms

708faa_b32355e392544560a647d25226d80c4f~mv2.jpg

708faa_b32355e392544560a647d25226d80c4f~mv2.jpg

409 ms

2024%20banner.jpg

2024%20banner.jpg

376 ms

qt%3Dq%2095.webp

qt%3Dq%2095.webp

402 ms

divider-line-png.png

divider-line-png.png

439 ms

divider-line-png.png

divider-line-png.png

463 ms

708faa_af50e172fb214d708ce1e81ee1fe417d~mv2.jpg

708faa_af50e172fb214d708ce1e81ee1fe417d~mv2.jpg

550 ms

Smart%20Tours.webp

Smart%20Tours.webp

606 ms

Untitled.jpg

Untitled.jpg

593 ms

divider-line-png.png

divider-line-png.png

527 ms

bundle.min.js

bundle.min.js

46 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

33 ms

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

33 ms

AvenirLTW05-85Heavy.woff

AvenirLTW05-85Heavy.woff

33 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

33 ms

100 ms

96 ms

92 ms

89 ms

91 ms

89 ms

134 ms

132 ms

128 ms

127 ms

132 ms

126 ms

deprecation-en.v5.html

deprecation-en.v5.html

4 ms

bolt-performance

bolt-performance

23 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

washtenawhistory.org accessibility score

98

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.

Best Practices

washtenawhistory.org best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

washtenawhistory.org SEO score

98

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 Washtenawhistory.org 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 Washtenawhistory.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

washtenawhistory.org

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