12.5 sec in total
5.3 sec
7 sec
174 ms
Click here to check amazing Wits Vuvuzela content for South Africa. Otherwise, check out these important facts you probably never knew about witsvuvuzela.com
Produced by Wits Journalism
Visit witsvuvuzela.comWe analyzed Witsvuvuzela.com page load time and found that the first response time was 5.3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
witsvuvuzela.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value8.0 s
3/100
25%
Value7.7 s
24/100
10%
Value360 ms
72/100
30%
Value0.063
97/100
15%
Value7.4 s
49/100
10%
5328 ms
81 ms
163 ms
201 ms
299 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 82% of them (70 requests) were addressed to the original Witsvuvuzela.com, 6% (5 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Witsvuvuzela.com.
Page size can be reduced by 1.6 MB (71%)
2.2 MB
647.0 kB
In fact, the total size of Witsvuvuzela.com 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 81.2 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 81.2 kB or 81% of the original size.
Potential reduce by 7.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. Wits Vuvuzela images are well optimized though.
Potential reduce by 733.4 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 733.4 kB or 73% of the original size.
Potential reduce by 729.5 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. Witsvuvuzela.com needs all CSS files to be minified and compressed as it can save up to 729.5 kB or 84% of the original size.
Number of requests can be reduced by 69 (83%)
83
14
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wits Vuvuzela. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
witsvuvuzela.com
5328 ms
webfont.js
81 ms
wp-emoji-release.min.js
163 ms
buttons.min.css
201 ms
dashicons.min.css
299 ms
mediaelementplayer.min.css
204 ms
wp-mediaelement.css
208 ms
media-views.min.css
207 ms
imgareaselect.css
249 ms
font-awesome.css
290 ms
polls-css.css
296 ms
style.css
296 ms
style.css
300 ms
easy-twitter-feed-widget.css
328 ms
font-awesome.min.css
371 ms
css
34 ms
css
54 ms
css
56 ms
bootstrap.min.css
382 ms
slick.css
379 ms
flexslider.css
375 ms
style.css
470 ms
styles.css
418 ms
magnific-popup.css
460 ms
js_composer.css
569 ms
jetpack.css
480 ms
jquery.js
598 ms
jquery-migrate.min.js
508 ms
utils.min.js
549 ms
plupload.full.min.js
662 ms
froogaloop.min.js
562 ms
flowplayer-3.2.10.min.js
618 ms
wpvp_flowplayer.js
648 ms
wpvp-front-end.js
677 ms
css
14 ms
js
26 ms
gmaps.js
699 ms
scripts.js
802 ms
underscore.min.js
802 ms
shortcode.min.js
803 ms
backbone.min.js
858 ms
wp-util.min.js
858 ms
devicepx-jetpack.js
6 ms
e-201611.js
6 ms
wp-backbone.min.js
851 ms
media-models.min.js
761 ms
wp-plupload.min.js
722 ms
core.min.js
717 ms
widget.min.js
759 ms
mouse.min.js
754 ms
sortable.min.js
719 ms
mediaelement-and-player.min.js
678 ms
wp-mediaelement.js
672 ms
media-views.min.js
682 ms
media-editor.min.js
756 ms
media-audiovideo.min.js
753 ms
polls-js.js
722 ms
bootstrap.min.js
681 ms
slick.js
683 ms
jquery.nicescroll.js
684 ms
grids.min.js
740 ms
jquery.flexslider.js
715 ms
jquery.form.min.js
672 ms
main.js
661 ms
widget-easy-twitter-feed-widget.js
656 ms
hoverIntent.min.js
633 ms
maxmegamenu.js
672 ms
wp-embed.min.js
662 ms
ga.js
26 ms
js_composer_front.js
631 ms
__utm.gif
257 ms
Kudu_logo3.jpg
718 ms
Ntandoyenkosi-570x381.jpg
741 ms
SoSS-banner-designed-FM-380x420.jpg
738 ms
image4-278x186.jpg
738 ms
__utm.gif
200 ms
css
165 ms
c73fe708-0559-4ff3-beca-ce53ddd20532-278x186.jpg
610 ms
fn-left.png
607 ms
fn-right.png
597 ms
fontawesome-webfont.woff
686 ms
fontawesome-webfont.woff
853 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
7 ms
widgets.js
288 ms
g.gif
10 ms
witsvuvuzela.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
witsvuvuzela.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
witsvuvuzela.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Witsvuvuzela.com 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 Witsvuvuzela.com 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.
witsvuvuzela.com
Open Graph data is detected on the main page of Wits Vuvuzela. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: