Tools & Wizards About Us
whereis.com.au screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

whereis.com.au

Whereis® | Maps of Australia, Street Directory, Driving Directions & Aerial Map

Page Load Speed

5 sec in total

First Response

490 ms

Resources Loaded

4.4 sec

Page Rendered

136 ms

whereis.com.au screenshot

About Website

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.au

Key Findings

We analyzed Whereis.com.au page load time and found that the first response time was 490 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

whereis.com.au performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

whereis.com.au

490 ms

www.whereis.com

943 ms

whereis-2ab886c11b969358f8093b7ce8a5978c.css

813 ms

745 ms

launch-2ba1b7e18e44.min.js

33 ms

Our browser made a total of 75 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, 64% (48 requests) were made to Tiles.ems.sensis.com.au and 11% (8 requests) were made to Api.ems.sensis.com.au. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Tiles.ems.sensis.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 613.2 kB (39%)

Content Size

1.6 MB

After Optimization

962.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whereis.com.au main page is 1.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. 35% of websites need less resources to load. Images take 743.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 107.9 kB

  • Original 144.5 kB
  • After minification 136.7 kB
  • After compression 36.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. 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 107.9 kB or 75% of the original size.

Image Optimization

-32%

Potential reduce by 239.4 kB

  • Original 743.9 kB
  • After minification 504.5 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. Obviously, Whereis needs image optimization as it can save up to 239.4 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-40%

Potential reduce by 265.4 kB

  • Original 659.0 kB
  • After minification 658.4 kB
  • After compression 393.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 265.4 kB or 40% of the original size.

CSS Optimization

-2%

Potential reduce by 526 B

  • Original 28.2 kB
  • After minification 28.2 kB
  • After compression 27.7 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (33%)

Requests Now

73

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 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 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

whereis.com.au

whereis.com.au

490 ms

www.whereis.com

www.whereis.com

943 ms

whereis-2ab886c11b969358f8093b7ce8a5978c.css

whereis-2ab886c11b969358f8093b7ce8a5978c.css

813 ms

745 ms

launch-2ba1b7e18e44.min.js

launch-2ba1b7e18e44.min.js

33 ms

whereis-5e81a8f1ab288eec6ea0eb53037de2a2.js

whereis-5e81a8f1ab288eec6ea0eb53037de2a2.js

411 ms

announcements.js

announcements.js

24 ms

5 ms

style.css

style.css

2 ms

j.php

j.php

246 ms

spritables-e73870b271645eac9d82208cbb254121.png

spritables-e73870b271645eac9d82208cbb254121.png

599 ms

spinner@2x-0472c9058033f76e62dd266e2ccbb1b8.gif

spinner@2x-0472c9058033f76e62dd266e2ccbb1b8.gif

233 ms

id

id

229 ms

AppMeasurement.min.js

AppMeasurement.min.js

208 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

217 ms

street

street

209 ms

middle.png

middle.png

85 ms

init

init

934 ms

street

street

128 ms

street

street

130 ms

street

street

128 ms

street

street

131 ms

street

street

133 ms

street

street

140 ms

street

street

133 ms

street

street

136 ms

street

street

131 ms

street

street

150 ms

street

street

140 ms

street

street

133 ms

street

street

132 ms

street

street

377 ms

street

street

136 ms

street

street

137 ms

street

street

141 ms

street

street

137 ms

street

street

139 ms

street

street

140 ms

street

street

144 ms

street

street

143 ms

street

street

701 ms

street

street

141 ms

street

street

141 ms

street

street

144 ms

street

street

146 ms

street

street

395 ms

street

street

607 ms

street

street

150 ms

street

street

691 ms

street

street

607 ms

street

street

856 ms

street

street

1055 ms

street

street

1057 ms

left.png

left.png

22 ms

right.png

right.png

35 ms

mapbox-wordmark.png

mapbox-wordmark.png

56 ms

ypol-logo-new-b62f27c92450ee674b318c07feb3ef8a.png

ypol-logo-new-b62f27c92450ee674b318c07feb3ef8a.png

600 ms

v.gif

v.gif

12 ms

dest5.html

dest5.html

76 ms

id

id

73 ms

RC7b263d672c504727a5516b902f88590b-source.min.js

RC7b263d672c504727a5516b902f88590b-source.min.js

9 ms

ibs:dpid=411&dpuuid=Zkh39gAAADcTCQN_

ibs:dpid=411&dpuuid=Zkh39gAAADcTCQN_

41 ms

street

street

934 ms

street

street

1232 ms

street

street

1111 ms

street

street

1312 ms

street

street

1306 ms

street

street

1455 ms

street

street

1358 ms

street

street

1532 ms

street

street

1725 ms

street

street

1312 ms

street

street

1561 ms

street

street

1713 ms

s13026677255984

s13026677255984

7 ms

Accessibility Review

whereis.com.au accessibility score

61

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whereis.com.au best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whereis.com.au SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: