Tools & Wizards About Us
mini-garden.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mini-garden.jp

ノノモを使ってみた口コミ！効果は嘘なのか徹底検証

Page Load Speed

6.2 sec in total

First Response

1.4 sec

Resources Loaded

4.5 sec

Page Rendered

238 ms

mini-garden.jp screenshot

About Website

Welcome to mini-garden.jp homepage info - get ready to check Mini Garden best content right away, or after learning these important things about mini-garden.jp

ノノモを使ってみた口コミをお届けしています。効果が嘘なのか、悪い商品じゃないのか気になっているならぜひご覧ください。ノノモは今までの除毛クリームのデメリットをなくした画期的なアイテムです。

Visit mini-garden.jp

Key Findings

We analyzed Mini-garden.jp page load time and found that the first response time was 1.4 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mini-garden.jp performance score

0

Network Requests Diagram

mini-garden.jp

1412 ms

import.css

334 ms

lightbox.css

338 ms

css.js

524 ms

navi.js

356 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 66% of them (67 requests) were addressed to the original Mini-garden.jp, 19% (19 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mini-garden.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.5 kB (43%)

Content Size

512.6 kB

After Optimization

290.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 49.9 kB

  • Original 57.9 kB
  • After minification 37.3 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 20.7 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.9 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 19.1 kB

  • Original 255.9 kB
  • After minification 236.8 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. Mini Garden images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 102.8 kB

  • Original 137.9 kB
  • After minification 106.1 kB
  • After compression 35.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 102.8 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 50.8 kB

  • Original 60.9 kB
  • After minification 35.8 kB
  • After compression 10.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. Mini-garden.jp needs all CSS files to be minified and compressed as it can save up to 50.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (45%)

Requests Now

101

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mini-garden.jp

mini-garden.jp

1412 ms

import.css

import.css

334 ms

lightbox.css

lightbox.css

338 ms

css.js

css.js

524 ms

navi.js

navi.js

356 ms

win_op.js

win_op.js

366 ms

site.js

site.js

843 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1357 ms

ceebox.css

ceebox.css

720 ms

jquery.ceebox.js

jquery.ceebox.js

1133 ms

orbit-1.2.3.css

orbit-1.2.3.css

698 ms

jquery.orbit-1.2.3.js

jquery.orbit-1.2.3.js

1090 ms

reset.css

reset.css

534 ms

common.css

common.css

781 ms

contents.css

contents.css

1026 ms

table.css

table.css

696 ms

bloc.css

bloc.css

865 ms

bloc_alpha.css

bloc_alpha.css

933 ms

popup.css

popup.css

958 ms

print.css

print.css

982 ms

logo.jpg

logo.jpg

246 ms

headbtn1_s1.jpg

headbtn1_s1.jpg

254 ms

headbtn2_s1.jpg

headbtn2_s1.jpg

252 ms

headbtn3_s1.jpg

headbtn3_s1.jpg

257 ms

menu_bg.jpg

menu_bg.jpg

261 ms

menu1_s1.jpg

menu1_s1.jpg

244 ms

menu2_s1.jpg

menu2_s1.jpg

485 ms

menu3_s1.jpg

menu3_s1.jpg

486 ms

menu4_s1.jpg

menu4_s1.jpg

483 ms

menu5_s1.jpg

menu5_s1.jpg

483 ms

menu6_s1.jpg

menu6_s1.jpg

486 ms

loading.gif

loading.gif

484 ms

topimg_close.jpg

topimg_close.jpg

903 ms

member_s1.jpg

member_s1.jpg

661 ms

mypage.jpg

mypage.jpg

681 ms

mypage_id.jpg

mypage_id.jpg

662 ms

mypage_pass.jpg

mypage_pass.jpg

681 ms

login_s1.jpg

login_s1.jpg

651 ms

arr.png

arr.png

900 ms

cart_s1.jpg

cart_s1.jpg

904 ms

search.jpg

search.jpg

902 ms

search_btn_s1.jpg

search_btn_s1.jpg

969 ms

osusume.jpg

osusume.jpg

970 ms

resize_image.php

resize_image.php

1663 ms

resize_image.php

resize_image.php

1582 ms

resize_image.php

resize_image.php

1661 ms

resize_image.php

resize_image.php

1676 ms

resize_image.php

resize_image.php

1645 ms

resize_image.php

resize_image.php

1666 ms

resize_image.php

resize_image.php

1940 ms

resize_image.php

resize_image.php

1944 ms

news.jpg

news.jpg

1860 ms

icon01_s1.jpg

icon01_s1.jpg

1848 ms

icon02_s1.jpg

icon02_s1.jpg

1853 ms

icon03_s1.jpg

icon03_s1.jpg

2044 ms

icon04_s1.jpg

icon04_s1.jpg

1995 ms

widgets.js

widgets.js

83 ms

likebox.php

likebox.php

251 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

128 ms

icon05_s1.jpg

icon05_s1.jpg

1795 ms

icon06_s1.jpg

icon06_s1.jpg

1813 ms

icon07_s1.jpg

icon07_s1.jpg

1865 ms

icon08_s1.jpg

icon08_s1.jpg

2034 ms

icon09_s1.jpg

icon09_s1.jpg

1943 ms

icon10_s1.jpg

icon10_s1.jpg

1958 ms

syndication

syndication

301 ms

332307224577851392

332307224577851392

319 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

45 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

47 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

53 ms

Ek6lpayKeeB.css

Ek6lpayKeeB.css

54 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

66 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

85 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

64 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

62 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

62 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

102 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

107 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

127 ms

1FCa-btixu2.js

1FCa-btixu2.js

105 ms

icon11_s1.jpg

icon11_s1.jpg

1924 ms

bnr_blog2.jpg

bnr_blog2.jpg

1764 ms

bnr_mura.jpg

bnr_mura.jpg

1800 ms

osusume_bg.jpg

osusume_bg.jpg

1885 ms

news_bg.jpg

news_bg.jpg

1907 ms

1378318_587130648013407_1815497506_n.jpg

1378318_587130648013407_1815497506_n.jpg

146 ms

254898_171163379610138_8333051_n.jpg

254898_171163379610138_8333051_n.jpg

186 ms

12733532_1010130802380054_4769074167199565637_n.jpg

12733532_1010130802380054_4769074167199565637_n.jpg

260 ms

12662037_998937793499355_2857428192485835896_n.jpg

12662037_998937793499355_2857428192485835896_n.jpg

62 ms

12592203_998937800166021_7744971054545523157_n.jpg

12592203_998937800166021_7744971054545523157_n.jpg

257 ms

1916855_982400298486438_5937548513467845513_n.jpg

1916855_982400298486438_5937548513467845513_n.jpg

258 ms

12345553_972642106128924_4240963693127417645_n.jpg

12345553_972642106128924_4240963693127417645_n.jpg

94 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

24 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

22 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

18 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

24 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

30 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

213 ms

MG_logo_normal.gif

MG_logo_normal.gif

193 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

71 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

71 ms

jot

jot

25 ms

SEO Factors

mini-garden.jp SEO score

0

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 Mini-garden.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 Mini-garden.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

mini-garden.jp

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