Tools & Wizards About Us
antioch.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

antioch.jp

The Light of Eternal Agape 東京アンテオケ教会 – The Light of Eternal Agape (永遠の、神の愛の恵みの光) 東京アンテオケ教会は、東京都杉並区高円寺にあるカリスマ系のプロテスタント・キリスト教会です。聖書は、唯一の誤りない神の言葉、信仰の唯一の規...

Page Load Speed

3.9 sec in total

First Response

547 ms

Resources Loaded

3 sec

Page Rendered

415 ms

antioch.jp screenshot

About Website

Click here to check amazing Antioch content for Japan. Otherwise, check out these important facts you probably never knew about antioch.jp

主の十字架クリスチャンセンター東京アンテオケ教会は、杉並区高円寺にあるキリスト教会です。教会では皆様のお越しをお待ちしております。 ...

Visit antioch.jp

Key Findings

We analyzed Antioch.jp page load time and found that the first response time was 547 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

antioch.jp performance score

0

Network Requests Diagram

antioch.jp

547 ms

tokyo.antioch.jp

726 ms

format.css

340 ms

layout_top.css

353 ms

colorbox.css

361 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Antioch.jp, 88% (22 requests) were made to Tokyo.antioch.jp and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Tokyo.antioch.jp.

Page Optimization Overview & Recommendations

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

Content Size

856.4 kB

After Optimization

742.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Antioch.jp main page is 856.4 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. 15% of websites need less resources to load. Images take 687.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 21.6 kB

  • Original 26.1 kB
  • After minification 23.8 kB
  • After compression 4.5 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 21.6 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 9.2 kB

  • Original 687.4 kB
  • After minification 678.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. Antioch images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 75.8 kB

  • Original 133.1 kB
  • After minification 126.6 kB
  • After compression 57.3 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 75.8 kB or 57% of the original size.

CSS Optimization

-78%

Potential reduce by 7.6 kB

  • Original 9.8 kB
  • After minification 7.2 kB
  • After compression 2.2 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. Antioch.jp needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Antioch. 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

antioch.jp

antioch.jp

547 ms

tokyo.antioch.jp

tokyo.antioch.jp

726 ms

format.css

format.css

340 ms

layout_top.css

layout_top.css

353 ms

colorbox.css

colorbox.css

361 ms

top_img02.jpg

top_img02.jpg

1854 ms

tlccclogo.png

tlccclogo.png

388 ms

1302mission.jpg

1302mission.jpg

418 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

843 ms

index.js

index.js

355 ms

jquery.scrollTo.js

jquery.scrollTo.js

367 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

403 ms

1302healing.jpg

1302healing.jpg

533 ms

1302gift.jpg

1302gift.jpg

546 ms

1302sanbi.jpg

1302sanbi.jpg

788 ms

1302israel.jpg

1302israel.jpg

613 ms

1302media.jpg

1302media.jpg

713 ms

1302orphanage.jpg

1302orphanage.jpg

726 ms

1302revival.jpg

1302revival.jpg

810 ms

1302woman.jpg

1302woman.jpg

896 ms

blank.gif

blank.gif

715 ms

ga.js

ga.js

4 ms

__utm.gif

__utm.gif

15 ms

border1.png

border1.png

179 ms

border2.png

border2.png

194 ms

SEO Factors

antioch.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antioch.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Antioch.jp 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

antioch.jp

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