6 sec in total
934 ms
4.3 sec
687 ms
Click here to check amazing Funto Ki content for Japan. Otherwise, check out these important facts you probably never knew about funto-ki.com
Visit funto-ki.comWe analyzed Funto-ki.com page load time and found that the first response time was 934 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
funto-ki.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value1.9 s
98/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.9 s
100/100
10%
934 ms
307 ms
516 ms
324 ms
389 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Funto-ki.com, 10% (14 requests) were made to Youtube.com and 10% (14 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Livedoor.blogimg.jp.
Page size can be reduced by 650.7 kB (65%)
995.0 kB
344.4 kB
In fact, the total size of Funto-ki.com main page is 995.0 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. 80% 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. Javascripts take 382.7 kB which makes up the majority of the site volume.
Potential reduce by 135.2 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 135.2 kB or 83% of the original size.
Potential reduce by 3.9 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. Funto Ki images are well optimized though.
Potential reduce by 243.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 243.9 kB or 64% of the original size.
Potential reduce by 267.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. Funto-ki.com needs all CSS files to be minified and compressed as it can save up to 267.7 kB or 83% of the original size.
Number of requests can be reduced by 72 (55%)
131
59
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funto Ki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
funto-ki.com
934 ms
template.css
307 ms
site.css
516 ms
c2.js
324 ms
smartphone.js
389 ms
ad.js
370 ms
bookmark_button.js
307 ms
share.js
311 ms
widgets.js
81 ms
plusone.js
63 ms
livedoor_profile_clap.js
513 ms
platform.js
39 ms
swfobject1_5.js
500 ms
blogparts-embed.js
627 ms
ldblog_calendar_plugin.js
154 ms
rank.php
1196 ms
kranking.php
521 ms
js1.php
1199 ms
ga.js
13 ms
button-only.gif
152 ms
0dffd8c5.jpg
1373 ms
91_17_1.gif
504 ms
0dffd8c5.jpg
512 ms
www88_31.gif
558 ms
musicalinstruments88_31.gif
1056 ms
banner_23.gif
453 ms
d_03.gif
225 ms
b-44438.gif
454 ms
b_b_g.gif
556 ms
kranking.gif
451 ms
766931dd-s.jpg
1054 ms
a8c6eace.jpg
521 ms
6933116f.jpg
567 ms
a0ac6463.jpg
563 ms
0ade57ab.jpg
569 ms
f62d4122.jpg
565 ms
f29a8d4c.jpg
808 ms
rranking.gif
1023 ms
br_c_1136_1.gif
449 ms
c
505 ms
header.gif
155 ms
__utm.gif
24 ms
title_line.gif
177 ms
icon_categry.gif
204 ms
icon_tag.gif
278 ms
share_button.html
335 ms
420 ms
cb=gapi.loaded_0
10 ms
cb=gapi.loaded_1
30 ms
fastbutton
126 ms
postmessageRelay
72 ms
like.php
231 ms
3193398744-postmessagerelay.js
57 ms
rpc:shindig_random.js
47 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
41 ms
share_button.html
341 ms
fastbutton
85 ms
cb=gapi.loaded_0
6 ms
share_button.html
326 ms
fastbutton
63 ms
3c_side_middle.gif
196 ms
3c_side_btm.gif
203 ms
3c_side_top.gif
195 ms
3c_ttl_btm.gif
195 ms
3c_ttl_top.gif
465 ms
arrow.gif
402 ms
like.php
149 ms
cb=gapi.loaded_2
11 ms
subscribe_embed
206 ms
like.php
205 ms
subscribe_embed
221 ms
qeKvIRsJabD.js
137 ms
LVx-xkvaJ0b.png
137 ms
bt_check_6.png
113 ms
subscribe_embed
169 ms
count
204 ms
subscribe_embed
143 ms
b-44438-x-098.gif
579 ms
count
558 ms
reset.css
77 ms
entry-button.css
75 ms
459 ms
464 ms
2016-03.json
522 ms
popular_articles.json
519 ms
mUqTNy4e7bw
66 ms
count
484 ms
button-counter.gif
35 ms
www-subscribe-embed-vflTum1sJ.css
70 ms
photo.jpg
223 ms
www-subscribe-embed.js
102 ms
5fy0F86kJ80
73 ms
W3ksHAX897k
145 ms
FpvaZIMAhjs
141 ms
photo.jpg
199 ms
photo.jpg
230 ms
photo.jpg
233 ms
www-embed-player-vflfNyN_r.css
145 ms
www-embed-player.js
185 ms
base.js
229 ms
clapping.gif
413 ms
www-hitchhiker-vflvB63an.png
101 ms
cb=gapi.loaded_0
145 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
130 ms
ad_status.js
112 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
51 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
51 ms
f.php
1057 ms
js2.php
360 ms
cb=gapi.loaded_3
79 ms
border_3.gif
65 ms
subscribe_embed
67 ms
subscribe_embed
71 ms
subscribe_embed
63 ms
subscribe_embed
59 ms
spacer.gif
14 ms
www-subscribe-embed-card-vflqARhQ4.css
10 ms
www-subscribe-embed-card.js
12 ms
border_3.gif
24 ms
bubbleSprite_3.png
26 ms
bubbleDropR_3.png
24 ms
bubbleDropB_3.png
25 ms
sdk.js
59 ms
u.js
549 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
127 ms
subscribe_embed
111 ms
47 ms
xd_arbiter.php
17 ms
xd_arbiter.php
69 ms
photo.jpg
34 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
52 ms
subscribe_embed
53 ms
jot.html
27 ms
135x45.gif
1086 ms
funto-ki.com accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
funto-ki.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
funto-ki.com 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
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funto-ki.com 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 Funto-ki.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
funto-ki.com
Open Graph description is not detected on the main page of Funto Ki. 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: