Analyze

cayto.jp: カイト株式会社|CAYTO,Inc.

カイトの[おしるこ]はシニア専用コミュニケーションアプリ。[GLANET COLLECTION-グラネットコレクション-]は芸術、植物、ITを融合したブランド。

Page load speed analysis

  • 52/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    568 ms

  • Resources loaded

    7 sec

  • Page rendered

    651 ms

  • Total page load time

    8.2 sec

Welcome to cayto.jp homepage info - get ready to check CAYTO best content for Japan right away, or after learning these important things about cayto.jp

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

Page optimization

  • HTML 21.4 kB
    Images 1.8 MB
    Javascripts 128.7 kB
    CSS 16.7 kB

    In fact, the total size of Cayto.jp main page is 2.0 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

    • Original 21.4 kB
    • After minification 19.2 kB
    • After compression 6.9 kB

    HTML optimization

    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 14.5 kB or 68% of the original size.

    • Original 1.8 MB
    • After optimization 1.7 MB

    Image optimization

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

    • Original 128.7 kB
    • After minification 126.7 kB
    • After compression 56.6 kB

    JavaScript optimization

    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 72.1 kB or 56% of the original size.

    • Original 16.7 kB
    • After minification 10.8 kB
    • After compression 3.0 kB

    CSS optimization

    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. Cayto.jp needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 82% of the original size.

Network requests diagram

  • cayto.jp
  • jquery-1.9.0.min.js
  • common.js
  • heightLine.js
  • common.css
  • top.css
  • ua.js
  • conversion.js
  • sdk.js
  • css
  • pc.css
  • top_tablet_01.jpg
  • logo_header.gif
  • btn_more.gif
  • img_top_02.jpg
  • txt_top_warp.png
  • btn_website.gif
  • deeplink_mac.png
  • txt_top_01.png
  • img_top_03.png
  • img_top_10.png
  • btn_app-store.gif
  • btn_google-play.gif
  • img_top_09.png
  • img_top_05.jpg
  • img_top_06.jpg
  • img_top_07.jpg
  • logo_footer.gif
  • xd_arbiter.php
  • xd_arbiter.php
  • cayto.jp
  • bg_body.gif
  • line_gnav.gif
  • arow_detail.png
  • line_top_01.gif
  • line_footer.gif
  • arow_footer.gif
  • ga.js
  • Roboto-Regular.ttf
  • NotoSansCJKjp-Regular.otf
  • __utm.gif
  • like_box.php
  • 0liJMUxv-Fj.css
  • _er37g1kpMx.css
  • RTH154O-1kj.css
  • KLPUEyHFSii.css
  • YNFoAzraZli.css
  • nwmgh3x3Fjp.css
  • CwYOxdGwg9T.css
  • _rx8naC75Dy.js
  • x5F9OMjKyLw.js
  • ICDbTSzjQEg.js
  • TTCre3391I0.js
  • njO1TPvGzoR.js
  • b_6HNn_J2BZ.js
  • 7cm7D75Y0Sf.js
  • rFmE1g6Dkoz.js
  • 336JejShbZp.js
  • DKRU1bYTkTw.js
  • W0OV23mIOyO.js
  • D6JJJzT-tB6.js
  • djdR_TwcMvh.js
  • 1380550_647116501995685_805477812_n.jpg
  • safe_image.php
  • safe_image.php
  • safe_image.php
  • safe_image.php
  • safe_image.php
  • safe_image.php
  • 7315_594769783897024_1047795459_n.png
  • 10687004_835108813243806_814650546631220267_n.jpg
  • 11600_770551723028161_1855037197327717355_n.jpg
  • 431897_159453737523427_1872542387_n.jpg
  • 12717441_1108538255836655_4343067774698887990_n.jpg
  • 11666256_711224405646147_1529116132030617883_n.jpg
  • 12227072_106052683095447_476011616144777513_n.jpg
  • 12049214_834932239966090_4832431375562428803_n.jpg
  • 11822357_707489299395109_6761144350385741426_n.jpg
  • 398495_358861150799056_1681036797_n.jpg
  • 10926415_1536393196630963_2952233207881126185_n.jpg
  • 12744619_1845762692317483_7601566678917015682_n.jpg
  • 7315_594769783897024_1047795459_n.png
  • wL6VQj7Ab77.png
  • s7jcwEQH7Sx.png
  • QDwYpIaRyfG.png
  • bNvHN6v1NeH.png
  • b53Ajb4ihCP.gif
  • a-ZN6WoEOje.png
  • I6-MnjEovm5.js
  • vlXaquuXMrr.js

Our browser made a total of 92 requests to load all elements on the main page. We found that 37% of them (34 requests) were addressed to the original Cayto.jp, 30% (28 requests) were made to Static.xx.fbcdn.net and 15% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Cayto.jp.

Additional info on cayto.jp

Requests

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

23

Javascripts

51

Images

10

CSS

5

AJAX

89

All

Possible request optimization

1

Javascripts

42

Images

1

CSS

5

AJAX

40

Optimized

49

All

Normal result

IP address

Cayto.jp uses IP addresses which are currently shared with 16 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

cayto.jp

vernongm.com

bibles.org

bereavedparentsusa.org

qool.com

52.85.135.16

cayto.jp

todai.tv

carsalestip.com

stillhouse.com

datomic.com

52.85.135.21

cayto.jp

devisubox.com

tokyo-hitorigurashi.com

alexanderinteractive.com

axn-mk.com

52.85.135.28

cayto.jp

agenda.com

sudannews.net

sportfondsen.nl

hallmarkmoviechannel.com

52.85.135.126

DNS records

Type Host Target/ip TTL Other
A

cayto.jp

13.32.204.118 60
A

cayto.jp

13.32.204.125 60
A

cayto.jp

13.32.204.124 60
A

cayto.jp

13.32.204.103 60
NS

cayto.jp

ns-891.awsdns-47.net 86400

HTTPS certificate

SSL Certificate

Cayto.jp has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 87.4% of all visits is Japan. It lies approximately 4830 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up Cayto.jp page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Good result

Social Sharing Optimization

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

cayto.jp

Language and encoding

Good result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cayto.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Cayto.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.

Share this report in social media

Analyze another website

Analyze