Tools & Wizards About Us
dutchwest.co.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

dutchwest.co.jp

薪ストーブのことならダッチウエストジャパン

Page Load Speed

18.9 sec in total

First Response

530 ms

Resources Loaded

17.9 sec

Page Rendered

456 ms

dutchwest.co.jp screenshot

About Website

Visit dutchwest.co.jp now to see the best up-to-date Dutchwest content for Japan and also check out these interesting facts you probably never knew about dutchwest.co.jp

薪ストーブをお探しなら職人徹底品質管理のダッチウエストジャパンへ。暖炉、煙突など関連商品も多数販売しております。

Visit dutchwest.co.jp

Key Findings

We analyzed Dutchwest.co.jp page load time and found that the first response time was 530 ms and then it took 18.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

dutchwest.co.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value28.0 s

0/100

10%

TBT (Total Blocking Time)

Value710 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

dutchwest.co.jp

530 ms

www.dutchwest.co.jp

2910 ms

homestyle.css

1234 ms

homecommon.js

1937 ms

ga.js

811 ms

Our browser made a total of 159 requests to load all elements on the main page. We found that 86% of them (137 requests) were addressed to the original Dutchwest.co.jp, 3% (4 requests) were made to Platform.twitter.com and 2% (3 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Dutchwest.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 675.6 kB (12%)

Content Size

5.8 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dutchwest.co.jp main page is 5.8 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. 70% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 92.2 kB

  • Original 116.2 kB
  • After minification 115.1 kB
  • After compression 24.1 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 92.2 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 339.7 kB

  • Original 5.3 MB
  • After minification 5.0 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. Dutchwest images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 130.2 kB

  • Original 243.8 kB
  • After minification 216.3 kB
  • After compression 113.7 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 130.2 kB or 53% of the original size.

CSS Optimization

-85%

Potential reduce by 113.6 kB

  • Original 134.2 kB
  • After minification 126.4 kB
  • After compression 20.6 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. Dutchwest.co.jp needs all CSS files to be minified and compressed as it can save up to 113.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (25%)

Requests Now

155

After Optimization

116

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dutchwest.co.jp

dutchwest.co.jp

530 ms

www.dutchwest.co.jp

www.dutchwest.co.jp

2910 ms

homestyle.css

homestyle.css

1234 ms

homecommon.js

homecommon.js

1937 ms

ga.js

ga.js

811 ms

style.min.css

style.min.css

1595 ms

pagenavi-css.css

pagenavi-css.css

709 ms

pinit.js

pinit.js

51 ms

getseal

getseal

274 ms

conversion.js

conversion.js

124 ms

platform.js

platform.js

51 ms

scale.js

scale.js

555 ms

bxslider.js

bxslider.js

774 ms

top.js

top.js

630 ms

wp-embed.min.js

wp-embed.min.js

751 ms

us.norton.com

us.norton.com

201 ms

homebase.css

homebase.css

386 ms

webfont.css

webfont.css

377 ms

ga.js

ga.js

121 ms

gtm.js

gtm.js

222 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

463 ms

pinit_fg_ja_rect_gray_20.png

pinit_fg_ja_rect_gray_20.png

126 ms

bg_header.png

bg_header.png

306 ms

logo.png

logo.png

503 ms

navi01.png

navi01.png

306 ms

navi02.png

navi02.png

330 ms

navi03.png

navi03.png

330 ms

navi04.png

navi04.png

461 ms

navi05.png

navi05.png

645 ms

navi06.png

navi06.png

509 ms

ttl01.png

ttl01.png

743 ms

img01.jpg

img01.jpg

1344 ms

btn_detail.png

btn_detail.png

656 ms

ttl17.png

ttl17.png

705 ms

img13.jpg

img13.jpg

1387 ms

ttl30.png

ttl30.png

1024 ms

img30.jpg

img30.jpg

1712 ms

ttl32.png

ttl32.png

1097 ms

img32.jpg

img32.jpg

1819 ms

ttl24.png

ttl24.png

1403 ms

img24.jpg

img24.jpg

2002 ms

ttl25.png

ttl25.png

1756 ms

img25.jpg

img25.jpg

2080 ms

ttl29.png

ttl29.png

1821 ms

img29.jpg

img29.jpg

2591 ms

ttl26.png

ttl26.png

1951 ms

img26.jpg

img26.jpg

2632 ms

ttl28.png

ttl28.png

2030 ms

img28.jpg

img28.jpg

2681 ms

ttl21.png

ttl21.png

2218 ms

img21.jpg

img21.jpg

3106 ms

ttl23.png

ttl23.png

2450 ms

img23.jpg

img23.jpg

3628 ms

ttl31.png

ttl31.png

2835 ms

img31.jpg

img31.jpg

3499 ms

arrow01.png

arrow01.png

2857 ms

sdk.js

sdk.js

168 ms

arrow02.png

arrow02.png

2876 ms

widgets.js

widgets.js

141 ms

__utm.gif

__utm.gif

98 ms

__utm.gif

__utm.gif

94 ms

109 ms

pinit_main.js

pinit_main.js

39 ms

sdk.js

sdk.js

28 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

36 ms

settings

settings

86 ms

116 ms

57 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3091 ms

slide01_off.png

slide01_off.png

2974 ms

slide19_off.png

slide19_off.png

2939 ms

slide20_off.png

slide20_off.png

3180 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

4 ms

embeds

embeds

21 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

14 ms

slide30_off.png

slide30_off.png

3362 ms

slide32_off.png

slide32_off.png

3350 ms

slide25_off.png

slide25_off.png

3315 ms

slide26_off.png

slide26_off.png

3394 ms

slide29_off.png

slide29_off.png

3435 ms

slide27_off.png

slide27_off.png

3604 ms

slide28_off.png

slide28_off.png

3660 ms

slide21_off.png

slide21_off.png

3502 ms

slide23_off.png

slide23_off.png

3234 ms

slide24_off.png

slide24_off.png

3029 ms

slide31_off.png

slide31_off.png

3209 ms

ttl_baner.png

ttl_baner.png

3217 ms

homeb1.jpg

homeb1.jpg

3379 ms

homeb1sp.jpg

homeb1sp.jpg

3041 ms

homeb2.jpg

homeb2.jpg

3053 ms

homeb2sp.jpg

homeb2sp.jpg

3113 ms

homeb5.jpg

homeb5.jpg

3218 ms

homeb5sp.jpg

homeb5sp.jpg

3220 ms

homeb4.jpg

homeb4.jpg

3428 ms

homeb4sp.jpg

homeb4sp.jpg

3325 ms

ttl_whatsnew.png

ttl_whatsnew.png

2994 ms

ttl_blog.png

ttl_blog.png

3246 ms

topbaner1.jpg

topbaner1.jpg

3252 ms

topbaner2.jpg

topbaner2.jpg

3198 ms

topbaner3.jpg

topbaner3.jpg

3091 ms

topbaner4.jpg

topbaner4.jpg

3381 ms

topbaner5.jpg

topbaner5.jpg

3225 ms

topbaner6.jpg

topbaner6.jpg

3177 ms

ttl_rais.png

ttl_rais.png

3276 ms

banerrais.jpg

banerrais.jpg

3151 ms

banerraissp.jpg

banerraissp.jpg

3116 ms

ttl_stovax.png

ttl_stovax.png

3028 ms

banerstovax.jpg

banerstovax.jpg

3373 ms

banerstovaxsp.jpg

banerstovaxsp.jpg

3148 ms

ttl_pickup.png

ttl_pickup.png

3222 ms

bnr_tools.jpg

bnr_tools.jpg

3094 ms

bnr_zuihou.jpg

bnr_zuihou.jpg

3021 ms

bnr_weber.jpg

bnr_weber.jpg

3378 ms

bnr_ptygrace.jpg

bnr_ptygrace.jpg

3384 ms

bnr_banesafe.jpg

bnr_banesafe.jpg

3275 ms

homecatalog2022.jpg

homecatalog2022.jpg

3482 ms

rais2022.jpg

rais2022.jpg

3495 ms

homecatalog6.jpg

homecatalog6.jpg

3225 ms

homecatalog3-2023.jpg

homecatalog3-2023.jpg

6225 ms

homecatalog4-2022.jpg

homecatalog4-2022.jpg

3615 ms

homecatalog7.jpg

homecatalog7.jpg

3839 ms

homecatalog5-2023.jpg

homecatalog5-2023.jpg

3833 ms

baner-pinterest.gif

baner-pinterest.gif

3201 ms

baner-facebook.gif

baner-facebook.gif

3106 ms

gototop.png

gototop.png

3255 ms

foot-insta.png

foot-insta.png

3265 ms

foot-line.png

foot-line.png

3199 ms

foot-tiktok.png

foot-tiktok.png

3244 ms

bnr_braisfoot.png

bnr_braisfoot.png

3250 ms

bnr_stovax.png

bnr_stovax.png

3212 ms

hearthlogo.png

hearthlogo.png

3305 ms

footlogo.png

footlogo.png

3335 ms

loading.gif

loading.gif

3316 ms

bg_navi.png

bg_navi.png

2942 ms

line.png

line.png

3139 ms

li5.jpg

li5.jpg

3380 ms

li7.jpg

li7.jpg

3127 ms

li6.jpg

li6.jpg

3188 ms

catalogtitle.jpg

catalogtitle.jpg

3181 ms

foot-x.svg

foot-x.svg

2962 ms

icontel.png

icontel.png

3119 ms

iconemail.png

iconemail.png

3091 ms

img09.jpg

img09.jpg

4115 ms

arrow01.gif

arrow01.gif

2832 ms

arrow02.gif

arrow02.gif

2772 ms

slide01_ov.png

slide01_ov.png

686 ms

slide19_ov.png

slide19_ov.png

569 ms

slide20_ov.png

slide20_ov.png

1417 ms

slide30_ov.png

slide30_ov.png

1137 ms

slide32_ov.png

slide32_ov.png

614 ms

slide25_ov.png

slide25_ov.png

687 ms

slide26_ov.png

slide26_ov.png

1018 ms

slide29_ov.png

slide29_ov.png

1035 ms

slide27_ov.png

slide27_ov.png

1106 ms

slide28_ov.png

slide28_ov.png

1117 ms

slide21_ov.png

slide21_ov.png

1400 ms

slide23_ov.png

slide23_ov.png

1468 ms

slide24_ov.png

slide24_ov.png

1521 ms

slide31_ov.png

slide31_ov.png

2581 ms

Accessibility Review

dutchwest.co.jp accessibility score

74

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

dutchwest.co.jp best practices score

67

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

SEO Factors

dutchwest.co.jp SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

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

dutchwest.co.jp

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