Tools & Wizards About Us
wchm.org.au screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wchm.org.au

Home - Women's Centre for Health Matters, Canberra

Page Load Speed

10.5 sec in total

First Response

736 ms

Resources Loaded

9.6 sec

Page Rendered

76 ms

wchm.org.au screenshot

About Website

Visit wchm.org.au now to see the best up-to-date Wchm content and also check out these interesting facts you probably never knew about wchm.org.au

Health Promotion, Social Research, Community Development, Capacity Building, Information Provision and Education and Advocacy, ACT Canberra and region women

Visit wchm.org.au

Key Findings

We analyzed Wchm.org.au page load time and found that the first response time was 736 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

wchm.org.au performance score

0

Network Requests Diagram

wchm.org.au

736 ms

www.wchm.org.au

2720 ms

css

49 ms

grid.css

696 ms

base.css

952 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 96% of them (111 requests) were addressed to the original Wchm.org.au, 3% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Wchm.org.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 983.6 kB (77%)

Content Size

1.3 MB

After Optimization

301.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wchm.org.au main page is 1.3 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. 45% of websites need less resources to load. CSS take 604.3 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 156.1 kB

  • Original 181.1 kB
  • After minification 180.3 kB
  • After compression 25.0 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 156.1 kB or 86% of the original size.

Image Optimization

-23%

Potential reduce by 15.0 kB

  • Original 65.7 kB
  • After minification 50.7 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. Obviously, Wchm needs image optimization as it can save up to 15.0 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 308.9 kB

  • Original 433.8 kB
  • After minification 347.3 kB
  • After compression 124.9 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 308.9 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 503.6 kB

  • Original 604.3 kB
  • After minification 503.4 kB
  • After compression 100.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. Wchm.org.au needs all CSS files to be minified and compressed as it can save up to 503.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 107 (97%)

Requests Now

110

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wchm.org.au

wchm.org.au

736 ms

www.wchm.org.au

www.wchm.org.au

2720 ms

css

css

49 ms

grid.css

grid.css

696 ms

base.css

base.css

952 ms

layout.css

layout.css

1183 ms

audio-player.css

audio-player.css

723 ms

blog.css

blog.css

952 ms

postslider.css

postslider.css

925 ms

buttons.css

buttons.css

954 ms

buttonrow.css

buttonrow.css

1156 ms

buttons_fullwidth.css

buttons_fullwidth.css

1176 ms

catalogue.css

catalogue.css

1183 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1319 ms

comments.css

comments.css

1164 ms

contact.css

contact.css

1187 ms

slideshow.css

slideshow.css

1190 ms

contentslider.css

contentslider.css

1188 ms

countdown.css

countdown.css

1384 ms

gallery.css

gallery.css

1391 ms

gallery_horizontal.css

gallery_horizontal.css

1416 ms

google_maps.css

google_maps.css

1417 ms

grid_row.css

grid_row.css

1417 ms

heading.css

heading.css

1417 ms

headline_rotator.css

headline_rotator.css

1613 ms

hr.css

hr.css

1621 ms

icon.css

icon.css

1644 ms

iconbox.css

iconbox.css

1644 ms

icongrid.css

icongrid.css

1644 ms

iconlist.css

iconlist.css

1646 ms

image.css

image.css

1841 ms

image_hotspots.css

image_hotspots.css

1848 ms

magazine.css

magazine.css

1872 ms

masonry_entries.css

masonry_entries.css

1874 ms

avia-snippet-site-preloader.css

avia-snippet-site-preloader.css

1872 ms

menu.css

menu.css

1874 ms

notification.css

notification.css

2070 ms

numbers.css

numbers.css

2076 ms

portfolio.css

portfolio.css

1639 ms

post_metadata.css

post_metadata.css

1614 ms

progressbar.css

progressbar.css

1420 ms

promobox.css

promobox.css

1412 ms

search.css

search.css

1581 ms

slideshow_accordion.css

slideshow_accordion.css

1586 ms

slideshow_feature_image.css

slideshow_feature_image.css

1610 ms

slideshow_fullsize.css

slideshow_fullsize.css

1412 ms

slideshow_fullscreen.css

slideshow_fullscreen.css

1385 ms

slideshow_layerslider.css

slideshow_layerslider.css

1380 ms

social_share.css

social_share.css

1574 ms

tab_section.css

tab_section.css

1384 ms

table.css

table.css

1383 ms

tabs.css

tabs.css

1384 ms

team.css

team.css

1385 ms

testimonials.css

testimonials.css

1382 ms

timeline.css

timeline.css

1614 ms

toggles.css

toggles.css

1383 ms

video.css

video.css

1383 ms

style.min.css

style.min.css

1615 ms

shortcodes.css

shortcodes.css

1383 ms

magnific-popup.css

magnific-popup.css

1385 ms

avia-snippet-lightbox.css

avia-snippet-lightbox.css

1392 ms

avia-snippet-widget.css

avia-snippet-widget.css

1407 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

1392 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1389 ms

custom.css

custom.css

1580 ms

style.css

style.css

1816 ms

post-9898.css

post-9898.css

1415 ms

jquery.min.js

jquery.min.js

1639 ms

jquery-migrate.min.js

jquery-migrate.min.js

1386 ms

avia-compat.js

avia-compat.js

1384 ms

avia.js

avia.js

1809 ms

shortcodes.js

shortcodes.js

1611 ms

audio-player.js

audio-player.js

1418 ms

contact.js

contact.js

1411 ms

slideshow.js

slideshow.js

1589 ms

countdown.js

countdown.js

1611 ms

gallery.js

gallery.js

1612 ms

gallery_horizontal.js

gallery_horizontal.js

1613 ms

headline_rotator.js

headline_rotator.js

1418 ms

icongrid.js

icongrid.js

1607 ms

iconlist.js

iconlist.js

1590 ms

image_hotspots.js

image_hotspots.js

1611 ms

magazine.js

magazine.js

1612 ms

isotope.js

isotope.js

1613 ms

masonry_entries.js

masonry_entries.js

1419 ms

menu.js

menu.js

1607 ms

notification.js

notification.js

1588 ms

numbers.js

numbers.js

1611 ms

portfolio.js

portfolio.js

1612 ms

progressbar.js

progressbar.js

1614 ms

slideshow-video.js

slideshow-video.js

1412 ms

slideshow_accordion.js

slideshow_accordion.js

1583 ms

slideshow_fullscreen.js

slideshow_fullscreen.js

1585 ms

slideshow_layerslider.js

slideshow_layerslider.js

1610 ms

tab_section.js

tab_section.js

1417 ms

tabs.js

tabs.js

1412 ms

testimonials.js

testimonials.js

1386 ms

timeline.js

timeline.js

1574 ms

toggles.js

toggles.js

1579 ms

video.js

video.js

1604 ms

avia-snippet-hamburger-menu.js

avia-snippet-hamburger-menu.js

1417 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1387 ms

avia-snippet-lightbox.js

avia-snippet-lightbox.js

1384 ms

avia-snippet-megamenu.js

avia-snippet-megamenu.js

1579 ms

responsive.css

responsive.css

1383 ms

avia-snippet-footer-effects.js

avia-snippet-footer-effects.js

1397 ms

avia-snippet-widget.js

avia-snippet-widget.js

1397 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1845 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1396 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1386 ms

whm-logo-and-slogan.png

whm-logo-and-slogan.png

461 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

22 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

25 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

29 ms

entypo-fontello.woff

entypo-fontello.woff

232 ms

analytics.js

analytics.js

32 ms

SEO Factors

wchm.org.au SEO score

0

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

Social Sharing Optimization

wchm.org.au

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