7.8 sec in total
739 ms
6.8 sec
238 ms
Welcome to ezipost.net.au homepage info - get ready to check Ezipost best content right away, or after learning these important things about ezipost.net.au
Visit ezipost.net.auWe analyzed Ezipost.net.au page load time and found that the first response time was 739 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ezipost.net.au performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value12.6 s
0/100
25%
Value13.1 s
2/100
10%
Value720 ms
41/100
30%
Value0.11
87/100
15%
Value19.1 s
3/100
10%
739 ms
1426 ms
636 ms
417 ms
1081 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ezipost.net.au, 93% (40 requests) were made to Econnectplus.com.au and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Econnectplus.com.au.
Page size can be reduced by 790.1 kB (49%)
1.6 MB
821.6 kB
In fact, the total size of Ezipost.net.au main page is 1.6 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. 25% of websites need less resources to load. Javascripts take 689.9 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 30.2 kB or 78% of the original size.
Potential reduce by 16.0 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. Ezipost images are well optimized though.
Potential reduce by 482.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 482.7 kB or 70% of the original size.
Potential reduce by 261.2 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. Ezipost.net.au needs all CSS files to be minified and compressed as it can save up to 261.2 kB or 86% of the original size.
Number of requests can be reduced by 21 (51%)
41
20
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ezipost. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ezipost.net.au
739 ms
econnectplus.com.au
1426 ms
wp-emoji-release.min.js
636 ms
styles.css
417 ms
settings.css
1081 ms
font-awesome.min.css
872 ms
bootstrap.css
1526 ms
style.css
1479 ms
bootstrap-responsive.css
1037 ms
custom-responsive.css
851 ms
customizecss.css.php
1512 ms
jquery.js
1743 ms
jquery-migrate.min.js
1245 ms
jquery.themepunch.tools.min.js
1740 ms
jquery.themepunch.revolution.min.js
2075 ms
modernizr.js
1723 ms
jquery.form.min.js
1752 ms
scripts.js
1548 ms
jquery-ui.min.js
2780 ms
jquery.easing.1.3.js
1753 ms
bootstrap.min.js
2022 ms
fitvids.js
1763 ms
custom.js
2019 ms
econnect.css
1080 ms
analytics.js
8 ms
spritespurple.jpg
232 ms
brandsprite.jpg
261 ms
econnect-logo1.jpg
880 ms
econnect-home1.jpg
1840 ms
econnect-home2.jpg
1769 ms
home-subbanner-post.jpg
1808 ms
home-subbanner-digitial.jpg
2041 ms
home-subbanner-office.jpg
2589 ms
home-subbanner-logistics.jpg
1955 ms
footer-logo-post1.jpg
258 ms
footer-logo-office1.jpg
259 ms
footer-logo-digital1.jpg
440 ms
footer-logo-logistics1.jpg
476 ms
collect
13 ms
loader.gif
249 ms
bullet.png
210 ms
large_left.png
219 ms
large_right.png
214 ms
ezipost.net.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
button, link, and menuitem elements do not have accessible names.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
ezipost.net.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ezipost.net.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezipost.net.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 Ezipost.net.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.
ezipost.net.au
Open Graph description is not detected on the main page of Ezipost. 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: