Tools & Wizards About Us
dictionary.bloom-s.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dictionary.bloom-s.co.jp

観葉植物 図鑑｜植物管理Dictionary

Page Load Speed

6.8 sec in total

First Response

1.7 sec

Resources Loaded

4.6 sec

Page Rendered

538 ms

dictionary.bloom-s.co.jp screenshot

About Website

Welcome to dictionary.bloom-s.co.jp homepage info - get ready to check Dictionary Bloom S best content for Japan right away, or after learning these important things about dictionary.bloom-s.co.jp

観葉植物やお花、野菜、多肉植物、コニファー、食虫植物などの育て方だけでなく、現在 ガーデニングや観葉植物の生きた情報、植物の育て方などが、現在 1７,０００ページ以上から検索できます！12ケ付き、野菜＆ハーブの種まき一覧表。ガーデニング月別作業カレンダーなどもご用意しております。毎日が楽しくなる情報が満載です。｜ブルーミングスケープ

Visit dictionary.bloom-s.co.jp

Key Findings

We analyzed Dictionary.bloom-s.co.jp page load time and found that the first response time was 1.7 sec and then it took 5.1 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

dictionary.bloom-s.co.jp performance score

0

Network Requests Diagram

dictionary.bloom-s.co.jp

1657 ms

001.css

335 ms

logo_s_01.gif

708 ms

spacer.gif

551 ms

to_home_circle.gif

554 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Dictionary.bloom-s.co.jp, 79% (87 requests) were made to Bloom-s.co.jp and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Bloom-s.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.9 kB (70%)

Content Size

310.6 kB

After Optimization

94.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dictionary.bloom-s.co.jp main page is 310.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. 40% of websites need less resources to load. HTML takes 192.5 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 177.2 kB

  • Original 192.5 kB
  • After minification 159.4 kB
  • After compression 15.4 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 33.1 kB, which is 17% 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 177.2 kB or 92% of the original size.

Image Optimization

-10%

Potential reduce by 8.1 kB

  • Original 78.6 kB
  • After minification 70.6 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. Dictionary Bloom S images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 24.3 kB

  • Original 31.1 kB
  • After minification 21.6 kB
  • After compression 6.7 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 24.3 kB or 78% of the original size.

CSS Optimization

-76%

Potential reduce by 6.4 kB

  • Original 8.3 kB
  • After minification 6.3 kB
  • After compression 2.0 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. Dictionary.bloom-s.co.jp needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (47%)

Requests Now

107

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dictionary.bloom-s.co.jp

dictionary.bloom-s.co.jp

1657 ms

001.css

001.css

335 ms

logo_s_01.gif

logo_s_01.gif

708 ms

spacer.gif

spacer.gif

551 ms

to_home_circle.gif

to_home_circle.gif

554 ms

header_4menu.gif

header_4menu.gif

558 ms

basket.gif

basket.gif

570 ms

header_arrow.gif

header_arrow.gif

580 ms

logo_s_02.gif

logo_s_02.gif

745 ms

header_menu.gif

header_menu.gif

743 ms

logo_s_03.gif

logo_s_03.gif

746 ms

t_dic.gif

t_dic.gif

769 ms

go_shopping.gif

go_shopping.gif

778 ms

t-welcome.gif

t-welcome.gif

881 ms

_.gif

_.gif

915 ms

t-ik.gif

t-ik.gif

915 ms

t-k8.gif

t-k8.gif

929 ms

t-ookime0.gif

t-ookime0.gif

964 ms

t-hy0.gif

t-hy0.gif

976 ms

t-desk0.gif

t-desk0.gif

1058 ms

t-living.gif

t-living.gif

1107 ms

t-gardening.gif

t-gardening.gif

1106 ms

t-interior.gif

t-interior.gif

1108 ms

osusume-banner.gif

osusume-banner.gif

1517 ms

bar.gif

bar.gif

1171 ms

frm_g_01.gif

frm_g_01.gif

1238 ms

frm_g_02.gif

frm_g_02.gif

1303 ms

banner_s_dictio.gif

banner_s_dictio.gif

1501 ms

t_images_gardening01.jpg

t_images_gardening01.jpg

1672 ms

com_banner_dic.gif

com_banner_dic.gif

1381 ms

arrow_com.gif

arrow_com.gif

1455 ms

bs_present.gif

bs_present.gif

1715 ms

i-ybm.gif

i-ybm.gif

1581 ms

facebook.gif

facebook.gif

1603 ms

twitter.gif

twitter.gif

1699 ms

googleplus.gif

googleplus.gif

1710 ms

instagram.gif

instagram.gif

1832 ms

pinterest.gif

pinterest.gif

1715 ms

okiniiri.gif

okiniiri.gif

1347 ms

okiniiri8.gif

okiniiri8.gif

1387 ms

bg.gif

bg.gif

1364 ms

frm_g_03.gif

frm_g_03.gif

1356 ms

frm_g_04.gif

frm_g_04.gif

1537 ms

sub_t_01.gif

sub_t_01.gif

1392 ms

arrow_dic.gif

arrow_dic.gif

1379 ms

frm_org_03.gif

frm_org_03.gif

1374 ms

frm_org_04.gif

frm_org_04.gif

1379 ms

sub_t_102.gif

sub_t_102.gif

1451 ms

sub_t_17.gif

sub_t_17.gif

1498 ms

sub_t_02.gif

sub_t_02.gif

1419 ms

oyorokobi1.gif

oyorokobi1.gif

1597 ms

sub_t_03.gif

sub_t_03.gif

1440 ms

title-sirabemono.gif

title-sirabemono.gif

1423 ms

icon-green.gif

icon-green.gif

1663 ms

icon-herb.gif

icon-herb.gif

1655 ms

icon-hana.gif

icon-hana.gif

1630 ms

plusone.js

plusone.js

103 ms

button-only.gif

button-only.gif

396 ms

bookmark_button.js

bookmark_button.js

396 ms

widgets.js

widgets.js

144 ms

icon-q-a.gif

icon-q-a.gif

1599 ms

icon_hoshi.gif

icon_hoshi.gif

1438 ms

icon-q-a1.gif

icon-q-a1.gif

1760 ms

icon-osiete.gif

icon-osiete.gif

1775 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

kanyou-keiziban.gif

kanyou-keiziban.gif

1765 ms

likebox.php

likebox.php

87 ms

sub_t_04.gif

sub_t_04.gif

1529 ms

IWXAbM4pe57.css

IWXAbM4pe57.css

35 ms

QbOSWkfpDnM.css

QbOSWkfpDnM.css

42 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

40 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

61 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

36 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

39 ms

arrow_g_s.gif

arrow_g_s.gif

1528 ms

230130_196354680408483_6675756_n.jpg

230130_196354680408483_6675756_n.jpg

37 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

11 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

9 ms

calendar.gif

calendar.gif

1458 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

12 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

4 ms

216 ms

sub_t_05.gif

sub_t_05.gif

1535 ms

sqr_icon_02.gif

sqr_icon_02.gif

1545 ms

sub_t_11.gif

sub_t_11.gif

1551 ms

sub_t_06.gif

sub_t_06.gif

1496 ms

i-qr.gif

i-qr.gif

1468 ms

reset.css

reset.css

8 ms

entry-button.css

entry-button.css

9 ms

bbtn-s_v3.png

bbtn-s_v3.png

9 ms

sub_t_101.gif

sub_t_101.gif

1499 ms

title-sodatekata.gif

title-sodatekata.gif

1520 ms

icon-kensaku.gif

icon-kensaku.gif

1527 ms

title-gardening.gif

title-gardening.gif

1423 ms

kensaku1.gif

kensaku1.gif

1438 ms

yasai.gif

yasai.gif

1424 ms

sub_t_071.gif

sub_t_071.gif

1486 ms

sub_t_20.gif

sub_t_20.gif

1504 ms

sub_t_19.gif

sub_t_19.gif

1448 ms

shasinkan.gif

shasinkan.gif

1565 ms

fuusui-kanyou.gif

fuusui-kanyou.gif

1396 ms

bnr-blog.jpg

bnr-blog.jpg

1774 ms

csr.gif

csr.gif

1482 ms

bnr-ac.jpg

bnr-ac.jpg

1848 ms

banner_bloom_gift.gif

banner_bloom_gift.gif

1406 ms

yahoo.gif

yahoo.gif

1412 ms

to_home.gif

to_home.gif

1501 ms

g_line.gif

g_line.gif

1456 ms

to_top.gif

to_top.gif

1480 ms

2002_copyright.gif

2002_copyright.gif

1352 ms

SEO Factors

dictionary.bloom-s.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dictionary.bloom-s.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dictionary.bloom-s.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

dictionary.bloom-s.co.jp

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