11.9 sec in total
556 ms
10.8 sec
550 ms
Click here to check amazing Freedrama Nekomoe content for Japan. Otherwise, check out these important facts you probably never knew about freedrama.nekomoe.net
無料で視聴できるドラマ
Visit freedrama.nekomoe.netWe analyzed Freedrama.nekomoe.net page load time and found that the first response time was 556 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
freedrama.nekomoe.net performance score
556 ms
176 ms
348 ms
365 ms
122 ms
Our browser made a total of 227 requests to load all elements on the main page. We found that 16% of them (36 requests) were addressed to the original Freedrama.nekomoe.net, 4% (10 requests) were made to Freemovie.nekomoe.net and 4% (10 requests) were made to X.bidswitch.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source I.yimg.jp.
Page size can be reduced by 549.3 kB (46%)
1.2 MB
635.1 kB
In fact, the total size of Freedrama.nekomoe.net main page is 1.2 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. 55% of websites need less resources to load. Javascripts take 513.4 kB which makes up the majority of the site volume.
Potential reduce by 43.9 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 43.9 kB or 80% of the original size.
Potential reduce by 38.5 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. Freedrama Nekomoe images are well optimized though.
Potential reduce by 296.4 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 296.4 kB or 58% of the original size.
Potential reduce by 170.5 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. Freedrama.nekomoe.net needs all CSS files to be minified and compressed as it can save up to 170.5 kB or 90% of the original size.
Number of requests can be reduced by 143 (71%)
202
59
The browser has sent 202 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freedrama Nekomoe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
freedrama.nekomoe.net
556 ms
style.css
176 ms
wgs.css
348 ms
head.load.min.js
365 ms
loader.js
122 ms
vertical-m.css
384 ms
rakuten_widget.js
1067 ms
base.js
382 ms
style.css%E2%80%99
352 ms
jquery.js
351 ms
jquery-migrate.min.js
196 ms
q2w3-fixed-widget.min.js
195 ms
analytics.js
80 ms
ad_imobile_pc_300x250.html
191 ms
519B9Ut8vVL.jpg
601 ms
31DPQ1TCEZL.jpg
610 ms
51iUdmJmjPL.jpg
612 ms
514lGlTcBDL.jpg
623 ms
20151107180635.jpg
631 ms
20160213084859.jpg
633 ms
51HXJEC2jYL.jpg
775 ms
5193TiCaXFL.jpg
789 ms
51FCwIAEC6L.jpg
792 ms
51iEdg+NfCL.jpg
808 ms
kabe.jpg
183 ms
logo.png
370 ms
20141106194612.jpg
371 ms
511-3Twz+cL.jpg
363 ms
51t3EQXdR9L.jpg
376 ms
51ms-26DEJL.jpg
380 ms
51EIPobC-PL.jpg
503 ms
20150708225323.jpg
550 ms
51JsgaxrR6L.jpg
561 ms
20150804084927.jpg
562 ms
51Cf0vAA46L.jpg
566 ms
51ALtRfFkUL.jpg
570 ms
20141124202715-120x170.jpg
673 ms
20160105220250-120x170.jpg
723 ms
20160105215926-120x170.jpg
756 ms
20160105215208-120x170.jpg
755 ms
20151017221508-120x170.jpg
756 ms
20151116223014-120x170.jpg
761 ms
20151116222459-120x170.jpg
842 ms
20151114231038-120x170.jpg
902 ms
20141125220303-120x170.jpg
955 ms
20141125215736-120x170.jpg
955 ms
collect
12 ms
ads.js
21 ms
adcore.js
11 ms
adcore_pc.js
21 ms
adcore_pc_inline.js
11 ms
ad_spot.aspx
536 ms
ad_spot.aspx
338 ms
mtwidget04.affiliate.rakuten.co.jp
367 ms
ad_admax_pc_300x250.html
412 ms
ssp.js
373 ms
style.css
163 ms
ad_creative.ashx
210 ms
style.css
210 ms
RestoreXidToMediaStorage.html
21 ms
pc_pcview_all.css
16 ms
front_merged.js
33 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
380 ms
65191.y.kau.li
452 ms
getMWConf.php
321 ms
loading.gif
10 ms
buttons.gif
10 ms
c35c8a38c06b732b1a6b0027af6a54e8
509 ms
260715.jpg
426 ms
a.gif
581 ms
f.js
444 ms
ha_sam.jpg
396 ms
kankoku504.jpg
203 ms
1.0.1.js
474 ms
sh.adingo.jp
396 ms
sync
734 ms
sync
448 ms
push_sync
621 ms
sync
66 ms
669f983cc2a2d28a4117add63c34190f
229 ms
i.adingo.jp
383 ms
sync
11 ms
1.0.0.js
165 ms
623 ms
613 ms
sync
175 ms
google_cse_v2.js
183 ms
wp-embed.min.js
213 ms
sync
13 ms
c35c8a38c06b732b1a6b0027af6a54e8
222 ms
sync
420 ms
sync
310 ms
push_sync
297 ms
cse.js
18 ms
cse.js
61 ms
320 ms
jsapi
33 ms
default+ja.css
8 ms
default.css
46 ms
default+ja.I.js
18 ms
default.css
33 ms
async-ads.js
38 ms
google_custom_search_watermark.gif
31 ms
js1
361 ms
small-logo.png
24 ms
search_box_icon.png
25 ms
clear.gif
25 ms
ib
174 ms
462 ms
669f983cc2a2d28a4117add63c34190f
237 ms
1.1.0.js
165 ms
cookiesync
264 ms
sync
256 ms
receive_sync
151 ms
ib
171 ms
js
487 ms
js
493 ms
sync
7 ms
ADTECH;cfp=1;rndc=1458413921;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1458413921358
256 ms
ADTECH;cfp=1;rndc=1458413921;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1458413921364
311 ms
sh.adingo.jp
387 ms
show.php
344 ms
sync
14 ms
pixel
16 ms
generic
9 ms
mapuser
295 ms
generic
5 ms
mapuser
293 ms
pixel
15 ms
mapuser
600 ms
mapuser
303 ms
mapuser
298 ms
mapuser
406 ms
0.gif
158 ms
mapuser
6 ms
sync
188 ms
cm
335 ms
sync
11 ms
sync
13 ms
sg.gif
305 ms
sh.adingo.jp
445 ms
show.php
364 ms
i.adingo.jp
322 ms
sg.gif
303 ms
157 ms
449 ms
437 ms
152 ms
296 ms
sync
8 ms
a1033892.js
372 ms
i.adingo.jp
320 ms
597 ms
jsk
354 ms
jsk
361 ms
sync
14 ms
mapuser
149 ms
js1
339 ms
push_sync
152 ms
pixel
12 ms
sync
9 ms
gl3
165 ms
gl3
176 ms
sync
159 ms
acs
167 ms
js
470 ms
js
545 ms
acs
179 ms
cs
164 ms
301 ms
cs
162 ms
cs
188 ms
acs
167 ms
cs
174 ms
yads.js
542 ms
sync
17 ms
yads_vimps-1.4.1.js
1097 ms
tag
527 ms
tag
547 ms
gcs
328 ms
gcs
324 ms
gcs
349 ms
3bf108464e28f4ae028fe4b80557c04b
20 ms
yads-iframe.html
260 ms
yads-iframe.html
356 ms
usermatch
18 ms
pixel.htm
42 ms
usermatch
24 ms
casale
18 ms
Vu2hZcAoJVAAATKIPvgAAAIG%26621
80 ms
93 ms
pm_match
24 ms
mapuser
219 ms
pixel.htm
78 ms
ddc.htm
65 ms
crum
196 ms
rum
99 ms
rum
75 ms
crum
71 ms
Pug
92 ms
pixel
81 ms
rtset
97 ms
u.php
96 ms
159 ms
mapuser
65 ms
um
188 ms
rum
112 ms
ddc.htm
101 ms
crum
132 ms
merge
97 ms
xrefid.xgi
96 ms
sd
95 ms
bd
98 ms
rum
48 ms
sync
114 ms
bd
34 ms
lr.gif
22 ms
pixel.gif
37 ms
sync
27 ms
tag
383 ms
rum
10 ms
tag
361 ms
NAX7009925463204067277
43 ms
oi
370 ms
oi
389 ms
tap.php
135 ms
sync
161 ms
freedrama.nekomoe.net SEO score
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freedrama.nekomoe.net 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 Freedrama.nekomoe.net 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.
freedrama.nekomoe.net
Open Graph description is not detected on the main page of Freedrama Nekomoe. 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: