86.3 sec in total
1 sec
51.9 sec
33.5 sec
Visit iol.co.za now to see the best up-to-date IOL content for South Africa and also check out these interesting facts you probably never knew about iol.co.za
Discover the world of IOL, bringing you a mix of current news across politics, sport, business, motoring and lifestyle. Telling your stories and driving change!
Visit iol.co.zaWe analyzed Iol.co.za page load time and found that the first response time was 1 sec and then it took 85.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 83 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
iol.co.za performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value5.9 s
14/100
25%
Value18.7 s
0/100
10%
Value15,190 ms
0/100
30%
Value0.033
100/100
15%
Value37.6 s
0/100
10%
1006 ms
3310 ms
3648 ms
892 ms
3910 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 11% of them (15 requests) were addressed to the original Iol.co.za, 52% (71 requests) were made to Image.iol.co.za and 14% (19 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (25 sec) relates to the external source Facebook.com.
Page size can be reduced by 1.3 MB (48%)
2.7 MB
1.4 MB
In fact, the total size of Iol.co.za main page is 2.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 402.4 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 402.4 kB or 87% of the original size.
Potential reduce by 32.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. IOL images are well optimized though.
Potential reduce by 577.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 577.4 kB or 68% of the original size.
Potential reduce by 292.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. Iol.co.za needs all CSS files to be minified and compressed as it can save up to 292.5 kB or 84% of the original size.
Number of requests can be reduced by 23 (49%)
47
24
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IOL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.iol.co.za
1006 ms
css
3310 ms
normalize@6.0.0
3648 ms
main.css
892 ms
smartbanner.min.css
3910 ms
12520 ms
jquery@2.2.4,es5.shim@4.1.0(es5-sham.min.js+es5-shim.min.js),lodash@3.10.1,react@0.14.7(react.min.js+react-dom.min.js+react-dom-server.min.js),fitvids@1.1.0,jquery.slick@1.6.0
7640 ms
jquery.cookie.js
2239 ms
jquery.dcd.doubletaptogo.min.js
2586 ms
mini.min.js
2584 ms
gpt.js
6868 ms
em.js
7388 ms
widgets.js
7286 ms
embeds.js
5355 ms
all.js
6867 ms
bundle.min.js
2886 ms
cc_af.js
7285 ms
smartbanner.min.js
7272 ms
gtm.js
7597 ms
hotjar-431190.js
8973 ms
fbevents.js
5237 ms
sdk.js
5479 ms
iol.png
4643 ms
620x349
8256 ms
620x349
8806 ms
620x349
21350 ms
620x349
21399 ms
250x141
21400 ms
250x141
21400 ms
250x141
21400 ms
250x141
21420 ms
460x259
21421 ms
400x225
21458 ms
400x225
21458 ms
400x225
21458 ms
400x225
21459 ms
400x225
21705 ms
400x225
21705 ms
400x225
21661 ms
300x169
21660 ms
300x169
21860 ms
160x160
21861 ms
160x160
21861 ms
160x160
21861 ms
160x160
21861 ms
160x160
21894 ms
160x160
21894 ms
460x259
21894 ms
460x259
21894 ms
400x225
21895 ms
400x225
21895 ms
160x160
21896 ms
160x160
21835 ms
160x160
21893 ms
160x160
21893 ms
160x160
21894 ms
400x225
21894 ms
400x225
21679 ms
400x225
21732 ms
play-btn.svg
3125 ms
facebook-ico.svg
2851 ms
twitter-ico.svg
2848 ms
instagram-ico.svg
3126 ms
Helvetica.woff
5058 ms
fontawesome-webfont.woff
3576 ms
Zd2E9abXLFGSr9G3YK2MsNxB8OB85xaNTJvVSB9YUjQ.woff
6581 ms
Zd2E9abXLFGSr9G3YK2MsBGHQKeb0EvJ8DYF0YR0-yA.woff
6582 ms
Zd2E9abXLFGSr9G3YK2MsFwu37KbvDt9e6Z0fLuB8wE.woff
22013 ms
Zd2E9abXLFGSr9G3YK2MsCPQ0s7SK4FpZRJaI6PHhaE.woff
22013 ms
Zd2E9abXLFGSr9G3YK2MsFfUSRPBbNa7P86U50abqjM.woff
22013 ms
Zd2E9abXLFGSr9G3YK2MsONnLQW_Aipv7papXhdJQVk.woff
22208 ms
Zd2E9abXLFGSr9G3YK2MsCs-rtsZsdMCO0Md9FlLJLk.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nPZRQUbYfRc-1FWT9T9EE8M.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nB_jhWV_8YFuhECuO-PeM6X2Ot9t5h1GRSTIE78Whtoh.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nEV7KvwZBtAeepuukQi02CH2Ot9t5h1GRSTIE78Whtoh.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nLsoL2ka76RTMJDhvsQpMf32Ot9t5h1GRSTIE78Whtoh.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nCwuWY7lHMe3F2tGE2nrD6j2Ot9t5h1GRSTIE78Whtoh.woff
22207 ms
b9QBgL0iMZfDSpmcXcE8nOUJnRMj5Vf2T5QzQ09Jpwr2Ot9t5h1GRSTIE78Whtoh.woff
22208 ms
b9QBgL0iMZfDSpmcXcE8nBRRnJbT7E9cprrN8Bc3TuP2Ot9t5h1GRSTIE78Whtoh.woff
22208 ms
nAKwuw6_dIh5kwvpj3ShNfesZW2xOQ-xsNqO47m55DA.woff
22208 ms
lJHK3MdZ4tadQZQahj7hrxTbgVql8nDJpwnrE27mub0.woff
22207 ms
O2mMrdLgt2qhfmg0F7EJcRTbgVql8nDJpwnrE27mub0.woff
22179 ms
VT0F-oM1OMR9P9mQqo4fbBTbgVql8nDJpwnrE27mub0.woff
22225 ms
3w-uydIBEkCwSHsOii6OVRTbgVql8nDJpwnrE27mub0.woff
22224 ms
794201197427829
1894 ms
20612 ms
0sTQzbapM8j.js
20350 ms
24996 ms
160x160
24946 ms
ado-1.1.4.js
24945 ms
160x160
23333 ms
analytics.js
20593 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
20538 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
20536 ms
23168 ms
f
20843 ms
0 ms
160x160
13037 ms
160x160
13037 ms
160x160
13047 ms
460x259
13038 ms
460x259
13017 ms
400x225
13025 ms
400x225
16342 ms
400x225
16342 ms
160x160
16341 ms
160x160
16340 ms
160x160
16094 ms
300x169
16093 ms
300x169
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
300x169
0 ms
160x160
0 ms
160x160
0 ms
160x160
0 ms
460x259
0 ms
250x141
0 ms
250x141
0 ms
250x141
0 ms
250x141
0 ms
250x141
0 ms
460x259
0 ms
pubads_impl_147.js
15796 ms
Widgets_118.js
17826 ms
ajax-loader.gif
3606 ms
620x349
11952 ms
slick.woff
2077 ms
container.html
5728 ms
ads
2030 ms
iol.co.za accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
iol.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
Missing source maps for large first-party JavaScript
iol.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
Image elements do not have [alt] attributes
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 Iol.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 Iol.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.
iol.co.za
Open Graph data is detected on the main page of IOL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: