Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

servicestatus.tpg.com.au

nbn®, Internet & Mobile Service Provider | TPG

Page Load Speed

18.7 sec in total

First Response

754 ms

Resources Loaded

12.9 sec

Page Rendered

5 sec

servicestatus.tpg.com.au screenshot

About Website

Visit servicestatus.tpg.com.au now to see the best up-to-date Service Status TPG content for Australia and also check out these interesting facts you probably never knew about servicestatus.tpg.com.au

TPG is Australia's second largest Fixed Internet Provider offering Home and Business NBN Plans as well as Fibre Broadband and Mobile SIM Only

Visit servicestatus.tpg.com.au

Key Findings

We analyzed Servicestatus.tpg.com.au page load time and found that the first response time was 754 ms and then it took 17.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

servicestatus.tpg.com.au performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,370 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

servicestatus.tpg.com.au

754 ms

servicestatus

1036 ms

servicestatus

2133 ms

js

448 ms

google_tag.script.js

1111 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Servicestatus.tpg.com.au, 36% (13 requests) were made to Support.tpg.com.au and 8% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Support.tpg.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.0 kB (43%)

Content Size

302.5 kB

After Optimization

171.5 kB

In fact, the total size of Servicestatus.tpg.com.au main page is 302.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 144.9 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 130.0 kB

  • Original 144.9 kB
  • After minification 91.5 kB
  • After compression 14.8 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 53.3 kB, which is 37% 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 130.0 kB or 90% of the original size.

JavaScript Optimization

-2%

Potential reduce by 922 B

  • Original 55.5 kB
  • After minification 55.5 kB
  • After compression 54.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 102.1 kB
  • After minification 102.1 kB
  • After compression 102.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. Servicestatus.tpg.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Service Status TPG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

servicestatus.tpg.com.au accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

servicestatus.tpg.com.au best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

servicestatus.tpg.com.au SEO score

84

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 uses legible font sizes

High

Tap targets are not sized appropriately

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 Servicestatus.tpg.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 Servicestatus.tpg.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

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