11.1 sec in total
704 ms
9.9 sec
519 ms
Click here to check amazing Floppy content for Japan. Otherwise, check out these important facts you probably never knew about floppy.jp
ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ!」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。
Visit floppy.jpWe analyzed Floppy.jp page load time and found that the first response time was 704 ms and then it took 10.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.
floppy.jp performance score
704 ms
1424 ms
1091 ms
1254 ms
1094 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Floppy.jp, 53% (71 requests) were made to Lolipop.jp and 5% (7 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 455.2 kB (37%)
1.2 MB
778.6 kB
In fact, the total size of Floppy.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 144.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 144.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, Floppy 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 87.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 87.0 kB or 36% 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. Floppy.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 68 (58%)
118
50
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floppy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
floppy.jp
704 ms
lolipop.jp
1424 ms
default.css
1091 ms
common.css
1254 ms
background.css
1094 ms
text_m.css
1102 ms
home.css
1384 ms
lightbox.css
1117 ms
owl.carousel.css
1289 ms
jquery.min.js
71 ms
base.js
1354 ms
lightbox.min.js
1124 ms
owl.carousel.min.js
1357 ms
home.js
1352 ms
scrollReveal.min.js
1355 ms
pixel.js
678 ms
mixpanel.js
1352 ms
fbds.js
271 ms
mixpanel-2-latest.min.js
237 ms
bg_night.gif
224 ms
close.png
224 ms
loading.gif
223 ms
prev.png
248 ms
next.png
282 ms
bg_content_side.png
282 ms
bg_main_bottom.gif
392 ms
bg_main_1column.png
377 ms
bg_submenu_top.gif
379 ms
h2_home_title.png
725 ms
megaphone.svg
466 ms
obj_home_plan_economy.svg
461 ms
obj_home_plan_lite.svg
536 ms
obj_home_plan_standard.svg
539 ms
obj_home_plan_ribbon.svg
571 ms
obj_home_plan_enterprise.svg
643 ms
btn_home_plan_function_detail.png
825 ms
btn_home_plan_price_detail.png
744 ms
bnr_lolipop_nextgen_201601.png
1252 ms
h3_home_title.png
1149 ms
obj_home_feature_wordpress.png
1190 ms
line_dot_11.gif
895 ms
obj_home_feature_backup.png
1249 ms
obj_home_feature_utilization.png
1236 ms
obj_home_feature_support.png
1250 ms
h3_home_functions.png
1321 ms
obj_home_functions_list.png
1554 ms
btn_feature._function_detail.png
1442 ms
btn_infomation_more.png
1420 ms
line_dot_02.gif
1428 ms
badge_light.png
245 ms
icon_star.gif
1312 ms
btn_h_serch.png
1399 ms
widgets.js
286 ms
line_dot_08.gif
1451 ms
btn_pagetop.gif
1455 ms
obj_lolipop_logo.png
1469 ms
obj_ojisan_normal.png
1683 ms
dc.js
113 ms
62 ms
obj_header_banner_text.png
1657 ms
51 ms
btn_header_order.png
1878 ms
__utm.gif
39 ms
__utm.gif
25 ms
__utm.gif
36 ms
__utm.gif
61 ms
bg_header_simple.png
2168 ms
obj_ppb_by_logo.png
1638 ms
obj_order_count_text.png
1639 ms
obj_numbers.png
1607 ms
menu_btn.png
1752 ms
menu_dot.gif
1660 ms
arrow_menu.gif
1653 ms
obj_logo_ppb.png
1669 ms
pixel
296 ms
pixel
102 ms
Pug
103 ms
sync.ad-stir.com
637 ms
sync
87 ms
sync
1155 ms
is
1239 ms
headerstyle.min.css
158 ms
sd
4 ms
pixel
15 ms
157 ms
tag.js
48 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
39 ms
obj_prev_item_icon.png
944 ms
obj_next_item_icon.png
969 ms
obj_dhw_ac_jp_thumb.jpg
1170 ms
obj_mtblanc_jp_thumb.jpg
1152 ms
obj_foresthuntingone_com_thumb.jpg
1189 ms
obj_sakelife_jp_thumb.jpg
1287 ms
tag
37 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
54 ms
jot
92 ms
lolipop.jp
1399 ms
lolipop.jp
2277 ms
lolipop.jp
1967 ms
mapuser
163 ms
lolipop.jp
1641 ms
lolipop.jp
1787 ms
nr-892.min.js
122 ms
__utm.gif
71 ms
roundtrip.js
105 ms
btn.png
61 ms
conversion_async.js
117 ms
41 ms
__utm.gif
50 ms
logo201601.png
62 ms
open_footer.png
97 ms
close_footer.png
157 ms
15936ac739
144 ms
125 ms
conversion.js
904 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
117 ms
49 ms
fbevents.hashing.js
96 ms
out
24 ms
out
82 ms
out
83 ms
out
82 ms
out
80 ms
out
145 ms
111 ms
sd
154 ms
sd
92 ms
u.php
88 ms
sync
70 ms
43 ms
in
34 ms
377928.gif
31 ms
tap.php
49 ms
conversion.js
995 ms
floppy.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floppy.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 Floppy.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.
floppy.jp
Open Graph data is detected on the main page of Floppy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: