Tools & Wizards About Us
mobilego.com.au screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mobilego.com.au

Mobile Go | Mobile Websites Design | Mobile Sites - Australia

Page Load Speed

5.3 sec in total

First Response

1.3 sec

Resources Loaded

3.8 sec

Page Rendered

164 ms

mobilego.com.au screenshot

About Website

Welcome to mobilego.com.au homepage info - get ready to check Mobile Go best content for India right away, or after learning these important things about mobilego.com.au

Australia's leading mobile website developer. We design, create & build professional mobile-friendly sites Australia-Wide. Call 1300 244 325 Today.

Visit mobilego.com.au

Key Findings

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

Performance Metrics

mobilego.com.au performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

mobilego.com.au

1335 ms

mobile.js

650 ms

theme.css

868 ms

icons.css

864 ms

jquery.tooltip.css

436 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 87% of them (45 requests) were addressed to the original Mobilego.com.au, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mobilego.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.9 kB (23%)

Content Size

967.9 kB

After Optimization

747.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobilego.com.au main page is 967.9 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. Images take 679.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 27.9 kB

  • Original 34.0 kB
  • After minification 23.8 kB
  • After compression 6.1 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.2 kB, which is 30% 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 27.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 12.9 kB

  • Original 679.9 kB
  • After minification 666.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. Mobile Go images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 155.6 kB

  • Original 226.1 kB
  • After minification 185.6 kB
  • After compression 70.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 155.6 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 24.5 kB

  • Original 28.0 kB
  • After minification 20.6 kB
  • After compression 3.5 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. Mobilego.com.au needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (55%)

Requests Now

49

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Go. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mobilego.com.au

mobilego.com.au

1335 ms

mobile.js

mobile.js

650 ms

theme.css

theme.css

868 ms

icons.css

icons.css

864 ms

jquery.tooltip.css

jquery.tooltip.css

436 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1515 ms

jquery.cookie.js

jquery.cookie.js

652 ms

jquery.cycle.all.js

jquery.cycle.all.js

1045 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1079 ms

jquery.tooltip.js

jquery.tooltip.js

868 ms

jquery.infieldlabel.min.js

jquery.infieldlabel.min.js

1080 ms

css

css

19 ms

WebResource.axd

WebResource.axd

1100 ms

WebResource.axd

WebResource.axd

1102 ms

script.opentracker.net

script.opentracker.net

133 ms

ga.js

ga.js

30 ms

background_hatch_1.png

background_hatch_1.png

213 ms

cardio@2x_5.png

cardio@2x_5.png

225 ms

box_shadow_2.png

box_shadow_2.png

224 ms

preview_icons.png

preview_icons.png

222 ms

box_shadow_1.png

box_shadow_1.png

224 ms

9_after.jpg

9_after.jpg

225 ms

15_after.jpg

15_after.jpg

633 ms

19_after.jpg

19_after.jpg

656 ms

27_after.jpg

27_after.jpg

657 ms

17_after.jpg

17_after.jpg

656 ms

22_after.jpg

22_after.jpg

656 ms

23_after.jpg

23_after.jpg

657 ms

10_after.jpg

10_after.jpg

844 ms

24_after.jpg

24_after.jpg

878 ms

25_after.jpg

25_after.jpg

1086 ms

20_after.jpg

20_after.jpg

1087 ms

26_after.jpg

26_after.jpg

1090 ms

circle_small_2.png

circle_small_2.png

852 ms

circle_small_3.png

circle_small_3.png

1032 ms

circle_small_1.png

circle_small_1.png

1072 ms

logo.png

logo.png

1071 ms

circle_2.png

circle_2.png

1243 ms

thin_right_arrow_5.png

thin_right_arrow_5.png

1280 ms

curved_arrow_2.png

curved_arrow_2.png

1282 ms

iphone.png

iphone.png

1286 ms

gomo.png

gomo.png

1287 ms

facebook_1.png

facebook_1.png

1287 ms

twitter_1.png

twitter_1.png

1453 ms

linked_in_1.png

linked_in_1.png

1496 ms

qr.png

qr.png

1497 ms

log.opentracker.net

log.opentracker.net

176 ms

__utm.gif

__utm.gif

12 ms

pager_active.png

pager_active.png

1414 ms

pager_inactive.png

pager_inactive.png

1412 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

10 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

15 ms

Accessibility Review

mobilego.com.au accessibility score

67

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.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

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

mobilego.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mobilego.com.au SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilego.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 Mobilego.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

mobilego.com.au

Open Graph description is not detected on the main page of Mobile Go. 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: