Tools & Wizards About Us
yadokari.net screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

yadokari.net

YADOKARI.net｜小屋・タイニーハウス・空き家・移住・コンテナハウスからこれからの暮らしを考え実践するメディア – YADOKARIは、小屋・タイニーハウス・空き家・移住・コンテナハウスからを通じ、暮らしの美意識を体現し、新たなカルチャーを創造し、発信します。

Page Load Speed

3.2 sec in total

First Response

602 ms

Resources Loaded

1.9 sec

Page Rendered

678 ms

yadokari.net screenshot

About Website

Visit yadokari.net now to see the best up-to-date YADOKARI content for Japan and also check out these interesting facts you probably never knew about yadokari.net

YADOKARIは、小屋・タイニーハウス・空き家・移住・コンテナハウスからを通じ、暮らしの美意識を体現し、新たなカルチャーを創造し、発信します。

Visit yadokari.net

Key Findings

We analyzed Yadokari.net page load time and found that the first response time was 602 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

yadokari.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value33.2 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

Network Requests Diagram

yadokari.net

602 ms

bootstrap.css

34 ms

shortcodes.css

20 ms

styles.css

19 ms

gallery.css

20 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 68% of them (43 requests) were addressed to the original Yadokari.net, 5% (3 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (772 ms) belongs to the original domain Yadokari.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 658.9 kB (20%)

Content Size

3.3 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yadokari.net main page is 3.3 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 64.6 kB

  • Original 82.9 kB
  • After minification 76.1 kB
  • After compression 18.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 64.6 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 17.9 kB

  • Original 2.4 MB
  • After minification 2.4 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. YADOKARI images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 380.7 kB

  • Original 565.5 kB
  • After minification 564.7 kB
  • After compression 184.8 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 380.7 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 195.6 kB

  • Original 231.4 kB
  • After minification 229.9 kB
  • After compression 35.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. Yadokari.net needs all CSS files to be minified and compressed as it can save up to 195.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (52%)

Requests Now

62

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yadokari.net

yadokari.net

602 ms

bootstrap.css

bootstrap.css

34 ms

shortcodes.css

shortcodes.css

20 ms

styles.css

styles.css

19 ms

gallery.css

gallery.css

20 ms

animate.min.css

animate.min.css

21 ms

jquery.js

jquery.js

24 ms

jquery-migrate.min.js

jquery-migrate.min.js

23 ms

bootstrap.js

bootstrap.js

25 ms

jquery.galleriffic.js

jquery.galleriffic.js

23 ms

jquery.masonry.min.js

jquery.masonry.min.js

24 ms

imagesloaded.js

imagesloaded.js

259 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

62 ms

jquery.custom.js

jquery.custom.js

61 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

61 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

61 ms

iscroll.js

iscroll.js

63 ms

jquery.mousewheel.js

jquery.mousewheel.js

61 ms

latest_twitter_widget.css

latest_twitter_widget.css

62 ms

loader.js

loader.js

95 ms

vertical.css

vertical.css

61 ms

style.css

style.css

61 ms

widgets.js

widgets.js

54 ms

jquery.form.min.js

jquery.form.min.js

15 ms

scripts.js

scripts.js

6 ms

public.min.js

public.min.js

5 ms

gpt.js

gpt.js

32 ms

logo_352.png

logo_352.png

24 ms

ico-search.png

ico-search.png

25 ms

%E6%9C%88%E6%A5%B5%E6%9C%AC_%E8%A1%A8%E7%B4%99_1_fb.jpg

%E6%9C%88%E6%A5%B5%E6%9C%AC_%E8%A1%A8%E7%B4%99_1_fb.jpg

28 ms

12498413_10205986808091495_1672172516_n-620x413.jpg

12498413_10205986808091495_1672172516_n-620x413.jpg

27 ms

yolo1.jpg

yolo1.jpg

21 ms

ougigata-tub01.jpg

ougigata-tub01.jpg

22 ms

echo03.jpg

echo03.jpg

24 ms

LODEC%E4%BA%8B%E5%8B%99%E6%89%80%E3%83%A1%E3%83%B3%E3%83%90%E3%83%BC-e1455114754721.jpg

LODEC%E4%BA%8B%E5%8B%99%E6%89%80%E3%83%A1%E3%83%B3%E3%83%90%E3%83%BC-e1455114754721.jpg

49 ms

3-e1456063491349.jpg

3-e1456063491349.jpg

71 ms

ariamaru-tub01.jpg

ariamaru-tub01.jpg

50 ms

holland0.jpg

holland0.jpg

50 ms

Vegan-House_Block-Architects_Photos-Quang-Tran_dezeen_468_01.jpg

Vegan-House_Block-Architects_Photos-Quang-Tran_dezeen_468_01.jpg

52 ms

503216-b64fbf0433840332b12555c46fd45f80563c5f07.jpg

503216-b64fbf0433840332b12555c46fd45f80563c5f07.jpg

48 ms

bnr_yadokari-supporters-400.gif

bnr_yadokari-supporters-400.gif

49 ms

pubads_impl_81.js

pubads_impl_81.js

25 ms

arrow_top.png

arrow_top.png

60 ms

analytics.js

analytics.js

29 ms

container.html

container.html

15 ms

all.js

all.js

64 ms

plusone.js

plusone.js

174 ms

pta.js

pta.js

503 ms

arrow-right-normal.png

arrow-right-normal.png

47 ms

QrOjF.gif

QrOjF.gif

132 ms

admin-ajax.php

admin-ajax.php

772 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

113 ms

collect

collect

87 ms

collect

collect

119 ms

162 ms

xd_arbiter.php

xd_arbiter.php

30 ms

xd_arbiter.php

xd_arbiter.php

42 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

41 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

17 ms

jot

jot

91 ms

1aca749c.js

1aca749c.js

487 ms

tsukigime_560-560.jpg

tsukigime_560-560.jpg

18 ms

close.png

close.png

16 ms

Accessibility Review

yadokari.net accessibility score

78

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

yadokari.net 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

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

yadokari.net SEO score

86

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

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 Yadokari.net 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 Yadokari.net 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

yadokari.net

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