3.5 sec in total
217 ms
2.9 sec
441 ms
Welcome to imogo.co.za homepage info - get ready to check Imogo best content for South Africa right away, or after learning these important things about imogo.co.za
Visit imogo.co.zaWe analyzed Imogo.co.za page load time and found that the first response time was 217 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
imogo.co.za performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
217 ms
80 ms
242 ms
153 ms
160 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 93% of them (64 requests) were addressed to the original Imogo.co.za, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Imogo.co.za.
Page size can be reduced by 4.0 MB (55%)
7.3 MB
3.3 MB
In fact, the total size of Imogo.co.za main page is 7.3 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 7.0 MB which makes up the majority of the site volume.
Potential reduce by 36.8 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 12.5 kB, which is 29% 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 36.8 kB or 87% of the original size.
Potential reduce by 3.7 MB
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. Obviously, Imogo needs image optimization as it can save up to 3.7 MB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 220.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 220.4 kB or 68% of the original size.
Number of requests can be reduced by 30 (51%)
59
29
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imogo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
imogo.co.za
217 ms
preload.css
80 ms
bootstrap.min.css
242 ms
yamm.css
153 ms
bootstrap-switch.min.css
160 ms
font-awesome.min.css
172 ms
animate.min.css
162 ms
slidebars.css
175 ms
lightbox.css
234 ms
jquery.bxslider.css
235 ms
shCore.css
238 ms
style-green4.css
322 ms
width-full.css
250 ms
buttons.css
335 ms
jquery.min.js
473 ms
jquery.cookie.js
334 ms
bootstrap.min.js
339 ms
bootstrap-switch.min.js
331 ms
wow.min.js
416 ms
slidebars.js
417 ms
jquery.bxslider.min.js
417 ms
holder.js
418 ms
buttons.js
417 ms
styleswitcher.js
510 ms
jquery.mixitup.min.js
511 ms
circles.min.js
513 ms
shCore.js
512 ms
shBrushXml.js
513 ms
shBrushJScript.js
547 ms
app.js
566 ms
index.js
569 ms
css
24 ms
analytics.js
67 ms
close.png
247 ms
loading.gif
207 ms
prev.png
248 ms
next.png
263 ms
bx_loader.gif
283 ms
imogologo.png
578 ms
468x60.gif
500 ms
logo.png
356 ms
logo_white2.png
436 ms
slide_back.jpg
922 ms
pre.png
653 ms
flights-sld.jpg
760 ms
moneyphone.png
1015 ms
funeralcover.png
1974 ms
medicalcover.png
1680 ms
travelinsure.png
2270 ms
wheelscover.png
1435 ms
mine.jpg
1088 ms
sm.jpg
1169 ms
farm.jpg
1220 ms
tea.jpg
1267 ms
fish.jpg
1370 ms
mun.jpg
1368 ms
garden.jpg
1476 ms
m12.jpg
1445 ms
wf2.jpg
1534 ms
Open%20Sans%20Regular-webfont.woff
1525 ms
_fUwxgthNvUM9WCtMyMvbA.woff
13 ms
collect
18 ms
collect
82 ms
fontawesome-webfont.woff
1544 ms
Lato%20Regular-webfont.woff
1509 ms
glyphicons-halflings-regular.woff
1516 ms
wf4.jpg
1661 ms
Open%20Sans%20Regular-webfont.ttf
139 ms
Open%20Sans%20Regular-webfont.svg
78 ms
imogo.co.za accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
imogo.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
imogo.co.za SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imogo.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 Imogo.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.
imogo.co.za
Open Graph description is not detected on the main page of Imogo. 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: