14.7 sec in total
2.6 sec
11.9 sec
193 ms
Click here to check amazing IWeek content. Otherwise, check out these important facts you probably never knew about iweek.co.za
An intelligent digest of the week's ICT events and trends that influence the lives of IT decision-makers
Visit iweek.co.zaWe analyzed Iweek.co.za page load time and found that the first response time was 2.6 sec and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
iweek.co.za performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value7.2 s
5/100
25%
Value14.3 s
1/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value7.4 s
48/100
10%
2591 ms
525 ms
532 ms
537 ms
803 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 77% of them (60 requests) were addressed to the original Iweek.co.za, 12% (9 requests) were made to Ad.mydigitallife.co.za and 4% (3 requests) were made to Secure-za.imrworldwide.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Iweek.co.za.
Page size can be reduced by 312.5 kB (44%)
704.9 kB
392.4 kB
In fact, the total size of Iweek.co.za main page is 704.9 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. 30% of websites need less resources to load. Images take 319.0 kB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.4 kB or 81% of the original size.
Potential reduce by 23.3 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. IWeek images are well optimized though.
Potential reduce by 117.3 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 117.3 kB or 67% of the original size.
Potential reduce by 124.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. Iweek.co.za needs all CSS files to be minified and compressed as it can save up to 124.4 kB or 82% of the original size.
Number of requests can be reduced by 54 (70%)
77
23
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IWeek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.iweek.co.za
2591 ms
rokbox-style.css
525 ms
gantry.css
532 ms
grid-16.css
537 ms
joomla.css
803 ms
joomla.css
799 ms
extended.css
780 ms
demo-styles.css
791 ms
splitmenu.css
802 ms
template.css
808 ms
overlay.css
1050 ms
typography.css
1060 ms
bsimagecaption.css
1077 ms
rokajaxsearch.css
1082 ms
rokajaxsearch-theme.css
1086 ms
roknewsflash.css
1091 ms
rokstories.css
1320 ms
rokmicronews.css
1325 ms
mediaobject-150.js
1103 ms
mootools.js
1401 ms
caption.js
1113 ms
rokbox.js
1372 ms
rokbox-config.js
1342 ms
gantry-totop.js
1344 ms
gantry-buildspans.js
1375 ms
gantry-inputs.js
1388 ms
roktabs.js
1614 ms
rokajaxsearch.js
1626 ms
roknewsflash.js
1645 ms
rokstories.js
1649 ms
rokmicronews.js
1665 ms
bsimagecaption.css
1669 ms
v60.js
62 ms
adjs.php
530 ms
adjs.php
541 ms
adjs.php
535 ms
adjs.php
519 ms
adjs.php
531 ms
adjs.php
533 ms
adjs.php
547 ms
adjs.php
557 ms
em.js
145 ms
airborne_logo.gif
523 ms
map.gif
1016 ms
SA-HEADS-FOR-FINAL_thumb.jpg
1040 ms
Dean_Young_thumb.jpg
285 ms
Angelique_robbertse_thumb.jpg
541 ms
Jed_Hewson_thumb.jpg
282 ms
Security_summit_thumb.jpg
532 ms
Sage_Forum_thumb.jpg
544 ms
Martin.jpg
557 ms
magix_logo.gif
561 ms
dimensiondata.jpg
809 ms
david_kan.jpg
1079 ms
sven_lesicnik.jpg
6804 ms
storageframe.html
23 ms
logo3.png
824 ms
overlay5.png
826 ms
black-25.png
1073 ms
submenu-overlay.png
1105 ms
button-overlay.png
1086 ms
nashuabest_practice.jpg
1344 ms
adlog.php
272 ms
black-5.png
1261 ms
search-icon.png
1308 ms
m
25 ms
black-45.png
1287 ms
divider.png
1313 ms
arrows.png
1316 ms
white-25.png
1501 ms
footer-overlay1.png
1537 ms
frame_2.3.3.html
168 ms
p
90 ms
details-bg.png
273 ms
drophere.png
273 ms
tab-l.png
278 ms
spinner.gif
272 ms
SA-HEADS-FOR-FINAL.jpg
268 ms
iweek.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
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
iweek.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
iweek.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
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iweek.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 Iweek.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.
iweek.co.za
Open Graph description is not detected on the main page of IWeek. 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: