Tools & Wizards About Us
timothytwo.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

timothytwo.org

Timothy Two Project International | Training Pastors

Page Load Speed

3.6 sec in total

First Response

1.2 sec

Resources Loaded

2.3 sec

Page Rendered

69 ms

timothytwo.org screenshot

About Website

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

Timothy Two Project International is a global missions agency committed to teaching indigenous pastors who cannot access formal theological training - and then training them to train others.

Visit timothytwo.org

Key Findings

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

Performance Metrics

timothytwo.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

www.timothytwo.org

1213 ms

minified.js

41 ms

focus-within-polyfill.js

39 ms

polyfill.min.js

440 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

47 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Timothytwo.org, 33% (13 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Timothytwo.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 944.8 kB (67%)

Content Size

1.4 MB

After Optimization

467.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Timothytwo.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. 15% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 882.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 191.3 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 882.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 40.6 kB
  • After minification 40.6 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. Timothy Two images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 62.5 kB

  • Original 297.7 kB
  • After minification 297.6 kB
  • After compression 235.2 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 62.5 kB or 21% 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 Timothy Two. 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.timothytwo.org

www.timothytwo.org

1213 ms

minified.js

minified.js

41 ms

focus-within-polyfill.js

focus-within-polyfill.js

39 ms

polyfill.min.js

polyfill.min.js

440 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

thunderbolt-commons.1e70fbb2.bundle.min.js

47 ms

main.42e492e1.bundle.min.js

main.42e492e1.bundle.min.js

48 ms

lodash.min.js

lodash.min.js

49 ms

react.production.min.js

react.production.min.js

48 ms

react-dom.production.min.js

react-dom.production.min.js

50 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

48 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

50 ms

99ec98fdb81945c29c25a3ad6c5606b1.jpg

99ec98fdb81945c29c25a3ad6c5606b1.jpg

170 ms

logo-bw-ko.png

logo-bw-ko.png

341 ms

ECFA_Accredited_CMYK_ET2_Med.jpg

ECFA_Accredited_CMYK_ET2_Med.jpg

466 ms

666d6e_a34626fb619e4f6bafd2be60269c20c0~mv2.jpg

666d6e_a34626fb619e4f6bafd2be60269c20c0~mv2.jpg

347 ms

11062b_2042bb7351284f0f982e4787d37415e6f000.jpg

11062b_2042bb7351284f0f982e4787d37415e6f000.jpg

261 ms

Optimized-Curtis-29_edited.jpg

Optimized-Curtis-29_edited.jpg

327 ms

1455021871_edited.png

1455021871_edited.png

356 ms

666d6e_dff41397789b4fd2997c276bffc8b883~mv2.jpg

666d6e_dff41397789b4fd2997c276bffc8b883~mv2.jpg

503 ms

bc97b991bed9d26c481b52c93e1e1ff0.jpg

bc97b991bed9d26c481b52c93e1e1ff0.jpg

444 ms

abd451ddb9fd4c11b4c562721ffa2513.jpg

abd451ddb9fd4c11b4c562721ffa2513.jpg

547 ms

67f06d27898a4a7b984f1d5e801e732b.jpg

67f06d27898a4a7b984f1d5e801e732b.jpg

349 ms

bundle.min.js

bundle.min.js

117 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

6 ms

92 ms

109 ms

109 ms

109 ms

106 ms

103 ms

129 ms

147 ms

144 ms

145 ms

145 ms

144 ms

deprecation-en.v5.html

deprecation-en.v5.html

8 ms

bolt-performance

bolt-performance

21 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

timothytwo.org SEO score

92

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

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

timothytwo.org

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