Tools & Wizards About Us
gauteng.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gauteng.com

Gauteng Events, Gauteng tourism, gauteng information, accommodation, travel, tourism, events, training, etc

Page Load Speed

6 sec in total

First Response

1.3 sec

Resources Loaded

4.1 sec

Page Rendered

518 ms

gauteng.com screenshot

About Website

Click here to check amazing Gauteng content for South Africa. Otherwise, check out these important facts you probably never knew about gauteng.com

Gauteng Events, Gauteng tourism and gauteng information with tour, travel, accommodation, esp covering Pretoria and Johannesburg

Visit gauteng.com

Key Findings

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

Performance Metrics

gauteng.com performance score

0

Network Requests Diagram

gauteng.com

1340 ms

wp-emoji-release.min.js

790 ms

style.css

542 ms

css

26 ms

css

39 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 80% of them (35 requests) were addressed to the original Gauteng.com, 16% (7 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Gauteng.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 553.6 kB (43%)

Content Size

1.3 MB

After Optimization

721.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gauteng.com main page is 1.3 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. 50% of websites need less resources to load. Images take 619.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 33.8 kB

  • Original 40.6 kB
  • After minification 36.9 kB
  • After compression 6.8 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 33.8 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 28.6 kB

  • Original 619.8 kB
  • After minification 591.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. Gauteng images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 175.2 kB

  • Original 250.0 kB
  • After minification 248.4 kB
  • After compression 74.8 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 175.2 kB or 70% of the original size.

CSS Optimization

-87%

Potential reduce by 315.9 kB

  • Original 364.6 kB
  • After minification 340.7 kB
  • After compression 48.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. Gauteng.com needs all CSS files to be minified and compressed as it can save up to 315.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (43%)

Requests Now

35

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gauteng.com

gauteng.com

1340 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

790 ms

style.css

style.css

542 ms

css

css

26 ms

css

css

39 ms

font-awesome.min.css

font-awesome.min.css

801 ms

bootstrap.min.css

bootstrap.min.css

1350 ms

hover.min.css

hover.min.css

1360 ms

slicknav.css

slicknav.css

542 ms

swiper.min.css

swiper.min.css

808 ms

default.css

default.css

1620 ms

jquery.js

jquery.js

1325 ms

jquery-migrate.min.js

jquery-migrate.min.js

1065 ms

external.js

external.js

1618 ms

custom.js

custom.js

1330 ms

navigation.js

navigation.js

1319 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

1333 ms

wp-embed.min.js

wp-embed.min.js

1351 ms

Training_ICON-4.png

Training_ICON-4.png

275 ms

training.png

training.png

784 ms

logotrans-600x600.png

logotrans-600x600.png

814 ms

trifocus.png

trifocus.png

287 ms

logo_smal2l-1.jpg

logo_smal2l-1.jpg

284 ms

claires_logo-1.png

claires_logo-1.png

800 ms

clinix.png

clinix.png

509 ms

camelot.png

camelot.png

542 ms

jcci-1.png

jcci-1.png

554 ms

inscape_logo-1.png

inscape_logo-1.png

781 ms

sastm-logo.jpg

sastm-logo.jpg

851 ms

Wits-Planetarium.jpg

Wits-Planetarium.jpg

842 ms

elite.jpg

elite.jpg

1063 ms

SATS.jpg

SATS.jpg

1057 ms

labour.jpg

labour.jpg

1075 ms

new_intelligence.png

new_intelligence.png

1102 ms

stat.jpg

stat.jpg

1120 ms

logo.jpg-instance.jpg

logo.jpg-instance.jpg

1123 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

28 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

51 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

88 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

89 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

87 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

88 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

87 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1101 ms

SEO Factors

gauteng.com SEO score

0

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 Gauteng.com 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 Gauteng.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.

Social Sharing Optimization

gauteng.com

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