11.3 sec in total
1.1 sec
9.9 sec
259 ms
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.jpWe 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.
daiken.jp performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value10.5 s
0/100
25%
Value10.4 s
8/100
10%
Value3,260 ms
2/100
30%
Value0.772
5/100
15%
Value18.8 s
3/100
10%
1140 ms
1355 ms
395 ms
821 ms
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 size can be reduced by 393.7 kB (35%)
1.1 MB
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.
Potential reduce by 14.3 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.
Potential reduce by 9.4 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.
Potential reduce by 272.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 272.2 kB or 79% of the original size.
Potential reduce by 97.8 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.
Number of requests can be reduced by 19 (32%)
60
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.
daiken.jp
1140 ms
12main.css
1355 ms
font_m.css
395 ms
10_basic.js
821 ms
jquery.js
5728 ms
jquery.innerfade.js
619 ms
10sub.css
792 ms
dc.js
29 ms
__utm.gif
11 ms
12_bg_toppage.gif
200 ms
12_bg_top_head.gif
579 ms
12_daiken_logo_l.gif
211 ms
12_daiken_logo_l.gif
212 ms
12_top_head_parts.gif
394 ms
12_bg_top_body.gif
407 ms
12_bg_kojin_side.gif
397 ms
70th_banner.jpg
1445 ms
70th_banner_Top.jpg
1934 ms
kokyo_banner_A.jpg
1734 ms
top2012_bg4_3.jpg
1985 ms
top2012_bg2_3.jpg
1428 ms
12_bg_top_3way.gif
967 ms
12_bg_top_kojin.gif
1167 ms
12_top_link_3way.gif
1560 ms
12_arrow.gif
1631 ms
12_bg_top_pro.gif
1649 ms
12_bg_top_company.gif
1754 ms
12_bg_top_important.gif
1836 ms
12_top_link_parts.gif
1851 ms
12_top_h3.gif
1925 ms
10_top_bg_news.gif
1945 ms
10_top_bg_dot.gif
2040 ms
12_top_news_04.gif
2055 ms
12_top_news_02.gif
2116 ms
12_top_news_06.gif
2136 ms
12_bg_top_pickup.gif
2330 ms
12_top_bana_l_003.jpg
2379 ms
15_top_bana_l_001.jpg
2250 ms
12_bg_top_side_end.gif
2256 ms
12_top_side_h2.gif
2305 ms
12_bg_side_link_l.gif
2540 ms
12_top_side_link.gif
2661 ms
12_top_bana_s_007.jpg
2465 ms
12_top_bana_s_011.jpg
2497 ms
tag.js
10 ms
12_top_bana_s_008.jpg
2485 ms
12_bana_018.gif
2385 ms
12_top_bana_s_001.gif
2465 ms
15_bana_003.gif
2485 ms
12_top_bana_s_005.gif
2328 ms
12_top_bana_s_002.gif
2353 ms
12_top_bana_s_003.gif
2377 ms
12_bg_foot.gif
2294 ms
12_bg_foot_navi_001.gif
1915 ms
12_bg_foot_parts.gif
1911 ms
12_bg_foot_links.gif
1488 ms
12_bg_foot_link.gif
1713 ms
12_bg_foot_foot.gif
1421 ms
12_bg_foot_foot_line.gif
1442 ms
12_bg_foot_foot_parts.gif
1437 ms
font_l.css
200 ms
daiken.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
daiken.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
daiken.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
daiken.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: