2.9 sec in total
285 ms
2 sec
697 ms
Welcome to rock.co.za homepage info - get ready to check Rock best content for South Africa right away, or after learning these important things about rock.co.za
The online South African Rock Encyclopedia covers the history of South African rock music from the 1950s up to the early 2000s
Visit rock.co.zaWe analyzed Rock.co.za page load time and found that the first response time was 285 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
rock.co.za performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value4.0 s
50/100
25%
Value8.6 s
17/100
10%
Value4,500 ms
0/100
30%
Value0.001
100/100
15%
Value21.7 s
1/100
10%
285 ms
40 ms
83 ms
5 ms
49 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Rock.co.za, 17% (21 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (611 ms) relates to the external source Primewholesale.com.
Page size can be reduced by 646.0 kB (29%)
2.2 MB
1.6 MB
In fact, the total size of Rock.co.za main page is 2.2 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 55.3 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 55.3 kB or 71% 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. Rock images are well optimized though.
Potential reduce by 438.2 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 438.2 kB or 59% of the original size.
Potential reduce by 147.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. Rock.co.za needs all CSS files to be minified and compressed as it can save up to 147.0 kB or 41% of the original size.
Number of requests can be reduced by 75 (60%)
124
49
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
rock.co.za
285 ms
style.css
40 ms
plusone.js
83 ms
adsbygoogle.js
5 ms
sugarmusicnews
49 ms
addthis_widget.js
21 ms
brand
48 ms
cb=gapi.loaded_0
106 ms
bg.jpg
121 ms
woordfees-facebook-advert.jpg
130 ms
b.gif
114 ms
276 ms
after-the-facts-page-001.jpg
197 ms
mabu-vinyl-in-business-day-july-2015.jpg
196 ms
311 ms
feed-icon-10x10.gif
125 ms
logo234x60.jpg
343 ms
samp3logo234x60.jpg
271 ms
google_custom_search_watermark.gif
170 ms
ga.js
148 ms
b.gif
79 ms
b.gif
78 ms
b.gif
78 ms
b.gif
78 ms
b.gif
78 ms
b.gif
78 ms
b.gif
82 ms
b.gif
86 ms
b.gif
86 ms
saturday-star-page-001.jpg
142 ms
image001.jpg
86 ms
top-of-the-charts.jpg
143 ms
black-cat-bones.jpg
77 ms
sarockdigest_logo.jpg
294 ms
mabuvinyl234x60.jpg
293 ms
rock.gif
85 ms
mabu.jpg
144 ms
buzzboost-pwrd.gif
86 ms
ca-pub-0505917757824939.js
134 ms
zrt_lookup.html
133 ms
show_ads_impl.js
77 ms
ads
220 ms
osd.js
70 ms
__utm.gif
59 ms
boost
52 ms
300lo.json
81 ms
all.js&version=v2.0
220 ms
cb=gapi.loaded_1
34 ms
fastbutton
150 ms
ads
256 ms
sh.07f0d9bf220d07a763adad1e.html
125 ms
likebox.php
315 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
267 ms
widget-0511d506.css
82 ms
widget-d9304090.js
160 ms
ads
244 ms
postmessageRelay
42 ms
_lfreshmusic_1269090859full.jpg
611 ms
3193398744-postmessagerelay.js
78 ms
rpc:shindig_random.js
61 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
50 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
135 ms
0_Is8B5ADf.jpg
452 ms
a.gif
34 ms
bcs0
120 ms
creative_add_on.js
172 ms
cb=gapi.loaded_0
20 ms
banner
197 ms
222 ms
a.gif
44 ms
creative_add_on.js
170 ms
bcs0
56 ms
0_H8Tzm6X6.jpg
339 ms
xd_arbiter.php
166 ms
xd_arbiter.php
254 ms
logo-200x120-177df3dd.png
126 ms
hDvwL1_H7g-.css
218 ms
udqjbTyb5Ue.css
293 ms
yZ--Yu0PDbV.css
368 ms
QD6_ejUFoCN.css
395 ms
xxJgcoj8mOR.css
417 ms
q68gy-v_YMF.js
435 ms
FJmpeSpHpjS.js
450 ms
0wM5s1Khldu.js
394 ms
1bNoFZUdlYZ.js
409 ms
njO1TPvGzoR.js
430 ms
1QuX41zDRrx.js
430 ms
Oagsvfb4VWi.js
473 ms
LTv6ZK-5zxz.js
505 ms
1FCa-btixu2.js
472 ms
surly.js
331 ms
ga.js
194 ms
visual-single-sound-cd67be80.js
116 ms
error-698b3c1d.js
87 ms
adServer.bs
254 ms
IconOnlyCollisionMarker.png
172 ms
CollisionAdMarker.png
220 ms
surly.js
263 ms
beacon.js
165 ms
logo_grey-377f1b9e.png
83 ms
smds
196 ms
oxds
144 ms
__utm.gif
68 ms
__utm.gif
67 ms
__utm.gif
87 ms
__utm.gif
76 ms
ba.html
73 ms
4.gif
96 ms
28f3ade9-8342-4cc4-aa2e-05588572b5bd.jpg
119 ms
2532.js
47 ms
box_19_top-right.png
147 ms
ci.png
143 ms
420305_10151351749740704_235215646_n.jpg
218 ms
safe_image.php
214 ms
safe_image.php
206 ms
safe_image.php
208 ms
10391946_346900225703_5064213_n.jpg
207 ms
wL6VQj7Ab77.png
72 ms
s7jcwEQH7Sx.png
71 ms
QDwYpIaRyfG.png
73 ms
K00K-UgnsKu.png
74 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
35 ms
ping
65 ms
like.php
159 ms
LVx-xkvaJ0b.png
18 ms
rock.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
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
rock.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
Page has valid source maps
rock.co.za 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 Rock.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 Rock.co.za 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.
rock.co.za
Open Graph description is not detected on the main page of Rock. 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: