Tools & Wizards About Us
niwablo.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

niwablo.jp

全国のお庭好きが集まるコミュニティサイト「庭ブロ」 | Niwablo

Page Load Speed

8.9 sec in total

First Response

512 ms

Resources Loaded

8.1 sec

Page Rendered

244 ms

niwablo.jp screenshot

About Website

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

「庭ブロ」は、バラやお花・植物を愛するすべての人と“共につくり、共に成長していくコミュニティサイト”です。お庭を通じて体験できる心豊かなコミュニケーションや成長の喜びなど、自然と呼吸する生命の感動をより多くの方と共有・共感できます。

Visit niwablo.jp

Key Findings

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

Performance Metrics

niwablo.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

niwablo.jp

512 ms

www.niwablo.jp

961 ms

reset.css

330 ms

blog_top.css

493 ms

public.css

338 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 66% of them (92 requests) were addressed to the original Niwablo.jp, 14% (19 requests) were made to Rgc.takasho.jp and 6% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Niwablo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.2 kB (16%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Niwablo.jp main page is 1.6 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 45.3 kB

  • Original 58.0 kB
  • After minification 52.5 kB
  • After compression 12.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 45.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 9.1 kB

  • Original 1.3 MB
  • After minification 1.2 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. Niwablo images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 177.3 kB

  • Original 293.1 kB
  • After minification 269.5 kB
  • After compression 115.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 177.3 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 28.5 kB

  • Original 34.5 kB
  • After minification 20.8 kB
  • After compression 6.1 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. Niwablo.jp needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

133

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

niwablo.jp

niwablo.jp

512 ms

www.niwablo.jp

www.niwablo.jp

961 ms

reset.css

reset.css

330 ms

blog_top.css

blog_top.css

493 ms

public.css

public.css

338 ms

prototype.js

prototype.js

845 ms

application.js

application.js

340 ms

main7.php

main7.php

343 ms

RGC2024_300x600.png

RGC2024_300x600.png

1834 ms

bnrlink_336x280.jpg

bnrlink_336x280.jpg

1275 ms

bn_JGTA234x60b.png

bn_JGTA234x60b.png

906 ms

sponsor_logo_gardenstory.png

sponsor_logo_gardenstory.png

873 ms

bnr_takasho2024.png

bnr_takasho2024.png

1039 ms

bgimg.gif

bgimg.gif

333 ms

header-img-bg.gif

header-img-bg.gif

662 ms

header-img.gif

header-img.gif

338 ms

btn_about.gif

btn_about.gif

339 ms

log_in.gif

log_in.gif

343 ms

btn_help.gif

btn_help.gif

665 ms

btn_contact.gif

btn_contact.gif

669 ms

store_gourmet.gif

store_gourmet.gif

670 ms

store_beauty.gif

store_beauty.gif

679 ms

title_bar_serch.gif

title_bar_serch.gif

688 ms

title_bar_movile.gif

title_bar_movile.gif

992 ms

qr_code.jpg

qr_code.jpg

991 ms

title_bar_ranking.gif

title_bar_ranking.gif

1000 ms

keep.jpg

keep.jpg

1022 ms

1.jpg

1.jpg

1016 ms

2.jpg

2.jpg

1018 ms

3.jpg

3.jpg

1321 ms

4.jpg

4.jpg

1322 ms

up.jpg

up.jpg

1328 ms

5.jpg

5.jpg

1344 ms

down.jpg

down.jpg

1355 ms

6.jpg

6.jpg

1362 ms

7.jpg

7.jpg

1658 ms

8.jpg

8.jpg

1664 ms

9.jpg

9.jpg

1679 ms

10.jpg

10.jpg

1684 ms

11.jpg

11.jpg

1695 ms

12.jpg

12.jpg

1689 ms

13.jpg

13.jpg

1988 ms

14.jpg

14.jpg

1992 ms

15.jpg

15.jpg

2008 ms

16.jpg

16.jpg

2021 ms

17.jpg

17.jpg

2033 ms

18.jpg

18.jpg

2041 ms

top_link.php

top_link.php

721 ms

lighting.html

lighting.html

723 ms

inline

inline

1022 ms

19.jpg

19.jpg

2270 ms

sdk.js

sdk.js

29 ms

ga.js

ga.js

12 ms

__utm.gif

__utm.gif

26 ms

sdk.js

sdk.js

4 ms

collect

collect

25 ms

ga-audiences

ga-audiences

76 ms

common.css

common.css

2007 ms

top.css

top.css

2008 ms

global.css

global.css

2017 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

2546 ms

jquery.cross-slide.js

jquery.cross-slide.js

2029 ms

20.jpg

20.jpg

2011 ms

21.jpg

21.jpg

2004 ms

22.jpg

22.jpg

2018 ms

23.jpg

23.jpg

2024 ms

24.jpg

24.jpg

2032 ms

25.jpg

25.jpg

2313 ms

top_link.css

top_link.css

353 ms

jquery.min.js

jquery.min.js

22 ms

bootstrap.min.js

bootstrap.min.js

351 ms

head_top_link.gif

head_top_link.gif

368 ms

img24544.jpg

img24544.jpg

560 ms

img17693.jpg

img17693.jpg

566 ms

lighting.css

lighting.css

376 ms

bnr_beafter.gif

bnr_beafter.gif

701 ms

img22298.jpg

img22298.jpg

1117 ms

26.jpg

26.jpg

2017 ms

27.jpg

27.jpg

2020 ms

28.jpg

28.jpg

2046 ms

29.jpg

29.jpg

2032 ms

30.jpg

30.jpg

2207 ms

title_bar_blog_pick_up.gif

title_bar_blog_pick_up.gif

2316 ms

fin.html

fin.html

2299 ms

bootstrap.min.js

bootstrap.min.js

1149 ms

bg_top_link.gif

bg_top_link.gif

371 ms

btn_top_link.gif

btn_top_link.gif

370 ms

bg_beafter.gif

bg_beafter.gif

533 ms

osusume_blog.gif

osusume_blog.gif

2030 ms

uHvFuS8o.gif

uHvFuS8o.gif

2063 ms

VmytZ4WR.jpg

VmytZ4WR.jpg

2055 ms

DzET1RQV.jpg

DzET1RQV.jpg

2198 ms

sw_community.gif

sw_community.gif

2304 ms

sw_blank2.gif

sw_blank2.gif

2023 ms

sw_blank3.gif

sw_blank3.gif

2026 ms

sw_blank4.gif

sw_blank4.gif

2047 ms

bar-title-news.gif

bar-title-news.gif

2058 ms

bar-title-latest_report.gif

bar-title-latest_report.gif

2204 ms

AOBno1HX.jpg

AOBno1HX.jpg

2313 ms

NcdkzRhK.jpg

NcdkzRhK.jpg

2032 ms

bar_title_new_arrival.gif

bar_title_new_arrival.gif

2036 ms

baner_tiiki.gif

baner_tiiki.gif

2057 ms

category_ippan.gif

category_ippan.gif

2049 ms

bnr_niwabloytc.png

bnr_niwabloytc.png

2198 ms

bunner-w160-2.gif

bunner-w160-2.gif

2307 ms

title_bar_login.gif

title_bar_login.gif

2032 ms

title_bar_comminity.gif

title_bar_comminity.gif

2039 ms

bar_title_comminity_new.gif

bar_title_comminity_new.gif

2068 ms

bar_title_comminity_category.gif

bar_title_comminity_category.gif

2053 ms

bar_title_help.gif

bar_title_help.gif

2215 ms

bar_title_stuff_blog.gif

bar_title_stuff_blog.gif

2032 ms

bnr_niwabloplus.png

bnr_niwabloplus.png

2023 ms

top150513_1.jpg

top150513_1.jpg

2878 ms

top150513_2.jpg

top150513_2.jpg

2687 ms

main7.php

main7.php

1406 ms

RGC2023_300x600.png

RGC2023_300x600.png

1146 ms

top_link.php

top_link.php

420 ms

lighting.html

lighting.html

457 ms

__utm.gif

__utm.gif

9 ms

bnr_takasho2021.png

bnr_takasho2021.png

657 ms

UK5JZe9o.jpg

UK5JZe9o.jpg

1544 ms

fpI8dglW.jpg

fpI8dglW.jpg

1654 ms

cmy_default_3.jpg

cmy_default_3.jpg

1658 ms

Fms7Yx2Q.jpg

Fms7Yx2Q.jpg

1709 ms

img21379.jpg

img21379.jpg

525 ms

img12766.jpg

img12766.jpg

560 ms

img7246.jpg

img7246.jpg

518 ms

page.php

page.php

116 ms

FadKU54ud94.css

FadKU54ud94.css

16 ms

fwJTNXSLwj7.js

fwJTNXSLwj7.js

22 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

21 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

49 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

47 ms

qwSlV7K_jlE.js

qwSlV7K_jlE.js

52 ms

zYzGplAqD4J.js

zYzGplAqD4J.js

51 ms

p55HfXW__mM.js

p55HfXW__mM.js

47 ms

379476773_682731663888381_3003517287352624139_n.jpg

379476773_682731663888381_3003517287352624139_n.jpg

48 ms

326808685_878427776773274_7075511708563866582_n.png

326808685_878427776773274_7075511708563866582_n.png

91 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

7 ms

Accessibility Review

niwablo.jp accessibility score

53

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

niwablo.jp SEO score

58

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

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

niwablo.jp

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