Tools & Wizards About Us
umchistory.org screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

umchistory.org

HSUMC | Historical Society of the United Methodist Church

Page Load Speed

1.4 sec in total

First Response

111 ms

Resources Loaded

1.2 sec

Page Rendered

72 ms

umchistory.org screenshot

About Website

Welcome to umchistory.org homepage info - get ready to check Umchistory best content right away, or after learning these important things about umchistory.org

The purpose of the HSUMC is to promote interest in the study, preservation, and dissemination of the history of the United Methodist Church.

Visit umchistory.org

Key Findings

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

Performance Metrics

umchistory.org performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

79/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.umchistory.org

111 ms

originTrials.41d7301a.bundle.min.js

33 ms

minified.js

41 ms

focus-within-polyfill.js

80 ms

polyfill.min.js

426 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 Umchistory.org, 44% (19 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 (598 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 444.6 kB (51%)

Content Size

876.8 kB

After Optimization

432.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-78%

Potential reduce by 382.5 kB

  • Original 489.9 kB
  • After minification 488.4 kB
  • After compression 107.4 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 382.5 kB or 78% of the original size.

Image Optimization

-36%

Potential reduce by 59.3 kB

  • Original 162.4 kB
  • After minification 103.2 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, Umchistory needs image optimization as it can save up to 59.3 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 224.5 kB
  • After minification 224.5 kB
  • After compression 221.7 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.

Requests Breakdown

Number of requests can be reduced by 11 (46%)

Requests Now

24

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.umchistory.org

www.umchistory.org

111 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

33 ms

minified.js

minified.js

41 ms

focus-within-polyfill.js

focus-within-polyfill.js

80 ms

polyfill.min.js

polyfill.min.js

426 ms

thunderbolt-commons.eb770ee8.bundle.min.js

thunderbolt-commons.eb770ee8.bundle.min.js

18 ms

main.578f27a3.bundle.min.js

main.578f27a3.bundle.min.js

62 ms

lodash.min.js

lodash.min.js

63 ms

react.production.min.js

react.production.min.js

62 ms

react-dom.production.min.js

react-dom.production.min.js

62 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

63 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

64 ms

3e66bb_72cf03b4cc3e4e7aa7865282f585c74f~mv2.png

3e66bb_72cf03b4cc3e4e7aa7865282f585c74f~mv2.png

316 ms

9d31bb_648596163c164a39a1fe77e9f59e3583~mv2.jpg

9d31bb_648596163c164a39a1fe77e9f59e3583~mv2.jpg

529 ms

3e66bb_36d8d272c9504d9a81123a4ea0fc3624~mv2.jpg

3e66bb_36d8d272c9504d9a81123a4ea0fc3624~mv2.jpg

477 ms

9d31bb_54d6d0a7df1646edbd34f8f396d64fa6~mv2.png

9d31bb_54d6d0a7df1646edbd34f8f396d64fa6~mv2.png

516 ms

9d31bb_cc27b119b6b64c5c8ff025d9da295948~mv2.jpg

9d31bb_cc27b119b6b64c5c8ff025d9da295948~mv2.jpg

493 ms

9d31bb_77eb253508f74d10941afe0b856be7c2~mv2.jpg

9d31bb_77eb253508f74d10941afe0b856be7c2~mv2.jpg

533 ms

9d31bb_9991af03827543aca86a0447721c66c8~mv2.jpg

9d31bb_9991af03827543aca86a0447721c66c8~mv2.jpg

470 ms

9d31bb_c6e7610f50ab41678b6a15fab1c745d1~mv2.jpeg

9d31bb_c6e7610f50ab41678b6a15fab1c745d1~mv2.jpeg

598 ms

bundle.min.js

bundle.min.js

62 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

52 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

52 ms

05b176f5-c622-4c35-af98-c0c056dd5b66.woff

05b176f5-c622-4c35-af98-c0c056dd5b66.woff

53 ms

129 ms

125 ms

124 ms

120 ms

113 ms

117 ms

153 ms

146 ms

143 ms

141 ms

138 ms

140 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

19 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

13 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

6 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

3 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

5 ms

Accessibility Review

umchistory.org accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

umchistory.org SEO score

86

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

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

umchistory.org

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