Tools & Wizards About Us
mywiwe.com.au screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

mywiwe.com.au

whizzy IT with sophisticated new and clever technology to drive your business with IT solutions and services by Globo Logic.

Page Load Speed

7.5 sec in total

First Response

714 ms

Resources Loaded

6 sec

Page Rendered

713 ms

mywiwe.com.au screenshot

About Website

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

whizzy IT with sophisticated new and clever technology to drive your business with IT solutions and services by Globo Logic.

Visit mywiwe.com.au

Key Findings

We analyzed Mywiwe.com.au page load time and found that the first response time was 714 ms and then it took 6.8 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

mywiwe.com.au performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

mywiwe.com.au

714 ms

globologic.com

1151 ms

css

29 ms

css

40 ms

css

45 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mywiwe.com.au, 82% (73 requests) were made to Globologic.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Globologic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.3 kB (6%)

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 83.1 kB

  • Original 91.9 kB
  • After minification 51.5 kB
  • After compression 8.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 40.4 kB, which is 44% 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 83.1 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 99.3 kB

  • Original 2.7 MB
  • After minification 2.6 MB

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. Mywiwe images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

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

CSS Optimization

-13%

Potential reduce by 13.7 kB

  • Original 101.8 kB
  • After minification 101.8 kB
  • After compression 88.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. Mywiwe.com.au needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (47%)

Requests Now

79

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mywiwe.com.au

mywiwe.com.au

714 ms

globologic.com

globologic.com

1151 ms

css

css

29 ms

css

css

40 ms

css

css

45 ms

css

css

46 ms

global.css

global.css

458 ms

structure.css

structure.css

896 ms

wallet.css

wallet.css

709 ms

custom.css

custom.css

675 ms

js

js

61 ms

settings.css

settings.css

675 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

1030 ms

jquery-migrate-3.4.0.min.js

jquery-migrate-3.4.0.min.js

718 ms

mfn.menu.js

mfn.menu.js

1056 ms

jquery.plugins.js

jquery.plugins.js

1588 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

1031 ms

animations.js

animations.js

1032 ms

translate3d.js

translate3d.js

1119 ms

scripts.js

scripts.js

1376 ms

scroll.js

scroll.js

1164 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1175 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1466 ms

revolution.extension.video.min.js

revolution.extension.video.min.js

1343 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

1376 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

1384 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

1557 ms

revolution.extension.kenburn.min.js

revolution.extension.kenburn.min.js

1626 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

1626 ms

revolution.extension.migration.min.js

revolution.extension.migration.min.js

1628 ms

revolution.extension.parallax.min.js

revolution.extension.parallax.min.js

1678 ms

js

js

138 ms

analytics.js

analytics.js

132 ms

retina-logo.png

retina-logo.png

820 ms

logo-text.png

logo-text.png

849 ms

logo.png

logo.png

1489 ms

box_shadow.png

box_shadow.png

855 ms

home_wallet_slider_bg.jpg

home_wallet_slider_bg.jpg

1073 ms

digital.png

digital.png

1794 ms

solutions.png

solutions.png

1031 ms

services.png

services.png

1072 ms

home_wallet_iconbox1.png

home_wallet_iconbox1.png

1075 ms

home_wallet_iconbox2.png

home_wallet_iconbox2.png

1252 ms

home_wallet_iconbox3.png

home_wallet_iconbox3.png

1286 ms

home_wallet_iconbox4.png

home_wallet_iconbox4.png

1288 ms

home_wallet_iconbox5.png

home_wallet_iconbox5.png

1289 ms

home_wallet_iconbox6.png

home_wallet_iconbox6.png

1465 ms

home_wallet_iconbox7.png

home_wallet_iconbox7.png

1499 ms

home_wallet_iconbox8.png

home_wallet_iconbox8.png

1500 ms

home_wallet_iconbox9.png

home_wallet_iconbox9.png

1503 ms

gl-qr.png

gl-qr.png

1607 ms

home_wallet_bgsection1.png

home_wallet_bgsection1.png

1626 ms

acscpartners.png

acscpartners.png

1852 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

70 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

90 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

112 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

110 ms

mfn-icons.woff

mfn-icons.woff

1831 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

110 ms

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

111 ms

cyberbiz-logo.png

cyberbiz-logo.png

1839 ms

collect

collect

45 ms

slide14.jpg

slide14.jpg

1942 ms

collect

collect

45 ms

nfp-solutions.jpg

nfp-solutions.jpg

1909 ms

retail-solutions.jpg

retail-solutions.jpg

1772 ms

sme-solutions.jpg

sme-solutions.jpg

1969 ms

ciobiz-logo.png

ciobiz-logo.png

1723 ms

ictbiz-logo.png

ictbiz-logo.png

1731 ms

services_cio.jpg

services_cio.jpg

1795 ms

services_backup.jpg

services_backup.jpg

2019 ms

services_audit.jpg

services_audit.jpg

1737 ms

services_nbn.jpg

services_nbn.jpg

1687 ms

services_networking.jpg

services_networking.jpg

2123 ms

services_software.jpg

services_software.jpg

1766 ms

bitdefender.jpg

bitdefender.jpg

1881 ms

cisco.jpg

cisco.jpg

1847 ms

revolution.extension.actions.min.js

revolution.extension.actions.min.js

1753 ms

dell.webp

dell.webp

1807 ms

404.php

404.php

1895 ms

lenovo.jpg

lenovo.jpg

1740 ms

microsoft.jpg

microsoft.jpg

1714 ms

polycom.jpg

polycom.jpg

1715 ms

seagate.jpg

seagate.jpg

1794 ms

symantec.jpg

symantec.jpg

1709 ms

veeam.jpg

veeam.jpg

1700 ms

vipre.jpg

vipre.jpg

1714 ms

home_wallet_bgsection2.jpg

home_wallet_bgsection2.jpg

1927 ms

logo_bottom.png

logo_bottom.png

1760 ms

Accessibility Review

mywiwe.com.au accessibility score

39

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

mywiwe.com.au best practices score

75

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mywiwe.com.au SEO score

84

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

mywiwe.com.au

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