Tools & Wizards About Us
jesushouse.org screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jesushouse.org

Jesus House Chicago | Family Church | Belong | Grow | Become

Page Load Speed

5.3 sec in total

First Response

650 ms

Resources Loaded

3.8 sec

Page Rendered

853 ms

jesushouse.org screenshot

About Website

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

Jesus House Chicago is a church dedicated to walking along side & preparing a people to become all that God has called them to be.

Visit jesushouse.org

Key Findings

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

Performance Metrics

jesushouse.org performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

jesushouse.org

650 ms

js

92 ms

js

101 ms

select2.min.css

121 ms

iconfonts.css

188 ms

Our browser made a total of 136 requests to load all elements on the main page. We found that 74% of them (100 requests) were addressed to the original Jesushouse.org, 15% (21 requests) were made to Fonts.gstatic.com and 7% (10 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Jesushouse.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 352.1 kB (13%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jesushouse.org main page is 2.7 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. Only a small number of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 158.6 kB

  • Original 191.9 kB
  • After minification 186.4 kB
  • After compression 33.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 158.6 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 127.4 kB

  • Original 1.7 MB
  • After minification 1.5 MB

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. Jesus House images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 42.6 kB

  • Original 563.9 kB
  • After minification 563.9 kB
  • After compression 521.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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 23.4 kB

  • Original 281.0 kB
  • After minification 280.8 kB
  • After compression 257.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. Jesushouse.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 90 (82%)

Requests Now

110

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jesushouse.org

jesushouse.org

650 ms

js

js

92 ms

js

js

101 ms

select2.min.css

select2.min.css

121 ms

iconfonts.css

iconfonts.css

188 ms

frontend.min.css

frontend.min.css

317 ms

tooltip.css

tooltip.css

191 ms

tooltipster-sideTip-shadow.min.css

tooltipster-sideTip-shadow.min.css

191 ms

featherlight.css

featherlight.css

193 ms

css

css

35 ms

lity.min.css

lity.min.css

192 ms

mec-general-calendar.css

mec-general-calendar.css

252 ms

css

css

35 ms

rs6.css

rs6.css

254 ms

style.css

style.css

339 ms

style.css

style.css

256 ms

grid.css

grid.css

256 ms

icons.css

icons.css

335 ms

js_composer.min.css

js_composer.min.css

388 ms

animations.css

animations.css

333 ms

grid_responsive.css

grid_responsive.css

335 ms

css

css

35 ms

font-awesome.css

font-awesome.css

377 ms

frontend.css

frontend.css

451 ms

responsive.css

responsive.css

403 ms

jquery.bxslider.css

jquery.bxslider.css

382 ms

prettyPhoto.css

prettyPhoto.css

381 ms

scroll-style.css

scroll-style.css

442 ms

Defaults.css

Defaults.css

446 ms

style.min.css

style.min.css

444 ms

ytprefs.min.css

ytprefs.min.css

448 ms

jquery.min.js

jquery.min.js

461 ms

jquery-migrate.min.js

jquery-migrate.min.js

505 ms

mec-general-calendar.js

mec-general-calendar.js

578 ms

frontend.js

frontend.js

530 ms

events.js

events.js

462 ms

frontend-gtag.min.js

frontend-gtag.min.js

466 ms

rbtools.min.js

rbtools.min.js

475 ms

rs6.min.js

rs6.min.js

590 ms

common.js

common.js

527 ms

libs.min.js

libs.min.js

601 ms

css

css

17 ms

formreset.min.css

formreset.min.css

574 ms

formsmain.min.css

formsmain.min.css

530 ms

readyclass.min.css

readyclass.min.css

461 ms

browsers.min.css

browsers.min.css

461 ms

background-style.css

background-style.css

531 ms

animate.min.css

animate.min.css

531 ms

animate.min.css

animate.min.css

531 ms

jquery.bxSlider.js

jquery.bxSlider.js

471 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

469 ms

jquery.scroller.js

jquery.scroller.js

470 ms

jquery.actual.js

jquery.actual.js

470 ms

frontend.js

frontend.js

442 ms

ultimate-params.min.js

ultimate-params.min.js

443 ms

ytprefs.min.js

ytprefs.min.js

442 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

426 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

524 ms

wp-polyfill.min.js

wp-polyfill.min.js

497 ms

dom-ready.min.js

dom-ready.min.js

500 ms

hooks.min.js

hooks.min.js

499 ms

i18n.min.js

i18n.min.js

478 ms

a11y.min.js

a11y.min.js

478 ms

jquery.json.min.js

jquery.json.min.js

440 ms

gravityforms.min.js

gravityforms.min.js

438 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

730 ms

core.min.js

core.min.js

727 ms

css

css

18 ms

css

css

19 ms

css

css

18 ms

css

css

27 ms

css

css

27 ms

css

css

28 ms

datepicker.min.js

datepicker.min.js

717 ms

jquery.typewatch.js

jquery.typewatch.js

716 ms

featherlight.js

featherlight.js

669 ms

select2.full.min.js

select2.full.min.js

667 ms

tooltip.js

tooltip.js

779 ms

lity.min.js

lity.min.js

773 ms

colorbrightness.min.js

colorbrightness.min.js

722 ms

owl.carousel.min.js

owl.carousel.min.js

718 ms

fitvids.min.js

fitvids.min.js

676 ms

js_composer_front.min.js

js_composer_front.min.js

667 ms

ultimate_bg.js

ultimate_bg.js

696 ms

jparallax.js

jparallax.js

697 ms

jquery.vhparallax.js

jquery.vhparallax.js

693 ms

jquery-appear.min.js

jquery-appear.min.js

697 ms

custom.min.js

custom.min.js

625 ms

vc-waypoints.min.js

vc-waypoints.min.js

626 ms

utils.min.js

utils.min.js

689 ms

vendor-theme.min.js

vendor-theme.min.js

692 ms

scripts-theme.min.js

scripts-theme.min.js

684 ms

tic-dcc.js

tic-dcc.js

399 ms

jesus_house_logo_color@2x.png

jesus_house_logo_color@2x.png

615 ms

jesus_house_logo_white@2x.png

jesus_house_logo_white@2x.png

612 ms

down_arrow@2x.png

down_arrow@2x.png

613 ms

grow_img1.jpg

grow_img1.jpg

1005 ms

icon_plus.png

icon_plus.png

686 ms

grow_img2.jpg

grow_img2.jpg

1007 ms

questions_icon@2x.png

questions_icon@2x.png

605 ms

Early-Risers-circle-sq-low-res-300x300.png

Early-Risers-circle-sq-low-res-300x300.png

604 ms

MwQ5bhbm2POE2V9BOA.ttf

MwQ5bhbm2POE2V9BOA.ttf

336 ms

TK3gWksYAxQ7jbsKcg8Ene8.ttf

TK3gWksYAxQ7jbsKcg8Ene8.ttf

336 ms

7cHqv4kjgoGqM7E3t-4s51op.ttf

7cHqv4kjgoGqM7E3t-4s51op.ttf

362 ms

7cHqv4kjgoGqM7E3q-0s51op.ttf

7cHqv4kjgoGqM7E3q-0s51op.ttf

364 ms

7cHqv4kjgoGqM7E3j-ws51op.ttf

7cHqv4kjgoGqM7E3j-ws51op.ttf

365 ms

7cHqv4kjgoGqM7E30-8s51op.ttf

7cHqv4kjgoGqM7E30-8s51op.ttf

365 ms

7cHqv4kjgoGqM7E3_-gs51op.ttf

7cHqv4kjgoGqM7E3_-gs51op.ttf

365 ms

7cHpv4kjgoGqM7E_DMs8.ttf

7cHpv4kjgoGqM7E_DMs8.ttf

365 ms

7cHqv4kjgoGqM7E3p-ks51op.ttf

7cHqv4kjgoGqM7E3p-ks51op.ttf

365 ms

7cHqv4kjgoGqM7E3w-os51op.ttf

7cHqv4kjgoGqM7E3w-os51op.ttf

412 ms

7cHrv4kjgoGqM7E3b_s7wHo.ttf

7cHrv4kjgoGqM7E3b_s7wHo.ttf

409 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

410 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

410 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

410 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

410 ms

icomoon.svg

icomoon.svg

918 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

413 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

411 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

412 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

412 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

410 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

412 ms

icomoon.woff

icomoon.woff

919 ms

jhc_logo_white_vertical@2x-300x289.png

jhc_logo_white_vertical@2x-300x289.png

734 ms

embed

embed

545 ms

Life_Groups_Home_Rev1.jpg

Life_Groups_Home_Rev1.jpg

796 ms

Life_At_JHC_Home.jpg

Life_At_JHC_Home.jpg

795 ms

acc_bgr.png

acc_bgr.png

797 ms

Simple-Line-Icons.woff

Simple-Line-Icons.woff

798 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

623 ms

showhidetoggledown.png

showhidetoggledown.png

623 ms

js

js

141 ms

pattern_bg.jpg

pattern_bg.jpg

217 ms

pattern_bg_left.jpg

pattern_bg_left.jpg

174 ms

have_questions_bg.jpg

have_questions_bg.jpg

175 ms

Accessibility Review

jesushouse.org accessibility score

81

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

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jesushouse.org best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

jesushouse.org SEO score

77

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

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

jesushouse.org

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