Tools & Wizards About Us
yardener.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

yardener.com

Home Page

Page Load Speed

5.1 sec in total

First Response

31 ms

Resources Loaded

4.8 sec

Page Rendered

276 ms

yardener.com screenshot

About Website

Visit yardener.com now to see the best up-to-date Yardener content for United States and also check out these interesting facts you probably never knew about yardener.com

Need help with Yardening? Access 3000+ pages of gardening, lawn care, and plant care tips to solve any problem and keep your yard healthy.: Yardener.com

Visit yardener.com

Key Findings

We analyzed Yardener.com page load time and found that the first response time was 31 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

yardener.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

48/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value4,140 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.25

49/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

Network Requests Diagram

yardener.com

31 ms

yardener.com

271 ms

gardening.yardener.com

457 ms

yardener2.css

306 ms

jquery-2.2.4.min.js

75 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Yardener.com, 16% (18 requests) were made to Cm.g.doubleclick.net and 11% (13 requests) were made to Gardening.yardener.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.8 kB (12%)

Content Size

1.1 MB

After Optimization

974.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yardener.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 705.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 122.1 kB

  • Original 153.5 kB
  • After minification 149.5 kB
  • After compression 31.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. 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 122.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 5.1 kB

  • Original 185.3 kB
  • After minification 180.2 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. Yardener images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

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

CSS Optimization

-2%

Potential reduce by 985 B

  • Original 62.0 kB
  • After minification 62.0 kB
  • After compression 61.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. Yardener.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (65%)

Requests Now

92

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yardener.com

yardener.com

31 ms

yardener.com

yardener.com

271 ms

gardening.yardener.com

gardening.yardener.com

457 ms

yardener2.css

yardener2.css

306 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

75 ms

jquery-ui.min.js

jquery-ui.min.js

80 ms

all.min.css

all.min.css

42 ms

brands.min.css

brands.min.css

53 ms

adsbygoogle.js

adsbygoogle.js

119 ms

js

js

50 ms

yardener2.png

yardener2.png

103 ms

facebook_32.png

facebook_32.png

102 ms

pinterest_32.png

pinterest_32.png

278 ms

twitter_32.png

twitter_32.png

359 ms

instagram_32.png

instagram_32.png

360 ms

linkedin_32.png

linkedin_32.png

358 ms

amazon_logo_100w.png

amazon_logo_100w.png

196 ms

shades_smile.gif

shades_smile.gif

202 ms

__2.jpeg

__2.jpeg

554 ms

copyscape.gif

copyscape.gif

305 ms

videoseries

videoseries

1181 ms

fa-brands-400.ttf

fa-brands-400.ttf

72 ms

bullet.svg

bullet.svg

372 ms

show_ads_impl.js

show_ads_impl.js

262 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

26 ms

collect

collect

42 ms

zrt_lookup.html

zrt_lookup.html

42 ms

ads

ads

821 ms

ads

ads

811 ms

ads

ads

789 ms

www-player.css

www-player.css

13 ms

www-embed-player.js

www-embed-player.js

27 ms

base.js

base.js

51 ms

ad_status.js

ad_status.js

203 ms

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js

245 ms

embed.js

embed.js

92 ms

BWRLbov4IxF5tTEtyFKhXa0z4kgn7YX1QHqnv3f8KGOXT86H1qCxnT-i4Tqu8Tjs-hK9dOzXHJ4=s68-c-k-c0x00ffffff-no-rj

BWRLbov4IxF5tTEtyFKhXa0z4kgn7YX1QHqnv3f8KGOXT86H1qCxnT-i4Tqu8Tjs-hK9dOzXHJ4=s68-c-k-c0x00ffffff-no-rj

300 ms

id

id

75 ms

reactive_library.js

reactive_library.js

236 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

204 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

205 ms

ads

ads

357 ms

ads

ads

551 ms

ads

ads

522 ms

ads

ads

517 ms

Create

Create

109 ms

GenerateIT

GenerateIT

72 ms

load_preloaded_resource.js

load_preloaded_resource.js

50 ms

abg_lite.js

abg_lite.js

41 ms

s

s

32 ms

window_focus.js

window_focus.js

49 ms

qs_click_protection.js

qs_click_protection.js

54 ms

ufs_web_display.js

ufs_web_display.js

22 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

48 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

222 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

222 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

207 ms

icon.png

icon.png

35 ms

2830412805907381911

2830412805907381911

213 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

255 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

213 ms

3b0c1a1c8750041eb27603629860e89a.js

3b0c1a1c8750041eb27603629860e89a.js

217 ms

f11bfab4e3c942216447974439595ef6.js

f11bfab4e3c942216447974439595ef6.js

231 ms

css

css

378 ms

activeview

activeview

385 ms

gdn

gdn

500 ms

cookie_push_onload.html

cookie_push_onload.html

263 ms

asr

asr

1111 ms

506 ms

ecmg

ecmg

515 ms

usersync.aspx

usersync.aspx

498 ms

sync

sync

499 ms

gcm

gcm

1061 ms

usersync.aspx

usersync.aspx

494 ms

ecmg

ecmg

520 ms

498 ms

GhmJCpBREX7wgGMT0ZiWZLwlRNdtIOd5PV2NPLMoOVM.js

GhmJCpBREX7wgGMT0ZiWZLwlRNdtIOd5PV2NPLMoOVM.js

46 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff

30 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff

216 ms

activeview

activeview

413 ms

activeview

activeview

401 ms

activeview

activeview

388 ms

sodar

sodar

76 ms

pixel

pixel

28 ms

pixel

pixel

26 ms

11 ms

sync

sync

19 ms

9 ms

pixel

pixel

31 ms

pixel

pixel

32 ms

12 ms

pixel

pixel

24 ms

pixel

pixel

22 ms

google

google

7 ms

ecc

ecc

34 ms

pixel

pixel

22 ms

pixel

pixel

20 ms

pixel

pixel

30 ms

pixel

pixel

28 ms

ecc

ecc

16 ms

pixel

pixel

17 ms

pixel

pixel

18 ms

pixel

pixel

19 ms

sodar2.js

sodar2.js

6 ms

pixel

pixel

19 ms

runner.html

runner.html

9 ms

aframe

aframe

21 ms

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

9 ms

pixel

pixel

21 ms

pixel

pixel

19 ms

pixel

pixel

17 ms

log_event

log_event

20 ms

pixel

pixel

18 ms

spacer.gif

spacer.gif

131 ms

Accessibility Review

yardener.com accessibility score

81

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

Best Practices

yardener.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yardener.com SEO score

89

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yardener.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yardener.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

yardener.com

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