Tools & Wizards About Us
jw.org screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

jw.org

Jehovah’s Witnesses—Official Website: jw.org | English

Page Load Speed

36.6 sec in total

First Response

246 ms

Resources Loaded

17 sec

Page Rendered

19.4 sec

jw.org screenshot

About Website

Visit jw.org now to see the best up-to-date Jw content for United States and also check out these interesting facts you probably never knew about jw.org

Jehovah’s Witnesses: Our official website provides online access to the Bible, Bible-based publications, and current news. It describes our beliefs and organization.

Visit jw.org

Key Findings

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

Performance Metrics

jw.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.9 s

0/100

25%

SI (Speed Index)

Value48.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

jw.org

246 ms

468 ms

i18n.js

116 ms

271fe50264-0.css

1615 ms

271fe50264-1.css

2266 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 9% of them (4 requests) were addressed to the original Jw.org, 91% (40 requests) were made to Assetsnffrgf-a.akamaihd.net. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Assetsnffrgf-a.akamaihd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (45%)

Content Size

4.1 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jw.org main page is 4.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 150.6 kB

  • Original 185.9 kB
  • After minification 158.0 kB
  • After compression 35.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. This page needs HTML code to be minified as it can gain 27.9 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 150.6 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 26.1 kB

  • Original 1.8 MB
  • After minification 1.8 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. Jw images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 592.7 kB

  • Original 817.9 kB
  • After minification 817.8 kB
  • After compression 225.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 592.7 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 163.8 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. Jw.org needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jw.org

jw.org

246 ms

468 ms

i18n.js

i18n.js

116 ms

271fe50264-0.css

271fe50264-0.css

1615 ms

271fe50264-1.css

271fe50264-1.css

2266 ms

271fe50264-2.css

271fe50264-2.css

1897 ms

jwplayer.js

jwplayer.js

1842 ms

thirdparty.js

thirdparty.js

5247 ms

js-core.js

js-core.js

3820 ms

cms.js

cms.js

3820 ms

jworgSite_print.png

jworgSite_print.png

1521 ms

jworgSiteLogo.svg

jworgSiteLogo.svg

1532 ms

primary-181c361e80.png

primary-181c361e80.png

1889 ms

lowres-f8ac6149cf.png

lowres-f8ac6149cf.png

1889 ms

list_roundDkGray.png

list_roundDkGray.png

1887 ms

slider-fb3e573a59.png

slider-fb3e573a59.png

1887 ms

bg_slideShadow.png

bg_slideShadow.png

1878 ms

list_squareDkGray.gif

list_squareDkGray.gif

1878 ms

donation.jpg

donation.jpg

1875 ms

signLanguage.jpg

signLanguage.jpg

1860 ms

insight.png

insight.png

695 ms

502018700_univ_pnr_lg.jpg

502018700_univ_pnr_lg.jpg

2962 ms

jworg.jwt

jworg.jwt

1904 ms

502018700_univ_cnt_1_sm.jpg

502018700_univ_cnt_1_sm.jpg

885 ms

502017724_univ_pnr_lg.jpg

502017724_univ_pnr_lg.jpg

885 ms

502017724_univ_cnt_1_sm.jpg

502017724_univ_cnt_1_sm.jpg

884 ms

502017725_univ_pnr_lg.jpg

502017725_univ_pnr_lg.jpg

901 ms

502017725_univ_cnt_1_sm.jpg

502017725_univ_cnt_1_sm.jpg

899 ms

502017723_univ_pnr_lg.jpg

502017723_univ_pnr_lg.jpg

901 ms

502017723_univ_cnt_1_sm.jpg

502017723_univ_cnt_1_sm.jpg

899 ms

1001061103_univ_pns_lg.jpg

1001061103_univ_pns_lg.jpg

899 ms

2017162_univ_lss_lg.jpg

2017162_univ_lss_lg.jpg

870 ms

102017122_univ_lss_lg.jpg

102017122_univ_lss_lg.jpg

951 ms

502017129_univ_sqs_sm.jpg

502017129_univ_sqs_sm.jpg

870 ms

502012503_univ_sqs_sm.jpg

502012503_univ_sqs_sm.jpg

870 ms

502017169_univ_sqs_sm.jpg

502017169_univ_sqs_sm.jpg

950 ms

502014315_univ_lss_lg.jpg

502014315_univ_lss_lg.jpg

902 ms

502013293_univ_lss_lg.jpg

502013293_univ_lss_lg.jpg

1114 ms

502015134_univ_lss_lg.jpg

502015134_univ_lss_lg.jpg

902 ms

502017168_univ_lss_lg.jpg

502017168_univ_lss_lg.jpg

1113 ms

502012232_univ_sqs_lg.jpg

502012232_univ_sqs_lg.jpg

1114 ms

1011214_univ_sqs_sm.jpg

1011214_univ_sqs_sm.jpg

1280 ms

1011229_univ_sqs_sm.jpg

1011229_univ_sqs_sm.jpg

1280 ms

1011207_univ_sqs_lg.jpg

1011207_univ_sqs_lg.jpg

1281 ms

Accessibility Review

jw.org accessibility score

96

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

jw.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

jw.org SEO score

78

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

High

Document doesn't have a valid hreflang

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

jw.org

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