7.7 sec in total
2.2 sec
5.2 sec
381 ms
Click here to check amazing Forum Rolling Stone content for Germany. Otherwise, check out these important facts you probably never knew about forum.rollingstone.de
Das Forum für das Musikmagazin: News, Live, Videos, Reviews
Visit forum.rollingstone.deWe analyzed Forum.rollingstone.de page load time and found that the first response time was 2.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
forum.rollingstone.de performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.1 s
48/100
25%
Value11.3 s
5/100
10%
Value400 ms
68/100
30%
Value0.277
44/100
15%
Value9.5 s
30/100
10%
2161 ms
31 ms
506 ms
545 ms
205 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 18% of them (29 requests) were addressed to the original Forum.rollingstone.de, 7% (12 requests) were made to Cdn1.smartadserver.com and 6% (10 requests) were made to Rtb-csync.smartadserver.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Forum.rollingstone.de.
Page size can be reduced by 426.3 kB (58%)
738.3 kB
312.0 kB
In fact, the total size of Forum.rollingstone.de main page is 738.3 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. 50% of websites need less resources to load. Javascripts take 479.9 kB which makes up the majority of the site volume.
Potential reduce by 141.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 141.9 kB or 86% of the original size.
Potential reduce by 42 B
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. Forum Rolling Stone images are well optimized though.
Potential reduce by 280.3 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 280.3 kB or 58% of the original size.
Potential reduce by 4.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. Forum.rollingstone.de needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 80% of the original size.
Number of requests can be reduced by 127 (88%)
145
18
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forum Rolling Stone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
forum.rollingstone.de
2161 ms
yuiloader-dom-event.js
31 ms
vbulletin-core.js
506 ms
css.php
545 ms
vbulletin_read_marker.js
205 ms
css.php
327 ms
css.php
227 ms
rollingstone.js
149 ms
css
26 ms
connection-min.js
12 ms
vbulletin_md5.js
211 ms
jquery.min.js
70 ms
iam.js
397 ms
webtrekk_v4.min.js
409 ms
ph-general-first.js
299 ms
asmb-tracking_alt.js
300 ms
rollingstone.png
303 ms
search.png
104 ms
navbit-home.png
104 ms
collapse_40b.png
105 ms
forum_old-48.png
107 ms
lastpost-right.png
105 ms
subforum_old-48.png
207 ms
poll_posticon.gif
203 ms
icon5.png
210 ms
users_online.png
208 ms
forum_stats.png
209 ms
legend.png
248 ms
forum_new-16.png
305 ms
forum_old-16.png
305 ms
category-16.png
305 ms
forum_link-16.png
306 ms
smartad.js
24 ms
adplayer.css
8 ms
c.html
9 ms
adplayer.js
11 ms
datafactor.js
10 ms
partner
168 ms
yield.js
8 ms
nuggad.js
11 ms
prebid.js
11 ms
meetrics.js
10 ms
adplayer.sas.js
4 ms
ovkvmf.js
5 ms
default.js
165 ms
p.min.js
4 ms
ihb.js
330 ms
24062,24064,24066,24068,134448,134452,232227,232229,261425
99 ms
data
374 ms
prebid.js
25 ms
mtrcs_147519.js
24 ms
partner
116 ms
ac
228 ms
diewelt.gif
113 ms
toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf
38 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
90 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
92 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
92 ms
newbtn_middle.png
139 ms
submit
311 ms
235 ms
selected-tab-gradient-with-top-alpha.png
109 ms
sortarrow-asc.png
109 ms
grey-up.png
115 ms
rss_40b.png
116 ms
gradient-greytowhite.png
116 ms
analytics.js
35 ms
wt
246 ms
qs.ioam.de
191 ms
tx.io
193 ms
1221
306 ms
a.js
353 ms
aip
112 ms
st.min.html
23 ms
index.html
33 ms
ca
58 ms
collect
23 ms
comp.asp
93 ms
ac
215 ms
adex.js
281 ms
adrtxtag.min.js
163 ms
Enabler.js
42 ms
collect
79 ms
ga-audiences
40 ms
tx.io
104 ms
2.gif
95 ms
CookieSync.html
9 ms
jstag
37 ms
quant.js
15 ms
CookieSync.min.js
19 ms
sync
21 ms
pixel.htm
35 ms
usermatch
28 ms
pixelpush
19 ms
p68r
19 ms
generic
21 ms
pixel
34 ms
92 ms
92 ms
94 ms
usermatch
22 ms
pixel;r=1525293719;a=p-T1nhLcmCjVzQS;fpan=1;fpa=P0-1910066995-1456762892415;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456762892414;tzo=-180;ref=http%3A%2F%2Fforum.rollingstone.de%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D251%26dcid%3D3;ogl=
10 ms
generic
14 ms
acj
41 ms
ddc.htm
32 ms
pixel
48 ms
t.js
129 ms
gr
38 ms
casale
35 ms
90 ms
Pug
64 ms
sd
41 ms
rtset
67 ms
rum
56 ms
u.php
110 ms
pixel
61 ms
72 ms
70 ms
a.js
1010 ms
rum
51 ms
rum
104 ms
pixel
113 ms
85 ms
sync
53 ms
merge
47 ms
pd
50 ms
ac
117 ms
mapuser
46 ms
xrefid.xgi
60 ms
rum
56 ms
bd
67 ms
crum
34 ms
daa57f38-369c-a719-e9e2-6236b10cf680
56 ms
pixel
35 ms
NAX5113506184130048247
54 ms
38 ms
lr.gif
18 ms
rum
20 ms
bd
52 ms
pixel.gif
74 ms
sd
16 ms
1.gif
92 ms
analytic.js
169 ms
172 ms
sd
14 ms
sd
12 ms
crum
19 ms
m
34 ms
show8.asp
106 ms
29 ms
crum
9 ms
url
21 ms
32 ms
jsinfo.asp
87 ms
1_wlg_120x600.jpg
12 ms
pixel
17 ms
cm.gif
92 ms
2.gif
97 ms
cap
4 ms
ca
8 ms
ca
8 ms
get
4 ms
get
6 ms
tap.php
379 ms
a.js
689 ms
forum.rollingstone.de 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Form elements do not have associated labels
Links do not have a discernible name
forum.rollingstone.de 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
forum.rollingstone.de SEO score
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
Tap targets are not sized appropriately
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forum.rollingstone.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Forum.rollingstone.de 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.
forum.rollingstone.de
Open Graph description is not detected on the main page of Forum Rolling Stone. 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: