Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

daiken.jp

DAIKEN - 大建工業株式会社 - 「建築資材の総合企業」へ

Page Load Speed

11.3 sec in total

First Response

1.1 sec

Resources Loaded

9.9 sec

Page Rendered

259 ms

daiken.jp screenshot

About Website

Visit daiken.jp now to see the best up-to-date DAIKEN content for Japan and also check out these interesting facts you probably never knew about daiken.jp

大建工業株式会社(DAIKEN)の公式ホームページです。大建工業グループは、創業以来、常に社会課題やニーズに応えるため、技術革新を重ね、暮らしに役立つさまざまな製品を開発してきました。これまでの歴史で積み重ねてきた強みを活かし、「住宅用建材のメーカー」から「建築資材の総合企業」へ、新たな価値を創出する企業への成長を目指します。

Visit daiken.jp

Key Findings

We analyzed Daiken.jp page load time and found that the first response time was 1.1 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

daiken.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,260 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.772

5/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

daiken.jp

1140 ms

12main.css

1355 ms

font_m.css

395 ms

10_basic.js

821 ms

jquery.js

5728 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 95% of them (58 requests) were addressed to the original Daiken.jp, 3% (2 requests) were made to Stats.g.doubleclick.net and 2% (1 request) were made to S.yjtag.jp. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Daiken.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 393.7 kB (35%)

Content Size

1.1 MB

After Optimization

732.4 kB

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

HTML Optimization

-72%

Potential reduce by 14.3 kB

  • Original 19.9 kB
  • After minification 18.9 kB
  • After compression 5.7 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 14.3 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 9.4 kB

  • Original 649.5 kB
  • After minification 640.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. DAIKEN images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 272.2 kB

  • Original 346.7 kB
  • After minification 208.6 kB
  • After compression 74.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 272.2 kB or 79% of the original size.

CSS Optimization

-89%

Potential reduce by 97.8 kB

  • Original 110.0 kB
  • After minification 85.2 kB
  • After compression 12.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. Daiken.jp needs all CSS files to be minified and compressed as it can save up to 97.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (32%)

Requests Now

60

After Optimization

41

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

Accessibility Review

daiken.jp accessibility score

83

Accessibility Issues

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

daiken.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

High

Page has valid source maps

SEO Factors

daiken.jp SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Daiken.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 Daiken.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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