Tools & Wizards About Us
dyflex.co.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

dyflex.co.jp

シーカ・ジャパン株式会社

Page Load Speed

7.1 sec in total

First Response

892 ms

Resources Loaded

6 sec

Page Rendered

160 ms

dyflex.co.jp screenshot

About Website

Click here to check amazing Dyflex content for Japan. Otherwise, check out these important facts you probably never knew about dyflex.co.jp

ウレタン防水のリーディングカンパニー、安心防水工法のシーカ・ジャパン株式会社

Visit dyflex.co.jp

Key Findings

We analyzed Dyflex.co.jp page load time and found that the first response time was 892 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

dyflex.co.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value39.6 s

0/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.589

11/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

Network Requests Diagram

www.dyflex.co.jp

892 ms

ga.js

20 ms

wp-emoji-release.min.js

326 ms

jquery.min.js

20 ms

workcase.css

344 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 96% of them (65 requests) were addressed to the original Dyflex.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Dyflex.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.2 kB (44%)

Content Size

552.3 kB

After Optimization

310.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 24.7 kB

  • Original 30.6 kB
  • After minification 24.4 kB
  • After compression 5.9 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 6.2 kB, which is 20% 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 24.7 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 2.7 kB

  • Original 190.9 kB
  • After minification 188.2 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. Dyflex images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 176.4 kB

  • Original 284.4 kB
  • After minification 280.0 kB
  • After compression 108.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 176.4 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 38.5 kB

  • Original 46.5 kB
  • After minification 33.1 kB
  • After compression 8.0 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. Dyflex.co.jp needs all CSS files to be minified and compressed as it can save up to 38.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.dyflex.co.jp

www.dyflex.co.jp

892 ms

ga.js

ga.js

20 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

326 ms

jquery.min.js

jquery.min.js

20 ms

workcase.css

workcase.css

344 ms

acordion.js

acordion.js

348 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

554 ms

reset.css

reset.css

380 ms

common.css

common.css

396 ms

design.css

design.css

686 ms

pagenavi-css.css

pagenavi-css.css

679 ms

common.js

common.js

688 ms

jquery.shadow.css

jquery.shadow.css

744 ms

jquery.shadow.js

jquery.shadow.js

742 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

909 ms

flexslider.css

flexslider.css

1015 ms

styles.css

styles.css

1052 ms

se-styles.css

se-styles.css

1053 ms

jquery.js

jquery.js

1261 ms

jquery-migrate.min.js

jquery-migrate.min.js

1103 ms

jquery.form.min.js

jquery.form.min.js

1242 ms

scripts.js

scripts.js

1368 ms

__utm.gif

__utm.gif

11 ms

logo.gif

logo.gif

378 ms

subnavi01.gif

subnavi01.gif

393 ms

subnavi02.gif

subnavi02.gif

408 ms

bg_gnavi.gif

bg_gnavi.gif

542 ms

gnavi01.gif

gnavi01.gif

612 ms

gnavi02.gif

gnavi02.gif

676 ms

gnavi03.gif

gnavi03.gif

682 ms

gnavi04.gif

gnavi04.gif

727 ms

gnavi05.gif

gnavi05.gif

772 ms

gnavi06.gif

gnavi06.gif

879 ms

bg_visual.gif

bg_visual.gif

974 ms

visual_index01.jpg

visual_index01.jpg

1180 ms

visual_index02.jpg

visual_index02.jpg

1406 ms

visual_index03.jpg

visual_index03.jpg

1294 ms

visual_index04.jpg

visual_index04.jpg

1632 ms

bg_index_menu.gif

bg_index_menu.gif

1243 ms

ttl_index_menu.gif

ttl_index_menu.gif

1322 ms

btn_index_menu01.gif

btn_index_menu01.gif

1529 ms

btn_index_menu02.gif

btn_index_menu02.gif

1597 ms

btn_index_menu03.gif

btn_index_menu03.gif

1673 ms

btn_index_menu04.gif

btn_index_menu04.gif

1677 ms

ttl_index_news.gif

ttl_index_news.gif

1769 ms

subttl_index_news.gif

subttl_index_news.gif

1871 ms

arr01.gif

arr01.gif

1977 ms

ttl_index_topics.gif

ttl_index_topics.gif

1983 ms

img_index_group01.gif

img_index_group01.gif

2042 ms

img_index_group02.gif

img_index_group02.gif

2058 ms

img_index_group03.gif

img_index_group03.gif

2101 ms

ttl_sidenavi01.gif

ttl_sidenavi01.gif

2218 ms

btn_sidenavi01.gif

btn_sidenavi01.gif

2306 ms

btn_sidenavi02.gif

btn_sidenavi02.gif

2312 ms

btn_sidenavi03.gif

btn_sidenavi03.gif

2377 ms

ttl_sidenavi02.gif

ttl_sidenavi02.gif

2368 ms

btn_sidenavi04.gif

btn_sidenavi04.gif

2242 ms

btn_sidenavi05.gif

btn_sidenavi05.gif

2334 ms

btn_sidenavi06.gif

btn_sidenavi06.gif

2311 ms

ttl_sidenavi03.gif

ttl_sidenavi03.gif

2330 ms

btn_sidenavi07.gif

btn_sidenavi07.gif

2372 ms

btn_sidenavi10.gif

btn_sidenavi10.gif

2376 ms

btn_sidenavi08.gif

btn_sidenavi08.gif

2268 ms

btn_sidenavi09.gif

btn_sidenavi09.gif

2372 ms

bnr_sidenavi01.gif

bnr_sidenavi01.gif

2366 ms

bg_footer.gif

bg_footer.gif

2372 ms

btn_sitemap.gif

btn_sitemap.gif

2390 ms

flexslider-icon.woff

flexslider-icon.woff

183 ms

Accessibility Review

dyflex.co.jp accessibility score

79

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

dyflex.co.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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

dyflex.co.jp SEO score

93

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dyflex.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dyflex.co.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

dyflex.co.jp

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