11.5 sec in total
533 ms
10.7 sec
316 ms
Visit bitter.jp now to see the best up-to-date Bitter content for Japan and also check out these interesting facts you probably never knew about bitter.jp
ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ!」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。
Visit bitter.jpWe analyzed Bitter.jp page load time and found that the first response time was 533 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
bitter.jp performance score
533 ms
1521 ms
349 ms
634 ms
515 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Bitter.jp, 53% (71 requests) were made to Lolipop.jp and 7% (10 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 440.2 kB (36%)
1.2 MB
778.3 kB
In fact, the total size of Bitter.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. 35% 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, Bitter 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. Bitter.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 Bitter. 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.
bitter.jp
533 ms
lolipop.jp
1521 ms
default.css
349 ms
common.css
634 ms
background.css
515 ms
text_m.css
529 ms
home.css
530 ms
lightbox.css
542 ms
owl.carousel.css
560 ms
jquery.min.js
66 ms
base.js
682 ms
lightbox.min.js
600 ms
owl.carousel.min.js
599 ms
home.js
599 ms
scrollReveal.min.js
617 ms
pixel.js
731 ms
mixpanel.js
618 ms
fbds.js
157 ms
mixpanel-2-latest.min.js
176 ms
bg_night.gif
267 ms
close.png
264 ms
loading.gif
269 ms
prev.png
329 ms
next.png
327 ms
bg_content_side.png
372 ms
bg_main_bottom.gif
440 ms
bg_main_1column.png
447 ms
bg_submenu_top.gif
451 ms
h2_home_title.png
623 ms
megaphone.svg
513 ms
obj_home_plan_economy.svg
540 ms
obj_home_plan_lite.svg
618 ms
obj_home_plan_standard.svg
626 ms
obj_home_plan_ribbon.svg
632 ms
obj_home_plan_enterprise.svg
701 ms
btn_home_plan_function_detail.png
874 ms
btn_home_plan_price_detail.png
794 ms
bnr_lolipop_nextgen_201601.png
1691 ms
h3_home_title.png
1940 ms
obj_home_feature_wordpress.png
1775 ms
line_dot_11.gif
1415 ms
obj_home_feature_backup.png
1771 ms
obj_home_feature_utilization.png
1586 ms
obj_home_feature_support.png
2603 ms
h3_home_functions.png
2232 ms
obj_home_functions_list.png
2383 ms
btn_feature._function_detail.png
2242 ms
btn_infomation_more.png
2253 ms
badge_light.png
186 ms
widgets.js
156 ms
line_dot_02.gif
2181 ms
icon_star.gif
3117 ms
btn_h_serch.png
3124 ms
line_dot_08.gif
3134 ms
btn_pagetop.gif
3111 ms
obj_lolipop_logo.png
3089 ms
125 ms
37 ms
dc.js
73 ms
obj_ojisan_normal.png
3210 ms
obj_header_banner_text.png
3307 ms
__utm.gif
21 ms
__utm.gif
12 ms
__utm.gif
21 ms
__utm.gif
34 ms
btn_header_order.png
3433 ms
bg_header_simple.png
3833 ms
obj_ppb_by_logo.png
3273 ms
obj_order_count_text.png
3290 ms
obj_numbers.png
3228 ms
menu_btn.png
3591 ms
menu_dot.gif
3284 ms
arrow_menu.gif
3300 ms
obj_logo_ppb.png
3286 ms
pixel
154 ms
pixel
62 ms
Pug
68 ms
sync.ad-stir.com
642 ms
sync
67 ms
sync
795 ms
is
828 ms
headerstyle.min.css
226 ms
pixel
17 ms
sd
9 ms
199 ms
tag.js
38 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
31 ms
obj_prev_item_icon.png
2702 ms
obj_next_item_icon.png
2797 ms
obj_dhw_ac_jp_thumb.jpg
2958 ms
obj_mtblanc_jp_thumb.jpg
2983 ms
tag
46 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
44 ms
obj_foresthuntingone_com_thumb.jpg
2956 ms
jot
87 ms
obj_sakelife_jp_thumb.jpg
2867 ms
lolipop.jp
1459 ms
lolipop.jp
2280 ms
lolipop.jp
1692 ms
lolipop.jp
1976 ms
lolipop.jp
1776 ms
nr-768.min.js
56 ms
roundtrip.js
153 ms
btn.png
30 ms
conversion_async.js
34 ms
38 ms
logo201601.png
56 ms
open_footer.png
83 ms
close_footer.png
110 ms
41 ms
conversion.js
908 ms
15936ac739
130 ms
35 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
453 ms
out
10 ms
tr
29 ms
24 ms
out
6 ms
out
8 ms
out
11 ms
out
17 ms
out
20 ms
out
19 ms
out
21 ms
u.php
74 ms
sync
11 ms
sd
111 ms
18 ms
sd
13 ms
pixel
29 ms
377928.gif
11 ms
in
8 ms
tap.php
177 ms
conversion.js
1013 ms
in
6 ms
bitter.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bitter.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 Bitter.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.
bitter.jp
Open Graph data is detected on the main page of Bitter. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: