10.8 sec in total
587 ms
9.9 sec
274 ms
Visit my.ezypay.com now to see the best up-to-date My Ezypay content for Australia and also check out these interesting facts you probably never knew about my.ezypay.com
Ezypay makes it easy for Australian businesses to take recurring direct debit payments across multiple sites, currencies and payment methods.
Visit my.ezypay.comWe analyzed My.ezypay.com page load time and found that the first response time was 587 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
my.ezypay.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value9.6 s
0/100
25%
Value20.2 s
0/100
10%
Value33,990 ms
0/100
30%
Value0.572
12/100
15%
Value61.8 s
0/100
10%
587 ms
3070 ms
184 ms
236 ms
275 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 60% of them (47 requests) were addressed to the original My.ezypay.com, 8% (6 requests) were made to Iconnect360.com and 6% (5 requests) were made to Tfaforms.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Iconnect360.com.
Page size can be reduced by 489.6 kB (50%)
975.0 kB
485.4 kB
In fact, the total size of My.ezypay.com main page is 975.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. CSS take 364.2 kB which makes up the majority of the site volume.
Potential reduce by 33.1 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 33.1 kB or 78% of the original size.
Potential reduce by 14.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. My Ezypay images are well optimized though.
Potential reduce by 127.8 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 127.8 kB or 47% of the original size.
Potential reduce by 314.1 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. My.ezypay.com needs all CSS files to be minified and compressed as it can save up to 314.1 kB or 86% of the original size.
Number of requests can be reduced by 39 (55%)
71
32
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Ezypay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
my.ezypay.com
587 ms
my.ezypay.com
3070 ms
wforms-layout.css
184 ms
default
236 ms
wforms.js
275 ms
localization-en_US.js
196 ms
styles.css
233 ms
css
85 ms
style.css
464 ms
shortcodes.css
923 ms
shortcodes_responsive.css
696 ms
thickbox.min.css
698 ms
jquery.min.js
94 ms
thickbox.min.js
1156 ms
www.iconnect360.com
4200 ms
forms2.min.js
74 ms
anti-spam-4.1.js
926 ms
jquery.form.min.js
1152 ms
scripts.js
1157 ms
comment-reply.min.js
1197 ms
jquery.fitvids.js
1381 ms
waypoints.min.js
1385 ms
jquery.magnific-popup.js
1387 ms
custom.js
1659 ms
wp-embed.min.js
1611 ms
fbstyle.css
1390 ms
wforms-jsonly.css
37 ms
analytics.js
42 ms
munchkin.js
68 ms
wp-emoji-release.min.js
1270 ms
collect
12 ms
munchkin.js
3 ms
visitWebPage
1290 ms
style.css
1852 ms
css
21 ms
css
33 ms
css
42 ms
ezypay-logo.png
359 ms
flag-malaysia.png
355 ms
flag-australia.png
407 ms
flag-newzealand.png
364 ms
flag-singapore.png
409 ms
flag-hongkong.png
407 ms
flag-philippines.png
682 ms
header-banner-1.png
1348 ms
main-1.png
1539 ms
main-2.png
966 ms
main-3.png
942 ms
awards.png
1856 ms
ctry-au.png
1162 ms
ctry-nz1.png
1446 ms
ctry-sg1.png
1241 ms
ctry-my.png
1630 ms
ctry-hk1.png
1485 ms
ctry-ph.png
1585 ms
icon-email-64x64.png
1685 ms
social-facebook.png
1714 ms
social-flicker.png
1767 ms
social-youtube.png
1822 ms
social-twitter.png
1860 ms
social-linkedin.png
1917 ms
social-rss.png
1944 ms
social-google+.png
1997 ms
flag-australia.png
255 ms
flag-newzealand.png
485 ms
flag-singapore.png
695 ms
flag-hongkong.png
697 ms
flag-philippines.png
698 ms
getForm
1306 ms
k3k702ZOKiLJc3WVjuplzI3LH2FgLjViKkqswU-xtII.ttf
102 ms
EInbV5DfGHOiMmvb1Xr-ho3LH2FgLjViKkqswU-xtII.ttf
105 ms
u-WUoqrET9fUeobQW7jkRSZ2oysoEQEeKwjgmXLRnTc.ttf
112 ms
DXI1ORHCpsQm3Vp6mXoaTY3LH2FgLjViKkqswU-xtII.ttf
114 ms
ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf
95 ms
loadingAnimation.gif
1902 ms
forms2.css
5 ms
forms2-theme-simple.css
6 ms
XDFrame
409 ms
my.ezypay.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
my.ezypay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
my.ezypay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 My.ezypay.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 My.ezypay.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.
my.ezypay.com
Open Graph description is not detected on the main page of My Ezypay. 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: