6.3 sec in total
1.3 sec
4.5 sec
515 ms
Visit spling.co.za now to see the best up-to-date SPLING content for South Africa and also check out these interesting facts you probably never knew about spling.co.za
Get movie reviews, celebrity interviews and film industry news from South African film critic, Spling. "Don't wing it, SPL!NG it!"
Visit spling.co.zaWe analyzed Spling.co.za page load time and found that the first response time was 1.3 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
spling.co.za performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value6.0 s
13/100
25%
Value29.2 s
0/100
10%
Value36,680 ms
0/100
30%
Value0.542
13/100
15%
Value58.4 s
0/100
10%
1324 ms
551 ms
501 ms
545 ms
543 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 38% of them (35 requests) were addressed to the original Spling.co.za, 8% (7 requests) were made to Mixcloud.com and 7% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Spling.co.za.
Page size can be reduced by 684.6 kB (42%)
1.6 MB
948.5 kB
In fact, the total size of Spling.co.za main page is 1.6 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 681.1 kB which makes up the majority of the site volume.
Potential reduce by 23.9 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 23.9 kB or 71% of the original size.
Potential reduce by 38.1 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. SPLING images are well optimized though.
Potential reduce by 348.7 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 348.7 kB or 59% of the original size.
Potential reduce by 273.9 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. Spling.co.za needs all CSS files to be minified and compressed as it can save up to 273.9 kB or 83% of the original size.
Number of requests can be reduced by 51 (60%)
85
34
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SPLING. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
spling.co.za
1324 ms
mootools.js
551 ms
caption.js
501 ms
system.css
545 ms
general.css
543 ms
template_css.css
545 ms
nav.css
543 ms
style2.css
751 ms
j15.css
798 ms
show_ads.js
6 ms
widgets.js
4 ms
ga.js
65 ms
poweredby_FFFFFF.gif
45 ms
pagetop_bg.png
260 ms
header_bg.png
258 ms
dns%20banner.jpg
1045 ms
header.png
783 ms
navcontainer.png
252 ms
nav_active_l.png
260 ms
nav_active_r.png
778 ms
nav_norm_l.png
778 ms
nav_norm_r.png
778 ms
top_has_left.png
778 ms
mid_left_right.png
995 ms
bullet.gif
994 ms
facebook.png
1014 ms
twitter.png
1014 ms
mod_heading.png
1016 ms
waynekramerbanner.jpg
1800 ms
spling%20logo.jpg
1825 ms
120x600%20spling%20on%20facebook.jpg
1795 ms
sinkmovie.jpg
1789 ms
splingometer8%20350.jpg
1557 ms
eyeintheskyimage.jpg
2341 ms
splingometer7%20350.jpg
1827 ms
ca-pub-9621917042969343.js
137 ms
zrt_lookup.html
143 ms
show_ads_impl.js
81 ms
QqFSK_n7mZc
183 ms
265 ms
-dzQqRXq7U0
232 ms
289 ms
__utm.gif
71 ms
bot_has_left.png
1962 ms
top_wide.png
1959 ms
mid_wide.png
1969 ms
bot_wide.png
1996 ms
like.php
149 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
83 ms
__utm.gif
62 ms
ads
628 ms
osd.js
24 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en-gb.html
14 ms
www-embed-player-vfl8xM8me.css
94 ms
www-embed-player.js
116 ms
qeKvIRsJabD.js
564 ms
LVx-xkvaJ0b.png
622 ms
player_widget_css.1d0ef58fbfb7c51fdb516f2a5569748f.css
31 ms
css
147 ms
32a011c9-5c1e-4421-854f-e59f4c83d959.jpg
88 ms
player_widget_js.7376156937e308fb6d91652dd4da34ed.js
85 ms
a0c4890f-0665-46ea-82fa-b28cd1eccf2b.jpg
452 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
315 ms
ad_status.js
423 ms
jot
427 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
393 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
416 ms
widget-sprite-8.png
333 ms
345 ms
32a011c9-5c1e-4421-854f-e59f4c83d959.jpg
359 ms
a0c4890f-0665-46ea-82fa-b28cd1eccf2b.jpg
334 ms
analytics.js
243 ms
250 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
146 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
158 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
146 ms
17432755777702272796
91 ms
abg.js
91 ms
m_js_controller.js
101 ms
googlelogo_color_112x36dp.png
100 ms
p2
25 ms
collect
23 ms
collect
83 ms
collect
35 ms
x_button_blue2.png
24 ms
s
21 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
nr-885.min.js
44 ms
ga-audiences
18 ms
68b8ba3b8c
101 ms
68b8ba3b8c
101 ms
activeview
16 ms
spling.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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
spling.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
spling.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 Spling.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 Spling.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.
spling.co.za
Open Graph description is not detected on the main page of SPLING. 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: