Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

daiken.jp

DAIKEN株式会社 - 「ずっと ここちいいね」を実現する企業

Page Load Speed

11.8 sec in total

First Response

653 ms

Resources Loaded

5.7 sec

Page Rendered

5.4 sec

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株式会社の公式ホームページです。DAIKENグループは、創業以来、常に社会課題やニーズに応えるため、技術革新を重ね、暮らしに役立つさまざまな製品を開発してきました。住宅から公共・商業建築へ、国内から海外へ、モノからコトへ。あらゆる場所で、あらゆる人に、サステナブルで快適な体験である「ずっと ここちいいね」を提供し、Well-beingな社会のために、よい循環=「Well Cycle」を...

Visit daiken.jp

Key Findings

We analyzed Daiken.jp page load time and found that the first response time was 653 ms and then it took 11.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

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

daiken.jp

653 ms

www.daiken.jp

1320 ms

index_cwv.css

437 ms

global_header.js

615 ms

base.js

616 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 90% of them (69 requests) were addressed to the original Daiken.jp, 4% (3 requests) were made to Cache.dga.jp and 4% (3 requests) were made to Cdn-au.onetrust.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Daiken.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.2 kB (41%)

Content Size

371.3 kB

After Optimization

218.1 kB

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

HTML Optimization

-82%

Potential reduce by 66.9 kB

  • Original 81.6 kB
  • After minification 71.9 kB
  • After compression 14.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 9.7 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 66.9 kB or 82% of the original size.

JavaScript Optimization

-28%

Potential reduce by 73.7 kB

  • Original 262.0 kB
  • After minification 257.5 kB
  • After compression 188.2 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 73.7 kB or 28% of the original size.

CSS Optimization

-45%

Potential reduce by 12.5 kB

  • Original 27.8 kB
  • After minification 27.4 kB
  • After compression 15.3 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 12.5 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (18%)

Requests Now

74

After Optimization

61

The browser has sent 74 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 11 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

93

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.

Tables and lists

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

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

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

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

Links do not have a discernible name

Best Practices

daiken.jp best practices score

83

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

Browser errors were logged to the console

SEO Factors

daiken.jp SEO score

100

Search Engine Optimization Advices

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

Open Graph data is detected on the main page of Daiken. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: