6.5 sec in total
625 ms
5.6 sec
288 ms
Welcome to cityscope.com.au homepage info - get ready to check Cityscope best content right away, or after learning these important things about cityscope.com.au
CoreLogic RP Data is a leading property information, analytics and services provider in Australia and New Zealand with growing partnerships throughout Asia.
Visit cityscope.com.auWe analyzed Cityscope.com.au page load time and found that the first response time was 625 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
cityscope.com.au performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.1 s
0/100
25%
Value10.5 s
7/100
10%
Value1,640 ms
12/100
30%
Value0.315
37/100
15%
Value13.6 s
11/100
10%
625 ms
486 ms
1405 ms
1374 ms
690 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cityscope.com.au, 73% (56 requests) were made to Corelogic.com.au and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Corelogic.com.au.
Page size can be reduced by 418.6 kB (38%)
1.1 MB
693.0 kB
In fact, the total size of Cityscope.com.au main page is 1.1 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. 45% of websites need less resources to load. Images take 613.5 kB which makes up the majority of the site volume.
Potential reduce by 147.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 29.5 kB, which is 17% 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 147.6 kB or 84% of the original size.
Potential reduce by 56.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. Cityscope images are well optimized though.
Potential reduce by 212.8 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 212.8 kB or 67% of the original size.
Potential reduce by 2.1 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. Cityscope.com.au needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 45% of the original size.
Number of requests can be reduced by 30 (45%)
67
37
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cityscope. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cityscope.com.au
625 ms
www.rpdata.com
486 ms
www.corelogic.com.au
1405 ms
bootstrap.css
1374 ms
bootstrap-responsive.css
690 ms
main.css
926 ms
font-awesome.min.css
692 ms
css
22 ms
component.css
464 ms
SM1.css
927 ms
LN.css
919 ms
modernizr-2.6.2-respond-1.1.0.min.js
918 ms
jquery-1.10.1.min.js
1363 ms
videoModal.js
701 ms
asx.js
473 ms
toucheffects.js
479 ms
bootstrap.js
940 ms
plugins.js
764 ms
main.js
764 ms
SM1.js
764 ms
LN-new.js
916 ms
jQuery-template.js
921 ms
jQuery-ticker.js
929 ms
conversion.js
13 ms
jquery.backgroundcover.js
708 ms
CL_Header-Logo.jpg
256 ms
menuIco.png
403 ms
menuUser.png
416 ms
WBF-RPDATA01-4-megamenu.jpg
420 ms
WBF-RPDATA01-5-megamenu.jpg
417 ms
WBF-RPDATA01-6-megamenu.jpg
424 ms
WBF-RPDATA01-7-megamenu.jpg
467 ms
WBF-RPDATA01-13-megamenu.jpg
632 ms
WBF-RPDATA01-12-megamenu.jpg
654 ms
WBF-RPDATA01-9-megamenu.jpg
654 ms
WBF-RPDATA01-11-megamenu.jpg
654 ms
WBF-RPDATA01-10-megamenu.jpg
657 ms
SMarrowBoldPrev.png
699 ms
SMarrowBold.png
862 ms
2016-03-11_208x120px_South%20Sydney.jpg
881 ms
177016741--208x120.jpg
1111 ms
201666_03_11_Perth%20Forrest_208x120px.jpg
1112 ms
339505666--208x120.jpg
887 ms
2016-04-02-Adelaide-208x120.jpg
930 ms
fb.png
1091 ms
tw.png
1112 ms
in.png
1120 ms
plus.png
1164 ms
yt.png
1321 ms
wordpress.png
1341 ms
corelogic-logo-footer.png
1341 ms
all.js
267 ms
box1.png
1335 ms
box2.png
1341 ms
box3.png
1385 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
57 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
57 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
58 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
59 ms
riskmark-bg.jpg
1501 ms
rismark-hover.jpg
1523 ms
fontawesome-webfont.woff
1634 ms
foot2.png
1406 ms
analytics.js
23 ms
country_dd.min.css
265 ms
country_dd_legacy.min.js
204 ms
collect
51 ms
collect
68 ms
65 ms
xd_arbiter.php
310 ms
xd_arbiter.php
483 ms
country-dropdown-json.aspx
83 ms
135 ms
ping
63 ms
homepage-hero-image-6_b.jpg
1899 ms
walpha.png
1024 ms
50 ms
cityscope.com.au 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
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>).
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.
cityscope.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
cityscope.com.au 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
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cityscope.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cityscope.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.
cityscope.com.au
Open Graph description is not detected on the main page of Cityscope. 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: