Tools & Wizards About Us
niimien.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

niimien.com

千葉県 東京都の造園 植栽 庭施工 【造園業専門店 新美園】

Page Load Speed

11.3 sec in total

First Response

1.2 sec

Resources Loaded

9.2 sec

Page Rendered

882 ms

niimien.com screenshot

About Website

Welcome to niimien.com homepage info - get ready to check Niimien best content right away, or after learning these important things about niimien.com

造園、植栽、千葉県・東京都の庭施工、坪庭・垣根施工。千葉県市川市の「住まいの造園施工専門会社」です。

Visit niimien.com

Key Findings

We analyzed Niimien.com page load time and found that the first response time was 1.2 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.

Performance Metrics

niimien.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

www.niimien.com

1240 ms

wp-emoji-release.min.js

422 ms

bizvektor_common_min.css

550 ms

wctokyo2012sp2.css

510 ms

style_bizvektor_sns.css

644 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 85% of them (55 requests) were addressed to the original Niimien.com, 5% (3 requests) were made to Niimien.vs1.biz and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Niimien.com.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Niimien.com main page is 3.4 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. 45% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 57.2 kB

  • Original 71.4 kB
  • After minification 67.7 kB
  • After compression 14.2 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 57.2 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 251.7 kB

  • Original 3.0 MB
  • After minification 2.8 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. Niimien images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 100.2 kB

  • Original 167.0 kB
  • After minification 166.8 kB
  • After compression 66.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 100.2 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 75.7 kB

  • Original 93.0 kB
  • After minification 81.5 kB
  • After compression 17.2 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. Niimien.com needs all CSS files to be minified and compressed as it can save up to 75.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (18%)

Requests Now

62

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.niimien.com

www.niimien.com

1240 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

422 ms

bizvektor_common_min.css

bizvektor_common_min.css

550 ms

wctokyo2012sp2.css

wctokyo2012sp2.css

510 ms

style_bizvektor_sns.css

style_bizvektor_sns.css

644 ms

font-awesome.min.css

font-awesome.min.css

7 ms

css

css

31 ms

html5.js

html5.js

25 ms

style.css

style.css

646 ms

comment-reply.min.js

comment-reply.min.js

492 ms

jquery.js

jquery.js

872 ms

jquery-migrate.min.js

jquery-migrate.min.js

799 ms

biz-vektor-min.js

biz-vektor-min.js

843 ms

ga.js

ga.js

151 ms

gofuan.jpg

gofuan.jpg

1304 ms

ba.jpg

ba.jpg

1285 ms

shinchiku.jpg

shinchiku.jpg

1156 ms

forpc.jpg

forpc.jpg

1107 ms

suma2.jpg

suma2.jpg

1084 ms

iconMenuOpen.png

iconMenuOpen.png

504 ms

slide1.jpg

slide1.jpg

2129 ms

slide2.jpg

slide2.jpg

1988 ms

slide3.jpg

slide3.jpg

1905 ms

oya1-150x146.jpg

oya1-150x146.jpg

955 ms

ma1-150x146.jpg

ma1-150x146.jpg

1309 ms

ko1-150x146.jpg

ko1-150x146.jpg

1633 ms

4cba6e34b96fd2ea2d9a9ffc4d4d4c7d.jpg

4cba6e34b96fd2ea2d9a9ffc4d4d4c7d.jpg

1990 ms

zu3.jpg

zu3.jpg

2005 ms

icon_try1_white.gif

icon_try1_white.gif

1990 ms

odenwa.jpg

odenwa.jpg

2761 ms

mo1.jpg

mo1.jpg

2642 ms

pc3.jpg

pc3.jpg

2690 ms

Mail_128px_1176503_easyicon.net_.png

Mail_128px_1176503_easyicon.net_.png

2328 ms

syokusaimenu2.jpg

syokusaimenu2.jpg

2884 ms

sibafumenu2.jpg

sibafumenu2.jpg

3002 ms

koniwamenu2.jpg

koniwamenu2.jpg

3199 ms

wafuu.jpg

wafuu.jpg

3600 ms

ikem.jpg

ikem.jpg

3744 ms

shizenm.jpg

shizenm.jpg

3833 ms

mekakushi.jpg

mekakushi.jpg

3967 ms

zassoutaisaku.jpg

zassoutaisaku.jpg

3849 ms

mmidashi.jpg

mmidashi.jpg

4027 ms

tenpomidashi.jpg

tenpomidashi.jpg

4441 ms

DSC_0265.jpg

DSC_0265.jpg

4979 ms

eye1.jpg

eye1.jpg

4909 ms

eye.jpg

eye.jpg

4744 ms

eye1.jpg

eye1.jpg

4949 ms

eye.jpg

eye.jpg

4922 ms

eye3.jpg

eye3.jpg

4985 ms

eye2.jpg

eye2.jpg

5320 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

26 ms

__utm.gif

__utm.gif

77 ms

collect

collect

62 ms

eye21.jpg

eye21.jpg

5171 ms

eye5.jpg

eye5.jpg

5366 ms

eye3.jpg

eye3.jpg

5182 ms

sentei.jpg

sentei.jpg

5164 ms

bnr_contact_ja.png

bnr_contact_ja.png

4424 ms

blog1.jpg

blog1.jpg

5127 ms

footer_pagetop.png

footer_pagetop.png

4687 ms

frogopng2.png

frogopng2.png

4498 ms

icon_arrow1_gray.gif

icon_arrow1_gray.gif

4345 ms

icon_arrow2_gray.gif

icon_arrow2_gray.gif

4126 ms

bg_control_nav.png

bg_control_nav.png

362 ms

bg_direction_nav2_30.png

bg_direction_nav2_30.png

387 ms

Accessibility Review

niimien.com accessibility score

79

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

niimien.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

niimien.com 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 Niimien.com 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 Niimien.com 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

niimien.com

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