15.3 sec in total
3.7 sec
11.4 sec
239 ms
Visit torch.co.za now to see the best up-to-date TORCH content and also check out these interesting facts you probably never knew about torch.co.za
Visit torch.co.zaWe analyzed Torch.co.za page load time and found that the first response time was 3.7 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
torch.co.za performance score
3669 ms
306 ms
684 ms
803 ms
803 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 81% of them (61 requests) were addressed to the original Torch.co.za, 5% (4 requests) were made to Googletagmanager.com and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Torch.co.za.
Page size can be reduced by 1.4 MB (36%)
3.9 MB
2.5 MB
In fact, the total size of Torch.co.za main page is 3.9 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. 75% 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 169.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 169.2 kB or 87% of the original size.
Potential reduce by 15.8 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. TORCH images are well optimized though.
Potential reduce by 431.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 431.5 kB or 70% of the original size.
Potential reduce by 770.1 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. Torch.co.za needs all CSS files to be minified and compressed as it can save up to 770.1 kB or 86% of the original size.
Number of requests can be reduced by 31 (46%)
68
37
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TORCH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.torch.co.za
3669 ms
wp-emoji-release.min.js
306 ms
style.min.css
684 ms
blocks.style.build.css
803 ms
styles.css
803 ms
email-subscribers-public.css
802 ms
settings.css
824 ms
css
50 ms
style.min.css
1288 ms
responsive.min.css
949 ms
style.css
1069 ms
Defaults.css
1084 ms
ultimate.min.css
1612 ms
icons.css
1128 ms
jquery.js
1511 ms
email-subscribers-public.js
1374 ms
jquery.themepunch.tools.min.js
1727 ms
jquery.themepunch.revolution.min.js
1492 ms
ultimate.min.js
1586 ms
js
61 ms
jquery.themepunch.tools.min.js
1913 ms
jquery.themepunch.revolution.min.js
1860 ms
js
90 ms
mpp-frontend.js
1882 ms
scripts.js
1917 ms
us.core.min.js
1951 ms
wp-embed.min.js
1951 ms
main.min.js
2098 ms
gtm.js
85 ms
5cca19ica5cc9a.png
430 ms
web-logo.png
432 ms
slide3-grey.jpg
1024 ms
slide3-overlay.png
1060 ms
slide3-final.jpg
1076 ms
overlay-orange.png
432 ms
slide6-grey.jpg
998 ms
slide6-overlay.png
2372 ms
slide6-final.jpg
1152 ms
blue-slide-in2.png
1311 ms
slide1-greyc.jpg
1322 ms
slide1-backgroundc.png
1828 ms
slide1-finalc.jpg
1357 ms
slide2-grey.jpg
1422 ms
slide2-overlay.png
1832 ms
slide2-final.jpg
1607 ms
slide8-grey2.jpg
1655 ms
slide8-overlay.png
1981 ms
slide8-final2.jpg
1907 ms
slide5-grey.jpg
1949 ms
slide5-overlay.png
3528 ms
slide5-final.jpg
2335 ms
slide7-grey.jpg
2406 ms
slide7-overlay.png
2597 ms
slide7-final.jpg
2346 ms
spinner.gif
2597 ms
6620.js
148 ms
analytics.js
152 ms
js
178 ms
fa-brands-400.woff
2482 ms
fa-regular-400.woff
3360 ms
fa-light-300.woff
2545 ms
fa-solid-900.woff
2747 ms
frontend.min.css
2667 ms
popup.min.css
2720 ms
icegram.min.js
2811 ms
revolution.extension.slideanims.min.js
2912 ms
revolution.extension.layeranimation.min.js
2893 ms
revolution.extension.navigation.min.js
2913 ms
collect
62 ms
collect
88 ms
collect
49 ms
collect
8 ms
collect
46 ms
ga-audiences
40 ms
revicons.woff
350 ms
torch.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 Torch.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 Torch.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.
torch.co.za
Open Graph description is not detected on the main page of TORCH. 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: