Tools & Wizards About Us
watchtower.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

watchtower.org

Jehovah’s Witnesses—Official Website: jw.org

Page Load Speed

1.2 sec in total

First Response

76 ms

Resources Loaded

758 ms

Page Rendered

403 ms

watchtower.org screenshot

About Website

Visit watchtower.org now to see the best up-to-date Watchtower content for Japan and also check out these interesting facts you probably never knew about watchtower.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 watchtower.org

Key Findings

We analyzed Watchtower.org page load time and found that the first response time was 76 ms and then it took 1.2 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

watchtower.org performance score

0

Network Requests Diagram

76 ms

i18n.js

11 ms

a7bcd70762-0.css

67 ms

a7bcd70762-1.css

79 ms

a7bcd70762-2.css

93 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Watchtower.org, 7% (3 requests) were made to Jw.org. The less responsive or slowest element that took the longest time to load (192 ms) relates to the external source Assetsnffrgf-a.akamaihd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (48%)

Content Size

2.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watchtower.org main page is 2.6 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 142.6 kB

  • Original 175.6 kB
  • After minification 148.5 kB
  • After compression 33.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. This page needs HTML code to be minified as it can gain 27.1 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 142.6 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 26.8 kB

  • Original 1.0 MB
  • After minification 997.5 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. Watchtower images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 594.9 kB

  • Original 820.8 kB
  • After minification 820.7 kB
  • After compression 225.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 594.9 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 489.5 kB

  • Original 573.2 kB
  • After minification 570.7 kB
  • After compression 83.7 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. Watchtower.org needs all CSS files to be minified and compressed as it can save up to 489.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (16%)

Requests Now

43

After Optimization

36

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watchtower. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

76 ms

i18n.js

i18n.js

11 ms

a7bcd70762-0.css

a7bcd70762-0.css

67 ms

a7bcd70762-1.css

a7bcd70762-1.css

79 ms

a7bcd70762-2.css

a7bcd70762-2.css

93 ms

a7bcd70762-3.css

a7bcd70762-3.css

69 ms

jwplayer.js

jwplayer.js

75 ms

thirdparty.js

thirdparty.js

192 ms

js-core.js

js-core.js

74 ms

cms.js

cms.js

189 ms

jworgSite_print.png

jworgSite_print.png

145 ms

jworgSiteLogo.svg

jworgSiteLogo.svg

146 ms

sprite1x-s1316c6c282.png

sprite1x-s1316c6c282.png

149 ms

sprite-s9e8f3bfa21.png

sprite-s9e8f3bfa21.png

156 ms

list_roundDkGray.png

list_roundDkGray.png

148 ms

slider-s83fdf21aa4.png

slider-s83fdf21aa4.png

149 ms

bg_slideShadow.png

bg_slideShadow.png

150 ms

list_squareDkGray.gif

list_squareDkGray.gif

153 ms

donation.jpg

donation.jpg

150 ms

signLanguage.jpg

signLanguage.jpg

153 ms

jwb-footer-logo--default.png

jwb-footer-logo--default.png

152 ms

insight.png

insight.png

107 ms

502016713_univ_pnr_lg.jpg

502016713_univ_pnr_lg.jpg

68 ms

502016713_univ_cnt_1_sm.jpg

502016713_univ_cnt_1_sm.jpg

12 ms

502016712_univ_pnr_lg.jpg

502016712_univ_pnr_lg.jpg

23 ms

502016712_univ_cnt_1_sm.jpg

502016712_univ_cnt_1_sm.jpg

13 ms

502014172_univ_pnr_lg.jpg

502014172_univ_pnr_lg.jpg

18 ms

502014172_univ_cnt_1_sm.jpg

502014172_univ_cnt_1_sm.jpg

13 ms

502014138_univ_pnr_lg.jpg

502014138_univ_pnr_lg.jpg

27 ms

502014138_univ_cnt_1_sm.jpg

502014138_univ_cnt_1_sm.jpg

14 ms

1001061103_univ_pns_lg.jpg

1001061103_univ_pns_lg.jpg

15 ms

2016162_univ_lss_lg.jpg

2016162_univ_lss_lg.jpg

17 ms

102016000_univ_lss_lg.jpg

102016000_univ_lss_lg.jpg

18 ms

502016140_univ_sqs_sm.jpg

502016140_univ_sqs_sm.jpg

20 ms

1001071934_univ_sqs_sm.jpg

1001071934_univ_sqs_sm.jpg

20 ms

502015143_univ_sqs_sm.jpg

502015143_univ_sqs_sm.jpg

20 ms

502016804_univ_lss_lg.jpg

502016804_univ_lss_lg.jpg

20 ms

102013446_univ_lss_lg.jpg

102013446_univ_lss_lg.jpg

24 ms

502015164_univ_lss_lg.jpg

502015164_univ_lss_lg.jpg

23 ms

502016201_univ_lss_lg.jpg

502016201_univ_lss_lg.jpg

23 ms

502012232_univ_sqs_sm.jpg

502012232_univ_sqs_sm.jpg

23 ms

1011443_univ_sqs_sm.jpg

1011443_univ_sqs_sm.jpg

24 ms

1011229_univ_sqs_sm.jpg

1011229_univ_sqs_sm.jpg

27 ms

1011207_univ_sqs_sm.jpg

1011207_univ_sqs_sm.jpg

27 ms

SEO Factors

watchtower.org SEO score

0

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

watchtower.org

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