Tools & Wizards About Us
bunsendo.net screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

bunsendo.net

(株)石井文泉堂

Page Load Speed

6.9 sec in total

First Response

522 ms

Resources Loaded

5.8 sec

Page Rendered

612 ms

bunsendo.net screenshot

About Website

Click here to check amazing Bunsendo content for Japan. Otherwise, check out these important facts you probably never knew about bunsendo.net

クリーニング店専門の印刷会社石井文泉堂のホームページに来て頂き、ありがとうございます。当社は洗える紙＋洗ってもインキが落ちない特殊印刷ができる日本でも数少ない特殊印刷メーカーです。

Visit bunsendo.net

Key Findings

We analyzed Bunsendo.net page load time and found that the first response time was 522 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

bunsendo.net performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.348

32/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

bunsendo.net

522 ms

bunsendo.net

820 ms

ishiibunsendo.com

1471 ms

bootstrap.min.css

48 ms

all.css

37 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Bunsendo.net, 74% (34 requests) were made to Ishiibunsendo.com and 9% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Ishiibunsendo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.3 kB (87%)

Content Size

423.6 kB

After Optimization

56.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Bunsendo.net main page is 423.6 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. 35% of websites need less resources to load. CSS take 334.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.3 kB

  • Original 64.0 kB
  • After minification 52.7 kB
  • After compression 11.8 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 11.3 kB, which is 18% 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 52.3 kB or 82% of the original size.

JavaScript Optimization

-78%

Potential reduce by 19.6 kB

  • Original 25.0 kB
  • After minification 17.8 kB
  • After compression 5.4 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 19.6 kB or 78% of the original size.

CSS Optimization

-88%

Potential reduce by 295.4 kB

  • Original 334.5 kB
  • After minification 204.8 kB
  • After compression 39.1 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. Bunsendo.net needs all CSS files to be minified and compressed as it can save up to 295.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (35%)

Requests Now

40

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bunsendo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

bunsendo.net

bunsendo.net

522 ms

bunsendo.net

bunsendo.net

820 ms

ishiibunsendo.com

ishiibunsendo.com

1471 ms

bootstrap.min.css

bootstrap.min.css

48 ms

all.css

all.css

37 ms

slick.css

slick.css

59 ms

style.css

style.css

1666 ms

customize2.css

customize2.css

1040 ms

slick.css

slick.css

540 ms

luminous-basic.min.css

luminous-basic.min.css

531 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

39 ms

js

js

87 ms

customize.css

customize.css

561 ms

bootstrap.min.js

bootstrap.min.js

13 ms

slick.min.js

slick.min.js

16 ms

function.js

function.js

202 ms

eccube.js

eccube.js

339 ms

Luminous.js

Luminous.js

346 ms

customize.js

customize.js

380 ms

search-dark.svg

search-dark.svg

214 ms

j_29.gif

j_29.gif

330 ms

j_30.gif

j_30.gif

361 ms

j_6.gif

j_6.gif

532 ms

j_9.gif

j_9.gif

499 ms

j_16.gif

j_16.gif

572 ms

j_28.gif

j_28.gif

567 ms

j_26.gif

j_26.gif

495 ms

j_17.gif

j_17.gif

715 ms

orange.gif

orange.gif

1639 ms

line-web.gif

line-web.gif

671 ms

l_4.gif

l_4.gif

709 ms

l_5.gif

l_5.gif

948 ms

l_6.gif

l_6.gif

771 ms

k_219_a_1.gif

k_219_a_1.gif

837 ms

k_219_b_1.gif

k_219_b_1.gif

887 ms

p_59_s-1.gif

p_59_s-1.gif

898 ms

p_59_s-2.gif

p_59_s-2.gif

967 ms

r_1.gif

r_1.gif

1006 ms

ad_2.gif

ad_2.gif

1065 ms

fa-solid-900.woff

fa-solid-900.woff

77 ms

fa-regular-400.woff

fa-regular-400.woff

101 ms

fa-brands-400.woff

fa-brands-400.woff

101 ms

j_13.gif

j_13.gif

919 ms

j_3-4.gif

j_3-4.gif

982 ms

j_1.gif

j_1.gif

1009 ms

j_12.gif

j_12.gif

1020 ms

Accessibility Review

bunsendo.net accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

bunsendo.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

bunsendo.net SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Bunsendo.net 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 Bunsendo.net 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

bunsendo.net

Open Graph description is not detected on the main page of Bunsendo. 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: