8.2 sec in total
1.4 sec
6.4 sec
376 ms
Welcome to fanky.jp homepage info - get ready to check Fanky best content for Japan right away, or after learning these important things about fanky.jp
ランキングサイト「コレダ!」がお届けする総合におけるGlobal Siteの人気ランキングサイトです。
Visit fanky.jpWe analyzed Fanky.jp page load time and found that the first response time was 1.4 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fanky.jp performance score
1353 ms
325 ms
678 ms
516 ms
1275 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fanky.jp, 11% (17 requests) were made to Apis.google.com and 6% (10 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Coreda.jp.
Page size can be reduced by 609.5 kB (64%)
947.5 kB
338.0 kB
In fact, the total size of Fanky.jp main page is 947.5 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. 70% of websites need less resources to load. Javascripts take 793.7 kB which makes up the majority of the site volume.
Potential reduce by 33.6 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 33.6 kB or 77% of the original size.
Potential reduce by 2.0 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. Fanky images are well optimized though.
Potential reduce by 528.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 528.9 kB or 67% of the original size.
Potential reduce by 44.9 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. Fanky.jp needs all CSS files to be minified and compressed as it can save up to 44.9 kB or 82% of the original size.
Number of requests can be reduced by 64 (43%)
148
84
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
1353 ms
import.css
325 ms
style.css
678 ms
roll.js
516 ms
jquery-1.5.2.min.js
1275 ms
jquery.ui.min.js
1858 ms
jquery.pagetop.js
670 ms
hoverIntent.js
706 ms
show_ads.js
40 ms
show_ads.js
32 ms
reset.css
422 ms
default.css
513 ms
gnavi.css
514 ms
ranking.js
365 ms
harippaban.js
21 ms
nexRt.js
34 ms
search
1708 ms
search
917 ms
plusone.js
206 ms
dc.js
73 ms
gpt.js
50 ms
bgt
1010 ms
bgt
1009 ms
bgt
1006 ms
bgt
1007 ms
bgt
427 ms
bgt
1761 ms
poweredby_FFFFFF.gif
237 ms
bg01.gif
426 ms
logo.gif
223 ms
Shutterstock.jpg
218 ms
rakutentit.gif
404 ms
rakutencard.gif
220 ms
pagetop_off.gif
214 ms
bgt
1350 ms
bgt
1001 ms
analytics.js
44 ms
header_bg.gif
397 ms
zrt_lookup.html
165 ms
show_ads_impl.js
60 ms
pubads_impl_83.js
47 ms
collect
24 ms
__utm.gif
113 ms
ads
267 ms
titicon.png
259 ms
container.html
55 ms
osd.js
34 ms
show_ads_impl.js
128 ms
cb=gapi.loaded_0
43 ms
ads
179 ms
toprankfoot.gif
239 ms
rank01.gif
235 ms
rank02.gif
235 ms
rank03.gif
219 ms
dot.gif
236 ms
rank04.gif
277 ms
rank05.gif
373 ms
ads
251 ms
rank06.gif
372 ms
rank07.gif
389 ms
rank08.gif
388 ms
rank09.gif
393 ms
15898034852552438104
81 ms
abg.js
91 ms
m_js_controller.js
141 ms
googlelogo_color_112x36dp.png
78 ms
ads
364 ms
ads
246 ms
branding.css
169 ms
s
93 ms
x_button_blue2.png
39 ms
favicon
170 ms
nessie_icon_tiamat_white.png
49 ms
branding.css
83 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
28 ms
10425832347283815008
37 ms
adj
154 ms
beacon
127 ms
ads
433 ms
ads
269 ms
favicon
45 ms
mobile_unified_button_icon_white.png
38 ms
ranking.cgi
306 ms
ajs.php
61 ms
lg.php
133 ms
harippaban.css
20 ms
MKC_RedPepper_300x250.jpg
170 ms
lidar.js
114 ms
sbhK2lTE.js
25 ms
1121004.jpg
426 ms
bg02.gif
1330 ms
footer_total.gif
208 ms
footer_arrow.gif
207 ms
footer_beauty.gif
205 ms
footer_entertainment.gif
207 ms
footer_tearching-learning.gif
204 ms
footer_finance.gif
387 ms
footer_shopping.gif
387 ms
footer_health.gif
388 ms
footer_gourmet.gif
441 ms
footer_business.gif
416 ms
footer_fashion.gif
551 ms
footer_life.gif
552 ms
footer_car-bike.gif
559 ms
footer_internet.gif
579 ms
footer_marriage.gif
613 ms
cb=gapi.loaded_1
122 ms
fastbutton
402 ms
fastbutton
160 ms
fastbutton
168 ms
fastbutton
165 ms
fastbutton
171 ms
fastbutton
151 ms
fastbutton
245 ms
fastbutton
261 ms
fastbutton
266 ms
rt
713 ms
cTrvNaRi.html
46 ms
adj
62 ms
rakuten.css
383 ms
er_2980_kago01m.jpg
183 ms
mj0003.jpg
180 ms
mochimugi1a.jpg
192 ms
rkt_logo48.gif
361 ms
beacon
52 ms
postmessageRelay
145 ms
rs=AGLTcCP3oxc7cWS41pXoMx-UY1nqx3xkGg
31 ms
0.gif
400 ms
cb=gapi.loaded_0
82 ms
cb=gapi.loaded_1
78 ms
expansion_embed.js
97 ms
1077434459-postmessagerelay.js
153 ms
rpc:shindig_random.js
127 ms
4191
397 ms
push
54 ms
cb=gapi.loaded_0
7 ms
pixel
15 ms
surly.js
166 ms
ba.html
59 ms
pixel
27 ms
4.gif
70 ms
pixel
35 ms
pixel
37 ms
4311.js
45 ms
8f85c9519a62fbc155a3bc4c0847ad46_2.html
180 ms
sd
7 ms
box_19_top-right.png
32 ms
pixel
24 ms
ci.png
102 ms
activeview
19 ms
pixel
13 ms
Pix-1x1.gif
25 ms
st.v2.js
214 ms
activeview
31 ms
768b38ede1976b664b56676d89567e72.jpg
82 ms
gr
38 ms
pixel_details.html
44 ms
fanky.jp SEO score
N/A
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanky.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Fanky.jp main page’s claimed encoding is shift_jis. 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.
fanky.jp
Open Graph data is detected on the main page of Fanky. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: