7.3 sec in total
319 ms
6.4 sec
584 ms
Visit b-three.jp now to see the best up-to-date B Three content for Japan and also check out these interesting facts you probably never knew about b-three.jp
ストレッチパンツ専門店B-THREE(ビースリー)の公式通販サイトです。神戸元町生まれのビースリーが開発した「魔法のパンツ」は体型や年齢に関係なく、全ての女性が気持ちよく美しくなれる特別な美脚ストレッチパンツです。
Visit b-three.jpWe analyzed B-three.jp page load time and found that the first response time was 319 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
b-three.jp performance score
319 ms
1404 ms
298 ms
890 ms
899 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 97% of them (119 requests) were addressed to the original B-three.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain B-three.jp.
Page size can be reduced by 846.0 kB (20%)
4.3 MB
3.4 MB
In fact, the total size of B-three.jp main page is 4.3 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. 50% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 31.4 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 31.4 kB or 83% of the original size.
Potential reduce by 101.8 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. B Three images are well optimized though.
Potential reduce by 427.7 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 427.7 kB or 70% of the original size.
Potential reduce by 285.2 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. B-three.jp needs all CSS files to be minified and compressed as it can save up to 285.2 kB or 86% of the original size.
Number of requests can be reduced by 44 (37%)
119
75
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of B Three. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
b-three.jp
319 ms
www.b-three.jp
1404 ms
normalize.css
298 ms
acms-admin.min.css
890 ms
acms.css
899 ms
off-canvas.css
302 ms
reset.css
305 ms
base.css
456 ms
slick.css
446 ms
top.css
451 ms
jquery-1.11.1.min.js
911 ms
acms.js
742 ms
modernizr.js
600 ms
main.js
608 ms
site.js
751 ms
jquery.js
1229 ms
base.js
908 ms
jquery.bxslider.min.js
1049 ms
top.js
1036 ms
analytics.js
40 ms
underscore-min.js
156 ms
config.js
155 ms
logo.png
150 ms
gnav01.png
247 ms
gnav02.png
262 ms
gnav03.png
289 ms
gnav04.png
371 ms
gnav05.png
372 ms
hnav01.png
394 ms
hnav02.png
411 ms
hnav03.png
434 ms
hnav04.png
441 ms
facebook.png
442 ms
search.png
444 ms
5d6e03298df2fdd217119cfcfc291ba2.jpg
836 ms
fa164ea84e1fbfde2a3bcffabb8e9c89.jpg
1307 ms
88f6e3364c4e8752320142b4421f8d28.jpg
1174 ms
5e692f0df3151ecce71033afb99e12cb.jpg
1197 ms
5fcce7af2cea9b805b169eca27938692.jpg
1050 ms
spacer.gif
592 ms
about_title.png
741 ms
about_btn01.png
1037 ms
about_btn02.png
984 ms
about_btn03.png
1135 ms
lineup_title.png
1185 ms
lineup01.png
1203 ms
lineup02.png
1283 ms
lineup03.png
1469 ms
contents_title.png
1337 ms
aa7b1c2414fe8080e76b1a56a0c3948e.jpg
1349 ms
1ef340bca19a02fb57ddb5b71b0d4cd9.jpg
1355 ms
620286cd36df54f56e0d577c9a49e928.jpg
1432 ms
c275ff3f942149c4c91303f0de1555d2.jpg
1454 ms
collect
13 ms
collect
57 ms
4a31a7abc9f76db9b1b50708aefe6610.jpg
1391 ms
349ae37a0b383b799fc82cf8f6d0cac2.jpg
1398 ms
ga-audiences
45 ms
b6016d0f10d898b94b061559b80fc69d.jpg
1375 ms
jquery-ui.min.js
1595 ms
7f710c552d47a94d84a62a4306de8403.jpg
1462 ms
48cff126223ff9823cddde9453708d9c.jpg
1377 ms
4c8c0e47ee1137866185278fef713afd.jpg
1376 ms
3506b7e740bec59dfb063957f23f1122.jpg
1372 ms
8f2105700d7b1c8b17a6bf4fb7d557b1.jpg
1297 ms
btn_list.png
1390 ms
newitem_title.png
1400 ms
78ee470a61130b4cf81c4c7ef40c4b91.jpg
1391 ms
97c7f9fb0d39603a8a0f27229c7e3ffc.jpg
1406 ms
c30968c299a03db5a34432fe31cd228f.jpg
1384 ms
a880aae35a355847c61522a115eb9d21.jpg
1445 ms
c76d6b71be8c0c74d23f816f789841f3.jpg
1469 ms
coordinate_title.png
1476 ms
7d4acad83db98e885348bbebe6bee9f0.jpg
1486 ms
coordinate_bg.png
1225 ms
btn_detail.png
1133 ms
b7778249a77527b7de754e5a8e6de7bc.jpg
1196 ms
34622d3337c4498930a2f6e4e59b3bac.jpg
1173 ms
c869a07bd13dad8b82d3ac394b978bce.jpg
1165 ms
bnav01.png
983 ms
bnav02.png
948 ms
bnav03.png
1041 ms
bnav04.png
1075 ms
news_title.png
1069 ms
news_ico01.png
1055 ms
news_ico02.png
1054 ms
pagetop.png
1024 ms
logo_footer.png
1025 ms
arrow.png
1068 ms
facebook_footer.png
992 ms
bar.png
1023 ms
copyright.png
1039 ms
78ee470a61130b4cf81c4c7ef40c4b91.jpg
1027 ms
97c7f9fb0d39603a8a0f27229c7e3ffc.jpg
1020 ms
c30968c299a03db5a34432fe31cd228f.jpg
1067 ms
a880aae35a355847c61522a115eb9d21.jpg
971 ms
c76d6b71be8c0c74d23f816f789841f3.jpg
1008 ms
arrow_slide03.png
1029 ms
arrow_slide04.png
1004 ms
7d4acad83db98e885348bbebe6bee9f0.jpg
1158 ms
jquery.cookie.js
975 ms
btn_detail.png
974 ms
b7778249a77527b7de754e5a8e6de7bc.jpg
1159 ms
34622d3337c4498930a2f6e4e59b3bac.jpg
1178 ms
c869a07bd13dad8b82d3ac394b978bce.jpg
1153 ms
5d6e03298df2fdd217119cfcfc291ba2.jpg
1219 ms
arrow_slide01.png
1003 ms
arrow_slide02.png
1063 ms
78ee470a61130b4cf81c4c7ef40c4b91.jpg
403 ms
97c7f9fb0d39603a8a0f27229c7e3ffc.jpg
435 ms
c30968c299a03db5a34432fe31cd228f.jpg
467 ms
a880aae35a355847c61522a115eb9d21.jpg
475 ms
c76d6b71be8c0c74d23f816f789841f3.jpg
477 ms
dispatch.js
459 ms
7d4acad83db98e885348bbebe6bee9f0.jpg
373 ms
btn_detail.png
253 ms
b7778249a77527b7de754e5a8e6de7bc.jpg
434 ms
34622d3337c4498930a2f6e4e59b3bac.jpg
442 ms
c869a07bd13dad8b82d3ac394b978bce.jpg
445 ms
5d6e03298df2fdd217119cfcfc291ba2.jpg
452 ms
5fcce7af2cea9b805b169eca27938692.jpg
477 ms
utility.js
306 ms
library.js
150 ms
b-three.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise B-three.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 B-three.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.
b-three.jp
Open Graph data is detected on the main page of B Three. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: