6.4 sec in total
606 ms
5.5 sec
271 ms
Visit iie.ac.za now to see the best up-to-date IIE content for South Africa and also check out these interesting facts you probably never knew about iie.ac.za
The IIE Home page
Visit iie.ac.zaWe analyzed Iie.ac.za page load time and found that the first response time was 606 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster. This domain responded with an error, which can significantly jeopardize Iie.ac.za rating and web reputation
iie.ac.za performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value4.4 s
38/100
25%
Value3.6 s
86/100
10%
Value470 ms
61/100
30%
Value0.002
100/100
15%
Value8.2 s
41/100
10%
606 ms
603 ms
658 ms
1001 ms
771 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 84% of them (59 requests) were addressed to the original Iie.ac.za, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Iie.ac.za.
Page size can be reduced by 1.9 MB (72%)
2.6 MB
730.2 kB
In fact, the total size of Iie.ac.za main page is 2.6 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 68.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. This page needs HTML code to be minified as it can gain 16.8 kB, which is 20% 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 68.5 kB or 81% of the original size.
Potential reduce by 10.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. IIE images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 73% of the original size.
Potential reduce by 678.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. Iie.ac.za needs all CSS files to be minified and compressed as it can save up to 678.0 kB or 86% of the original size.
Number of requests can be reduced by 42 (67%)
63
21
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IIE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
iie.ac.za
606 ms
www.iie.ac.za
603 ms
default.aspx
658 ms
corev15.css
1001 ms
bootstrap.css
771 ms
theme2.css
521 ms
flexslider.css
524 ms
nivo-slider.css
526 ms
default.css
531 ms
init.js
1039 ms
initstrings.js
780 ms
strings.js
1284 ms
ie55up.js
1049 ms
ScriptResource.axd
1261 ms
blank.js
1035 ms
ScriptResource.axd
1245 ms
bootstrap-responsive.css
1322 ms
bootstrap-custom.css
1324 ms
jquery-1.8.3.min.js
1624 ms
bootstrap.min.js
1507 ms
bootstrap-custom.js
1519 ms
WebResource.axd
1536 ms
jquery-1.9.1.min.js
2061 ms
Concero.Proteus.css
1558 ms
Concero.Proteus.js
1756 ms
Concero.Proteus.Controls.js
1767 ms
Concero.Proteus.WebParts.js
1793 ms
Proteus.css
1822 ms
js
1880 ms
jquery.nivo.slider.js
1783 ms
jquery.easing.js
1790 ms
jquery.flexslider.js
1866 ms
jquery.mousewheel.js
1866 ms
spcommon.png
844 ms
IIE.ico
975 ms
logo.png
980 ms
ajax-loader.gif
1013 ms
social_LinkedIn.png
1027 ms
social_Twitter.png
1050 ms
social_FaceBook.png
1108 ms
social_YouTube.png
1392 ms
facultiesProgrammes.jpg
1392 ms
campusesLocations.jpg
1539 ms
logo_small.png
1393 ms
icpdf.png
1401 ms
icon_telephone.png
1404 ms
icon_mail.png
1499 ms
icon_mapMarker.png
1505 ms
Background.jpg
1285 ms
topNavArrow.png
784 ms
titleBackground.png
909 ms
containerBackground.png
972 ms
WhiteOut.png
967 ms
loading.gif
1013 ms
awesomeLI.png
1049 ms
footerbackground.png
1148 ms
analytics.js
29 ms
sp.init.js
1164 ms
core.js
1660 ms
items
1225 ms
2nCmEanFcmU
121 ms
collect
19 ms
collect
55 ms
www-embed-player-vflQrT_sR.css
62 ms
www-embed-player.js
82 ms
base.js
153 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
57 ms
ad_status.js
60 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
103 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
112 ms
iie.ac.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
iie.ac.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
iie.ac.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 Iie.ac.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 Iie.ac.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.
iie.ac.za
Open Graph description is not detected on the main page of IIE. 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: