Tools & Wizards About Us
woza.io screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

woza.io

Register Domains – CO.ZA @ R70 – Cheapest - Domains South Africa

Page Load Speed

12 sec in total

First Response

4.7 sec

Resources Loaded

6.5 sec

Page Rendered

733 ms

woza.io screenshot

About Website

Click here to check amazing Wo ZA content for Kenya. Otherwise, check out these important facts you probably never knew about woza.io

Register CO.ZA Domain from Best Wordpress WebHosting from Truehost Africa. Website Builder and Hosting Better than WIX.

Visit woza.io

Key Findings

We analyzed Woza.io page load time and found that the first response time was 4.7 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

woza.io performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

truehost.co.za

4749 ms

js

89 ms

style.min.css

66 ms

blocks.style.build.css

54 ms

style.css

122 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Woza.io, 11% (9 requests) were made to Cdnjs.cloudflare.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Truehost.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.1 kB (21%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Woza.io main page is 1.6 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. 80% 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. Javascripts take 564.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 111.6 kB

  • Original 134.6 kB
  • After minification 134.6 kB
  • After compression 23.0 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 111.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 528.9 kB
  • After minification 527.6 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. Wo ZA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.3 kB

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

CSS Optimization

-57%

Potential reduce by 226.9 kB

  • Original 395.0 kB
  • After minification 344.9 kB
  • After compression 168.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. Woza.io needs all CSS files to be minified and compressed as it can save up to 226.9 kB or 57% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

truehost.co.za

truehost.co.za

4749 ms

js

js

89 ms

style.min.css

style.min.css

66 ms

blocks.style.build.css

blocks.style.build.css

54 ms

style.css

style.css

122 ms

slick.css

slick.css

119 ms

bdp-public.css

bdp-public.css

218 ms

fontawesome-all.min.css

fontawesome-all.min.css

122 ms

designer_css.css

designer_css.css

67 ms

style.css

style.css

199 ms

style.css

style.css

220 ms

titan-framework-wdc-options-css.css

titan-framework-wdc-options-css.css

219 ms

style.css

style.css

129 ms

bootstrap.min.css

bootstrap.min.css

207 ms

theme.min.css

theme.min.css

220 ms

freak_flags.css

freak_flags.css

214 ms

bootstrap-icons.css

bootstrap-icons.css

226 ms

css

css

62 ms

frontend-gtag.min.js

frontend-gtag.min.js

164 ms

jquery.min.js

jquery.min.js

179 ms

jquery-migrate.min.js

jquery-migrate.min.js

178 ms

imagesloaded.min.js

imagesloaded.min.js

182 ms

masonry.min.js

masonry.min.js

165 ms

ticker.min.js

ticker.min.js

184 ms

designer.js

designer.js

188 ms

chatwoot.js

chatwoot.js

179 ms

priority-menu.js

priority-menu.js

178 ms

email-decode.min.js

email-decode.min.js

12 ms

fontawesome-all.min.css

fontawesome-all.min.css

178 ms

style-min.css

style-min.css

188 ms

touch-keyboard-navigation.js

touch-keyboard-navigation.js

176 ms

index.js

index.js

177 ms

bootstrap.min.js

bootstrap.min.js

188 ms

main.min.js

main.min.js

178 ms

tween.umd.js

tween.umd.js

188 ms

client-counter.js

client-counter.js

179 ms

geo-location-popup.js

geo-location-popup.js

187 ms

ads.js

ads.js

187 ms

velocity.min.js

velocity.min.js

183 ms

floatMenu-min.js

floatMenu-min.js

183 ms

css2

css2

43 ms

print.css

print.css

84 ms

sdk.js

sdk.js

586 ms

logo.png

logo.png

49 ms

cloudflare-logo.png

cloudflare-logo.png

47 ms

cloudlinux-logo.png

cloudlinux-logo.png

54 ms

litespeed-logo.png

litespeed-logo.png

45 ms

wordpress-logo.png

wordpress-logo.png

47 ms

easy-to-set-up-1024x682.jpg

easy-to-set-up-1024x682.jpg

49 ms

10x-faster.png

10x-faster.png

52 ms

10x-ssd.png

10x-ssd.png

55 ms

24-7-support-1024x683.jpg

24-7-support-1024x683.jpg

54 ms

fast-1-1024x682.jpg

fast-1-1024x682.jpg

55 ms

Untitled-design.png

Untitled-design.png

51 ms

polyfill.min.js

polyfill.min.js

164 ms

flagSprite42.png

flagSprite42.png

134 ms

worryfreecloud-min.jpeg

worryfreecloud-min.jpeg

134 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXNis.woff

112 ms

font

font

200 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXNis.woff

234 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNis.woff

234 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNis.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QNis.woff

234 ms

fa-regular-400.ttf

fa-regular-400.ttf

38 ms

fa-solid-900.woff

fa-solid-900.woff

38 ms

fa-solid-900.ttf

fa-solid-900.ttf

109 ms

fa-brands-400.woff

fa-brands-400.woff

109 ms

fa-brands-400.ttf

fa-brands-400.ttf

38 ms

callpage.js

callpage.js

260 ms

fa-solid-900.ttf

fa-solid-900.ttf

77 ms

fa-regular-400.ttf

fa-regular-400.ttf

74 ms

fa-brands-400.ttf

fa-brands-400.ttf

75 ms

vue.min.js

vue.min.js

13 ms

vuex.min.js

vuex.min.js

12 ms

vue-router.min.js

vue-router.min.js

15 ms

raven.min.js

raven.min.js

36 ms

widget

widget

340 ms

vue.min.js

vue.min.js

15 ms

vue-i18n.min.js

vue-i18n.min.js

9 ms

popper.min.js

popper.min.js

10 ms

jstz.min.js

jstz.min.js

18 ms

widget-0e7ed9608d48f1509d55.js

widget-0e7ed9608d48f1509d55.js

468 ms

widget-f4552c72.css

widget-f4552c72.css

365 ms

Accessibility Review

woza.io accessibility score

93

Accessibility Issues

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

button, link, and menuitem elements do not have accessible names.

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

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

Links do not have a discernible name

Best Practices

woza.io 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

Page has valid source maps

SEO Factors

woza.io SEO score

93

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

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 Woza.io 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 Woza.io 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

woza.io

Open Graph data is detected on the main page of Wo ZA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: