33.8 sec in total
927 ms
29.3 sec
3.6 sec
Visit allaboutphones.co.za now to see the best up-to-date Allabout Phone S content and also check out these interesting facts you probably never knew about allaboutphones.co.za
Get the great Cell Phone deals, Contracts, Specials Data packages for Telkom, MTN, Cell C and Vodacom
Visit allaboutphones.co.zaWe analyzed Allaboutphones.co.za page load time and found that the first response time was 927 ms and then it took 32.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
allaboutphones.co.za performance score
927 ms
2878 ms
53 ms
146 ms
13 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 8% of them (12 requests) were addressed to the original Allaboutphones.co.za, 34% (50 requests) were made to Cm.g.doubleclick.net and 11% (16 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Googlecm.hit.gemius.pl.
Page size can be reduced by 127.7 kB (33%)
386.8 kB
259.1 kB
In fact, the total size of Allaboutphones.co.za main page is 386.8 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. 65% of websites need less resources to load. Images take 186.6 kB which makes up the majority of the site volume.
Potential reduce by 102.0 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 102.0 kB or 83% of the original size.
Potential reduce by 16.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. Allabout Phone S images are well optimized though.
Potential reduce by 8.8 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 8.8 kB or 17% of the original size.
Potential reduce by 769 B
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. Allaboutphones.co.za has all CSS files already compressed.
Number of requests can be reduced by 100 (74%)
136
36
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Allabout Phone S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
allaboutphones.co.za
927 ms
www.allaboutphones.co.za
2878 ms
adsbygoogle.js
53 ms
js
146 ms
javascript;base64,CiAgd2luZG93LmRhdGFMYXllciA9IHdpbmRvdy5kYXRhTGF5ZXIgfHwgW107CiAgZnVuY3Rpb24gZ3RhZygpe2RhdGFMYXllci5wdXNoKGFyZ3VtZW50cyk7fQogIGd0YWcoJ2pzJywgbmV3IERhdGUoKSk7CgogIGd0YWcoJ2NvbmZpZycsICdHLVFKNEIzU0UyRjInKTsK
13 ms
YyhlLmNvbmNhdGVtb2ppKTplLndwZW1vamkmJmUudHdlbW9qaSYmKGMoZS50d2Vtb2ppKSxjKGUud3BlbW9qaSkpKX0od2luZG93LGRvY3VtZW50LHdpbmRvdy5fd3BlbW9qaVNldHRpbmdzKTsK
10 ms
style.min.css
311 ms
menu-animation.min.css
617 ms
style.min.css
908 ms
autoptimize_single_e6fae855021a88a0067fcc58121c594f.css
912 ms
contact-form-7-main.min.css
913 ms
javascript;base64,CnZhciBhc3RyYSA9IHsiYnJlYWtfcG9pbnQiOiI5MjEiLCJpc1J0bCI6IiJ9Owo=
3 ms
style.min.js
939 ms
regenerator-runtime.min.js
903 ms
wp-polyfill.min.js
939 ms
javascript;base64,CnZhciB3cGNmNyA9IHsiYXBpIjp7InJvb3QiOiJodHRwczpcL1wvd3d3LmFsbGFib3V0cGhvbmVzLmNvLnphXC93cC1qc29uXC8iLCJuYW1lc3BhY2UiOiJjb250YWN0LWZvcm0tN1wvdjEifX07Cg==
2 ms
autoptimize_single_cfb428c02811f0cbe515d5f3dca61de6.js
1218 ms
javascript;base64,DQoJCQkvKHRyaWRlbnR8bXNpZSkvaS50ZXN0KG5hdmlnYXRvci51c2VyQWdlbnQpJiZkb2N1bWVudC5nZXRFbGVtZW50QnlJZCYmd2luZG93LmFkZEV2ZW50TGlzdGVuZXImJndpbmRvdy5hZGRFdmVudExpc3RlbmVyKCJoYXNoY2hhbmdlIixmdW5jdGlvbigpe3ZhciB0LGU9bG9jYXRpb24uaGFzaC5zdWJzdHJpbmcoMSk7L15bQS16MC05Xy1dKyQvLnRlc3QoZSkmJih0PWRvY3VtZW50LmdldEVsZW1lbnRCeUlkKGUpKSYmKC9eKD86YXxzZWxlY3R8aW5wdXR8YnV0dG9ufHRleHRhcmVhKSQvaS50ZXN0KHQudGFnTmFtZSl8fCh0LnRhYkluZGV4PS0xKSx0LmZvY3VzKCkpfSwhMSk7DQoJCQk=
2 ms
show_ads_impl.js
85 ms
zrt_lookup.html
99 ms
cookie.js
55 ms
integrator.js
52 ms
ads
342 ms
ads
805 ms
reactive_library.js
32 ms
integrator.js
24 ms
zrt_lookup.html
21 ms
5bbe539ad7c95ad1b7dc2874c2ab6f46.js
47 ms
load_preloaded_resource.js
81 ms
2c31c29323708f8c18cb525f4f35abd1.js
57 ms
abg_lite.js
82 ms
window_focus.js
94 ms
qs_click_protection.js
95 ms
rx_lidar.js
93 ms
fac60d4cdc0b8be56d9f8d6f9ac54a3d.js
79 ms
icon.png
33 ms
downsize_200k_v1
178 ms
s
189 ms
activeview
109 ms
integrator.js
116 ms
ads
813 ms
afr.php
211 ms
activeview
50 ms
ads
1409 ms
integrator.js
22 ms
ads
985 ms
ads
1149 ms
integrator.js
45 ms
ads
792 ms
privacy_small.svg
216 ms
lg.php
231 ms
webfontloader.js
213 ms
adchoices_en.svg
210 ms
close_button.svg
226 ms
back_button2.svg
230 ms
ads
1018 ms
animejs.js
197 ms
img
284 ms
criteo_logo_2021.svg
191 ms
privacy.svg
191 ms
img
279 ms
img
279 ms
ab61ffb7c62a40a194552a9753cbe000_marketsans-regular.woff
184 ms
7fb0a997a1f04f65ac898832e60c1d50_marketsans-semibold.woff
189 ms
integrator.js
156 ms
ads
1281 ms
ads
1517 ms
ads
1847 ms
wp-emoji-release.min.js
352 ms
view_pixel_1x1.gif
21 ms
downsize_200k_v1
88 ms
cookie_push_onload.html
72 ms
dpixel
95 ms
googleredir
144 ms
css
95 ms
pixel
86 ms
pixel
19 ms
pixel
19 ms
pixel
20 ms
pixel
20 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff
18 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff
25 ms
googleredir
19508 ms
pixel
84 ms
pixel
83 ms
pixel
81 ms
pixel
78 ms
activeview
304 ms
activeview
311 ms
activeview
298 ms
pixel
208 ms
pixel
209 ms
pixel
207 ms
GqdA_Tv7WdpTYI8K1v09aLIv-PCgI0anbpiD0lWdf3k.js
216 ms
pixel
210 ms
downsize_200k_v1
143 ms
googleredir
20104 ms
dpixel
136 ms
pixel
108 ms
pixel
99 ms
pixel
101 ms
pixel
98 ms
pixel
195 ms
pixel
186 ms
pixel
187 ms
activeview
174 ms
pixel
173 ms
pixel
171 ms
pixel
171 ms
pixel
234 ms
pixel
235 ms
pixel
173 ms
pixel
170 ms
pixel
166 ms
pixel
168 ms
pixel
169 ms
activeview
153 ms
activeview
142 ms
pixel
143 ms
pixel
172 ms
pixel
172 ms
pixel
168 ms
pixel
168 ms
nessie_icon_tiamat_white.png
161 ms
15618461712909038391
113 ms
pixel
171 ms
pixel
66 ms
pixel
86 ms
pixel
66 ms
pixel
90 ms
pixel
89 ms
activeview
72 ms
pixel
69 ms
pixel
66 ms
pixel
94 ms
downsize_200k_v1
87 ms
466606.gif
118 ms
pixel
107 ms
pixel
107 ms
pixel
24 ms
pixel
23 ms
activeview
22 ms
pixel
15 ms
pixel
28 ms
sodar
17 ms
sodar2.js
72 ms
runner.html
9 ms
aframe
32 ms
allaboutphones.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 Allaboutphones.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 Allaboutphones.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.
allaboutphones.co.za
Open Graph description is not detected on the main page of Allabout Phone S. 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: