10.2 sec in total
633 ms
9.3 sec
299 ms
Visit fool.jp now to see the best up-to-date Fool content for Japan and also check out these interesting facts you probably never knew about fool.jp
Visit fool.jpWe analyzed Fool.jp page load time and found that the first response time was 633 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fool.jp performance score
633 ms
1140 ms
305 ms
622 ms
482 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fool.jp, 54% (71 requests) were made to Lolipop.jp and 7% (9 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 440.2 kB (36%)
1.2 MB
781.2 kB
In fact, the total size of Fool.jp 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. 40% of websites need less resources to load. Images take 707.6 kB which makes up the majority of the site volume.
Potential reduce by 143.3 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 143.3 kB or 85% of the original size.
Potential reduce by 125.4 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. Obviously, Fool needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 73.0 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 73.0 kB or 32% of the original size.
Potential reduce by 98.4 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. Fool.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.
Number of requests can be reduced by 65 (57%)
115
50
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fool. 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 8 to 1 for CSS and as a result speed up the page load time.
fool.jp
633 ms
lolipop.jp
1140 ms
default.css
305 ms
common.css
622 ms
background.css
482 ms
text_m.css
479 ms
home.css
668 ms
lightbox.css
504 ms
owl.carousel.css
543 ms
jquery.min.js
63 ms
base.js
681 ms
lightbox.min.js
502 ms
owl.carousel.min.js
700 ms
home.js
625 ms
scrollReveal.min.js
676 ms
pixel.js
634 ms
mixpanel.js
676 ms
fbds.js
194 ms
mixpanel-2-latest.min.js
191 ms
bg_night.gif
183 ms
close.png
267 ms
loading.gif
298 ms
prev.png
299 ms
next.png
300 ms
bg_content_side.png
328 ms
bg_main_bottom.gif
343 ms
bg_main_1column.png
411 ms
bg_submenu_top.gif
454 ms
h2_home_title.png
768 ms
megaphone.svg
458 ms
obj_home_plan_economy.svg
496 ms
obj_home_plan_lite.svg
510 ms
obj_home_plan_standard.svg
592 ms
obj_home_plan_ribbon.svg
612 ms
obj_home_plan_enterprise.svg
617 ms
btn_home_plan_function_detail.png
829 ms
btn_home_plan_price_detail.png
678 ms
bnr_lolipop_nextgen_201601.png
1323 ms
h3_home_title.png
1096 ms
obj_home_feature_wordpress.png
1097 ms
line_dot_11.gif
846 ms
obj_home_feature_backup.png
1096 ms
obj_home_feature_utilization.png
1165 ms
obj_home_feature_support.png
1349 ms
h3_home_functions.png
1270 ms
obj_home_functions_list.png
1418 ms
btn_feature._function_detail.png
1269 ms
btn_infomation_more.png
1334 ms
line_dot_02.gif
1426 ms
badge_light.png
173 ms
icon_star.gif
1353 ms
widgets.js
78 ms
btn_h_serch.png
1419 ms
line_dot_08.gif
1375 ms
btn_pagetop.gif
1388 ms
dc.js
75 ms
obj_lolipop_logo.png
1587 ms
obj_ojisan_normal.png
1586 ms
obj_header_banner_text.png
1569 ms
64 ms
18 ms
__utm.gif
23 ms
__utm.gif
11 ms
__utm.gif
22 ms
__utm.gif
34 ms
btn_header_order.png
1580 ms
bg_header_simple.png
1883 ms
obj_ppb_by_logo.png
1553 ms
obj_order_count_text.png
1515 ms
obj_numbers.png
1537 ms
menu_btn.png
1724 ms
menu_dot.gif
1633 ms
arrow_menu.gif
1543 ms
obj_logo_ppb.png
1535 ms
pixel
154 ms
pixel
68 ms
Pug
79 ms
sync.ad-stir.com
617 ms
sync
907 ms
is
1239 ms
headerstyle.min.css
225 ms
sync
6 ms
pixel
17 ms
189 ms
sd
27 ms
tag.js
38 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
5 ms
obj_prev_item_icon.png
946 ms
obj_next_item_icon.png
1086 ms
obj_dhw_ac_jp_thumb.jpg
1288 ms
obj_mtblanc_jp_thumb.jpg
1249 ms
obj_foresthuntingone_com_thumb.jpg
1296 ms
obj_sakelife_jp_thumb.jpg
2262 ms
tag
69 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
17 ms
jot
187 ms
lolipop.jp
2073 ms
lolipop.jp
2302 ms
lolipop.jp
2635 ms
lolipop.jp
2757 ms
lolipop.jp
1064 ms
nr-768.min.js
113 ms
roundtrip.js
79 ms
btn.png
38 ms
conversion_async.js
44 ms
10 ms
logo201601.png
55 ms
open_footer.png
84 ms
close_footer.png
118 ms
42 ms
conversion.js
939 ms
69 ms
15936ac739
152 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
14 ms
out
15 ms
tr
14 ms
out
42 ms
out
52 ms
out
65 ms
out
54 ms
out
65 ms
out
65 ms
35 ms
sync
30 ms
u.php
51 ms
sd
35 ms
sd
49 ms
in
6 ms
377928.gif
10 ms
tap.php
208 ms
in
4 ms
conversion.js
944 ms
fool.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fool.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 Fool.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.
fool.jp
Open Graph data is detected on the main page of Fool. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: