Tools & Wizards About Us
daiken.ne.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    53% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

daiken.ne.jp

株式会社ダイケン|庇・自転車置場・物置など建築金物総合メーカー

Page Load Speed

14.1 sec in total

First Response

1.3 sec

Resources Loaded

12.6 sec

Page Rendered

279 ms

daiken.ne.jp screenshot

About Website

Welcome to daiken.ne.jp homepage info - get ready to check Daiken best content for Japan right away, or after learning these important things about daiken.ne.jp

株式会社ダイケンは1924年（大正13年）創業。庇（ひさし）、自転車置場、宅配ボックス、物置、ゴミ収集庫、点検口、ポスト、ハンガーレール、雪庇軽減装置など外装・内装建材や建築金物、エクステリア製品の製造販売を行う建築金物総合メーカー。

Visit daiken.ne.jp

Key Findings

We analyzed Daiken.ne.jp page load time and found that the first response time was 1.3 sec and then it took 12.8 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.ne.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.341

33/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

daiken.ne.jp

1295 ms

reset.css

341 ms

common.css

558 ms

jquery.min.js

2026 ms

stickysidebar.jquery.js

371 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 74% of them (45 requests) were addressed to the original Daiken.ne.jp, 7% (4 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (8.7 sec) belongs to the original domain Daiken.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 702.4 kB (48%)

Content Size

1.5 MB

After Optimization

757.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 20.6 kB

  • Original 26.0 kB
  • After minification 21.8 kB
  • After compression 5.4 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 4.2 kB, which is 16% 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 20.6 kB or 79% of the original size.

Image Optimization

-25%

Potential reduce by 187.7 kB

  • Original 742.3 kB
  • After minification 554.5 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. Obviously, Daiken needs image optimization as it can save up to 187.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 213.7 kB

  • Original 355.8 kB
  • After minification 347.1 kB
  • After compression 142.0 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 213.7 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 280.4 kB

  • Original 335.6 kB
  • After minification 318.2 kB
  • After compression 55.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.ne.jp needs all CSS files to be minified and compressed as it can save up to 280.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (31%)

Requests Now

55

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 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 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

daiken.ne.jp

daiken.ne.jp

1295 ms

reset.css

reset.css

341 ms

common.css

common.css

558 ms

jquery.min.js

jquery.min.js

2026 ms

stickysidebar.jquery.js

stickysidebar.jquery.js

371 ms

scrolltopcontrol.js

scrolltopcontrol.js

402 ms

common.js

common.js

371 ms

jquery.js

jquery.js

23 ms

jquery.mb.YTPlayer.min.js

jquery.mb.YTPlayer.min.js

725 ms

banner_slider.css

banner_slider.css

554 ms

banner_slider.js

banner_slider.js

560 ms

analytics.js

analytics.js

72 ms

player_api

player_api

45 ms

logo.png

logo.png

581 ms

global.png

global.png

204 ms

bg_hblack.png

bg_hblack.png

203 ms

mainvisual04.jpg

mainvisual04.jpg

8703 ms

mainvisual.jpg

mainvisual.jpg

2113 ms

mainvisual02.jpg

mainvisual02.jpg

6751 ms

mainvisual03.jpg

mainvisual03.jpg

6458 ms

ttl_category.png

ttl_category.png

761 ms

bg_category.png

bg_category.png

1548 ms

img_category01.png

img_category01.png

949 ms

img_category02.png

img_category02.png

1134 ms

img_category03.png

img_category03.png

1319 ms

img_category04.png

img_category04.png

2315 ms

img_category05.png

img_category05.png

2103 ms

img_category06.png

img_category06.png

2293 ms

img_category07.png

img_category07.png

2668 ms

banner_catalog.jpg

banner_catalog.jpg

4261 ms

banner_data.jpg

banner_data.jpg

4724 ms

banner_movie_sp.jpg

banner_movie_sp.jpg

5002 ms

bna_pc.png

bna_pc.png

4828 ms

icon_pc_arrow02.png

icon_pc_arrow02.png

4915 ms

side_banner01.png

side_banner01.png

5758 ms

side_banner02.png

side_banner02.png

5655 ms

bg_side_banner03.jpg

bg_side_banner03.jpg

5377 ms

side_banner03.png

side_banner03.png

5564 ms

side_banner04.png

side_banner04.png

5752 ms

side_banner05.png

side_banner05.png

6207 ms

side_banner06.png

side_banner06.png

6507 ms

side_banner07.png

side_banner07.png

6314 ms

icon_pc_arrow01.png

icon_pc_arrow01.png

6607 ms

footer_logo.png

footer_logo.png

6867 ms

btn_pagetop.png

btn_pagetop.png

6824 ms

collect

collect

13 ms

collect

collect

70 ms

www-widgetapi.js

www-widgetapi.js

28 ms

XMpHbcUU9DM

XMpHbcUU9DM

56 ms

ga-audiences

ga-audiences

45 ms

XMpHbcUU9DM

XMpHbcUU9DM

54 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

7 ms

www-embed-player.js

www-embed-player.js

24 ms

base.js

base.js

44 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

9 ms

ad_status.js

ad_status.js

50 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

42 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

47 ms

sp.css

sp.css

391 ms

arrow_prev.png

arrow_prev.png

189 ms

arrow_next.png

arrow_next.png

188 ms

Accessibility Review

daiken.ne.jp accessibility score

77

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

daiken.ne.jp best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

daiken.ne.jp SEO score

85

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 Daiken.ne.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.ne.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

daiken.ne.jp

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: