Tools & Wizards About Us
planetagarden.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

planetagarden.com

The best resource to help you grow a beautiful garden and vegetable garden | Planetagarden

Page Load Speed

3.5 sec in total

First Response

52 ms

Resources Loaded

3.3 sec

Page Rendered

175 ms

planetagarden.com screenshot

About Website

Visit planetagarden.com now to see the best up-to-date Planetagarden content for Spain and also check out these interesting facts you probably never knew about planetagarden.com

Practical advice on growing a garden and vegetable garden. Make your garden attractive and recognizable and your garden fruitful

Visit planetagarden.com

Key Findings

We analyzed Planetagarden.com page load time and found that the first response time was 52 ms and then it took 3.4 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

planetagarden.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.377

28/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

planetagarden.com

52 ms

www.planetagarden.com

560 ms

main.min.css

16 ms

6faad5be-5832-4269-811d-f2cbd697a7eb.min.js

47 ms

plugin.min.js

44 ms

Our browser made a total of 168 requests to load all elements on the main page. We found that 40% of them (68 requests) were addressed to the original Planetagarden.com, 13% (21 requests) were made to Cm.g.doubleclick.net and 11% (19 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (801 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.8 kB (24%)

Content Size

827.7 kB

After Optimization

632.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planetagarden.com main page is 827.7 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. Javascripts take 498.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.9 kB

  • Original 64.7 kB
  • After minification 49.3 kB
  • After compression 8.8 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 15.5 kB, which is 24% 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 55.9 kB or 86% of the original size.

Image Optimization

-8%

Potential reduce by 21.0 kB

  • Original 251.5 kB
  • After minification 230.5 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. Planetagarden images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 117.0 kB

  • Original 498.7 kB
  • After minification 498.5 kB
  • After compression 381.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 117.0 kB or 23% of the original size.

CSS Optimization

-14%

Potential reduce by 1.8 kB

  • Original 12.7 kB
  • After minification 12.7 kB
  • After compression 11.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. Planetagarden.com needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 90 (76%)

Requests Now

119

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

planetagarden.com

planetagarden.com

52 ms

www.planetagarden.com

www.planetagarden.com

560 ms

main.min.css

main.min.css

16 ms

6faad5be-5832-4269-811d-f2cbd697a7eb.min.js

6faad5be-5832-4269-811d-f2cbd697a7eb.min.js

47 ms

plugin.min.js

plugin.min.js

44 ms

dr6.biz

dr6.biz

384 ms

js

js

88 ms

script.js

script.js

49 ms

adsbygoogle.js

adsbygoogle.js

231 ms

bundle.min.js

bundle.min.js

33 ms

logo.svg

logo.svg

33 ms

search.svg

search.svg

37 ms

langs.svg

langs.svg

53 ms

en.png

en.png

44 ms

cs.png

cs.png

47 ms

da.png

da.png

51 ms

de.png

de.png

52 ms

es.png

es.png

50 ms

fr.png

fr.png

51 ms

it.png

it.png

55 ms

nl.png

nl.png

57 ms

no.png

no.png

57 ms

pl.png

pl.png

58 ms

pt.png

pt.png

59 ms

ro.png

ro.png

58 ms

sv.png

sv.png

62 ms

bg.png

bg.png

62 ms

et.png

et.png

82 ms

fi.png

fi.png

61 ms

hr.png

hr.png

80 ms

hu.png

hu.png

81 ms

id.png

id.png

83 ms

lt.png

lt.png

82 ms

lv.png

lv.png

85 ms

ms.png

ms.png

84 ms

sk.png

sk.png

86 ms

sl.png

sl.png

87 ms

sr.png

sr.png

86 ms

tr.png

tr.png

88 ms

search-white.svg

search-white.svg

89 ms

1px.png

1px.png

91 ms

loader.gif

loader.gif

47 ms

logo.svg

logo.svg

21 ms

logo.svg

logo.svg

11 ms

search.svg

search.svg

56 ms

en.png

en.png

12 ms

cs.png

cs.png

13 ms

es.png

es.png

31 ms

fr.png

fr.png

41 ms

da.png

da.png

31 ms

langs.svg

langs.svg

32 ms

de.png

de.png

34 ms

it.png

it.png

33 ms

no.png

no.png

31 ms

nl.png

nl.png

35 ms

pl.png

pl.png

34 ms

ro.png

ro.png

36 ms

pt.png

pt.png

35 ms

fi.png

fi.png

33 ms

bg.png

bg.png

33 ms

sv.png

sv.png

33 ms

hr.png

hr.png

16 ms

hu.png

hu.png

13 ms

et.png

et.png

14 ms

lt.png

lt.png

15 ms

id.png

id.png

14 ms

ms.png

ms.png

18 ms

lv.png

lv.png

16 ms

sk.png

sk.png

15 ms

sr.png

sr.png

19 ms

sl.png

sl.png

24 ms

tr.png

tr.png

17 ms

search-white.svg

search-white.svg

25 ms

1px.png

1px.png

19 ms

slotcar_library.js

slotcar_library.js

163 ms

show_ads_impl.js

show_ads_impl.js

509 ms

event

event

356 ms

zrt_lookup.html

zrt_lookup.html

30 ms

ads

ads

493 ms

sodar

sodar

87 ms

ads

ads

574 ms

sodar2.js

sodar2.js

19 ms

runner.html

runner.html

17 ms

aframe

aframe

41 ms

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

3 ms

event

event

363 ms

reactive_library.js

reactive_library.js

224 ms

ads

ads

195 ms

ads

ads

389 ms

ads

ads

801 ms

ads

ads

270 ms

ads

ads

385 ms

444604e78ca73015217834c7b910356d.js

444604e78ca73015217834c7b910356d.js

18 ms

load_preloaded_resource.js

load_preloaded_resource.js

5 ms

29320645bc6a56198d70d58933af2b82.js

29320645bc6a56198d70d58933af2b82.js

26 ms

abg_lite.js

abg_lite.js

10 ms

window_focus.js

window_focus.js

14 ms

qs_click_protection.js

qs_click_protection.js

12 ms

ufs_web_display.js

ufs_web_display.js

10 ms

f664811c17e0f3afcb66ee2be6c8df63.js

f664811c17e0f3afcb66ee2be6c8df63.js

110 ms

icon.png

icon.png

107 ms

s

s

90 ms

css

css

59 ms

pixel

pixel

92 ms

14993930231633649722

14993930231633649722

89 ms

abg_lite.js

abg_lite.js

48 ms

omrhp.js

omrhp.js

49 ms

Q12zgMmT.js

Q12zgMmT.js

46 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

34 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

34 ms

gen_204

gen_204

89 ms

pixel

pixel

67 ms

dv3.js

dv3.js

248 ms

62bHydCX.html

62bHydCX.html

22 ms

gen_204

gen_204

62 ms

pixel

pixel

53 ms

pixel

pixel

52 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

29 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

35 ms

XCSEbScD2TvrcCbmOAwzw3FcKGiduMdvSHMNJDgnGcc.js

XCSEbScD2TvrcCbmOAwzw3FcKGiduMdvSHMNJDgnGcc.js

209 ms

activeview

activeview

124 ms

Y16-9k_leQJvG3Q5vrkxkKUWjGmjQjFi00_HgyssuhY.js

Y16-9k_leQJvG3Q5vrkxkKUWjGmjQjFi00_HgyssuhY.js

46 ms

rum

rum

50 ms

bounce

bounce

72 ms

871e6652be53811fc75f968251dcc8ef.js

871e6652be53811fc75f968251dcc8ef.js

4 ms

2bbefa48e780f0171741373010dbd4b2.js

2bbefa48e780f0171741373010dbd4b2.js

63 ms

pixel

pixel

66 ms

cookie_push_onload.html

cookie_push_onload.html

52 ms

rum

rum

34 ms

google

google

3 ms

pixel

pixel

21 ms

pixel

pixel

19 ms

ad

ad

66 ms

pixel

pixel

44 ms

68 ms

pixel

pixel

28 ms

activeview

activeview

112 ms

pixel

pixel

29 ms

pixel

pixel

28 ms

skeleton.js

skeleton.js

104 ms

9727625667498121184

9727625667498121184

69 ms

pixel

pixel

35 ms

activeview

activeview

69 ms

pixel

pixel

115 ms

gen_204

gen_204

98 ms

13502298465569212781

13502298465569212781

64 ms

google

google

36 ms

cookiesync

cookiesync

101 ms

150 ms

activeview

activeview

93 ms

pixel

pixel

47 ms

pixel

pixel

33 ms

pixel

pixel

33 ms

pixel

pixel

40 ms

setuid

setuid

71 ms

rum

rum

43 ms

pixel

pixel

22 ms

pixel

pixel

21 ms

pixel

pixel

21 ms

pixel

pixel

32 ms

rum

rum

19 ms

report

report

6 ms

CookieSyncRedirect

CookieSyncRedirect

41 ms

23 ms

pixel

pixel

13 ms

generic

generic

4 ms

pixel

pixel

14 ms

pixel

pixel

28 ms

Accessibility Review

planetagarden.com accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

planetagarden.com 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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

planetagarden.com SEO score

98

Search Engine Optimization Advices

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

planetagarden.com

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