Tools & Wizards About Us
niwashyu.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

niwashyu.jp

ガーデン デザインショップ 庭衆

Page Load Speed

3.3 sec in total

First Response

862 ms

Resources Loaded

2.4 sec

Page Rendered

104 ms

niwashyu.jp screenshot

About Website

Click here to check amazing Niwashyu content. Otherwise, check out these important facts you probably never knew about niwashyu.jp

Visit niwashyu.jp

Key Findings

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

Performance Metrics

niwashyu.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.15

76/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

niwashyu.jp

862 ms

style.min.css

384 ms

animate.css

356 ms

styles.css

358 ms

style.css

361 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 80% of them (33 requests) were addressed to the original Niwashyu.jp, 12% (5 requests) were made to Use.fontawesome.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (909 ms) belongs to the original domain Niwashyu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.9 kB (14%)

Content Size

946.8 kB

After Optimization

811.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Niwashyu.jp main page is 946.8 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. 60% of websites need less resources to load. Images take 601.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 52.2 kB

  • Original 65.9 kB
  • After minification 65.0 kB
  • After compression 13.7 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 52.2 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 7.4 kB

  • Original 601.9 kB
  • After minification 594.5 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. Niwashyu images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 51.5 kB

  • Original 177.6 kB
  • After minification 176.8 kB
  • After compression 126.1 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 51.5 kB or 29% of the original size.

CSS Optimization

-24%

Potential reduce by 23.9 kB

  • Original 101.4 kB
  • After minification 101.4 kB
  • After compression 77.5 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. Niwashyu.jp needs all CSS files to be minified and compressed as it can save up to 23.9 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (69%)

Requests Now

35

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

niwashyu.jp

niwashyu.jp

862 ms

style.min.css

style.min.css

384 ms

animate.css

animate.css

356 ms

styles.css

styles.css

358 ms

style.css

style.css

361 ms

css2

css2

22 ms

ionicons.min.css

ionicons.min.css

379 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

386 ms

jquery.fancybox.css

jquery.fancybox.css

532 ms

flickity.css

flickity.css

533 ms

style.css

style.css

540 ms

all.css

all.css

34 ms

v4-shims.css

v4-shims.css

43 ms

jquery.min.js

jquery.min.js

745 ms

jquery-migrate.min.js

jquery-migrate.min.js

562 ms

ays-pb-public.js

ays-pb-public.js

565 ms

modernizr-custom.js

modernizr-custom.js

709 ms

ays-pb-public-min.css

ays-pb-public-min.css

535 ms

index.js

index.js

543 ms

index.js

index.js

674 ms

superfish.js

superfish.js

673 ms

jquery.mmenu.all.js

jquery.mmenu.all.js

886 ms

jquery.fancybox.js

jquery.fancybox.js

891 ms

imagesloaded.min.js

imagesloaded.min.js

722 ms

jquery.flex-images.js

jquery.flex-images.js

751 ms

flickity.pkgd.js

flickity.pkgd.js

755 ms

alvar.js

alvar.js

758 ms

gardendesignshop-logo.png

gardendesignshop-logo.png

317 ms

niwashyu-logo.jpg

niwashyu-logo.jpg

710 ms

otoiawaseform.png

otoiawaseform.png

356 ms

K%EF%BC%91-800x600.jpg

K%EF%BC%91-800x600.jpg

909 ms

%E3%83%BB0-450x600.jpg

%E3%83%BB0-450x600.jpg

652 ms

0-1-900x600.jpg

0-1-900x600.jpg

660 ms

OK_0204-900x600.jpg

OK_0204-900x600.jpg

892 ms

DSC06700-400x600.jpg

DSC06700-400x600.jpg

716 ms

cropped-rjg_logojpg.jpg

cropped-rjg_logojpg.jpg

830 ms

P5sfzZCDf9_T_3cV7NCUECyoxNk3CstsBxDAVQMAaw.ttf

P5sfzZCDf9_T_3cV7NCUECyoxNk3CstsBxDAVQMAaw.ttf

116 ms

P5sfzZCDf9_T_3cV7NCUECyoxNk37cxsBxDAVQMAaw.ttf

P5sfzZCDf9_T_3cV7NCUECyoxNk37cxsBxDAVQMAaw.ttf

302 ms

fa-solid-900.woff

fa-solid-900.woff

17 ms

fa-regular-400.woff

fa-regular-400.woff

33 ms

fa-brands-400.woff

fa-brands-400.woff

19 ms

Accessibility Review

niwashyu.jp accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

niwashyu.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

niwashyu.jp SEO score

79

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 doesn't use 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 Niwashyu.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 Niwashyu.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

niwashyu.jp

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