26 sec in total
1 sec
13.4 sec
11.5 sec
Click here to check amazing 24 content for South Africa. Otherwise, check out these important facts you probably never knew about 24.com
We believe that technology should improve and simplify our lives. 24.com is committed to creating innovative digital infrastructure to facilitate the stories that matter most.
Visit 24.comWe analyzed 24.com page load time and found that the first response time was 1 sec and then it took 25 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
24.com performance score
name
value
score
weighting
Value11.9 s
0/100
10%
Value16.3 s
0/100
25%
Value16.5 s
0/100
10%
Value1,550 ms
13/100
30%
Value0.305
39/100
15%
Value12.3 s
15/100
10%
1013 ms
1200 ms
652 ms
435 ms
435 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 54% of them (41 requests) were addressed to the original 24.com, 24% (18 requests) were made to Cdn.24.co.za and 4% (3 requests) were made to Scripts.24.co.za. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Images.prop24.com.
Page size can be reduced by 1.2 MB (42%)
2.8 MB
1.6 MB
In fact, the total size of 24.com main page is 2.8 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 77.4 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.2 kB, which is 13% 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 77.4 kB or 82% of the original size.
Potential reduce by 243.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. Obviously, 24 needs image optimization as it can save up to 243.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 685.6 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 685.6 kB or 68% of the original size.
Potential reduce by 159.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. 24.com needs all CSS files to be minified and compressed as it can save up to 159.0 kB or 83% of the original size.
Number of requests can be reduced by 29 (40%)
72
43
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 24. 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 as a result speed up the page load time.
24.com
1013 ms
www.24.com
1200 ms
layout.css
652 ms
adDomReady.js
435 ms
common.functions.js
435 ms
jquery-1.7.2.min.js
1087 ms
common.min.js
403 ms
24AdScript.min.js
356 ms
prototype.ashx
442 ms
core.ashx
572 ms
converter.ashx
776 ms
TwentyFour.Sites.TwoFourCom.UI.Site.WeatherAjax,TwoFourCom.ashx
774 ms
SprySlidingPanels.js
522 ms
Weather.js
454 ms
jquery-1.2.6.min.js
649 ms
jquery-ui-personalized-1.6rc2.min.js
1149 ms
cookie.jquery.js
473 ms
jquery.functions.js
1150 ms
analytics.js
214 ms
d9aff8713f1843c78d1bf97bc1a8306c.png
2056 ms
fin24.png
137 ms
FetchImage.ashx
3580 ms
xdl~qb.jpg
2039 ms
1c381a0afc574f97971ab5bfdadb9760.png
2042 ms
934dc9a15183469cbe8812d4af93c409.jpg
2956 ms
2d58319b742a411a95c9b02a43240a60.jpg
2040 ms
4832a40178ba4bc79a43a94f321b4ff7.jpg
2040 ms
54c66e408eaa405db6d0b6449a774a3d.jpg
3556 ms
9dc432f368cb4e0aad9b564f1e2eea27.jpg
2279 ms
47df34ac4a284803a931c523d42422f6.jpg
2279 ms
aa4857d50c5a447c9b7bb05c5a997a16.png
2278 ms
13ebebe06de24aedb9e0a0b1e6123698.jpg
2355 ms
1890d7065ba44d35acff5375ac825340.jpg
3173 ms
ace1c30bc1104aa9a5f11bd88a8aa245.jpg
3172 ms
d0ceb5e1752047b4aeb6006a9fd707dc.jpg
3193 ms
11af383ab8b6432193722777b1d45b13.jpg
3193 ms
8f3ace3ed05d4dc19ed185ee37819d85.jpg
3437 ms
44752cf1db6c47dda32745641140820f.jpg
3412 ms
6b39bf71d0e34dbeb13e19538d032c32.jpg
3496 ms
3259c882ac134a10a12ab6bde9757a91.jpg
3474 ms
btn_search.png
944 ms
logo_overlay_link.gif
903 ms
ajax-loader.gif
919 ms
iabLogo.png
919 ms
em.js
876 ms
collect
204 ms
collect
2246 ms
bluegrad_bg.png
965 ms
frame_2.3.7.html
2138 ms
input_bg.png
927 ms
focus_alpha.png
644 ms
widget_head_bg.png
1235 ms
widgethead_news.png
1321 ms
dotted.gif
1322 ms
li_bg.gif
1321 ms
widgethead_sport.png
1321 ms
p
250 ms
Homepage;sz=300x250;posno=2;kw=;artid=;dcopt=ist;tile=1;ord=567433815449476.2
136 ms
widgethead_food.png
470 ms
widgethead_channel.png
425 ms
widgethead_fin.png
424 ms
widgethead_health.png
425 ms
widgethead_parent.png
425 ms
widgethead_property.png
424 ms
widgethead_wheels.png
408 ms
invitation-default.js
664 ms
video.min.js
458 ms
Homepage;sz=300x250;posno=1;kw=;artid=;tile=2;ord=567433815449476.2
116 ms
widgethead_weather.png
1422 ms
W24.png
1358 ms
love2meet.png
1299 ms
1780_24.png
669 ms
88bfac63-f1b9-4c33-b83f-e7628b23e754.gif
141 ms
widgethead_traveller.png
351 ms
footer_bg.png
1413 ms
functions.js.css
654 ms
24.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
24.com 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
24.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 24.com 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 24.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
24.com
Open Graph description is not detected on the main page of 24. 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: