Tools & Wizards About Us
why-bonsai.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

why-bonsai.com

Bonsai Tree Information: General Information about Bonsai Trees

Page Load Speed

3.9 sec in total

First Response

369 ms

Resources Loaded

3.3 sec

Page Rendered

243 ms

why-bonsai.com screenshot

About Website

Visit why-bonsai.com now to see the best up-to-date Why Bonsai content and also check out these interesting facts you probably never knew about why-bonsai.com

Bonsai Tree Information: Bonsai trees are often thought to have originated from Japan, but records over 2,000 years old show trees being grown in China, as part of landscapes planted in shallow contai...

Visit why-bonsai.com

Key Findings

We analyzed Why-bonsai.com page load time and found that the first response time was 369 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

why-bonsai.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

why-bonsai.com

369 ms

styles2.css

267 ms

css

54 ms

plusone.js

31 ms

brand

24 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original Why-bonsai.com, 17% (19 requests) were made to Cm.g.doubleclick.net and 15% (16 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.0 kB (8%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Why-bonsai.com main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 936.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.9 kB

  • Original 44.4 kB
  • After minification 43.6 kB
  • After compression 10.5 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 33.9 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 5.4 kB

  • Original 158.3 kB
  • After minification 152.9 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. Why Bonsai images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 46.4 kB

  • Original 936.5 kB
  • After minification 936.5 kB
  • After compression 890.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. This website has mostly compressed JavaScripts.

CSS Optimization

-57%

Potential reduce by 12.2 kB

  • Original 21.5 kB
  • After minification 19.7 kB
  • After compression 9.3 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. Why-bonsai.com needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (74%)

Requests Now

92

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

why-bonsai.com

why-bonsai.com

369 ms

styles2.css

styles2.css

267 ms

css

css

54 ms

plusone.js

plusone.js

31 ms

brand

brand

24 ms

show_ads.js

show_ads.js

35 ms

brandjs.js

brandjs.js

31 ms

addthis_widget.js

addthis_widget.js

38 ms

dc95c816512ad95ca56da69b76d68dc0.js

dc95c816512ad95ca56da69b76d68dc0.js

220 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

48 ms

cse.js

cse.js

26 ms

rentalcars_banner.jpg

rentalcars_banner.jpg

226 ms

gprofile_button-16.png

gprofile_button-16.png

34 ms

header-container-bg2.png

header-container-bg2.png

104 ms

bonsai_logo.jpg

bonsai_logo.jpg

272 ms

sprite-icons.png

sprite-icons.png

211 ms

google-search-btn.png

google-search-btn.png

210 ms

bonsai_garden7.jpg

bonsai_garden7.jpg

209 ms

bonsai_garden_aerial2.jpg

bonsai_garden_aerial2.jpg

292 ms

copyscape.gif

copyscape.gif

211 ms

cse.js

cse.js

116 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

55 ms

adsbygoogle.js

adsbygoogle.js

106 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

34 ms

footer-title-bg.png

footer-title-bg.png

221 ms

sprite-icons.png

sprite-icons.png

211 ms

jquery.min.js

jquery.min.js

15 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

12 ms

fastbutton

fastbutton

31 ms

postmessageRelay

postmessageRelay

144 ms

cse_element__en.js

cse_element__en.js

94 ms

default+en.css

default+en.css

131 ms

default.css

default.css

135 ms

show_ads_impl.js

show_ads_impl.js

118 ms

developers.google.com

developers.google.com

308 ms

2254111616-postmessagerelay.js

2254111616-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

10 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

zrt_lookup.html

zrt_lookup.html

30 ms

ads

ads

37 ms

ads

ads

673 ms

ads

ads

522 ms

ads

ads

36 ms

ads

ads

647 ms

ads

ads

1400 ms

ads

ads

2187 ms

5108237886230795125

5108237886230795125

27 ms

load_preloaded_resource.js

load_preloaded_resource.js

24 ms

icon.png

icon.png

20 ms

abg_lite.js

abg_lite.js

115 ms

window_focus.js

window_focus.js

22 ms

qs_click_protection.js

qs_click_protection.js

23 ms

ufs_web_display.js

ufs_web_display.js

28 ms

d942f9c06b5c8b2a7b10e2aa64f849f5.js

d942f9c06b5c8b2a7b10e2aa64f849f5.js

16 ms

pixel

pixel

145 ms

dv3.js

dv3.js

145 ms

gen_204

gen_204

183 ms

66ae89f2617258e0764c7688d2bf0f7c.js

66ae89f2617258e0764c7688d2bf0f7c.js

10 ms

3be5b51930de5c19fd903926958d1ee0.js

3be5b51930de5c19fd903926958d1ee0.js

15 ms

e3946b124bfe764ee0f4582cc669ca1d.js

e3946b124bfe764ee0f4582cc669ca1d.js

12 ms

s

s

115 ms

cookie_push_onload.html

cookie_push_onload.html

116 ms

ad

ad

73 ms

activeview

activeview

152 ms

css

css

190 ms

dUj1dtArZQhaInfp_nVTk_t6yOisSU7Ftkha2fMerB4.js

dUj1dtArZQhaInfp_nVTk_t6yOisSU7Ftkha2fMerB4.js

40 ms

abg_lite.js

abg_lite.js

116 ms

Q12zgMmT.js

Q12zgMmT.js

108 ms

115 ms

rum

rum

83 ms

62bHydCX.html

62bHydCX.html

19 ms

pixel

pixel

44 ms

pixel

pixel

46 ms

pixel

pixel

37 ms

bounce

bounce

25 ms

pixel

pixel

36 ms

WqYGM8XWxxfYfqmbFHwiDdyBvPFKrTTEqLcuhhrG-xI.js

WqYGM8XWxxfYfqmbFHwiDdyBvPFKrTTEqLcuhhrG-xI.js

22 ms

activeview

activeview

84 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

49 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

50 ms

rum

rum

35 ms

pixel

pixel

36 ms

ftUtils.js

ftUtils.js

70 ms

pixel

pixel

23 ms

pixel

pixel

20 ms

activeview

activeview

79 ms

pixel

pixel

21 ms

gen_204

gen_204

90 ms

pixel

pixel

84 ms

dvbm.js

dvbm.js

149 ms

14526946617626482637

14526946617626482637

124 ms

omrhp.js

omrhp.js

72 ms

aplus.js

aplus.js

124 ms

pixel

pixel

50 ms

pixel

pixel

51 ms

rum

rum

50 ms

setuid

setuid

48 ms

pixel

pixel

46 ms

pixel

pixel

46 ms

activeview

activeview

87 ms

pixel

pixel

26 ms

pixel

pixel

32 ms

rum

rum

32 ms

pixel

pixel

32 ms

pixel

pixel

32 ms

pixel

pixel

27 ms

pixel

pixel

29 ms

pixel

pixel

23 ms

Accessibility Review

why-bonsai.com accessibility score

69

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

why-bonsai.com best practices score

67

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

why-bonsai.com SEO score

62

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Why-bonsai.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Why-bonsai.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

why-bonsai.com

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