9.3 sec in total
3.1 sec
5.6 sec
498 ms
Click here to check amazing Greengardenz content. Otherwise, check out these important facts you probably never knew about greengardenz.com.au
First Name Last Name Email Phone Address Suburb Post Co [...]
Visit greengardenz.com.auWe analyzed Greengardenz.com.au page load time and found that the first response time was 3.1 sec and then it took 6.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.
greengardenz.com.au performance score
3147 ms
23 ms
98 ms
116 ms
129 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 89% of them (127 requests) were addressed to the original Greengardenz.com.au, 3% (4 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Greengardenz.com.au.
Page size can be reduced by 2.1 MB (45%)
4.7 MB
2.6 MB
In fact, the total size of Greengardenz.com.au main page is 4.7 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 56.3 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 56.3 kB or 83% of the original size.
Potential reduce by 98.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. Greengardenz images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 73% of the original size.
Potential reduce by 888.4 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. Greengardenz.com.au needs all CSS files to be minified and compressed as it can save up to 888.4 kB or 86% of the original size.
Number of requests can be reduced by 111 (80%)
138
27
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greengardenz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 44 to 1 for CSS and as a result speed up the page load time.
greengardenz.com.au
3147 ms
css
23 ms
style.css
98 ms
style-Green.css
116 ms
colorbox.css
129 ms
font-awesome.css
164 ms
front.css
179 ms
font-awesome.css
194 ms
font-awesome.css
168 ms
styles.css
175 ms
styles.css
212 ms
style.css
222 ms
style.css
214 ms
jquery.prettyphoto.css
223 ms
idangerous.swiper.css
233 ms
mb.YTVPlayer.css
240 ms
timer2.css
255 ms
mb-comingsoon.css
265 ms
animate.css
273 ms
contact-ui.css
275 ms
shortcodes.css
279 ms
pbs.css
292 ms
minimalist.css
303 ms
progressbar.css
307 ms
style.css
325 ms
bbpress.css
411 ms
styles.css
372 ms
jquery-ui-1.10.3.custom.css
377 ms
contact_form_maker_frontend.css
379 ms
settings.css
427 ms
social_widget.css
415 ms
wpvi-fa4.css
435 ms
style.css
429 ms
shortcodes.css
455 ms
style.css
507 ms
uploadify.css
524 ms
jquery.fancybox-1.3.4.css
494 ms
js
59 ms
css
13 ms
page_templates.css
448 ms
colorbox.min.css
415 ms
wide-plain.css
450 ms
jquery.js
520 ms
jquery-migrate.min.js
425 ms
widgets_controller.js
402 ms
swfobject.js
406 ms
buttons_styles.css
420 ms
optin_styles.css
414 ms
flippingbook.js
474 ms
jquery.colorbox-min.js
449 ms
jquery.colorbox.js
454 ms
form_validate.js
437 ms
jquery.sideswap.js
430 ms
if_gmap_front_end.js
470 ms
cfm_main_front_end.js
468 ms
css
14 ms
jquery.themepunch.plugins.min.js
501 ms
jquery.themepunch.revolution.min.js
502 ms
jquery.cycle.all.min.js
453 ms
jquery.easing.1.3.js
455 ms
superfish.js
471 ms
jquery.color.min.js
508 ms
widget.min.js
507 ms
core.min.js
487 ms
jquery.ui.mouse.min.js
465 ms
slider.min.js
459 ms
accordion.min.js
463 ms
sortable.min.js
430 ms
datepicker.min.js
432 ms
jquery.ui.draggable.min.js
428 ms
jquery.prettyphoto.js
430 ms
idangerous.swiper.js
484 ms
swfobject.js
439 ms
jquery.metadata.js
432 ms
jquery.mb.YTPlayer.js
394 ms
timer.min.js
542 ms
jquery.mb-comingsoon.js
402 ms
shortcodes.js
440 ms
jquery.easypiechart.min.js
417 ms
chart.js
499 ms
raphael.2.1.0.min.js
499 ms
justgage.1.0.1.js
487 ms
isotope.pkgd.min.js
468 ms
pbs.min.js
460 ms
modernizr-2.6.2-respond-1.1.0.min.js
416 ms
flowplayer.min.js
423 ms
pb_main.js
415 ms
comment-reply.min.js
491 ms
editor.js
415 ms
jquery.form.min.js
451 ms
scripts.js
382 ms
effect.min.js
365 ms
effect-shake.min.js
428 ms
jquery.colorbox.1.5.9-min.js
475 ms
button.min.js
401 ms
jquery.watermark.js
440 ms
ga.js
36 ms
jquery.uploadify.js
448 ms
imscrapidmailer-system.js
404 ms
jquery.easing-1.3.pack.js
403 ms
067_diKxPmk
93 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
26 ms
jquery.fancybox-1.3.4.pack.js
412 ms
__utm.gif
18 ms
et-ptemplates-frontend.js
388 ms
wp-emoji-release.min.js
441 ms
transparent-top.png
437 ms
bg-body.jpg
565 ms
header_tile.png
432 ms
header_bg.jpg
425 ms
logo.png
632 ms
menu_separator.png
415 ms
menuitem-current.png
412 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
42 ms
base.js
66 ms
footer-widget-bg.png
402 ms
footer-bullet.png
399 ms
featured-bg.jpg
405 ms
ajax-loader.gif
383 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
103 ms
ad_status.js
95 ms
LillyPillyUnderAttack.jpg
754 ms
5NoxiousWeeds.jpg
790 ms
t5.jpg
657 ms
Slider_PoW_5.jpg
1378 ms
t4.jpg
947 ms
prevlink.png
475 ms
nextlink.png
533 ms
LillyPillyUnderAttack-72x72.jpg
579 ms
vid-bg.png
629 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
85 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
127 ms
NL_AD2.jpg
828 ms
services-bg.png
697 ms
1.jpg
755 ms
bg.jpg
723 ms
DXI1ORHCpsQm3Vp6mXoaTcDdSZkkecOE1hvV7ZHvhyU.ttf
23 ms
2.jpg
830 ms
ba.jpg
778 ms
bb.jpg
766 ms
thumb-bg.png
58 ms
activethumb.png
59 ms
greengardenz.com.au SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greengardenz.com.au can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Greengardenz.com.au 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.
greengardenz.com.au
Open Graph data is detected on the main page of Greengardenz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: