Access board.co.jp. ボード株式会社

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value61.6 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value38.6 s

0/100

10%

board.co.jp

629 ms

index.css

185 ms

jquery.min.js

29 ms

jquery-ui.min.js

34 ms

jquery.tablefix_1.0.1.js

351 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 93% of them (55 requests) were addressed to the original Board.co.jp, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Board.co.jp.

Content Size

604.5 kB

After Optimization

531.1 kB

In fact, the total size of Board.co.jp main page is 604.5 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. 25% of websites need less resources to load. Images take 473.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.5 kB

Original 13.5 kB
After minification 10.2 kB
After compression 3.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 25% 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 10.5 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

Original 473.0 kB
After minification 473.0 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. Board images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 52.7 kB

Original 104.2 kB
After minification 86.2 kB
After compression 51.6 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 52.7 kB or 51% of the original size.

CSS Optimization

-75%

Potential reduce by 10.3 kB

Original 13.7 kB
After minification 10.3 kB
After compression 3.5 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. Board.co.jp needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 75% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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 Board.co.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 Board.co.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

board.co.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

ボード株式会社

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

board.co.jp

index.css

jquery.min.js

jquery-ui.min.js

jquery.tablefix_1.0.1.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

board.co.jp

index.css

jquery.min.js

jquery-ui.min.js

jquery.tablefix_1.0.1.js

lightbox-2.6.min.js

modernizr.custom.js

common.js

jquery.galleryview-3.0-dev.js

jquery.timers-1.2.js

jquery.easing.1.3.js

urchin.js

base.css

common.css

top.css

mainv.jpg

btn_search.jpg

logo.jpg

tit_news.gif

btn_more.gif

tit_attention_maintenance.jpg

for_maintenance.jpg

tit_rec.gif

for_pro.jpg

for_ama.jpg

tit_catalog.gif

catalog.jpg

btn_catalog.jpg

tit_case.gif

case01.jpg

case02.jpg

case03.jpg

tit_show.jpg

show_room01.jpg

tit_pickup.gif

pickup01.jpg

pickup02_l.jpg

pickup02_r.jpg

btn_pagetop.gif

fmenu01.gif

fmenu02.gif

fmenu03.gif

fmenu04.gif