8.2 sec in total
568 ms
7 sec
651 ms
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
カイトの[おしるこ]はシニア専用コミュニケーションアプリ。[GLANET COLLECTION-グラネットコレクション-]は芸術、植物、ITを融合したブランド。
Visit cayto.jpWe 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 85% of websites can load faster.
cayto.jp performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value6.8 s
7/100
25%
Value3.9 s
82/100
10%
Value70 ms
99/100
30%
Value0.004
100/100
15%
Value5.2 s
74/100
10%
568 ms
728 ms
292 ms
313 ms
314 ms
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.
Page size can be reduced by 170.7 kB (9%)
2.0 MB
1.8 MB
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.
Potential reduce by 14.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 14.5 kB or 68% of the original size.
Potential reduce by 77.7 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. CAYTO images are well optimized though.
Potential reduce by 64.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 64.9 kB or 47% of the original size.
Potential reduce by 13.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. 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.
Number of requests can be reduced by 40 (45%)
89
49
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.
cayto.jp
568 ms
jquery-1.9.0.min.js
728 ms
common.js
292 ms
heightLine.js
313 ms
common.css
314 ms
top.css
313 ms
ua.js
442 ms
conversion.js
36 ms
sdk.js
33 ms
css
24 ms
pc.css
295 ms
top_tablet_01.jpg
1602 ms
logo_header.gif
294 ms
btn_more.gif
294 ms
img_top_02.jpg
934 ms
txt_top_warp.png
469 ms
btn_website.gif
584 ms
deeplink_mac.png
1166 ms
txt_top_01.png
607 ms
img_top_03.png
1250 ms
img_top_10.png
1018 ms
btn_app-store.gif
919 ms
btn_google-play.gif
1231 ms
img_top_09.png
1803 ms
img_top_05.jpg
1641 ms
img_top_06.jpg
1633 ms
img_top_07.jpg
1667 ms
logo_footer.gif
1562 ms
70 ms
xd_arbiter.php
63 ms
xd_arbiter.php
87 ms
cayto.jp
1723 ms
bg_body.gif
147 ms
line_gnav.gif
293 ms
arow_detail.png
326 ms
line_top_01.gif
324 ms
line_footer.gif
325 ms
arow_footer.gif
326 ms
ga.js
29 ms
Roboto-Regular.ttf
852 ms
NotoSansCJKjp-Regular.otf
3671 ms
__utm.gif
12 ms
like_box.php
222 ms
0liJMUxv-Fj.css
63 ms
_er37g1kpMx.css
57 ms
RTH154O-1kj.css
65 ms
KLPUEyHFSii.css
76 ms
YNFoAzraZli.css
71 ms
nwmgh3x3Fjp.css
64 ms
CwYOxdGwg9T.css
69 ms
_rx8naC75Dy.js
80 ms
x5F9OMjKyLw.js
95 ms
ICDbTSzjQEg.js
92 ms
TTCre3391I0.js
93 ms
njO1TPvGzoR.js
92 ms
b_6HNn_J2BZ.js
93 ms
7cm7D75Y0Sf.js
104 ms
rFmE1g6Dkoz.js
111 ms
336JejShbZp.js
92 ms
DKRU1bYTkTw.js
109 ms
W0OV23mIOyO.js
107 ms
D6JJJzT-tB6.js
107 ms
djdR_TwcMvh.js
106 ms
1380550_647116501995685_805477812_n.jpg
267 ms
safe_image.php
829 ms
48 ms
safe_image.php
62 ms
safe_image.php
79 ms
safe_image.php
63 ms
safe_image.php
2495 ms
safe_image.php
241 ms
7315_594769783897024_1047795459_n.png
118 ms
10687004_835108813243806_814650546631220267_n.jpg
49 ms
11600_770551723028161_1855037197327717355_n.jpg
47 ms
431897_159453737523427_1872542387_n.jpg
66 ms
12717441_1108538255836655_4343067774698887990_n.jpg
48 ms
11666256_711224405646147_1529116132030617883_n.jpg
54 ms
12227072_106052683095447_476011616144777513_n.jpg
78 ms
12049214_834932239966090_4832431375562428803_n.jpg
55 ms
11822357_707489299395109_6761144350385741426_n.jpg
65 ms
398495_358861150799056_1681036797_n.jpg
82 ms
10926415_1536393196630963_2952233207881126185_n.jpg
73 ms
12744619_1845762692317483_7601566678917015682_n.jpg
74 ms
7315_594769783897024_1047795459_n.png
80 ms
wL6VQj7Ab77.png
25 ms
s7jcwEQH7Sx.png
22 ms
QDwYpIaRyfG.png
22 ms
bNvHN6v1NeH.png
43 ms
b53Ajb4ihCP.gif
25 ms
a-ZN6WoEOje.png
24 ms
I6-MnjEovm5.js
9 ms
vlXaquuXMrr.js
15 ms
cayto.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
cayto.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cayto.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
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.
cayto.jp
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: