10.2 sec in total
793 ms
9.2 sec
175 ms
Visit whereis.com.au now to see the best up-to-date Whereis content and also check out these interesting facts you probably never knew about whereis.com.au
Maps of Australian cities, towns and travel destinations with driving directions and traveller information. Use Whereis® Maps and start your journey.
Visit whereis.com.auWe analyzed Whereis.com.au page load time and found that the first response time was 793 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whereis.com.au performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value15.2 s
0/100
25%
Value17.3 s
0/100
10%
Value9,170 ms
0/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
793 ms
1783 ms
80 ms
805 ms
532 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whereis.com.au, 32% (48 requests) were made to Tiles.ems.sensis.com.au and 11% (17 requests) were made to Secure.flashtalking.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Tiles.ems.sensis.com.au.
Page size can be reduced by 1.7 MB (60%)
2.9 MB
1.2 MB
In fact, the total size of Whereis.com.au main page is 2.9 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 52.7 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 52.7 kB or 77% of the original size.
Potential reduce by 5.9 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. Whereis images are well optimized though.
Potential reduce by 1.5 MB
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 1.5 MB or 71% of the original size.
Potential reduce by 175.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. Whereis.com.au needs all CSS files to be minified and compressed as it can save up to 175.1 kB or 87% of the original size.
Number of requests can be reduced by 78 (55%)
143
65
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whereis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and as a result speed up the page load time.
whereis.com.au
793 ms
www.whereis.com
1783 ms
fbds.js
80 ms
805 ms
sXVuY7u5EkMSylamwgYke8LEa4DANhcSZmd6hXsLEcr.css
532 ms
4ldhsuIY5y8bcC2F64SVol42fvpE0NfpAm2uHcWaYAn.js
1047 ms
mqIVrst1dqrhCnBBLcUM7ZZa2n3NyXpOrepoiZP3VOm.js
526 ms
Sa2XbROzIJlEw7wfNHEQXdmdKOzHgEF2A81kcxC7a6A.js
2116 ms
19 ms
1606 ms
style.css
271 ms
7IOL3SdB392eOx1F5kH7TcMQAzLFjwaTAedS9QGqcEJ.gif
297 ms
mFwMimvENd9qkz3CARMU4A0ZhXwvaMwYBKNt9Bgks14.png
1855 ms
street
1544 ms
init
271 ms
opentag-112905-1846444.js
16 ms
middle.png
478 ms
left.png
527 ms
right.png
526 ms
street
1702 ms
street
1708 ms
street
1459 ms
street
1444 ms
street
1460 ms
street
1705 ms
street
1721 ms
street
1721 ms
street
1981 ms
street
1962 ms
street
1967 ms
street
1971 ms
street
1983 ms
street
1984 ms
street
2322 ms
street
2228 ms
street
2233 ms
street
2343 ms
street
2243 ms
street
2344 ms
street
2489 ms
street
2495 ms
street
2505 ms
street
2580 ms
street
2604 ms
street
2705 ms
street
2748 ms
street
2758 ms
street
2765 ms
street
2941 ms
street
2866 ms
street
3066 ms
street
3009 ms
street
3022 ms
street
3026 ms
controltag
16 ms
gpt.js
11 ms
pubads_impl_82.js
11 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
47 ms
ads
187 ms
container.html
36 ms
tag2
174 ms
a
132 ms
osd.js
9 ms
s9178455929271
38 ms
banner
338 ms
yi
78 ms
s_0RCgeny2mO_1939542802.html
23 ms
get-user-id
94 ms
cl
37 ms
creative_add_on.js
128 ms
211 ms
lidar.js
42 ms
controltag
60 ms
rs.js
43 ms
smart_tag.js
336 ms
g-3295.xgi
41 ms
UCookieSetPug
52 ms
pixel
47 ms
%7BSSP_USER_ID%7D
78 ms
UCookieSetPug
26 ms
95E47816-128A-43C8-9F0E-97617C18BA38
68 ms
img
30 ms
j-1439489-1151259.js
59 ms
main.html
12 ms
ftpagefold_v4.4.0.js
84 ms
controltag.js.f8e94fa978cc2569e4b4423df4245d7e
31 ms
rpc.flow
147 ms
vce_st.js
99 ms
html5API.js
44 ms
adlib-min.js
74 ms
surly.js
86 ms
dvtp_src.js
89 ms
ai.htm
439 ms
a.gif
240 ms
p2
45 ms
data.json
50 ms
ft.stat
81 ms
p
31 ms
p
34 ms
0.gif
95 ms
manifest.js
11 ms
ba.html
5 ms
4.gif
17 ms
dvtp_src_internal26.js
14 ms
2532.js
61 ms
1151259.json
59 ms
t2tv7.html
68 ms
visit.js
54 ms
dish-80_369563_300x171.jpg
22 ms
fabric-16_369468_300x80.png
12 ms
bug-24_469502_76x74.png
21 ms
logo-flag_413327_94x67.png
21 ms
txt-1a-24_469507_218x17.png
19 ms
txt1-24_469508_200x21.png
19 ms
txt2-24_469509_278x19.png
20 ms
cta-over-24_469505_241x40.png
23 ms
cta-normal-24_469504_241x40.png
21 ms
btnReplay-24_369463_48x25.png
20 ms
avs5639.js
7 ms
event.jpg
68 ms
379708.gif
19 ms
street
1686 ms
street
1850 ms
street
1820 ms
street
1832 ms
pixel
12 ms
m
22 ms
get
70 ms
optout_check
39 ms
379708.gif
27 ms
genericusersync.ashx
59 ms
box_19_top-right.png
45 ms
ci.png
28 ms
generic
4 ms
Pix-1x1.gif
19 ms
street
1695 ms
street
1731 ms
street
1694 ms
activeview
16 ms
street
1819 ms
pixel.gif
54 ms
street
1833 ms
street
1706 ms
street
1690 ms
street
1704 ms
activeview
14 ms
nr-885.min.js
36 ms
optout_check
27 ms
get
29 ms
8 ms
whereis.com.au accessibility score
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
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
Image elements do not have [alt] attributes
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.
whereis.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
whereis.com.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whereis.com.au 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 Whereis.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.
whereis.com.au
Open Graph description is not detected on the main page of Whereis. 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: