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

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

daiken.ne.jp

507 ms

daiken.ne.jp

1119 ms

gtm.js

47 ms

reset.css

480 ms

renewal_common.css

670 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 74% of them (68 requests) were addressed to the original Daiken.ne.jp, 9% (8 requests) were made to Youtube.com and 3% (3 requests) were made to Cache.dga.jp. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Daiken.ne.jp.

Content Size

3.2 MB

After Optimization

3.0 MB

In fact, the total size of Daiken.ne.jp main page is 3.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 60.0 kB

Original 69.2 kB
After minification 49.6 kB
After compression 9.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. This page needs HTML code to be minified as it can gain 19.6 kB, which is 28% 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 60.0 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 33.3 kB

Original 2.7 MB
After minification 2.6 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. Daiken images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 50.8 kB

Original 317.8 kB
After minification 316.4 kB
After compression 267.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 50.8 kB or 16% of the original size.

CSS Optimization

-18%

Potential reduce by 20.7 kB

Original 115.1 kB
After minification 114.7 kB
After compression 94.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. Daiken.ne.jp needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 18% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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 the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

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

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

daiken.ne.jp

daiken.ne.jp

gtm.js

reset.css

renewal_common.css

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

daiken.ne.jp

daiken.ne.jp

gtm.js

reset.css

renewal_common.css

jquery.js

jquery.easing.1.3.js

stickysidebar.jquery.js

scrolltopcontrol.js

common.js

temp.css

slick.min.js

renewal_top.css

slick.css

slick-theme.css

jquery.mb.YTPlayer.min.js

search_tool_n3.js

analytics.js

logo.png

img_exteriort04_1.jpg

img_exteriort02_3.jpg

img_exteriort06_3.jpg

img_interior07_2.jpg

img_interior04_1.jpg

img_entrance02_3.jpg

img_entrance01_1.jpg

img_fittings02_1.jpg

img_fittings05_1.jpg

img_environment05_1.jpg

LLM_D2000.jpg

img_environment02_4.jpg

img_home01_2.jpg

img_home05_1.jpg

img_lock_security00_1.jpg

banner_catalog.jpg

banner_data.jpg

banner_movie_sp.jpg

banner_FAQ_sp.jpg

bannerlist_10.jpg

top_daichan-banner.jpg

top_ar-banner2023.jpg

bannerlist_11.jpg

bna_pc.png