13.2 sec in total
1.1 sec
12 sec
185 ms
Click here to check amazing Yellow Local content. Otherwise, check out these important facts you probably never knew about yellowlocal.co.nz
WOW! Grab your ** FREE Business Directory Listing ** Auckland's top directory to help your local business gain more leads, traffic, & sales.
Visit yellowlocal.co.nzWe analyzed Yellowlocal.co.nz page load time and found that the first response time was 1.1 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yellowlocal.co.nz performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value7.4 s
4/100
25%
Value7.9 s
23/100
10%
Value200 ms
89/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
1083 ms
1159 ms
971 ms
394 ms
454 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yellowlocal.co.nz, 8% (4 requests) were made to Apis.google.com and 8% (4 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Yellow.co.nz.
Page size can be reduced by 842.0 kB (57%)
1.5 MB
641.4 kB
In fact, the total size of Yellowlocal.co.nz main page is 1.5 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. 55% of websites need less resources to load. Javascripts take 731.0 kB which makes up the majority of the site volume.
Potential reduce by 66.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. This page needs HTML code to be minified as it can gain 10.1 kB, which is 11% 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 66.6 kB or 73% of the original size.
Potential reduce by 4.7 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. Yellow Local images are well optimized though.
Potential reduce by 467.5 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 467.5 kB or 64% of the original size.
Potential reduce by 303.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. Yellowlocal.co.nz needs all CSS files to be minified and compressed as it can save up to 303.2 kB or 85% of the original size.
Number of requests can be reduced by 28 (64%)
44
16
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yellow Local. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
yellow.co.nz
1083 ms
yellow.min.css
1159 ms
jquery.min.js
971 ms
google-tag.js
394 ms
nelson.js
454 ms
js
35 ms
e4cf8ef97ce7.js
7314 ms
browser-update.js
218 ms
gpt.js
6487 ms
v60a.js
6489 ms
yolLogo.svg
830 ms
appLogoAppleAppstore.svg
868 ms
appLogoGooglePlay.svg
865 ms
yellow-windows-store1.svg
833 ms
gtm.js
44 ms
fernyellowpetals2.jpg
2806 ms
pubads_impl_82.js
31 ms
storageframe.html
801 ms
shortlist-icons.svg
844 ms
all.js
89 ms
client:plusone.js
783 ms
roboto-regular-webfont.woff
822 ms
roboto-bold-webfont.woff
820 ms
roboto-light-webfont.woff
821 ms
fontawesome-webfont.woff
820 ms
container.html
655 ms
bat.js
685 ms
dc.js
681 ms
analytics.js
648 ms
195 ms
cb=gapi.loaded_0
23 ms
xd_arbiter.php
81 ms
xd_arbiter.php
103 ms
collect
59 ms
__utm.gif
55 ms
postmessageRelay
94 ms
m
31 ms
collect
19 ms
__utm.gif
41 ms
ga-audiences
46 ms
collect
57 ms
ga-audiences
23 ms
3193398744-postmessagerelay.js
23 ms
rpc:shindig_random.js
32 ms
cb=gapi.loaded_0
3 ms
auth
73 ms
2637085964-postmessage.js
4 ms
nr-885.min.js
16 ms
update.js
7 ms
c.png
8 ms
4649912473
45 ms
xd_arbiter.php
9 ms
yellowlocal.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yellowlocal.co.nz 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
yellowlocal.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Yellowlocal.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 Yellowlocal.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.
yellowlocal.co.nz
Open Graph description is not detected on the main page of Yellow Local. 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: