Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

vonex.com.au

Custom Business Phone & Internet Solutions | Vonex

Page Load Speed

6.7 sec in total

First Response

504 ms

Resources Loaded

5.7 sec

Page Rendered

484 ms

About Website

Click here to check amazing Vonex content for Australia. Otherwise, check out these important facts you probably never knew about vonex.com.au

Vonex provides custom built business phone and business internet solutions around Australia designed to keep businesses connected wherever they go.

Visit vonex.com.au

Key Findings

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

Performance Metrics

vonex.com.au performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

vonex.com.au

504 ms

vonex.com.au

1207 ms

gtm.js

80 ms

owl.carousel.min.css

238 ms

owl.theme.default.min.css

476 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 84% of them (67 requests) were addressed to the original Vonex.com.au, 8% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Vonex.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 857.7 kB (41%)

Content Size

2.1 MB

After Optimization

1.2 MB

In fact, the total size of Vonex.com.au main page is 2.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. 55% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 148.2 kB

  • Original 184.3 kB
  • After minification 180.7 kB
  • After compression 36.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. 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 148.2 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 63.0 kB

  • Original 1.0 MB
  • After minification 983.7 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. Vonex images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 377.4 kB

  • Original 555.3 kB
  • After minification 555.3 kB
  • After compression 177.9 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 377.4 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 269.1 kB

  • Original 316.9 kB
  • After minification 305.7 kB
  • After compression 47.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. Vonex.com.au needs all CSS files to be minified and compressed as it can save up to 269.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (75%)

Requests Now

65

After Optimization

16

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

Accessibility Review

vonex.com.au accessibility score

96

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

Heading elements are not in a sequentially-descending order

Best Practices

vonex.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

vonex.com.au SEO score

91

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vonex.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 Vonex.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 data is detected on the main page of Vonex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: