11.2 sec in total
1.6 sec
8.6 sec
982 ms
Welcome to localz.co homepage info - get ready to check Localz best content right away, or after learning these important things about localz.co
Real-time customer engagement with location tracking and two-way customer communications for curbside collection, service and product delivery.
Visit localz.coWe analyzed Localz.co page load time and found that the first response time was 1.6 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
localz.co performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value15.1 s
0/100
25%
Value13.0 s
2/100
10%
Value910 ms
31/100
30%
Value0.342
33/100
15%
Value18.7 s
3/100
10%
1563 ms
280 ms
384 ms
514 ms
294 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Localz.co, 80% (104 requests) were made to Localz.com and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Localz.com.
Page size can be reduced by 2.4 MB (49%)
4.8 MB
2.5 MB
In fact, the total size of Localz.co main page is 4.8 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 177.9 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 177.9 kB or 79% of the original size.
Potential reduce by 4.8 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. Localz images are well optimized though.
Potential reduce by 985.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 985.7 kB or 71% of the original size.
Potential reduce by 1.2 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. Localz.co needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 80% of the original size.
Number of requests can be reduced by 77 (68%)
114
37
The browser has sent 114 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 55 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
localz.co
1563 ms
wp-emoji-release.min.js
280 ms
shortcodes.css
384 ms
linecons.css
514 ms
pixelicons.css
294 ms
dashicons.min.css
400 ms
jquery-ui-dialog.min.css
297 ms
styles.css
391 ms
events_manager.css
412 ms
settings.css
416 ms
js_composer.min.css
815 ms
style.css
518 ms
font-awesome.min.css
533 ms
icomoon.css
537 ms
steadysets.css
599 ms
mediaelementplayer.css
617 ms
mobius-grid.css
625 ms
form-basic.min.css
630 ms
css
106 ms
post-like.css
626 ms
jquery.js
797 ms
jquery-migrate.min.js
732 ms
core.min.js
745 ms
widget.min.js
750 ms
mouse.min.js
752 ms
resizable.min.js
923 ms
draggable.min.js
930 ms
button.min.js
933 ms
position.min.js
935 ms
dialog.min.js
939 ms
sortable.min.js
940 ms
datepicker.min.js
948 ms
menu.min.js
958 ms
autocomplete.min.js
961 ms
events-manager.js
965 ms
jquery.themepunch.tools.min.js
1108 ms
jquery.themepunch.revolution.min.js
1011 ms
css
129 ms
css
172 ms
css
173 ms
api.js
222 ms
font-awesome.css
1265 ms
pe-icon-7-stroke.css
786 ms
modernizr.js
792 ms
easypiechart.js
1124 ms
jquery.appear.js
829 ms
themeone-shortcodes.js
824 ms
wpdialog.min.js
815 ms
post-like.js
844 ms
jquery.form.min.js
775 ms
scripts.js
841 ms
ssba.min.js
818 ms
ssba-st.min.js
963 ms
js_composer_front.min.js
963 ms
mediaelement-and-player.min.js
902 ms
owl.carousel.js
885 ms
easing.js
877 ms
hammer.js
876 ms
isotope.js
956 ms
sly.js
938 ms
custom.js
1076 ms
comment-reply.min.js
1317 ms
mobius-grid.js
920 ms
search_autocomplete.js
878 ms
ajax-comments.js
760 ms
wp-embed.min.js
747 ms
forms-api.min.js
1202 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
191 ms
localz-logo-transparentbg-300w.png
619 ms
localz_logo.png
619 ms
dummy.png
620 ms
few-of-our-clients-txt.jpg
853 ms
homepass.jpg
854 ms
john-lewis.jpg
854 ms
grand-national.jpg
868 ms
dpd.jpg
868 ms
woolworths.jpg
871 ms
winners-of-the-following-competitions-txt.jpg
871 ms
john-lewis-jlab.jpg
874 ms
ibm-smartcamp.jpg
875 ms
start-tank.jpg
878 ms
retail-recharged.jpg
903 ms
package-table-cnc-home-page-text-image.jpg
799 ms
mobile-500x350.jpg
781 ms
Easter-egg-hunt-clues.jpg
782 ms
Screen-Shot-2016-03-22-at-09.59.43-453x350.png
2906 ms
Hipster-with-Smartphone-back-cropped-1200-e1450785235721.jpg
745 ms
Thunderhead_LogoIcon_Aubergine-500x247.png
2883 ms
localz-icon-500x350.jpg
2752 ms
IMG_0036-500x350.jpg
2734 ms
retail2.png
2746 ms
95007f94-544a-40f1-9023-01b5cef7fb64-original-500x350.jpeg
2745 ms
bit10.jpg
2744 ms
Woolworths_logo_2014.svg_-500x350.png
2743 ms
NRF-2015-Logo.png
2978 ms
s-BiyweUPV0v-yRb-cjciL3hpw3pgy2gAi-Ip7WPMi0.woff
173 ms
EFpQQyG9GqCrobXxL-KRMXbFhgvWbfSbdVg11QabG8w.woff
184 ms
steadysets.ttf
2975 ms
analytics.js
157 ms
icomoon.woff
2892 ms
fontawesome-webfont.woff
3245 ms
london_platform_BW.jpg
2913 ms
collect
249 ms
iframe_api
2171 ms
collect
2413 ms
recaptcha__en.js
2628 ms
revolution.extension.video.min.js
819 ms
revolution.extension.slideanims.min.js
932 ms
revolution.extension.actions.min.js
932 ms
revolution.extension.layeranimation.min.js
932 ms
revolution.extension.kenburn.min.js
937 ms
revolution.extension.navigation.min.js
947 ms
revolution.extension.parallax.min.js
949 ms
localz.co
1095 ms
admin-ajax.php
1741 ms
ajax-loader.gif
580 ms
Pe-icon-7-stroke.woff
627 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
65 ms
cIFypx4yrWPDz3zOxk7hIQLUuEpTyoUstqEm5AMlJo4.woff
165 ms
www-widgetapi.js
239 ms
froogaloop2.min.js
153 ms
SmartphoneatTable1.jpg
2466 ms
Bike-Motion-for-CnC-Slider-image.jpg
233 ms
RetailShoppingStreet-for-Case-Studies-slider.jpg
985 ms
revicons.woff
139 ms
anchor
92 ms
styles__ltr.css
244 ms
logo_48.png
32 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
168 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
220 ms
localz.co 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
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.co 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.co 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.co 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.co 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.co
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: