4.4 sec in total
182 ms
3.7 sec
494 ms
Visit reachlocal.co.nz now to see the best up-to-date Reachlocal content for New Zealand and also check out these interesting facts you probably never knew about reachlocal.co.nz
LocaliQ helps businesses across New Zealand build their brand, generate quality leads and drive conversions. Contact us today to see how we can grow your brand.
Visit reachlocal.co.nzWe analyzed Reachlocal.co.nz page load time and found that the first response time was 182 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
reachlocal.co.nz performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value19.8 s
0/100
25%
Value32.5 s
0/100
10%
Value40,540 ms
0/100
30%
Value0.128
82/100
15%
Value62.8 s
0/100
10%
182 ms
87 ms
174 ms
234 ms
254 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Reachlocal.co.nz, 4% (3 requests) were made to Reachlocallivechat.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (965 ms) relates to the external source Platform.linkedin.com.
Page size can be reduced by 1.3 MB (51%)
2.6 MB
1.3 MB
In fact, the total size of Reachlocal.co.nz main page is 2.6 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. 50% of websites need less resources to load. Images take 976.0 kB which makes up the majority of the site volume.
Potential reduce by 71.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. This page needs HTML code to be minified as it can gain 13.1 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 71.5 kB or 81% of the original size.
Potential reduce by 85.1 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. Reachlocal images are well optimized though.
Potential reduce by 533.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 533.7 kB or 69% of the original size.
Potential reduce by 632.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. Reachlocal.co.nz needs all CSS files to be minified and compressed as it can save up to 632.2 kB or 84% of the original size.
Number of requests can be reduced by 42 (60%)
70
28
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reachlocal. 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.
en
182 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
87 ms
css_m0Ri2pR7baRgm3u4M6o9QIxqsIiCHMdGwMbD3adIWtc.css
174 ms
css_Dat7BvQ6FUUcOm_YyTCI9HkXYLZ7_KAlfase3OuhT2o.css
234 ms
css_dvdn0izE8gIKSD8eh_APct4jG1hhrGm2o44k0VRLZhw.css
254 ms
css_F2xshFA6VQVkA4Vz5Bw6t4ZfKXDmtsQKQARUXEnFjQM.css
433 ms
js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js
343 ms
js_R9UbiVw2xuTUI0GZoaqMDOdX0lrZtgX-ono8RVOUEVc.js
265 ms
js_MDvaZIsckY07mi1aUDJ6Gc56GW00KxFzHWmb-Wh860Y.js
408 ms
in.js
965 ms
js_jxKZMTB0RWnlpWAnYhtcdUGakSj70vGO9BzO1HfrDS8.js
309 ms
js_r5zpnu4_DgQCpkzQa5qz4BVJF4exgJ662ZsYFHRdOQk.js
421 ms
jquery-ui-1-8-5.min.js
528 ms
heroslider-style.css
387 ms
modernizr.js
428 ms
main.js
476 ms
js_gjR5MS6uQNgSSscNvUlxNQFvls9RNntaBvxe_owPjds.js
508 ms
iframe_api
164 ms
nz.png
156 ms
au.png
156 ms
br.png
156 ms
ca.png
155 ms
de.png
155 ms
nl.png
154 ms
at.png
260 ms
uk.png
260 ms
us.png
278 ms
reachlocal_favicon.png
231 ms
logo.png
329 ms
au_tdms_img_outline_bkg.png
514 ms
reachlocal_edge_img.png
329 ms
screen_shot_2015-04-14_at_4.29.37_pm.png
428 ms
clarin-logo-ar.png
259 ms
grupo-one-logo-co.png
247 ms
in-click-logo-chile.png
239 ms
pagoranking-logo-chile.png
259 ms
au_reachlocal_ebook_img_0.png
572 ms
gtm.js
152 ms
social-nav-icons-sprite.png
311 ms
menu-leaf.png
341 ms
award-winning-services_1280x680_b.jpg
465 ms
nz_home-vnew-slider-1.jpg
925 ms
RobotoSlab-Regular-webfont.woff
424 ms
FunctionPro-Book-webfont.woff
445 ms
fontawesome-webfont.woff
632 ms
FunctionPro-Demi-webfont.woff
596 ms
YOvJGQzoDKc
163 ms
reachlocal_edge_promo_bg_0.jpg
852 ms
reachlocal_ebook_bg.jpg
444 ms
dyns.js
108 ms
widgets.js
55 ms
sdk.js
501 ms
secureAnonymousFramework
455 ms
resource_center_icons.woff
447 ms
analytics.js
40 ms
www-widgetapi.js
70 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
5 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
25 ms
collect
15 ms
collect
110 ms
info.json
130 ms
invitation.ashx
288 ms
www-embed-player-vflfNyN_r.css
32 ms
www-embed-player.js
50 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
69 ms
ad_status.js
71 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
67 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
88 ms
jot
98 ms
apexchat.js
772 ms
xdrpc.html
262 ms
139 ms
xd_arbiter.php
430 ms
followcompany
58 ms
reachlocal.co.nz 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
Image elements do not have [alt] attributes
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
reachlocal.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
reachlocal.co.nz 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
Image elements do not have [alt] attributes
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 Reachlocal.co.nz 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 Reachlocal.co.nz 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.
reachlocal.co.nz
Open Graph description is not detected on the main page of Reachlocal. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: