Tools & Wizards About Us
performaball.co.za screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

performaball.co.za

Afrihost - Fibre, Mobile, ADSL, VDSL and Web Hosting

Page Load Speed

9.9 sec in total

First Response

2.9 sec

Resources Loaded

6.8 sec

Page Rendered

242 ms

performaball.co.za screenshot

About Website

Visit performaball.co.za now to see the best up-to-date Performaball content and also check out these interesting facts you probably never knew about performaball.co.za

Get ADSL, VDSL, Cellular, Mobile Data, Fibre, Web Hosting & Domains, from Afrihost, South Africa's award-winning Broadband and Telecoms service provider

Visit performaball.co.za

Key Findings

We analyzed Performaball.co.za page load time and found that the first response time was 2.9 sec and then it took 7 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

performaball.co.za performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

performaball.co.za

2861 ms

stylesheet.css

1078 ms

responsive.css

856 ms

slideshow.css

857 ms

jquery-1.7.1.min.js

1139 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Performaball.co.za, 46% (32 requests) were made to Static.xx.fbcdn.net and 36% (25 requests) were made to Healthyfitness.co.za. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Performaball.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 322.4 kB (30%)

Content Size

1.1 MB

After Optimization

744.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Performaball.co.za main page is 1.1 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. Images take 648.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 11.9 kB

  • Original 15.2 kB
  • After minification 14.3 kB
  • After compression 3.3 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 11.9 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 9.9 kB

  • Original 648.7 kB
  • After minification 638.8 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. Performaball images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 239.4 kB

  • Original 330.1 kB
  • After minification 317.2 kB
  • After compression 90.7 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 239.4 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 61.2 kB

  • Original 72.6 kB
  • After minification 56.1 kB
  • After compression 11.4 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. Performaball.co.za needs all CSS files to be minified and compressed as it can save up to 61.2 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

performaball.co.za

performaball.co.za

2861 ms

stylesheet.css

stylesheet.css

1078 ms

responsive.css

responsive.css

856 ms

slideshow.css

slideshow.css

857 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1139 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

1409 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

862 ms

common.js

common.js

1135 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1154 ms

responsiveslides.css

responsiveslides.css

1154 ms

responsiveslides.js

responsiveslides.js

1781 ms

css

css

25 ms

bg.jpg

bg.jpg

1300 ms

menu2.png

menu2.png

332 ms

tiles.png

tiles.png

314 ms

facebook.png

facebook.png

285 ms

p_logo.jpg

p_logo.jpg

546 ms

yoss.png

yoss.png

1298 ms

arrow-down.png

arrow-down.png

592 ms

button-search.png

button-search.png

617 ms

menu.png

menu.png

905 ms

ad_1-980x280.jpg

ad_1-980x280.jpg

1351 ms

extra-980x280.jpg

extra-980x280.jpg

2485 ms

Gymnic-Classic-Plus_1-200x200.jpg

Gymnic-Classic-Plus_1-200x200.jpg

900 ms

Faster-Blaster_1-200x200.jpg

Faster-Blaster_1-200x200.jpg

1297 ms

IczWvq5y_Cwwv_rBjOtT0w.woff

IczWvq5y_Cwwv_rBjOtT0w.woff

32 ms

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

44 ms

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

59 ms

footer.png

footer.png

1059 ms

themes.png

themes.png

1021 ms

likebox.php

likebox.php

590 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

39 ms

wakJkBioHgT.css

wakJkBioHgT.css

54 ms

6qHpHChjY_J.css

6qHpHChjY_J.css

54 ms

ztINr5qMqM_.css

ztINr5qMqM_.css

41 ms

uVjHKJ0glvg.css

uVjHKJ0glvg.css

60 ms

ZY-3seVVf0G.css

ZY-3seVVf0G.css

71 ms

W9IvqTWpWa9.css

W9IvqTWpWa9.css

58 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

86 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

104 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

101 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

104 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

101 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

119 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

117 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

125 ms

1FCa-btixu2.js

1FCa-btixu2.js

124 ms

IjqSyiwKeaX.js

IjqSyiwKeaX.js

152 ms

yasHAKDGNFx.js

yasHAKDGNFx.js

156 ms

n6VgtouijQL.js

n6VgtouijQL.js

149 ms

7BE0CZr3HTs.js

7BE0CZr3HTs.js

149 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

151 ms

_UYztdBNTjs.js

_UYztdBNTjs.js

154 ms

kvx5eeRG4FE.js

kvx5eeRG4FE.js

170 ms

Nn19HjwCsOL.js

Nn19HjwCsOL.js

169 ms

270408_10151127106123927_969493257_n.jpg

270408_10151127106123927_969493257_n.jpg

160 ms

b8XhdWI9eAN.js

b8XhdWI9eAN.js

41 ms

11127486_10152848143003927_8955060425244286460_n.png

11127486_10152848143003927_8955060425244286460_n.png

22 ms

12800129_10153505184098927_4381314907157989625_n.jpg

12800129_10153505184098927_4381314907157989625_n.jpg

52 ms

12419474_10153502296428927_1826647114_n.jpg

12419474_10153502296428927_1826647114_n.jpg

38 ms

12419470_10153502261233927_1654749019_n.jpg

12419470_10153502261233927_1654749019_n.jpg

36 ms

12323339_10153499358743927_482428725_n.jpg

12323339_10153499358743927_482428725_n.jpg

46 ms

12720245_10153496967568927_1085308033_n.jpg

12720245_10153496967568927_1085308033_n.jpg

104 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

20 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

18 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

19 ms

l5aPruN9xMM.png

l5aPruN9xMM.png

21 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

21 ms

K_65vAc89SX.png

K_65vAc89SX.png

23 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

5 ms

Accessibility Review

performaball.co.za accessibility score

89

Accessibility Issues

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

Best Practices

performaball.co.za best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

performaball.co.za SEO score

64

Search Engine Optimization Advices

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 Performaball.co.za 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 Performaball.co.za 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

performaball.co.za

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