7 sec in total
805 ms
4.9 sec
1.3 sec
Visit indyrock.es now to see the best up-to-date Indy Rock content for Spain and also check out these interesting facts you probably never knew about indyrock.es
Revista de musica creada en 1997, Cronicas de conciertos, agenda de conciertos, festivales, noticias de musica, grupos musicales, fotos en directo, videos de conciertos, informacion de bandas, musica ...
Visit indyrock.esWe analyzed Indyrock.es page load time and found that the first response time was 805 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
indyrock.es performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value9.9 s
0/100
25%
Value9.3 s
12/100
10%
Value3,770 ms
1/100
30%
Value0.366
29/100
15%
Value20.3 s
2/100
10%
805 ms
261 ms
810 ms
10 ms
6 ms
Our browser made a total of 190 requests to load all elements on the main page. We found that 27% of them (52 requests) were addressed to the original Indyrock.es, 8% (16 requests) were made to Www8.smartadserver.com and 6% (12 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Indyrock.es.
Page size can be reduced by 870.5 kB (42%)
2.1 MB
1.2 MB
In fact, the total size of Indyrock.es main page is 2.1 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 42.0 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 42.0 kB or 75% of the original size.
Potential reduce by 47.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. Indy Rock images are well optimized though.
Potential reduce by 775.1 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 775.1 kB or 67% of the original size.
Potential reduce by 6.2 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. Indyrock.es needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 76% of the original size.
Number of requests can be reduced by 93 (54%)
173
80
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy 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 44 to 1 for JavaScripts and as a result speed up the page load time.
indyrock.es
805 ms
indybasico.css
261 ms
combined.js
810 ms
show_ads.js
10 ms
adsbygoogle.js
6 ms
BrightcoveExperiences.js
10 ms
gpt.js
8 ms
pubads_impl_82.js
8 ms
container.html
14 ms
jquery.mousewheel.min.js
8 ms
rocklogo-menu.jpg
498 ms
boton-enportada-1220.jpg
382 ms
boton-acciones-portada-1.jpg
376 ms
imagenindy-840.jpg
577 ms
negro.jpg
380 ms
conciertos-mini.jpg
375 ms
festivales-mini.jpg
669 ms
noticias-mini.jpg
670 ms
concursos-mini.jpg
670 ms
tablon-mini.jpg
673 ms
productoras-mini.jpg
764 ms
locales-mini.jpg
811 ms
grupos-mini.jpg
900 ms
estudios-mini.jpg
947 ms
sesiones-mini.jpg
1025 ms
boton-contenidos-1220.jpg
1029 ms
latino-mini.jpg
1136 ms
linea-gris-325px.jpg
1295 ms
imagenindy-50.jpg
1299 ms
imagenindy-8.jpg
1561 ms
imagenindy-9.jpg
1630 ms
imagenindy-2.jpg
1637 ms
imagenindy-5.jpg
1564 ms
imagenindy-10.jpg
1731 ms
imagenindy-4.jpg
1729 ms
imagenindy-6.jpg
2020 ms
imagenindy-5-2.jpg
1951 ms
091guit.JPG
1942 ms
imagenindy-100.jpg
2365 ms
imagenindy-22.jpg
2349 ms
flecha1-negra.jpg
2255 ms
091-2006-1.jpg
2362 ms
video-icono.jpg
2362 ms
boton-festivales-avance-400.jpg
2362 ms
imagenindy-60.jpg
2355 ms
imagenindy-3.jpg
2790 ms
beacon.js
9 ms
ga.js
31 ms
ca-pub-0855266518209567.js
262 ms
zrt_lookup.html
251 ms
show_ads_impl.js
100 ms
__utm.gif
203 ms
sdk.js
291 ms
ads
324 ms
ads
217 ms
osd.js
86 ms
imagenindy-7-2.jpg
2284 ms
imagenindy.jpg
2450 ms
tendencias-mini.jpg
2293 ms
videos-boton.jpg
2277 ms
ads
338 ms
galerias-boton.jpg
2100 ms
galerias-boton2.jpg
2234 ms
upgrade_flash_player2.gif
78 ms
187 ms
container.html
76 ms
ads
132 ms
abg.js
235 ms
imagenindy-1.jpg
2211 ms
escenario159.jpg
2212 ms
indy-promocion-1.jpg
2212 ms
ads
327 ms
boton-indyrock-tira-1220.jpg
2267 ms
ads
391 ms
m_js_controller.js
261 ms
googlelogo_color_112x36dp.png
530 ms
8853858147196721803
378 ms
gris-claro.jpg
2255 ms
widgets.js
266 ms
player-javascript.php
559 ms
rocklogo-corto.jpg
2222 ms
s
208 ms
redir.html
530 ms
rocklogo-menu.jpg
2263 ms
x_button_blue2.png
202 ms
ads
611 ms
negro.jpg
2216 ms
ads
551 ms
11560.js
319 ms
nessie_icon_tiamat_white.png
159 ms
ads
393 ms
ads
254 ms
ads
252 ms
xd_arbiter.php
171 ms
xd_arbiter.php
309 ms
player.js
122 ms
8581531730848267780
101 ms
iframe.html
105 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
167 ms
ac
274 ms
activeview
156 ms
styles-slider.css
332 ms
LiveRail.AdManager-1.0.js
202 ms
sync
193 ms
ffffff_new_ico.gif
92 ms
ac
270 ms
402792-2.js
120 ms
show0.asp
118 ms
handshake.html
301 ms
social-icons-facebook.gif
324 ms
social-icons-twitter.gif
408 ms
social-icons-google.gif
410 ms
play_large.png
410 ms
2.jpg
479 ms
CookieSync.html
296 ms
ads
357 ms
jsinfo.asp
262 ms
show0.asp
258 ms
quant.js
109 ms
CookieSync.min.js
106 ms
ads
190 ms
jsinfo.asp
77 ms
ac
176 ms
sync
43 ms
pixel.htm
75 ms
usermatch
55 ms
pixelpush
39 ms
p68r
104 ms
generic
57 ms
pixel
74 ms
usermatch
75 ms
184 ms
generic
69 ms
177 ms
ddc.htm
108 ms
ac
246 ms
174 ms
172 ms
pixel;r=1144544201;a=p-T1nhLcmCjVzQS;fpan=1;fpa=P0-1498308046-1458135514136;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458135514135;tzo=-180;ref=;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1588%26dcid%3D5;ogl=
97 ms
Vulh2sAoJYAAAjwttdAAAABn%26949
156 ms
ecs
130 ms
141 ms
casale
125 ms
140 ms
show0.asp
154 ms
Pug
148 ms
pixel
148 ms
rtset
136 ms
rum
125 ms
u.php
130 ms
um
223 ms
127 ms
129 ms
ecc
83 ms
crum
84 ms
match
84 ms
103 ms
rum
80 ms
crum
84 ms
merge
79 ms
tap.php
80 ms
mapuser
81 ms
ads
125 ms
crum
72 ms
xrefid.xgi
73 ms
lr.gif
70 ms
bd
85 ms
78 ms
sd
80 ms
pixel.gif
57 ms
show0.asp
78 ms
rum
69 ms
crum
66 ms
rum
65 ms
sync
100 ms
bd
57 ms
ads
103 ms
ac
116 ms
30 ms
NAX4583630508212501902
36 ms
ac
128 ms
show0.asp
44 ms
ads
119 ms
show0.asp
44 ms
ads
126 ms
ca-pub-6954290567593225.js
52 ms
ads
331 ms
ac
110 ms
show0.asp
129 ms
favicon
98 ms
indyrock.es 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
Heading elements are not in a sequentially-descending order
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
indyrock.es 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
indyrock.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
ES
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indyrock.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Indyrock.es 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.
indyrock.es
Open Graph description is not detected on the main page of Indy 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: