16.5 sec in total
3.8 sec
11.8 sec
988 ms
Visit joburg.co.za now to see the best up-to-date Joburg content for South Africa and also check out these interesting facts you probably never knew about joburg.co.za
Nowhere to go? Know where to go!
Visit joburg.co.zaWe analyzed Joburg.co.za page load time and found that the first response time was 3.8 sec and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
joburg.co.za performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.3 s
11/100
25%
Value5.4 s
57/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value5.8 s
66/100
10%
3756 ms
40 ms
13 ms
520 ms
75 ms
Our browser made a total of 203 requests to load all elements on the main page. We found that 46% of them (93 requests) were addressed to the original Joburg.co.za, 7% (14 requests) were made to Static.xx.fbcdn.net and 4% (9 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Joburg.co.za.
Page size can be reduced by 1.9 MB (34%)
5.7 MB
3.7 MB
In fact, the total size of Joburg.co.za main page is 5.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 288.5 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 288.5 kB or 87% of the original size.
Potential reduce by 307.4 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. Joburg images are well optimized though.
Potential reduce by 952.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 952.8 kB or 72% of the original size.
Potential reduce by 398.0 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. Joburg.co.za needs all CSS files to be minified and compressed as it can save up to 398.0 kB or 84% of the original size.
Number of requests can be reduced by 112 (59%)
189
77
The browser has sent 189 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Joburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.joburg.co.za
3756 ms
css
40 ms
shareaholic.js
13 ms
awesome-weather.css
520 ms
css
75 ms
frontend.css
522 ms
styles.css
532 ms
wpcloudy.min.css
534 ms
jquery.mmenu.all.css
536 ms
fullcalendar.min.css
12 ms
flexslider.css
783 ms
jquery-ui.css
784 ms
font-awesome.min.css
10 ms
style.css
793 ms
bootstrap.css
1047 ms
responsive-nav.css
798 ms
admin_style.min.css
798 ms
jquery.js
1309 ms
jquery-migrate.min.js
1061 ms
jquery.simpleWeather.min.js
1060 ms
jquery.flexslider-min.js
1064 ms
select.js
1062 ms
js.cookie.js
1314 ms
jquery-ui.min.js
1318 ms
jquery.mmenu.all.min.js
1319 ms
js
93 ms
moment.min.js
1327 ms
fullcalendar.js
48 ms
bootstrap.min.js
1326 ms
responsive-nav.min.js
1567 ms
horizontal-slim-10_7.css
47 ms
wp-emoji-release.min.js
1536 ms
943881c2324287359c4469cff03a8d5d.json
58 ms
eif_style.css
1339 ms
formreset.min.css
1347 ms
datepicker.min.css
1350 ms
formsmain.min.css
1348 ms
readyclass.min.css
1598 ms
browsers.min.css
1602 ms
jquery.adrotate.clicktracker.js
1604 ms
awesome-weather-widget-frontend.js
1611 ms
js-cookie.js
1609 ms
jquery.form.min.js
1612 ms
scripts.js
1857 ms
ssba.min.js
1859 ms
wp-cloudy-ajax.js
1597 ms
main.js
1603 ms
navigation.js
1597 ms
skip-link-focus-fix.js
1593 ms
wp-embed.min.js
1844 ms
easy-feed.js
1840 ms
core.min.js
1597 ms
datepicker.min.js
1696 ms
style.css
1590 ms
jquery.json.js
1694 ms
gravityforms.min.js
1946 ms
datepicker.min.js
1686 ms
jquery.maskedinput.min.js
1685 ms
analytics.js
39 ms
LoadResource.ashx
2026 ms
joburg_logo.png
365 ms
Joburg_Wallpaper.jpg
2553 ms
Johannesburg-Slider-1.jpg
2562 ms
Slider_02-3.jpg
1768 ms
vday2-2.jpg
1775 ms
Slider_03-2.jpg
1814 ms
Slider_01-2.jpg
1922 ms
logo-2-150x150.jpg
2033 ms
img_3147-150x150.jpg
2040 ms
FotorCreated-14-150x150.jpg
2209 ms
italia-150x150.jpg
2232 ms
free-yoga-150x150.png
2557 ms
Juicers-150x150.jpg
2305 ms
FotorCreated-12-150x150.jpg
2357 ms
23-Fix-It-Hacks-You-Will-Want-To-Share-On-Facebook-150x150.jpg
2505 ms
magnum1-150x150.jpg
2574 ms
landscape-1450716655-gettyimages-sb10065823b-001-150x150.jpg
2627 ms
BWLogo-Green-JPEG-150x150.jpg
2776 ms
InnerCity-Shopping-150x150.jpg
2811 ms
Fugard.gif
2817 ms
123.jpg
2832 ms
Kingfisher-1.jpg
3096 ms
Edible.jpg
3654 ms
FotorCreated1-2.jpg
3301 ms
5585756069_ab025f02d5_b.jpg
3340 ms
StudentAccommodation.jpg
3853 ms
943919_987329688026916_3454875782887516933_n.jpg
3101 ms
ddlogo.png
3365 ms
Amaizing.png-2.png
4378 ms
Healthyfood.jpeg
3826 ms
protea.png
3622 ms
surfingheader2.jpg
3632 ms
sdk.js
254 ms
gpt.js
23 ms
jd-white.png
3886 ms
shrMain.min.js
18 ms
collect
50 ms
pubads_impl_81.js
48 ms
jquery.min.js
45 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
110 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
202 ms
fontawesome-webfont.woff
104 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
209 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
323 ms
ads
224 ms
container.html
105 ms
artill_clean_icons-webfont.woff
3650 ms
weathericons-regular-webfont.woff
3683 ms
ctd-white.png
3844 ms
tripadvisor.png
3770 ms
pageview.gif
134 ms
2214758150989295396
799 ms
1431324433792361337
751 ms
15106878439473199142
783 ms
16208208044753035667
785 ms
widgets.js
704 ms
osd.js
678 ms
830 ms
vglnk.js
645 ms
partners.js
689 ms
xd_arbiter.php
735 ms
xd_arbiter.php
903 ms
353 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
163 ms
pixel.gif
25 ms
pixel.gif
24 ms
page.php
261 ms
sholic.js
29 ms
usermatch
62 ms
beacon.js
58 ms
cms-sh2c.html
105 ms
12424650_1583610781964090_1001470231_n.jpg
52 ms
eexelate.js
25 ms
26 ms
12750314_1525760227720858_1911312586_n.jpg
73 ms
12797805_451567351708429_155202001_n.jpg
115 ms
12750375_1657700841121371_2018811192_n.jpg
120 ms
usermatch
21 ms
ep
29 ms
ep
30 ms
VtR6hMAoJG4AAAiB97oAAAHg%26391
246 ms
csle
170 ms
pm_match
132 ms
i.gif
175 ms
pixelssl.htm
213 ms
pixel
92 ms
ping_match.gif
82 ms
137 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
77 ms
casale
73 ms
2964
145 ms
rum
133 ms
rum
143 ms
d5xjefPVHuZ.css
217 ms
6nlzH2Enh9a.css
258 ms
_rx8naC75Dy.js
377 ms
t-KLv3gqZy0.js
330 ms
uLtKx7ldlvR.js
443 ms
wyIfBc7KBcg.js
415 ms
wFYNJ9lyaMJ.js
419 ms
Xs81m_2832G.js
417 ms
crum
134 ms
rum
139 ms
check
50 ms
pixel
124 ms
net.php
40 ms
rum
86 ms
ddcssl.htm
150 ms
rs
79 ms
cfcm.ashx
43 ms
jot
133 ms
match-result
50 ms
flexslider-icon.woff
2402 ms
pixel.gif
28 ms
pixel.gif
24 ms
VMLogo1.png
2408 ms
52154.gif
13 ms
crum
12 ms
ping
31 ms
xrefid.xgi
7 ms
domains
48 ms
DMMA_member2.png
2445 ms
bb_extop_cloud_bg.jpg
2362 ms
bg_Footer.png
2398 ms
12734268_1235428396486596_4557764692273856425_n.jpg
115 ms
556689_546623402033769_1775169596_n.jpg
115 ms
1234702_404875012945848_464765143_n.jpg
117 ms
942801_529311690576557_1068580227845803009_n.jpg
116 ms
12524074_607996309353821_2493041743588431127_n.jpg
304 ms
12507552_10205686227856899_2714353208731533992_n.jpg
197 ms
10441264_10205442597329915_3110200645337554605_n.jpg
115 ms
10670204_10152554255895800_6717236799142945440_n.jpg
118 ms
12745446_184181845284780_8533726852217807791_n.jpg
229 ms
wL6VQj7Ab77.png
105 ms
CSXXCvknpgK.png
105 ms
smallSlider.png
2239 ms
calendar.png
2396 ms
activeview
13 ms
activeview
14 ms
R9a_DtVRZgv.js
42 ms
cUDgRFxaoIk.js
43 ms
0JBr1QHp8Gi.js
39 ms
kDOzhTr2W91.js
43 ms
joburg.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
joburg.co.za 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
Browser errors were logged to the console
joburg.co.za 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Joburg.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 Joburg.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.
joburg.co.za
Open Graph data is detected on the main page of Joburg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: