Tools & Wizards About Us
provinginnocence.org screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

provinginnocence.org

Proving Innocence | Assisting the Wrongfully Convicted

Page Load Speed

4 sec in total

First Response

89 ms

Resources Loaded

3.8 sec

Page Rendered

54 ms

provinginnocence.org screenshot

About Website

Visit provinginnocence.org now to see the best up-to-date Proving Innocence content and also check out these interesting facts you probably never knew about provinginnocence.org

Proving Innocence is a Michigan non-profit committed to fighting many aspects of wrongful convictions: investigation, support of the exonerated and education of the public.

Visit provinginnocence.org

Key Findings

We analyzed Provinginnocence.org page load time and found that the first response time was 89 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

provinginnocence.org performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

www.provinginnocence.org

89 ms

minified.js

40 ms

focus-within-polyfill.js

39 ms

polyfill.min.js

31 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

105 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Provinginnocence.org, 43% (16 requests) were made to Static.parastorage.com and 32% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (276 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (67%)

Content Size

1.8 MB

After Optimization

590.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Provinginnocence.org main page is 1.8 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. 30% of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 250.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 1.1 MB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 99.4 kB
  • After minification 99.4 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. Proving Innocence images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 142.5 kB

  • Original 383.5 kB
  • After minification 383.5 kB
  • After compression 240.9 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 142.5 kB or 37% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proving Innocence. 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.provinginnocence.org

www.provinginnocence.org

89 ms

minified.js

minified.js

40 ms

focus-within-polyfill.js

focus-within-polyfill.js

39 ms

polyfill.min.js

polyfill.min.js

31 ms

thunderbolt-commons.60ed9a5a.bundle.min.js

thunderbolt-commons.60ed9a5a.bundle.min.js

105 ms

main.dda15fae.bundle.min.js

main.dda15fae.bundle.min.js

104 ms

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

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

103 ms

lodash.min.js

lodash.min.js

104 ms

react.production.min.js

react.production.min.js

122 ms

react-dom.production.min.js

react-dom.production.min.js

122 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

121 ms

6039b0_bceb6f00f19a49d88e1de163073b65f4~mv2.png

6039b0_bceb6f00f19a49d88e1de163073b65f4~mv2.png

76 ms

bundle.min.js

bundle.min.js

62 ms

3b366c_e95d39e2a7444419b8508555121a319a~mv2.jpg

3b366c_e95d39e2a7444419b8508555121a319a~mv2.jpg

72 ms

3plus1recipients.jpg

3plus1recipients.jpg

205 ms

OE%20Logo.jpg

OE%20Logo.jpg

208 ms

FabFiveCapture%20(1).jpg

FabFiveCapture%20(1).jpg

276 ms

108 ms

106 ms

104 ms

100 ms

102 ms

101 ms

129 ms

128 ms

133 ms

129 ms

129 ms

127 ms

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

aDjpMND83pDErGXlVEr-SRsxEYwM7FgeyaSgU71cLG0.woff

24 ms

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

9VWMTeb5jtXkNoTv949NpRsxEYwM7FgeyaSgU71cLG0.woff

7 ms

h3r77AwDsldr1E_2g4qqGBsxEYwM7FgeyaSgU71cLG0.woff

h3r77AwDsldr1E_2g4qqGBsxEYwM7FgeyaSgU71cLG0.woff

7 ms

p0A1C4_gK5NzKtuGSwNurQ.woff

p0A1C4_gK5NzKtuGSwNurQ.woff

3 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 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

provinginnocence.org accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

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

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

provinginnocence.org SEO score

93

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

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

provinginnocence.org

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