Tools & Wizards About Us
buhlewaste.co.za screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

buhlewaste.co.za

Buhle Waste

Page Load Speed

12.9 sec in total

First Response

4.5 sec

Resources Loaded

8.3 sec

Page Rendered

101 ms

buhlewaste.co.za screenshot

About Website

Welcome to buhlewaste.co.za homepage info - get ready to check Buhle Waste best content right away, or after learning these important things about buhlewaste.co.za

Visit buhlewaste.co.za

Key Findings

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

buhlewaste.co.za performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

buhlewaste.co.za

4505 ms

analytics.js

421 ms

autotrack.ca946afc.js

793 ms

wp-emoji-release.min.js

460 ms

style.min.css

293 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 61% of them (23 requests) were addressed to the original Buhlewaste.co.za, 26% (10 requests) were made to C0.wp.com and 13% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Buhlewaste.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.0 kB (68%)

Content Size

622.4 kB

After Optimization

197.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buhlewaste.co.za main page is 622.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. CSS take 466.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 56.8 kB

  • Original 69.1 kB
  • After minification 68.5 kB
  • After compression 12.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 56.8 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 18 B

  • Original 974 B
  • After minification 956 B

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

JavaScript Optimization

-0%

Potential reduce by 381 B

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

CSS Optimization

-79%

Potential reduce by 367.8 kB

  • Original 466.9 kB
  • After minification 432.4 kB
  • After compression 99.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. Buhlewaste.co.za needs all CSS files to be minified and compressed as it can save up to 367.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (83%)

Requests Now

36

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buhlewaste.co.za

buhlewaste.co.za

4505 ms

analytics.js

analytics.js

421 ms

autotrack.ca946afc.js

autotrack.ca946afc.js

793 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

460 ms

style.min.css

style.min.css

293 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

264 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

291 ms

styles.css

styles.css

521 ms

settings.css

settings.css

873 ms

be.css

be.css

2412 ms

animations.min.css

animations.min.css

1129 ms

fontawesome.css

fontawesome.css

954 ms

jplayer.blue.monday.min.css

jplayer.blue.monday.min.css

704 ms

responsive.css

responsive.css

1175 ms

style.css

style.css

926 ms

linkid.js

linkid.js

78 ms

jetpack.css

jetpack.css

80 ms

jquery.min.js

jquery.min.js

112 ms

jquery-migrate.min.js

jquery-migrate.min.js

112 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1416 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1190 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

135 ms

wp-polyfill.min.js

wp-polyfill.min.js

127 ms

index.js

index.js

980 ms

core.min.js

core.min.js

134 ms

tabs.min.js

tabs.min.js

135 ms

plugins.js

plugins.js

1677 ms

menu.js

menu.js

1202 ms

animations.min.js

animations.min.js

1236 ms

jplayer.min.js

jplayer.min.js

1429 ms

translate3d.js

translate3d.js

1442 ms

scripts.js

scripts.js

1735 ms

collect

collect

38 ms

ga.js

ga.js

6 ms

buhle_waste_logo.png

buhle_waste_logo.png

1512 ms

stripes_3_b.png

stripes_3_b.png

258 ms

__utm.gif

__utm.gif

35 ms

icons.woff

icons.woff

716 ms

Accessibility Review

buhlewaste.co.za accessibility score

82

Accessibility Issues

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

buhlewaste.co.za best practices score

92

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

SEO Factors

buhlewaste.co.za SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

buhlewaste.co.za

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