Tools & Wizards About Us
bun-en.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

bun-en.com

分煙の取り組み | JTウェブサイト

Page Load Speed

8.5 sec in total

First Response

525 ms

Resources Loaded

7.6 sec

Page Rendered

324 ms

bun-en.com screenshot

About Website

Visit bun-en.com now to see the best up-to-date Bun En content and also check out these interesting facts you probably never knew about bun-en.com

JTでは、これまで培ったノウハウを生かし、かつ法令や条例を遵守しながら、たばこを吸われる方・吸われない方の双方を考慮した空間造り、そして双方が共存できる社会の実現に取り組んでいます。

Visit bun-en.com

Key Findings

We analyzed Bun-en.com page load time and found that the first response time was 525 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

bun-en.com performance score

0

Network Requests Diagram

bun-en.com

525 ms

top.css

487 ms

jt.js

814 ms

analytics.js

31 ms

header00.png

312 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 98% of them (79 requests) were addressed to the original Bun-en.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Bun-en.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.2 kB (7%)

Content Size

1.0 MB

After Optimization

954.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bun-en.com main page is 1.0 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. 25% of websites need less resources to load. Images take 935.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 8.2 kB

  • Original 10.8 kB
  • After minification 9.5 kB
  • After compression 2.6 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. This page needs HTML code to be minified as it can gain 1.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 8.2 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 14.6 kB

  • Original 935.5 kB
  • After minification 920.9 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. Bun En images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 41.1 kB

  • Original 70.0 kB
  • After minification 55.0 kB
  • After compression 28.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 41.1 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 12.4 kB

  • Original 14.8 kB
  • After minification 11.7 kB
  • After compression 2.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. Bun-en.com needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

80

After Optimization

80

  • Images
  • JavaScript
  • CSS

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bun En. According to our analytics all requests are already optimized.

Network Requests Diagram

bun-en.com

bun-en.com

525 ms

top.css

top.css

487 ms

jt.js

jt.js

814 ms

analytics.js

analytics.js

31 ms

header00.png

header00.png

312 ms

header01_off.gif

header01_off.gif

322 ms

header02_off.gif

header02_off.gif

326 ms

header03_off.gif

header03_off.gif

342 ms

navi_wrp.png

navi_wrp.png

345 ms

dot_active.png

dot_active.png

345 ms

dot_off.png

dot_off.png

645 ms

kv01.gif

kv01.gif

1004 ms

kv02.jpg

kv02.jpg

1644 ms

kv03.gif

kv03.gif

1257 ms

kv04.gif

kv04.gif

1146 ms

gnavi01_off.gif

gnavi01_off.gif

686 ms

gnavi02_off.gif

gnavi02_off.gif

991 ms

gnavi03_off.gif

gnavi03_off.gif

1029 ms

gnavi04_off.gif

gnavi04_off.gif

1315 ms

gnavi05_off.gif

gnavi05_off.gif

1325 ms

gnavi06.gif

gnavi06.gif

1360 ms

top01_off.jpg

top01_off.jpg

1962 ms

top02_off.jpg

top02_off.jpg

2102 ms

top03_off.jpg

top03_off.jpg

2168 ms

top04_off.jpg

top04_off.jpg

2358 ms

top05_off.jpg

top05_off.jpg

2399 ms

top06_off.jpg

top06_off.jpg

2522 ms

top07_off.jpg

top07_off.jpg

2830 ms

top08_off.jpg

top08_off.jpg

3063 ms

all_sort_btn_off.gif

all_sort_btn_off.gif

2487 ms

banner_off.gif

banner_off.gif

2697 ms

pagetop_off.gif

pagetop_off.gif

2720 ms

footer01.gif

footer01.gif

2815 ms

footer15_off.gif

footer15_off.gif

2860 ms

footer16_off.gif

footer16_off.gif

3024 ms

footer02.gif

footer02.gif

3062 ms

footer03_off.gif

footer03_off.gif

3138 ms

footer04_off.gif

footer04_off.gif

3149 ms

footer05.gif

footer05.gif

3206 ms

footer06_off.gif

footer06_off.gif

3356 ms

collect

collect

14 ms

footer07.gif

footer07.gif

3085 ms

footer08_off.gif

footer08_off.gif

3076 ms

footer09_off.gif

footer09_off.gif

3154 ms

footer10_off.gif

footer10_off.gif

3129 ms

footer11.gif

footer11.gif

3215 ms

footer12_off.gif

footer12_off.gif

3378 ms

footer13.gif

footer13.gif

3079 ms

footer14_off.gif

footer14_off.gif

3050 ms

footer17.gif

footer17.gif

2819 ms

footer18.gif

footer18.gif

2840 ms

header01_on.gif

header01_on.gif

163 ms

header02_on.gif

header02_on.gif

328 ms

header03_on.gif

header03_on.gif

341 ms

dot_on.png

dot_on.png

349 ms

gnavi01_on.gif

gnavi01_on.gif

349 ms

gnavi02_on.gif

gnavi02_on.gif

366 ms

gnavi03_on.gif

gnavi03_on.gif

489 ms

gnavi04_on.gif

gnavi04_on.gif

667 ms

gnavi05_on.gif

gnavi05_on.gif

662 ms

top01_on.jpg

top01_on.jpg

1187 ms

top02_on.jpg

top02_on.jpg

1191 ms

top03_on.jpg

top03_on.jpg

1274 ms

top04_on.jpg

top04_on.jpg

1482 ms

top05_on.jpg

top05_on.jpg

1427 ms

top06_on.jpg

top06_on.jpg

1393 ms

top07_on.jpg

top07_on.jpg

2003 ms

top08_on.jpg

top08_on.jpg

2042 ms

all_sort_btn_on.gif

all_sort_btn_on.gif

1595 ms

banner_on.gif

banner_on.gif

1717 ms

pagetop_on.gif

pagetop_on.gif

1772 ms

footer15_on.gif

footer15_on.gif

1827 ms

footer16_on.gif

footer16_on.gif

1958 ms

footer03_on.gif

footer03_on.gif

2042 ms

footer04_on.gif

footer04_on.gif

2092 ms

footer06_on.gif

footer06_on.gif

2151 ms

footer08_on.gif

footer08_on.gif

2279 ms

footer09_on.gif

footer09_on.gif

2331 ms

footer10_on.gif

footer10_on.gif

2342 ms

footer12_on.gif

footer12_on.gif

2368 ms

footer14_on.gif

footer14_on.gif

2419 ms

SEO Factors

bun-en.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bun-en.com 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 Bun-en.com 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.

Social Sharing Optimization

bun-en.com

Open Graph description is not detected on the main page of Bun En. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: