27.5 sec in total
1.5 sec
25.6 sec
404 ms
Click here to check amazing Is content for South Africa. Otherwise, check out these important facts you probably never knew about is.co.za
Our technology, innovation and comprehensive portfolio of global services enable your business transformation. Learn more about NTT Ltd.
Visit is.co.zaWe analyzed Is.co.za page load time and found that the first response time was 1.5 sec and then it took 26 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
is.co.za performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value12.0 s
0/100
25%
Value9.3 s
12/100
10%
Value1,970 ms
8/100
30%
Value0.128
82/100
15%
Value13.2 s
12/100
10%
1533 ms
1931 ms
539 ms
2565 ms
1280 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 44% of them (47 requests) were addressed to the original Is.co.za, 21% (22 requests) were made to Maps.google.com and 7% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Freegeoip.net.
Page size can be reduced by 795.7 kB (55%)
1.5 MB
661.7 kB
In fact, the total size of Is.co.za main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 588.7 kB which makes up the majority of the site volume.
Potential reduce by 57.2 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 57.2 kB or 82% of the original size.
Potential reduce by 31.0 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. Is images are well optimized though.
Potential reduce by 401.5 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 401.5 kB or 68% of the original size.
Potential reduce by 305.9 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. Is.co.za needs all CSS files to be minified and compressed as it can save up to 305.9 kB or 89% of the original size.
Number of requests can be reduced by 57 (59%)
97
40
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Is. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
is.co.za
1533 ms
www.is.co.za
1931 ms
video-js.css
539 ms
Site.css
2565 ms
style.css
1280 ms
jquery-1.11.1.min.js
1807 ms
video.js
1614 ms
leaflet.js
1817 ms
app.js
776 ms
jquery.scrollTo-1.4.3.1-min.js
1040 ms
jquery.localscroll-1.2.7-min.js
1259 ms
foundation.js
1299 ms
foundation.topbar.js
1518 ms
foundation.forms.js
1565 ms
waypoints.min.js
1601 ms
waypoints-sticky.min.js
1781 ms
idangerous.swiper.js
2066 ms
main.js
1829 ms
custom.js
1861 ms
js
62 ms
Google.js
2042 ms
spin.min.js
2079 ms
jquery.cookie.js
2096 ms
css
56 ms
logo-block.png
323 ms
search-icon.png
323 ms
map1.jpg
1336 ms
our-company-who.png
324 ms
our-company-what.png
325 ms
our-company-speak.png
324 ms
gtm.js
88 ms
bg-content.png
545 ms
arrow.png
546 ms
nav_bg.jpg
550 ms
blue-arrow-down.png
601 ms
icon-cross.png
550 ms
white-arrow-down.png
846 ms
home-secondary-cta-bg.jpg
847 ms
widgets.js
298 ms
arrow-invert.png
808 ms
slider-left.png
810 ms
slider-right.png
834 ms
speech-bubbles.png
1048 ms
letter.png
1048 ms
clouds.png
1049 ms
clock.png
1050 ms
social-icons.png
1095 ms
Z6xYy_2MlN1cUISkeodEPA.woff
212 ms
footer-pointer.png
1262 ms
analytics.js
214 ms
conversion_async.js
214 ms
19565 ms
common.js
130 ms
map.js
171 ms
marker-icon.png
1096 ms
marker-shadow.png
1096 ms
footer-dropdown.png
1098 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
53 ms
util.js
33 ms
onion.js
32 ms
collect
50 ms
133 ms
ViewportInfoService.GetViewportInfo
203 ms
stats.js
41 ms
controls.js
36 ms
syndication
375 ms
392922402771845120
431 ms
392922402771845120
461 ms
transparent.png
206 ms
css
41 ms
google4.png
284 ms
mapcnt6.png
321 ms
sv5.png
320 ms
514 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
51 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
107 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
164 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
223 ms
vt
189 ms
vt
181 ms
vt
215 ms
vt
229 ms
vt
230 ms
vt
230 ms
vt
229 ms
vt
230 ms
vt
241 ms
vt
243 ms
vt
243 ms
vt
276 ms
vt
268 ms
vt
249 ms
vt
281 ms
ga-audiences
350 ms
proxy.jpg
64 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
35 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
65 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
76 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
125 ms
4353f77b3eaab3d4cc6a562d245555fa_normal.jpeg
266 ms
AuthenticationService.Authenticate
267 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
75 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
107 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
39 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
45 ms
jot.html
62 ms
QuotaService.RecordEvent
33 ms
is.co.za accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
is.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
is.co.za SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Is.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 Is.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.
is.co.za
Open Graph description is not detected on the main page of Is. 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: