6.2 sec in total
442 ms
5.3 sec
409 ms
Visit citysearch.com.au now to see the best up-to-date Citysearch content and also check out these interesting facts you probably never knew about citysearch.com.au
{{vm.Seo.description.get()}}
Visit citysearch.com.auWe analyzed Citysearch.com.au page load time and found that the first response time was 442 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
citysearch.com.au performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.6 s
0/100
25%
Value11.4 s
5/100
10%
Value2,290 ms
5/100
30%
Value0.084
93/100
15%
Value16.8 s
5/100
10%
442 ms
637 ms
96 ms
57 ms
31 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 Citysearch.com.au, 24% (10 requests) were made to Truelocal.com.au and 20% (8 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Media.truelocal.com.au.
Page size can be reduced by 558.9 kB (70%)
794.4 kB
235.5 kB
In fact, the total size of Citysearch.com.au main page is 794.4 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. 40% of websites need less resources to load. Javascripts take 497.0 kB which makes up the majority of the site volume.
Potential reduce by 227.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 36.8 kB, which is 14% 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 227.6 kB or 84% of the original size.
Potential reduce by 48 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. Citysearch images are well optimized though.
Potential reduce by 331.3 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 331.3 kB or 67% of the original size.
Number of requests can be reduced by 17 (52%)
33
16
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citysearch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
citysearch.com.au
442 ms
www.truelocal.com.au
637 ms
tl-icon.css
96 ms
app.f299a6d8.css
57 ms
launch-05a5289ade15.min.js
31 ms
app.4e71e8dc.js
1219 ms
announcements.js
39 ms
configuration.constant.js
163 ms
platform.min.js
47 ms
validator.min.js
158 ms
j.php
73 ms
93YL3-T2N6L-2N8NZ-99HFC-RSAUM
227 ms
id
94 ms
AppMeasurement.min.js
29 ms
AppMeasurement_Module_ActivityMap.min.js
51 ms
validator.min.js
38 ms
v.gif
22 ms
va-10061b2cefd3f41a5d436ea025bd598c.js
13 ms
track-10061b2cefd3f41a5d436ea025bd598c.js
41 ms
opa-653609cce76db17051e7d9d28615ab1d.js
41 ms
NationalWeb-Book.woff
96 ms
dest5.html
40 ms
id
44 ms
settings.js
24 ms
worker-70faafffa0475802f5ee03ca5ff74179.js
10 ms
ibs:dpid=411&dpuuid=ZjaBcgAAAEEsCQN_
8 ms
config.json
28 ms
logo.png
135 ms
homepage.html
206 ms
footer-logo.png
236 ms
icon.ttf
91 ms
fjallaone-regular-webfont.woff
119 ms
151 ms
popular-categories
1757 ms
HOME_BG_4.jpg
2211 ms
right.svg
182 ms
shadow.png
148 ms
NationalWeb-Bold.woff
307 ms
s29008214098867
34 ms
api.js
208 ms
settings.js
40 ms
citysearch.com.au 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
button, link, and menuitem elements do not have accessible names.
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
citysearch.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
citysearch.com.au 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citysearch.com.au can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Citysearch.com.au 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.
citysearch.com.au
Open Graph description is not detected on the main page of Citysearch. 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: