6.9 sec in total
683 ms
6.1 sec
113 ms
Welcome to homeplay.com.au homepage info - get ready to check Homeplay best content right away, or after learning these important things about homeplay.com.au
Learn more about Adelaide based Homeplay Electronics and their consumer and custom electronics solutions for the modern home.
Visit homeplay.com.auWe analyzed Homeplay.com.au page load time and found that the first response time was 683 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
homeplay.com.au performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value14.1 s
0/100
25%
Value16.3 s
0/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
683 ms
2244 ms
217 ms
420 ms
421 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 97% of them (66 requests) were addressed to the original Homeplay.com.au, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Homeplay.com.au.
Page size can be reduced by 103.4 kB (11%)
932.3 kB
828.9 kB
In fact, the total size of Homeplay.com.au main page is 932.3 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. 50% of websites need less resources to load. Images take 604.2 kB which makes up the majority of the site volume.
Potential reduce by 27.8 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 4.6 kB, which is 13% 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 27.8 kB or 78% of the original size.
Potential reduce by 22.3 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. Homeplay images are well optimized though.
Potential reduce by 47.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 47.2 kB or 19% of the original size.
Potential reduce by 6.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. Homeplay.com.au needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 13% of the original size.
Number of requests can be reduced by 49 (77%)
64
15
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homeplay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
homeplay.com.au
683 ms
www.homeplay.com.au
2244 ms
rokbox.css
217 ms
grid-responsive.css
420 ms
master.css
421 ms
gantry-core.css
420 ms
joomla-core.css
426 ms
main-light.css
432 ms
utilities.css
428 ms
typography.css
630 ms
responsive.css
631 ms
thirdparty-k2.css
632 ms
thirdparty-k2-light.css
639 ms
template.css
637 ms
template-gecko.css
644 ms
fusionmenu.css
840 ms
rt_ximenia_responsive-custom.css
841 ms
showcase.css
841 ms
jquery.min.js
1061 ms
jquery-noconflict.js
853 ms
jquery-migrate.min.js
857 ms
caption.js
1049 ms
mootools-core.js
1475 ms
core.js
1054 ms
mootools-more.js
1502 ms
rokbox.js
1289 ms
gantry-totop.js
1266 ms
browser-engines.js
1265 ms
load-transition.js
1268 ms
fusion.js
1486 ms
mootools-mobile.js
1487 ms
rokmediaqueries.js
1487 ms
roksprocket.js
1529 ms
moofx.js
1688 ms
features.js
1688 ms
showcase.js
1686 ms
rokajaxsearch.js
1693 ms
analytics.js
58 ms
HPLogo125190.png
212 ms
search-controls.png
215 ms
quote-l.png
213 ms
quote-r.png
213 ms
ribbon-waves.png
629 ms
readon.png
215 ms
icon-home.png
441 ms
arrows.png
454 ms
bg-showcase.jpg
650 ms
home-theatre.png
687 ms
features-top-wide.png
446 ms
dark-25.png
652 ms
features-middle.png
660 ms
features-middle-r.png
663 ms
features-bottom-wide.png
837 ms
RTI%20Controls.png
1277 ms
HEOS-Multi-room.png
1278 ms
showcase-arrows.png
873 ms
showcase-page.png
873 ms
buttonlogo300.png
900 ms
footer-overlay.png
1048 ms
brands-logo-white.gif
1291 ms
fp-footer-icon1.png
1086 ms
fp-footer-icon2.png
1112 ms
fp-footer-icon3.png
1258 ms
digitalgoo40x100logo.png
1299 ms
fontawesome-webfont.woff
1288 ms
Oxygen-webfont.woff
1430 ms
collect
26 ms
totop.png
1414 ms
homeplay.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
homeplay.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
General
Impact
Issue
Detected JavaScript libraries
homeplay.com.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
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 Homeplay.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 Homeplay.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.
homeplay.com.au
Open Graph description is not detected on the main page of Homeplay. 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: