Tools & Wizards About Us
wiza.ug screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wiza.ug

HOME - Wiza Limited - IT solutions in Uganda

Page Load Speed

19.5 sec in total

First Response

317 ms

Resources Loaded

18.7 sec

Page Rendered

524 ms

wiza.ug screenshot

About Website

Visit wiza.ug now to see the best up-to-date Wiza content for Uganda and also check out these interesting facts you probably never knew about wiza.ug

Wiza Limited is Uganda’s leading System Design, Mobile apps design, SEO & website design company in Kampala -Uganda

Visit wiza.ug

Key Findings

We analyzed Wiza.ug page load time and found that the first response time was 317 ms and then it took 19.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

wiza.ug performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value21.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.969

2/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

wiza.ug

317 ms

wiza.ug

16490 ms

css

31 ms

js

67 ms

style.min.css

434 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 71% of them (64 requests) were addressed to the original Wiza.ug, 13% (12 requests) were made to Embed.tawk.to and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (16.5 sec) belongs to the original domain Wiza.ug.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (62%)

Content Size

2.2 MB

After Optimization

829.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wiza.ug main page is 2.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. 60% of websites need less resources to load. CSS take 985.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 155.9 kB

  • Original 189.9 kB
  • After minification 168.4 kB
  • After compression 34.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. This page needs HTML code to be minified as it can gain 21.5 kB, which is 11% 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 155.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 514 B

  • Original 170.8 kB
  • After minification 170.2 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. Wiza images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 368.9 kB

  • Original 814.9 kB
  • After minification 809.5 kB
  • After compression 446.0 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 368.9 kB or 45% of the original size.

CSS Optimization

-82%

Potential reduce by 806.8 kB

  • Original 985.4 kB
  • After minification 931.4 kB
  • After compression 178.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. Wiza.ug needs all CSS files to be minified and compressed as it can save up to 806.8 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

82

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wiza.ug

wiza.ug

317 ms

wiza.ug

wiza.ug

16490 ms

css

css

31 ms

js

js

67 ms

style.min.css

style.min.css

434 ms

view.css

view.css

299 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

308 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

305 ms

styles.css

styles.css

306 ms

dashicons.min.css

dashicons.min.css

550 ms

frontend.min.css

frontend.min.css

395 ms

frontend.min.css

frontend.min.css

403 ms

frontend-lite.min.css

frontend-lite.min.css

699 ms

swiper.min.css

swiper.min.css

403 ms

post-3873.css

post-3873.css

495 ms

all.min.css

all.min.css

702 ms

v4-shims.min.css

v4-shims.min.css

502 ms

global.css

global.css

539 ms

post-10.css

post-10.css

692 ms

css

css

28 ms

bootstrap.min.css

bootstrap.min.css

798 ms

font-awesome.min.css

font-awesome.min.css

648 ms

animate.css

animate.css

656 ms

iconfont.css

iconfont.css

757 ms

isotope.css

isotope.css

765 ms

magnific-popup.css

magnific-popup.css

791 ms

owl.carousel.min.css

owl.carousel.min.css

795 ms

owl.theme.default.min.css

owl.theme.default.min.css

795 ms

woocommerce.css

woocommerce.css

867 ms

blog.css

blog.css

874 ms

gutenberg-custom.css

gutenberg-custom.css

890 ms

master.css

master.css

992 ms

style.css

style.css

779 ms

general.min.css

general.min.css

780 ms

css

css

18 ms

jetpack.css

jetpack.css

969 ms

frontend-gtag.min.js

frontend-gtag.min.js

867 ms

v4-shims.min.js

v4-shims.min.js

874 ms

jquery.min.js

jquery.min.js

983 ms

jquery-migrate.min.js

jquery-migrate.min.js

885 ms

wpstg-blank-loader.js

wpstg-blank-loader.js

1000 ms

e-202410.js

e-202410.js

23 ms

animations.min.css

animations.min.css

977 ms

index.js

index.js

858 ms

index.js

index.js

850 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

941 ms

bootstrap.min.js

bootstrap.min.js

944 ms

popper.min.js

popper.min.js

862 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

853 ms

jquery.countdown.min.js

jquery.countdown.min.js

852 ms

jquery.appear.min.js

jquery.appear.min.js

823 ms

jquery-mixtub.js

jquery-mixtub.js

838 ms

owl.carousel.min.js

owl.carousel.min.js

819 ms

script.js

script.js

781 ms

general.min.js

general.min.js

773 ms

webpack.runtime.min.js

webpack.runtime.min.js

669 ms

frontend-modules.min.js

frontend-modules.min.js

685 ms

waypoints.min.js

waypoints.min.js

727 ms

core.min.js

core.min.js

724 ms

frontend.min.js

frontend.min.js

724 ms

elementor.js

elementor.js

668 ms

underscore.min.js

underscore.min.js

675 ms

wp-util.min.js

wp-util.min.js

649 ms

frontend.min.js

frontend.min.js

723 ms

launcher.js

launcher.js

140 ms

gt.jpg

gt.jpg

400 ms

font

font

67 ms

font

font

67 ms

iconfont.ttf

iconfont.ttf

400 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

424 ms

default

default

221 ms

wizalogo1.png

wizalogo1.png

306 ms

fa-brands-400.woff

fa-brands-400.woff

303 ms

5f8da54f1820124f91978708

5f8da54f1820124f91978708

197 ms

details

details

241 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

58 ms

twk-event-polyfill.js

twk-event-polyfill.js

111 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

99 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

99 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

289 ms

twk-main.js

twk-main.js

111 ms

twk-vendor.js

twk-vendor.js

64 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

75 ms

twk-chunk-common.js

twk-chunk-common.js

87 ms

twk-runtime.js

twk-runtime.js

96 ms

twk-app.js

twk-app.js

170 ms

minified.js

minified.js

76 ms

widget.js

widget.js

53 ms

a3.png

a3.png

161 ms

font

font

32 ms

Accessibility Review

wiza.ug accessibility score

83

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

[aria-hidden="true"] elements contain focusable descendents

High

ARIA progressbar 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.

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

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

wiza.ug 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wiza.ug SEO score

86

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

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 Wiza.ug 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 Wiza.ug 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

wiza.ug

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