3.5 sec in total
606 ms
2.6 sec
260 ms
Welcome to infobel.co.za homepage info - get ready to check Infobel best content for South Africa right away, or after learning these important things about infobel.co.za
Search throughout South Africa with the online telephone directory, search in the Business directory and in the residential directory!
Visit infobel.co.zaWe analyzed Infobel.co.za page load time and found that the first response time was 606 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
infobel.co.za performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value7.1 s
5/100
25%
Value4.7 s
68/100
10%
Value370 ms
71/100
30%
Value0.504
16/100
15%
Value9.2 s
32/100
10%
606 ms
50 ms
26 ms
11 ms
15 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Infobel.co.za, 14% (13 requests) were made to Infobel.com and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (606 ms) relates to the external source Infobel.com.
Page size can be reduced by 832.0 kB (62%)
1.4 MB
518.2 kB
In fact, the total size of Infobel.co.za main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 531.5 kB which makes up the majority of the site volume.
Potential reduce by 194.1 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 87.4 kB, which is 40% 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 194.1 kB or 89% of the original size.
Potential reduce by 5.5 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. Infobel images are well optimized though.
Potential reduce by 295.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 295.5 kB or 56% of the original size.
Potential reduce by 337.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. Infobel.co.za needs all CSS files to be minified and compressed as it can save up to 337.0 kB or 85% of the original size.
Number of requests can be reduced by 58 (73%)
80
22
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Infobel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
southafrica
606 ms
css
50 ms
kendo.common.min.css
26 ms
kendo.default.min.css
11 ms
bootstrap.min.css
15 ms
css
187 ms
css
267 ms
ads.js
48 ms
adsbygoogle.js
21 ms
cookieconsent.min.js
38 ms
jquery-2.1.4.min.js
13 ms
jquery
327 ms
kendo.core.min.js
22 ms
kendo.data.min.js
35 ms
kendo.popup.min.js
34 ms
kendo.list.min.js
36 ms
kendo.autocomplete.min.js
38 ms
kendo.dropdownlist.min.js
37 ms
kendo.panelbar.min.js
41 ms
kendo.tooltip.min.js
36 ms
kendo.upload.min.js
37 ms
kendo.combobox.min.js
38 ms
kendo.multiselect.min.js
40 ms
kendo.validator.min.js
38 ms
kendo.aspnetmvc.min.js
40 ms
other
350 ms
custom
195 ms
platform.js
71 ms
in.js
6 ms
ga.js
83 ms
infobel-logo-color.png
105 ms
macbook.png
290 ms
sdk.js
185 ms
home-banner-business.jpg
457 ms
__utm.gif
15 ms
toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf
53 ms
ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf
54 ms
toadOcfmlt9b38dHJxOBGGvd-IutAbwf5FQ8ZpuI2w4.ttf
70 ms
Infobel-Iconfont.woff
122 ms
ca-pub-7219613918654603.js
58 ms
zrt_lookup.html
56 ms
show_ads_impl.js
57 ms
fontawesome-webfont.woff
373 ms
infobel-categories.woff
354 ms
ads
375 ms
osd.js
30 ms
ads
479 ms
widgets.js
156 ms
299 ms
infobel-others.ttf
191 ms
secureAnonymousFramework
191 ms
loading.gif
133 ms
cb=gapi.loaded_0
187 ms
cb=gapi.loaded_1
279 ms
sharebutton
503 ms
xd_arbiter.php
246 ms
xd_arbiter.php
553 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
193 ms
inspectlet.js
103 ms
share
229 ms
sprite_connect_v14.png
208 ms
m_js_controller.js
203 ms
abg.js
247 ms
like.php
146 ms
1327419040
243 ms
postmessageRelay
241 ms
share_button.php
293 ms
rU2ubZ6l1Q5.js
491 ms
LVx-xkvaJ0b.png
483 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
29 ms
favicon
311 ms
favicon
314 ms
googlelogo_color_112x36dp.png
231 ms
nessie_icon_thin_arrow_big_white.png
121 ms
rs=AGLTcCMjQOKLzmHw4jAL4LZH64_0PwYekw
135 ms
rs=AGLTcCM_4QRxOE6D7i046ieS6uXn08HhGg
135 ms
favicon
285 ms
favicon
308 ms
s
169 ms
favicon
208 ms
favicon
210 ms
favicon
287 ms
favicon
259 ms
favicon
258 ms
favicon
207 ms
favicon
200 ms
x_button_blue2.png
147 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
295 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
296 ms
jot
287 ms
api.js
170 ms
core:rpc:shindig.random:shindig.sha1.js
241 ms
2536007149-postmessagerelay.js
226 ms
rU2ubZ6l1Q5.js
373 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
21 ms
infobel.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
infobel.co.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
Page has valid source maps
infobel.co.za SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infobel.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Infobel.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.
infobel.co.za
Open Graph description is not detected on the main page of Infobel. 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: