1.9 sec in total
10 ms
1.5 sec
383 ms
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
Customer order tracking for last mile delivery and field service.
Visit localz.ioWe analyzed Localz.io page load time and found that the first response time was 10 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
localz.io performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.2 s
5/100
25%
Value5.8 s
50/100
10%
Value570 ms
52/100
30%
Value0.044
99/100
15%
Value7.3 s
49/100
10%
10 ms
276 ms
48 ms
39 ms
40 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Localz.io, 90% (37 requests) were made to Localz.com and 2% (1 request) were made to Cmp.osano.com. The less responsive or slowest element that took the longest time to load (379 ms) relates to the external source Cmp.osano.com.
Page size can be reduced by 52.8 kB (8%)
647.1 kB
594.3 kB
In fact, the total size of Localz.io main page is 647.1 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. 60% of websites need less resources to load. Javascripts take 289.4 kB which makes up the majority of the site volume.
Potential reduce by 47.5 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.5 kB or 78% of the original size.
Potential reduce by 0 B
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. Localz images are well optimized though.
Potential reduce by 2.9 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 2.3 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 has all CSS files already compressed.
Number of requests can be reduced by 24 (62%)
39
15
The browser has sent 39 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 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
localz.io
10 ms
www.localz.com
276 ms
style-static.min.css
48 ms
style.css
39 ms
jquery.min.js
40 ms
jquery-migrate.min.js
35 ms
osano.js
379 ms
script.js
46 ms
v4.js
113 ms
et-core-unified-1505.min.css
108 ms
et-core-unified-deferred-1505.min.css
41 ms
mediaelementplayer-legacy.min.css
108 ms
wp-mediaelement.min.css
108 ms
scripts.min.js
109 ms
smoothscroll.js
107 ms
jquery.fitvids.js
109 ms
comment-reply.min.js
108 ms
jquery.mobile.js
109 ms
magnific-popup.js
110 ms
easypiechart.js
109 ms
salvattore.js
110 ms
common.js
110 ms
mediaelement-and-player.min.js
110 ms
mediaelement-migrate.min.js
110 ms
wp-mediaelement.min.js
113 ms
motion-effects.js
110 ms
sticky-elements.js
111 ms
dsg-localz-logo-white.png
77 ms
woman-phone_205129152-2-1600.jpg
63 ms
308_Delivery_Route_Scheduling_LA.svg
66 ms
298_Bookings_LA.svg
65 ms
103-Ecommerce-Market-Integration-LA.svg
62 ms
Fleet_AdobeStock_513736510.jpg
64 ms
HSS_Hire_logo-white-500.png
69 ms
Fairhive-logo-white.png
71 ms
Customer-Engagement-Ebook-Mockup-2.png
71 ms
004-Solution-Broker-Forwarder-Enterprise-Systems-LA.svg
68 ms
191_Process_General_LA.svg
69 ms
094-Back-Office-Systems-LA.svg
72 ms
dsg-localz-logo.png
124 ms
style.min.css
62 ms
localz.io 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.
localz.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 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: