Tools & Wizards About Us
buso.ac.jp screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

buso.ac.jp

武相中学・高等学校

Page Load Speed

4.8 sec in total

First Response

806 ms

Resources Loaded

3.9 sec

Page Rendered

157 ms

buso.ac.jp screenshot

About Website

Click here to check amazing Buso content for Japan. Otherwise, check out these important facts you probably never knew about buso.ac.jp

武相中学・高等学校

Visit buso.ac.jp

Key Findings

We analyzed Buso.ac.jp page load time and found that the first response time was 806 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

buso.ac.jp performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

buso.ac.jp

806 ms

style.css

439 ms

jquery.min.js

8 ms

jquery.bxslider.min.js

593 ms

script.js

444 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 84% of them (54 requests) were addressed to the original Buso.ac.jp, 6% (4 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Buso.ac.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.3 kB (6%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buso.ac.jp main page is 2.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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.2 kB

  • Original 28.4 kB
  • After minification 26.9 kB
  • After compression 6.2 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 22.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 23.6 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Buso images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 18.2 kB

  • Original 78.6 kB
  • After minification 77.9 kB
  • After compression 60.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 18.2 kB or 23% of the original size.

CSS Optimization

-83%

Potential reduce by 46.3 kB

  • Original 55.6 kB
  • After minification 35.5 kB
  • After compression 9.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. Buso.ac.jp needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (38%)

Requests Now

63

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buso. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

buso.ac.jp

buso.ac.jp

806 ms

style.css

style.css

439 ms

jquery.min.js

jquery.min.js

8 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

593 ms

script.js

script.js

444 ms

buso.js

buso.js

416 ms

pagenavi-css.css

pagenavi-css.css

429 ms

widgets.js

widgets.js

92 ms

base.css

base.css

281 ms

contents.css

contents.css

436 ms

category.css

category.css

267 ms

footer.css

footer.css

281 ms

header.css

header.css

270 ms

layout.css

layout.css

336 ms

nav.css

nav.css

533 ms

table.css

table.css

542 ms

tag.css

tag.css

531 ms

top.css

top.css

519 ms

jquery.bxslider.css

jquery.bxslider.css

547 ms

logo.jpg

logo.jpg

306 ms

anavin_1a.gif

anavin_1a.gif

298 ms

anavin_2a.gif

anavin_2a.gif

301 ms

anavin_3a.gif

anavin_3a.gif

302 ms

anavin_4a.gif

anavin_4a.gif

294 ms

anavin_5a.gif

anavin_5a.gif

307 ms

gnavi_1b.gif

gnavi_1b.gif

582 ms

gnavi_2a.gif

gnavi_2a.gif

600 ms

gnavi_3a.gif

gnavi_3a.gif

593 ms

gnavi_4a.gif

gnavi_4a.gif

599 ms

gnavi_5a.gif

gnavi_5a.gif

601 ms

80th.png

80th.png

1579 ms

top_2.png

top_2.png

1672 ms

top_360.png

top_360.png

1650 ms

TopBanner_preexam.png

TopBanner_preexam.png

864 ms

TopBanner_ex.png

TopBanner_ex.png

1194 ms

TopApp_advice.png

TopApp_advice.png

1023 ms

TopBanner03.png

TopBanner03.png

1210 ms

TopBanner04.png

TopBanner04.png

1215 ms

TopBanner_open_elementary.png

TopBanner_open_elementary.png

1597 ms

x_buso.png

x_buso.png

1433 ms

instagram_buso.png

instagram_buso.png

1434 ms

youtube_buso.png

youtube_buso.png

1644 ms

grayline.gif

grayline.gif

1647 ms

purpleline.gif

purpleline.gif

1782 ms

SideBanner_staffrecruitment.png

SideBanner_staffrecruitment.png

1807 ms

SideBanner04.png

SideBanner04.png

1911 ms

SideBanner05.png

SideBanner05.png

1898 ms

SideBanner06.png

SideBanner06.png

1899 ms

SideBanner07.png

SideBanner07.png

1916 ms

SideBanner_uniform.png

SideBanner_uniform.png

1996 ms

pagetop.gif

pagetop.gif

2024 ms

footerlogo.gif

footerlogo.gif

2184 ms

footerback.gif

footerback.gif

2138 ms

clearfix.gif

clearfix.gif

2132 ms

analytics.js

analytics.js

24 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

bx_loader.gif

bx_loader.gif

2105 ms

collect

collect

37 ms

settings

settings

71 ms

js

js

64 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

66 ms

embeds

embeds

22 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

39 ms

controls.png

controls.png

1916 ms

Accessibility Review

buso.ac.jp accessibility score

80

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Best Practices

buso.ac.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

buso.ac.jp SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Buso.ac.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 Buso.ac.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.

Social Sharing Optimization

buso.ac.jp

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