11.6 sec in total
507 ms
10.6 sec
442 ms
Click here to check amazing But content for Japan. Otherwise, check out these important facts you probably never knew about but.jp
ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ!」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。
Visit but.jpWe analyzed But.jp page load time and found that the first response time was 507 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
but.jp performance score
507 ms
1386 ms
340 ms
630 ms
512 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original But.jp, 55% (71 requests) were made to Lolipop.jp and 5% (7 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 477.3 kB (38%)
1.2 MB
762.9 kB
In fact, the total size of But.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.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 143.0 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, But 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 110.5 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 110.5 kB or 44% 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. But.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 64 (56%)
114
50
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of But. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
but.jp
507 ms
lolipop.jp
1386 ms
default.css
340 ms
common.css
630 ms
background.css
512 ms
text_m.css
515 ms
home.css
686 ms
lightbox.css
518 ms
owl.carousel.css
532 ms
jquery.min.js
63 ms
base.js
697 ms
lightbox.min.js
611 ms
owl.carousel.min.js
710 ms
home.js
611 ms
scrollReveal.min.js
652 ms
pixel.js
668 ms
mixpanel.js
706 ms
fbds.js
184 ms
mixpanel-2-latest.min.js
125 ms
bg_night.gif
178 ms
close.png
190 ms
loading.gif
253 ms
prev.png
338 ms
next.png
337 ms
bg_content_side.png
348 ms
bg_main_bottom.gif
347 ms
bg_main_1column.png
365 ms
bg_submenu_top.gif
403 ms
h2_home_title.png
678 ms
megaphone.svg
507 ms
obj_home_plan_economy.svg
519 ms
obj_home_plan_lite.svg
523 ms
obj_home_plan_standard.svg
540 ms
obj_home_plan_ribbon.svg
568 ms
obj_home_plan_enterprise.svg
878 ms
btn_home_plan_function_detail.png
1073 ms
btn_home_plan_price_detail.png
903 ms
bnr_lolipop_nextgen_201601.png
1429 ms
h3_home_title.png
2263 ms
obj_home_feature_wordpress.png
2231 ms
line_dot_11.gif
1982 ms
obj_home_feature_backup.png
2344 ms
obj_home_feature_utilization.png
2418 ms
obj_home_feature_support.png
3230 ms
h3_home_functions.png
2905 ms
obj_home_functions_list.png
3179 ms
btn_feature._function_detail.png
2999 ms
btn_infomation_more.png
3020 ms
badge_light.png
108 ms
line_dot_02.gif
2963 ms
icon_star.gif
3803 ms
widgets.js
135 ms
btn_h_serch.png
3799 ms
line_dot_08.gif
3793 ms
48 ms
dc.js
96 ms
btn_pagetop.gif
3737 ms
obj_lolipop_logo.png
3754 ms
21 ms
obj_ojisan_normal.png
3922 ms
obj_header_banner_text.png
4045 ms
__utm.gif
20 ms
__utm.gif
11 ms
__utm.gif
21 ms
__utm.gif
33 ms
btn_header_order.png
4742 ms
bg_header_simple.png
5022 ms
obj_ppb_by_logo.png
4566 ms
obj_order_count_text.png
4530 ms
obj_numbers.png
4407 ms
menu_btn.png
4754 ms
menu_dot.gif
4565 ms
arrow_menu.gif
4562 ms
obj_logo_ppb.png
4539 ms
pixel
155 ms
Pug
75 ms
sync.ad-stir.com
613 ms
sync
53 ms
sync
945 ms
is
1231 ms
headerstyle.min.css
199 ms
sd
4 ms
pixel
15 ms
172 ms
tag.js
39 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
34 ms
obj_prev_item_icon.png
4065 ms
obj_next_item_icon.png
4067 ms
obj_dhw_ac_jp_thumb.jpg
4259 ms
obj_mtblanc_jp_thumb.jpg
4256 ms
tag
80 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
53 ms
jot
89 ms
obj_foresthuntingone_com_thumb.jpg
4189 ms
obj_sakelife_jp_thumb.jpg
3627 ms
lolipop.jp
1885 ms
lolipop.jp
2719 ms
lolipop.jp
2959 ms
lolipop.jp
2106 ms
lolipop.jp
1053 ms
nr-768.min.js
57 ms
roundtrip.js
36 ms
btn.png
27 ms
conversion_async.js
56 ms
12 ms
logo201601.png
43 ms
open_footer.png
73 ms
close_footer.png
110 ms
15936ac739
118 ms
41 ms
conversion.js
980 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
181 ms
47 ms
out
8 ms
tr
8 ms
48 ms
out
6 ms
out
13 ms
out
42 ms
out
53 ms
u.php
59 ms
sync
36 ms
sd
17 ms
sd
44 ms
28 ms
pixel
26 ms
377928.gif
11 ms
in
5 ms
tap.php
100 ms
in
4 ms
but.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise But.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 But.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.
but.jp
Open Graph data is detected on the main page of But. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: