9.9 sec in total
511 ms
7.9 sec
1.5 sec
Welcome to disasterrecovery.com.au homepage info - get ready to check Disaster Recovery best content right away, or after learning these important things about disasterrecovery.com.au
Emergency water damage, fire, mould & storm restoration across Australia. IICRC-certified contractors, priority emergency response, 24/7. Lodge a claim online.
Visit disasterrecovery.com.auWe analyzed Disasterrecovery.com.au page load time and found that the first response time was 511 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
disasterrecovery.com.au performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value14.1 s
0/100
25%
Value11.9 s
4/100
10%
Value2,450 ms
5/100
30%
Value0
100/100
15%
Value22.6 s
1/100
10%
511 ms
1397 ms
75 ms
475 ms
706 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 98% of them (121 requests) were addressed to the original Disasterrecovery.com.au, 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Disasterrecovery.com.au.
Page size can be reduced by 2.5 MB (78%)
3.3 MB
715.4 kB
In fact, the total size of Disasterrecovery.com.au main page is 3.3 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. 70% of websites need less resources to load. CSS take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 321.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 321.1 kB or 88% of the original size.
Potential reduce by 8.2 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. Disaster Recovery images are well optimized though.
Potential reduce by 553.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 553.7 kB or 73% of the original size.
Potential reduce by 1.7 MB
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. Disasterrecovery.com.au needs all CSS files to be minified and compressed as it can save up to 1.7 MB or 88% of the original size.
Number of requests can be reduced by 77 (66%)
116
39
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Disaster Recovery. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
disasterrecovery.com.au
511 ms
disasterrecovery.com.au
1397 ms
js
75 ms
styles.css
475 ms
style.css
706 ms
dittyDisplays.css
707 ms
all.css
1385 ms
bundle.min.css
712 ms
learndash_quiz_front.min.css
712 ms
jquery.dropdown.min.css
721 ms
learndash_lesson_video.min.css
945 ms
style.css
1182 ms
all.min.css
1188 ms
c1fe95eb8ea8fae43f308a50d85a0138-layout-bundle.css
1183 ms
public-main.css
1202 ms
learndash.min.css
1876 ms
elementor-icons.min.css
1426 ms
frontend.min.css
1653 ms
swiper.min.css
1432 ms
e-swiper.min.css
1445 ms
post-1288.css
1623 ms
frontend.min.css
2586 ms
global.css
1903 ms
widget-heading.min.css
1689 ms
fadeInDown.min.css
1861 ms
fadeIn.min.css
1891 ms
widget-text-editor.min.css
1933 ms
widget-spacer.min.css
2101 ms
widget-video.min.css
2113 ms
widget-image-carousel.min.css
2129 ms
widget-image.min.css
2139 ms
fadeInUp.min.css
2174 ms
widget-menu-anchor.min.css
2341 ms
widget-icon-list.min.css
2355 ms
e-animation-float.min.css
2364 ms
widget-divider.min.css
2376 ms
flash.min.css
2425 ms
widget-toggle.min.css
2581 ms
js
85 ms
post-1238.css
2621 ms
post-1222.css
2146 ms
post-1221.css
1919 ms
jquery.magnificpopup.min.css
1971 ms
bootstrap-4.min.css
2351 ms
skin-660d42345a9f4.css
2122 ms
style.css
2135 ms
animate.min.css
1932 ms
fontawesome.min.css
1975 ms
solid.min.css
1890 ms
e-animation-rotate.min.css
1894 ms
frontend-gtag.min.js
1892 ms
jquery.min.js
1733 ms
jquery-migrate.min.js
1875 ms
imagesloaded.min.js
1882 ms
bundle.min.js
1882 ms
public-main.js
1712 ms
page-transitions.min.js
1706 ms
swiped-events.min.js
1838 ms
effect.min.js
1681 ms
ditty-news-ticker.js
1679 ms
elementor.js
1680 ms
jquery.ba-throttle-debounce.min.js
1668 ms
jquery.waypoints.min.js
1670 ms
6ebeb33ac6a6e49e16dfbcba92c92f17-layout-bundle.js
1778 ms
learndash.js
1671 ms
instant-page.min.js
1673 ms
jquery.magnificpopup.min.js
1675 ms
jquery.fitvids.min.js
1637 ms
bootstrap-4.min.js
1502 ms
theme.min.js
1668 ms
jquery.smartmenus.min.js
1677 ms
jquery.sticky.min.js
1676 ms
webpack-pro.runtime.min.js
1630 ms
webpack.runtime.min.js
1507 ms
frontend-modules.min.js
1761 ms
hooks.min.js
1652 ms
i18n.min.js
1667 ms
frontend.min.js
1624 ms
core.min.js
1471 ms
frontend.min.js
1490 ms
elements-handlers.min.js
1655 ms
b9666e45-87fd-4090-b525-e04379c12ea7.webp
1211 ms
YI.png
1211 ms
SC.png
1211 ms
RACQ.png
1212 ms
QBE.png
1213 ms
IAG.png
1328 ms
HD.png
1358 ms
AL.png
1369 ms
AG.png
1369 ms
Disaster-Recovery-Qld-1st-Page-Image.webp
1401 ms
Storm-Flooding-Water-Damage-Restoration-Services-300x300.webp
1442 ms
Fire-Smoke-Odour-Damage-Restoration-Services-300x300.webp
1463 ms
fa-solid-900.woff
1495 ms
fa-solid-900.woff
1538 ms
fa-solid-900.ttf
1709 ms
fa-regular-400.woff
1510 ms
fa-regular-400.ttf
1588 ms
Sewage-Sanitisation-Restoration-Services-300x300.webp
1625 ms
Residential-Multi-Living-Business-Commercial-Remediation-Services-300x300.png
1537 ms
Mould-Remediation-Services-300x300.webp
1519 ms
Crime-Scene-Clandestine-Remediation-Services-300x300.webp
1510 ms
Emergency-Response-300x300.webp
1538 ms
Insurance-Services-300x300.webp
1624 ms
Major-Loss-Services-300x300.webp
1617 ms
Content-Restoration-300x300.webp
1484 ms
Water-Storm-Damage-300x300.webp
1470 ms
Fire-Smoke-Damage-300x300.webp
1493 ms
Mould-Biohazard-Services-300x300.webp
1539 ms
Structural-Specialised-Drying-Services-300x300.webp
1619 ms
Packout-Storage-Services-300x300.webp
1485 ms
Strata-Remediation-Services-300x300.webp
1472 ms
Building-Management-Restoration-Services-300x300.webp
1460 ms
Property-Maintenance-Restoration-Services-300x300.webp
1490 ms
TESA-1.png
1513 ms
RTI.png
1590 ms
RSA.png
1365 ms
RDA.png
1372 ms
ITI.png
1376 ms
C8.png
1405 ms
AC.png
1461 ms
zoom-carsi-logo.png
1484 ms
Emergency-Disaster-Recovery-Experts.webp
1489 ms
disasterrecovery.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.
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
disasterrecovery.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
disasterrecovery.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 Disasterrecovery.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 Disasterrecovery.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.
disasterrecovery.com.au
Open Graph data is detected on the main page of Disaster Recovery. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: