3.3 sec in total
41 ms
2.3 sec
1 sec
Visit localz.io now to see the best up-to-date Localz content for Australia and also check out these interesting facts you probably never knew about localz.io
Real-time customer engagement with location tracking and two-way customer communications for curbside collection, service and product delivery.
Visit localz.ioWe analyzed Localz.io page load time and found that the first response time was 41 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
localz.io performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value17.0 s
0/100
25%
Value9.2 s
13/100
10%
Value770 ms
38/100
30%
Value0.338
33/100
15%
Value18.0 s
3/100
10%
41 ms
643 ms
183 ms
43 ms
231 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Localz.io, 64% (56 requests) were made to Localz.com and 6% (5 requests) were made to No-cache.hubspot.com. The less responsive or slowest element that took the longest time to load (748 ms) relates to the external source Localz.com.
Page size can be reduced by 721.4 kB (14%)
5.1 MB
4.4 MB
In fact, the total size of Localz.io main page is 5.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. 80% 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 4.9 MB which makes up the majority of the site volume.
Potential reduce by 113.6 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 113.6 kB or 84% of the original size.
Potential reduce by 584.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. Obviously, Localz needs image optimization as it can save up to 584.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 82 B
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.2 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. Localz.io needs all CSS files to be minified and compressed as it can save up to 23.2 kB or 21% of the original size.
Number of requests can be reduced by 29 (37%)
79
50
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Localz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
localz.io
41 ms
www.localz.com
643 ms
main.min.css
183 ms
all.min.css
43 ms
_header_row_01_01.min.css
231 ms
module_-2712622_Site_Search_Input.min.css
69 ms
module_33474973185_Atomic_-_Feature_01.min.css
153 ms
css
49 ms
Atomic_Localz.min.css
253 ms
current.js
74 ms
jquery.min.js
49 ms
jquery-migrate.min.js
52 ms
slick.min.js
268 ms
scroll_reveal.min.js
291 ms
magnificpopup.min.js
394 ms
stickykit.min.js
393 ms
matchheight.min.js
393 ms
vide.min.js
394 ms
isotope.min.js
392 ms
chart.min.js
470 ms
main.min.js
670 ms
project.js
464 ms
project.js
421 ms
module_-2712622_Site_Search_Input.min.js
94 ms
v2.js
482 ms
4450883.js
463 ms
index.js
460 ms
gtm.js
161 ms
27530952-04c1-4273-b69c-ebd2bc140493.png
222 ms
localz-logo-transparentbg-300w1.png
411 ms
undraw_Checklist__re_2w7v.png
413 ms
undraw_timeline_9u4u.png
411 ms
undraw_building_websites_i78t.png
428 ms
equipment%20comms%204.png
583 ms
curbside-sollection-2.png
465 ms
product-delivery-hero.png
431 ms
service-tracking-solution.png
465 ms
social_housing_hero_2.png
466 ms
undraw_online_1qud.png
466 ms
undraw_newspaper_k72w.png
495 ms
undraw_update_uxn2.png
500 ms
undraw_Books_l33t.png
500 ms
ulps.png
638 ms
welsh-water-logo.png
512 ms
HSS%20panel.png
574 ms
localz-customer-engagement-homepage-hero-1.png
582 ms
atomic-grid.svg
406 ms
2ca84ed4-edfb-433f-8895-e5904e3026b6.png
395 ms
91f7ff08-291d-460f-9dc1-0383f9e9cb88.png
405 ms
0b2c7011-0ffb-4d0d-ba10-54842215b69a.png
406 ms
b3c4cec1-dc91-44ce-b52d-b2f54046611c.png
405 ms
service-tracking-hero-2x-1.png
691 ms
on-my-way-product-blog-hero%20(2).png
625 ms
MRI%20Square.png
714 ms
Oneserve%20Square.png
624 ms
FieldAware%20Square.png
622 ms
ServiceMax%20Square.png
748 ms
S6uyw4BMUTPHjx4wWw.ttf
140 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
141 ms
chat-my-way-product-blog-hero%20(1).png
611 ms
Woolworths-01.png
518 ms
Ovo_Energy_logo.png
517 ms
autoglass_logo_casestudy.png
546 ms
rac.png
541 ms
onehousing.png
559 ms
analytics.js
237 ms
insight.min.js
295 ms
1200px-Wates_Group.svg.png
497 ms
clarion%20logo%202.jpg
493 ms
vale%20of%20aylesbury%20housing%20logo.png
495 ms
phjones.png
660 ms
NewUKLandlordLaws.png
499 ms
4450883.js
192 ms
leadflows.js
191 ms
fb.js
186 ms
4450883.js
253 ms
json
376 ms
carbon_footprint.png
366 ms
collect
37 ms
generic
122 ms
collect
147 ms
pixel
94 ms
ga-audiences
68 ms
pixel
39 ms
7 ms
rubicon
105 ms
getuid
68 ms
17 ms
localz.io accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
localz.io 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
Missing source maps for large first-party JavaScript
localz.io 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 Localz.io 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 Localz.io 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.
localz.io
Open Graph data is detected on the main page of Localz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: