Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

vivides.com.au

Xero Small Business Bookkeeping Services | Melbourne, Victoria

Page Load Speed

3.2 sec in total

First Response

941 ms

Resources Loaded

2.2 sec

Page Rendered

57 ms

About Website

Visit vivides.com.au now to see the best up-to-date Vivides content and also check out these interesting facts you probably never knew about vivides.com.au

Do you want a faster and smarter way to do your bookkeeping? We're here to help you streamline your processes. Book in a FREE consult or call 03 9069 5552

Visit vivides.com.au

Key Findings

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

Performance Metrics

vivides.com.au performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value5,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

www.vivides.com.au

941 ms

originTrials.41d7301a.bundle.min.js

34 ms

minified.js

37 ms

focus-within-polyfill.js

73 ms

polyfill.min.js

435 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Vivides.com.au, 43% (19 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Vivides.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.6 kB (33%)

Content Size

1.3 MB

After Optimization

873.6 kB

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

HTML Optimization

-78%

Potential reduce by 357.3 kB

  • Original 456.9 kB
  • After minification 455.3 kB
  • After compression 99.7 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 357.3 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 16.7 kB

  • Original 555.1 kB
  • After minification 538.4 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. Vivides images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 62.6 kB

  • Original 298.1 kB
  • After minification 298.1 kB
  • After compression 235.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 62.6 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (44%)

Requests Now

25

After Optimization

14

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

Accessibility Review

vivides.com.au accessibility score

98

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.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vivides.com.au SEO score

100

Search Engine Optimization Advices

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

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 Vivides.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 Vivides.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 Vivides. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: