Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

3.1 sec in total

First Response

914 ms

Resources Loaded

2.1 sec

Page Rendered

67 ms

ozgo.com.au screenshot

About Website

Click here to check amazing Ozgo content. Otherwise, check out these important facts you probably never knew about ozgo.com.au

Visit ozgo.com.au

Key Findings

We analyzed Ozgo.com.au page load time and found that the first response time was 914 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

ozgo.com.au performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

ozgo.com.au

914 ms

home

934 ms

263 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Ozgo.com.au and no external sources were called. The less responsive or slowest element that took the longest time to load (934 ms) belongs to the original domain Ozgo.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.5 kB (14%)

Content Size

567.3 kB

After Optimization

489.8 kB

In fact, the total size of Ozgo.com.au main page is 567.3 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 376.3 kB which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 152 B

  • Original 377 B
  • After minification 374 B
  • After compression 225 B

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 152 B or 40% of the original size.

Image Optimization

-4%

Potential reduce by 14.6 kB

  • Original 376.3 kB
  • After minification 361.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. Ozgo images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 21.5 kB

  • Original 136.2 kB
  • After minification 136.2 kB
  • After compression 114.7 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 21.5 kB or 16% of the original size.

CSS Optimization

-76%

Potential reduce by 41.2 kB

  • Original 54.4 kB
  • After minification 37.9 kB
  • After compression 13.2 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. Ozgo.com.au needs all CSS files to be minified and compressed as it can save up to 41.2 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

ozgo.com.au accessibility score

68

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

Document doesn't have a <title> element

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

Best Practices

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

SEO Factors

ozgo.com.au SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozgo.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 Ozgo.com.au main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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