10.9 sec in total
1.2 sec
9.4 sec
280 ms
Visit ecases.com.au now to see the best up-to-date ECases content and also check out these interesting facts you probably never knew about ecases.com.au
Shop powered by PrestaShop
Visit ecases.com.auWe analyzed Ecases.com.au page load time and found that the first response time was 1.2 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ecases.com.au performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value8.2 s
2/100
25%
Value10.6 s
7/100
10%
Value590 ms
51/100
30%
Value0.01
100/100
15%
Value7.8 s
44/100
10%
1213 ms
23 ms
1211 ms
584 ms
577 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 79% of them (70 requests) were addressed to the original Ecases.com.au, 18% (16 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Ecases.com.au.
Page size can be reduced by 124.9 kB (16%)
794.1 kB
669.2 kB
In fact, the total size of Ecases.com.au main page is 794.1 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. 55% of websites need less resources to load. Images take 362.0 kB which makes up the majority of the site volume.
Potential reduce by 107.7 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 17.9 kB, which is 15% 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 107.7 kB or 88% of the original size.
Potential reduce by 651 B
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. ECases images are well optimized though.
Potential reduce by 5.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.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. Ecases.com.au has all CSS files already compressed.
Number of requests can be reduced by 48 (69%)
70
22
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECases. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
ecases.com.au
1213 ms
jquery.min.js
23 ms
theme.css
1211 ms
front.css
584 ms
quickmenu.css
577 ms
paypal_fo.css
578 ms
css
57 ms
font-awesome.min.css
586 ms
animations.min.css
853 ms
frontend.min.css
1150 ms
smartblogstyle.css
1167 ms
posrotatorimg.css
1182 ms
front.css
1183 ms
posthemeoptions_s_1.css
1437 ms
posfakeorder.css
1743 ms
posmegamenu_s_1.css
1727 ms
posvegamenu_s_1.css
1780 ms
possizechart.css
1758 ms
posproductcomments.css
1801 ms
front.css
2035 ms
custom.css
2323 ms
css
65 ms
global-1.css
2300 ms
4010000.css
2352 ms
5010000.css
2340 ms
6010000.css
2466 ms
core.js
2931 ms
theme.js
3176 ms
front.js
2640 ms
ps_emailsubscription.js
2632 ms
mailalerts.js
2642 ms
quickmenu.js
2707 ms
waypoints.min.js
3197 ms
jquery-numerator.min.js
3201 ms
slick.min.js
3215 ms
frontend.min.js
3267 ms
ajax-wishlist.js
3516 ms
front.js
3762 ms
front.js
3763 ms
front.js
3764 ms
front.js
3504 ms
front.js
3559 ms
front.js
3800 ms
pospopup.js
4058 ms
front.js
3782 ms
posshoppingcart.js
3493 ms
House.svg
2305 ms
FullShoppingCart.svg
2406 ms
Tools.svg
2636 ms
logo-1673316337.jpg
3686 ms
icon_cms1.png
2901 ms
icon_cms2.png
2898 ms
icon_cms3.png
2881 ms
icon_cms4.png
2992 ms
dig1_2.jpg
2934 ms
dig1_3.jpg
3746 ms
dig2_1.jpg
3770 ms
dig2_2.jpg
4006 ms
2.jpg
3497 ms
1.jpg
3598 ms
dig_logo_footer.png
3941 ms
KFOmCnqEu92Fr1Mu4mxM.woff
43 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
66 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
68 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
67 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
67 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
69 ms
roadthemes-icon.ttf
4615 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
69 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
69 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
71 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff
70 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff
72 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff
71 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff
71 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff
73 ms
fontawesome-webfont.woff
4247 ms
dig_contact_footer.png
3718 ms
app_store.png
3784 ms
google_play.png
3958 ms
payment.png
3807 ms
dig4_s2.jpg
4317 ms
dig4_s1.jpg
4335 ms
lazy-load.svg
3745 ms
House.svg
2912 ms
FullShoppingCart.svg
2466 ms
Tools.svg
3025 ms
ecases.com.au 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
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
Links do not have a discernible name
ecases.com.au 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ecases.com.au SEO score
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 Ecases.com.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 Ecases.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.
ecases.com.au
Open Graph data is detected on the main page of ECases. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: