8.4 sec in total
529 ms
7.7 sec
180 ms
Visit potofoo.jp now to see the best up-to-date Potofoo content for Japan and also check out these interesting facts you probably never knew about potofoo.jp
ロリポップ!レンタルサーバー 2016年01月27日 新着情報「特典サービス「potofoo」提供終了のご案内」についてのページです。
Visit potofoo.jpWe analyzed Potofoo.jp page load time and found that the first response time was 529 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
potofoo.jp performance score
529 ms
1331 ms
300 ms
616 ms
474 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Potofoo.jp, 34% (46 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 (3 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 362.5 kB (45%)
808.7 kB
446.2 kB
In fact, the total size of Potofoo.jp main page is 808.7 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. 50% of websites need less resources to load. Images take 321.9 kB which makes up the majority of the site volume.
Potential reduce by 149.0 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 149.0 kB or 84% of the original size.
Potential reduce by 66.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, Potofoo needs image optimization as it can save up to 66.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 64.8 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 64.8 kB or 30% of the original size.
Potential reduce by 82.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. Potofoo.jp needs all CSS files to be minified and compressed as it can save up to 82.4 kB or 84% of the original size.
Number of requests can be reduced by 83 (68%)
122
39
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potofoo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
potofoo.jp
529 ms
1331 ms
default.css
300 ms
common.css
616 ms
background.css
474 ms
text_m.css
503 ms
info.css
503 ms
jquery.min.js
30 ms
base.js
621 ms
info.js
391 ms
pixel.js
716 ms
mixpanel.js
536 ms
fbds.js
387 ms
mixpanel-2-latest.min.js
216 ms
button-only.gif
647 ms
bg_night.gif
466 ms
bg_content_side.png
491 ms
bg_main_bottom.gif
480 ms
bg_main.png
478 ms
bg_submenu_top.gif
471 ms
bg_submenu_bottom.png
494 ms
bg_submenu.gif
626 ms
arrow_submenu.gif
639 ms
arrow_pan.gif
646 ms
line_dot_02.gif
807 ms
btn_s_serch.png
821 ms
obj_s_order_01.gif
1491 ms
bnr_s_cam_053.gif
1619 ms
bnr_s_lolipop_news_050.gif
1630 ms
bnr_s_lolipop_news_051.gif
1643 ms
bnr_s_lolipop_news_052.gif
1643 ms
obj_s_account_chk_01.gif
1491 ms
btn_s_check.gif
1672 ms
btn_h_serch.png
1670 ms
badge_light.png
172 ms
widgets.js
103 ms
all.js
539 ms
bookmark_button.js
693 ms
plusone.js
134 ms
obj_to_infotop.gif
1736 ms
line_dot_08.gif
1739 ms
btn_pagetop.gif
1762 ms
title_s_side_03.png
2262 ms
title_s_side_02.png
1979 ms
title_s_side_01.png
1978 ms
obj_lolipop_logo.png
2031 ms
obj_ojisan_normal.png
2038 ms
obj_header_banner_text.png
2079 ms
btn_header_order.png
2600 ms
bg_header_simple.png
2956 ms
obj_ppb_by_logo.png
2417 ms
obj_order_count_text.png
2414 ms
obj_numbers.png
2419 ms
menu_btn.png
2587 ms
menu_dot.gif
2575 ms
dc.js
106 ms
arrow_menu.gif
2504 ms
cb=gapi.loaded_0
43 ms
cb=gapi.loaded_1
58 ms
fastbutton
125 ms
95 ms
postmessageRelay
100 ms
__utm.gif
56 ms
__utm.gif
55 ms
__utm.gif
50 ms
__utm.gif
54 ms
cb=gapi.loaded_0
24 ms
cb=gapi.loaded_1
25 ms
3193398744-postmessagerelay.js
30 ms
rpc:shindig_random.js
37 ms
100 ms
cb=gapi.loaded_0
21 ms
obj_logo_ppb.png
2196 ms
57 ms
xd_arbiter.php
455 ms
909 ms
pixel
154 ms
pixel
88 ms
Pug
91 ms
sync.ad-stir.com
668 ms
sync
1000 ms
is
1181 ms
headerstyle.min.css
217 ms
sync
4 ms
pixel
15 ms
sd
4 ms
160 ms
tag.js
34 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
14 ms
like.php
131 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
22 ms
tag
27 ms
xd_arbiter.php
137 ms
wy1X4hBW7e7.js
495 ms
LVx-xkvaJ0b.png
557 ms
jot
98 ms
reset.css
176 ms
entry-button.css
351 ms
mapuser
151 ms
bbtn-l_v3.png
180 ms
nr-892.min.js
69 ms
__utm.gif
34 ms
roundtrip.js
61 ms
btn.png
32 ms
conversion_async.js
51 ms
25 ms
__utm.gif
14 ms
logo201601.png
63 ms
open_footer.png
93 ms
close_footer.png
120 ms
15936ac739
108 ms
50 ms
conversion.js
896 ms
ICMGDSMXLRFAXHJ6Q7LKCW.js
363 ms
34 ms
fbevents.hashing.js
73 ms
out
14 ms
37 ms
out
29 ms
out
28 ms
out
43 ms
out
44 ms
out
43 ms
out
43 ms
sync
35 ms
u.php
68 ms
28 ms
sd
53 ms
sd
26 ms
pixel
27 ms
22 ms
in
9 ms
377928.gif
12 ms
tap.php
21 ms
conversion.js
1351 ms
in
5 ms
potofoo.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potofoo.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 Potofoo.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.
potofoo.jp
Open Graph data is detected on the main page of Potofoo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: