8.3 sec in total
1.9 sec
5.5 sec
856 ms
Welcome to detectaleak.com.au homepage info - get ready to check Detect A Leak best content right away, or after learning these important things about detectaleak.com.au
Scott Hogan and team can quickly locate your water leak or cable fault. In Sydney, Illawarra and the South Coast, we use specialist equipment to save you $$$
Visit detectaleak.com.auWe analyzed Detectaleak.com.au page load time and found that the first response time was 1.9 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
detectaleak.com.au performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value10.6 s
0/100
25%
Value14.4 s
1/100
10%
Value16,640 ms
0/100
30%
Value0.001
100/100
15%
Value24.9 s
0/100
10%
1864 ms
70 ms
488 ms
465 ms
495 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 29% of them (38 requests) were addressed to the original Detectaleak.com.au, 37% (49 requests) were made to Maps.googleapis.com and 10% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Detectaleak.com.au.
Page size can be reduced by 111.2 kB (10%)
1.1 MB
1.0 MB
In fact, the total size of Detectaleak.com.au main page is 1.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 649.7 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.1 kB or 83% of the original size.
Potential reduce by 24.6 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. Detect A Leak images are well optimized though.
Potential reduce by 16.1 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 23.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. Detectaleak.com.au needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 24% of the original size.
Number of requests can be reduced by 78 (67%)
117
39
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Detect A Leak. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
detectaleak.com.au
1864 ms
analytics.js
70 ms
wp-emoji-release.min.js
488 ms
style.min.css
465 ms
elementor-icons.min.css
495 ms
animations.min.css
487 ms
frontend-legacy.min.css
503 ms
frontend.min.css
597 ms
post-988.css
908 ms
frontend.min.css
1169 ms
global.css
951 ms
post-792.css
929 ms
post-886.css
925 ms
post-804.css
1031 ms
css
70 ms
fontawesome.min.css
1345 ms
solid.min.css
1373 ms
jquery.min.js
1357 ms
jquery-migrate.min.js
1396 ms
gtm4wp-form-move-tracker.js
1476 ms
email-decode.min.js
1186 ms
wp-embed.min.js
1640 ms
jquery.smartmenus.min.js
1837 ms
comment-reply.min.js
1840 ms
webpack.runtime.min.js
2047 ms
frontend-modules.min.js
2049 ms
jquery.sticky.min.js
2051 ms
frontend.min.js
2487 ms
core.min.js
2271 ms
dialog.min.js
2261 ms
waypoints.min.js
2324 ms
share-link.min.js
2325 ms
swiper.min.js
2455 ms
collect
15 ms
frontend.min.js
2525 ms
gtm.js
117 ms
embed
231 ms
Detect-a-leak-logo.png
1183 ms
Rectangle-1.jpg
1240 ms
Truck.jpg
1749 ms
samuel-scrimshaw-ebbFZvavGy4-unsplash.jpg
1350 ms
image2.png
1863 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
26 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
67 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
65 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
65 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
67 ms
fa-solid-900.woff
2217 ms
collect
15 ms
gtm.js
32 ms
rs=ABjfnFV49bNVd8wFgij6shOTofNCIRQuLA
44 ms
css
25 ms
js
80 ms
m=gmeviewer_base
124 ms
conversion_async.js
316 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
254 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
252 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
254 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
254 ms
gen_204
218 ms
lazy.min.js
139 ms
m=ws9Tlc
100 ms
common.js
82 ms
util.js
82 ms
map.js
57 ms
overlay.js
56 ms
poly.js
122 ms
geocoder.js
114 ms
controls.js
112 ms
places_impl.js
115 ms
gen204
167 ms
info-000.png
96 ms
gm-close000.png
97 ms
179 ms
openhand_8_8.cur
101 ms
onion.js
56 ms
ViewportInfoService.GetViewportInfo
72 ms
transparent.png
28 ms
151 ms
undo_poly.png
126 ms
AuthenticationService.Authenticate
39 ms
vt
79 ms
vt
72 ms
vt
72 ms
vt
73 ms
vt
70 ms
vt
87 ms
vt
77 ms
vt
88 ms
vt
101 ms
vt
101 ms
vt
101 ms
vt
114 ms
vt
102 ms
vt
103 ms
vt
117 ms
vt
130 ms
QuotaService.RecordEvent
101 ms
vt
19 ms
vt
30 ms
vt
47 ms
vt
47 ms
vt
18 ms
vt
31 ms
viewer-icons001.png
274 ms
star4.png
350 ms
1492-wht-polygon-blank.png&filter=ff0097A7
356 ms
gen204
273 ms
stats.js
248 ms
css
157 ms
css
157 ms
MyMaps_Icons003.png
86 ms
mymaps_32.png
86 ms
v1_4593b7d7.png
128 ms
google-my-maps-logo-small-001.png
124 ms
kh
183 ms
vt
42 ms
vt
37 ms
vt
38 ms
vt
56 ms
vt
18 ms
vt
50 ms
vt
28 ms
vt
32 ms
vt
29 ms
vt
50 ms
vt
50 ms
vt
47 ms
detectaleak.com.au accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
detectaleak.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
detectaleak.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Detectaleak.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 Detectaleak.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.
detectaleak.com.au
Open Graph data is detected on the main page of Detect A Leak. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: