9.5 sec in total
406 ms
8.9 sec
206 ms
Click here to check amazing Greens content for Australia. Otherwise, check out these important facts you probably never knew about greens.org.au
The Greens are fighting for your future. Together we can tackle the climate crisis, the housing crisis and economic inequality, and create a better life for all. We're fighting for a future for a...
Visit greens.org.auWe analyzed Greens.org.au page load time and found that the first response time was 406 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
greens.org.au performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value11.5 s
0/100
25%
Value12.9 s
2/100
10%
Value350 ms
73/100
30%
Value0.015
100/100
15%
Value11.9 s
17/100
10%
406 ms
1047 ms
388 ms
585 ms
594 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 98% of them (170 requests) were addressed to the original Greens.org.au, 1% (2 requests) were made to Cdn.jsdelivr.net and 1% (1 request) were made to Nimblebird.co. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Greens.org.au.
Page size can be reduced by 120.7 kB (12%)
997.0 kB
876.4 kB
In fact, the total size of Greens.org.au main page is 997.0 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. Images take 703.6 kB which makes up the majority of the site volume.
Potential reduce by 63.9 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 9.5 kB, which is 12% 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 63.9 kB or 83% of the original size.
Potential reduce by 17.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. Greens images are well optimized though.
Potential reduce by 23.4 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 23.4 kB or 18% of the original size.
Potential reduce by 15.8 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. Greens.org.au needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 18% of the original size.
Number of requests can be reduced by 153 (95%)
161
8
The browser has sent 161 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 83 to 1 for CSS and as a result speed up the page load time.
greens.org.au
406 ms
greens.org.au
1047 ms
ajax-progress.module.css
388 ms
align.module.css
585 ms
autocomplete-loading.module.css
594 ms
fieldgroup.module.css
782 ms
container-inline.module.css
790 ms
clearfix.module.css
876 ms
details.module.css
895 ms
hidden.module.css
917 ms
item-list.module.css
977 ms
js.module.css
987 ms
nowrap.module.css
1023 ms
position-container.module.css
1072 ms
progress.module.css
1092 ms
reset-appearance.module.css
1116 ms
resize.module.css
1174 ms
sticky-header.module.css
1185 ms
system-status-counter.css
1220 ms
system-status-report-counters.css
1269 ms
system-status-report-general-info.css
1287 ms
tabledrag.module.css
1314 ms
tablesort.module.css
1372 ms
tree-child.module.css
1385 ms
webform.form.css
1416 ms
webform.element.details.toggle.css
1464 ms
webform.element.message.css
1484 ms
blazy.css
1513 ms
blazy.loading.css
1568 ms
blazy.filter.css
1581 ms
blazy.ratio.css
1614 ms
eu_cookie_compliance.css
1661 ms
accordion.frontend.css
1681 ms
paragraphs.unpublished.css
1714 ms
webform.theme.classy.css
1764 ms
webform.ajax.css
1779 ms
global.css
2011 ms
ls.unveilhooks.min.js
43 ms
superfish.min.js
60 ms
layout.css
1673 ms
action-links.css
1497 ms
breadcrumb.css
1333 ms
collapse-processed.css
1375 ms
container-inline.css
1202 ms
details.css
1271 ms
exposed-filters.css
1206 ms
field.css
1222 ms
icons.css
1247 ms
inline-form.css
1202 ms
item-list.css
1227 ms
link.css
1235 ms
links.css
1205 ms
menu.css
1224 ms
more-link.css
1245 ms
pager.css
1203 ms
tabledrag.css
1226 ms
tableselect.css
1234 ms
tablesort.css
1216 ms
tabs.css
1229 ms
textarea.css
1243 ms
ui-dialog.css
1202 ms
messages.css
1223 ms
progress.css
1234 ms
node.css
1216 ms
cookie-footer.css
1229 ms
page-footer.css
1241 ms
crm-form.css
1202 ms
more-link.css
1224 ms
alt-box.css
1233 ms
box.css
1215 ms
action-box.css
1233 ms
page-section.css
1236 ms
call-to-action.css
1203 ms
hero-image.css
1223 ms
hero-image-with-sidebar.css
1185 ms
nav-small.css
1196 ms
nav-cta.css
1200 ms
page-header-small.css
1184 ms
nav-drop-down.css
1188 ms
page-header.css
1182 ms
utility-classes.css
1384 ms
alert_strap_footer-0e0e6f7fb1801842202e72f4d4b250a2.css
1197 ms
google_optimize_content_flicker-eec399f160c4c9b3bfb2eebc10da2867.css
1202 ms
manifesto_tweaks-0e5877937fbf2122e0026ad289a8ced3.css
1184 ms
real_big_buttons-17d7b39e18b487c675d68bbb109ef973.css
1188 ms
video_embed_fix-bdbb68ed2af7249c5e7aa3dfbd7f99f7.css
1190 ms
zoomify-002fcf51ad8791d6157daa334dd7efbf.css
1219 ms
jquery.min.js
1437 ms
element.matches.js
1230 ms
once.min.js
1204 ms
drupalSettingsLoader.js
1224 ms
drupal.js
1230 ms
drupal.init.js
1219 ms
autopilot_tracking-4ad082001cd69dec6740bfd06008ef81.js
1259 ms
google_optimize_content_flicker-cdd2e16f3ab592fdcb6a23ee1a05c93b.js
1248 ms
high_contrast_mode-f9cce5fb73ed51975d74385904aebff1.js
1241 ms
newsletter_signup_ga_event_trigger-68aeadf666f5d1d95b4bea3afcf5d21e.js
1265 ms
facebook_pixel.js
1261 ms
blazy.polyfill.min.js
1309 ms
nodelist.foreach.js
1280 ms
object.assign.js
1249 ms
css.escape.js
1245 ms
es6-promise.auto.min.js
1265 ms
blazy.classlist.min.js
1261 ms
blazy.promise.min.js
1266 ms
blazy.raf.min.js
1257 ms
jquery.once.min.js
1244 ms
debounce.js
1252 ms
dblazy.min.js
1265 ms
blazy.once.min.js
1267 ms
blazy.sanitizer.min.js
1267 ms
blazy.dom.min.js
1256 ms
blazy.base.min.js
1244 ms
blazy.dataset.min.js
1252 ms
blazy.viewport.min.js
1263 ms
blazy.xlazy.min.js
1267 ms
blazy.observer.min.js
1236 ms
blazy.loading.min.js
1216 ms
blazy.webp.min.js
1209 ms
blazy.min.js
1235 ms
bio.min.js
1227 ms
bio.media.min.js
1221 ms
blazy.drupal.min.js
1233 ms
blazy.filter.min.js
1184 ms
blazy.load.min.js
1189 ms
blazy.compat.min.js
1199 ms
index.umd.min.js
1186 ms
js.cookie.min.js
1194 ms
eu_cookie_compliance.min.js
1190 ms
gtm.js
1183 ms
gtag.js
1189 ms
progress.js
1198 ms
jquery.once.bc.js
1185 ms
loadjs.min.js
1105 ms
ajax.js
1155 ms
ajax.js
1161 ms
gtag.ajax.js
1189 ms
accordion.frontend.min.js
1196 ms
form.js
1184 ms
webform.behaviors.js
1194 ms
states.js
1201 ms
webform.states.js
1183 ms
webform.form.js
1189 ms
webform.element.details.save.js
1189 ms
announce.js
1183 ms
webform.element.details.toggle.js
1188 ms
webform.element.message.js
1202 ms
federal_election_call_to_action
1196 ms
webform.scroll.js
1190 ms
webform.ajax.js
1191 ms
jquery.form.min.js
1185 ms
hero-image-with-sidebar.js
1186 ms
nav-small.js
1200 ms
page-header-small.js
1195 ms
nav-drop-down.js
1190 ms
page-header.js
1188 ms
nunito-sans-v12-latin-regular.woff
1202 ms
nunito-sans-v12-latin-600.woff
1383 ms
nunito-sans-v12-latin-700.woff
1198 ms
nunito-sans-v12-latin-800.woff
1201 ms
fa-solid-900.ttf
2755 ms
fa-regular-400.ttf
1384 ms
roboto-condensed-v25-latin-700.woff
1185 ms
roboto-condensed-v25-latin-regular.woff
1247 ms
anton-v23-latin-regular.woff
1209 ms
fa-brands-400.ttf
1875 ms
logo.svg
1299 ms
2021_mosaic__v_april_2024_v2.jpg
1907 ms
mar2024-tax-handouts-thumb.jpg
1304 ms
Untitled%20design%20%283%29.png
1718 ms
vic--platform--first-nations-justice.jpg
1534 ms
no-more-coal-gas-speech-bubble.png
874 ms
95b0245a891b4004849e7fef8c7730810477d4d77493456f8ca6c5a01033d485
160 ms
greens.org.au accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
greens.org.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
greens.org.au SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greens.org.au 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 Greens.org.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.
greens.org.au
Open Graph description is not detected on the main page of Greens. 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: