7.2 sec in total
658 ms
6.4 sec
173 ms
Welcome to irec.com.au homepage info - get ready to check Irec best content right away, or after learning these important things about irec.com.au
Most people only sell their home once or twice in their lifetime, they are not expected to know the tricks that agents use. But we do, and will happily share.
Visit irec.com.auWe analyzed Irec.com.au page load time and found that the first response time was 658 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
irec.com.au performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.2 s
24/100
25%
Value9.7 s
10/100
10%
Value1,280 ms
18/100
30%
Value0.697
7/100
15%
Value15.7 s
6/100
10%
658 ms
905 ms
1339 ms
65 ms
38 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 53% of them (34 requests) were addressed to the original Irec.com.au, 20% (13 requests) were made to Embed.tawk.to and 11% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Irec.com.au.
Page size can be reduced by 98.4 kB (7%)
1.4 MB
1.3 MB
In fact, the total size of Irec.com.au main page is 1.4 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. 55% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 52.4 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 7.5 kB, which is 12% 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 52.4 kB or 87% of the original size.
Potential reduce by 14.5 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. Irec images are well optimized though.
Potential reduce by 28.6 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 28.6 kB or 11% of the original size.
Potential reduce by 2.9 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. Irec.com.au has all CSS files already compressed.
Number of requests can be reduced by 39 (75%)
52
13
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Irec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
irec.com.au
658 ms
irec.com.au
905 ms
www.irec.com.au
1339 ms
gtm.js
65 ms
css
38 ms
css
55 ms
bootstrap.min.css
441 ms
font-awesome.css
659 ms
pe-icon-7-stroke.css
656 ms
animate.min.css
662 ms
flexslider.css
658 ms
styles-arec.css
679 ms
styles.css
677 ms
helpers.css
878 ms
style.css
882 ms
js
124 ms
js
124 ms
counter.js
36 ms
jquery-1.12.3.min.js
1317 ms
bootstrap.min.js
884 ms
bootstrap-hover-dropdown.min.js
901 ms
jquery.inview.min.js
915 ms
isMobile.min.js
1100 ms
back-to-top.js
1101 ms
jquery.placeholder.js
1109 ms
wowslider.js
1129 ms
script.js
1126 ms
main.js
1378 ms
css
21 ms
fbevents.js
131 ms
logo.jpg
466 ms
slider1.jpg
1542 ms
slider2.jpg
2432 ms
slider3.jpg
2005 ms
bullet.png
624 ms
slider1.jpg
622 ms
slider2.jpg
625 ms
slider3.jpg
841 ms
S6uyw4BMUTPHjx4wWw.ttf
60 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
69 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
78 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
74 ms
Pe-icon-7-stroke.woff
1163 ms
fontawesome-webfont.woff
1604 ms
t.php
126 ms
arrows.png
602 ms
S6u8w4BMUTPHjxsAXC-v.ttf
10 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
9 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf
10 ms
pause.png
819 ms
default
171 ms
widget.js
18 ms
twk-arr-find-polyfill.js
63 ms
twk-object-values-polyfill.js
74 ms
twk-event-polyfill.js
68 ms
twk-entries-polyfill.js
82 ms
twk-iterator-polyfill.js
69 ms
twk-promise-polyfill.js
70 ms
twk-main.js
82 ms
twk-vendor.js
92 ms
twk-chunk-vendors.js
84 ms
twk-chunk-common.js
90 ms
twk-runtime.js
90 ms
twk-app.js
91 ms
irec.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
irec.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
Browser errors were logged to the console
Page has valid source maps
irec.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 Irec.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 Irec.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.
irec.com.au
Open Graph description is not detected on the main page of Irec. 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: