6.9 sec in total
1.9 sec
4 sec
1 sec
Visit rollingstone.com.mx now to see the best up-to-date Rolling Stone content for Mexico and also check out these interesting facts you probably never knew about rollingstone.com.mx
Conoce historias exclusivas, noticias relevantes de música y lo mejor del entretenimiento en Rolling Stone en Español México.
Visit rollingstone.com.mxWe analyzed Rollingstone.com.mx page load time and found that the first response time was 1.9 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rollingstone.com.mx performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value17.1 s
0/100
25%
Value12.4 s
3/100
10%
Value2,670 ms
4/100
30%
Value0.015
100/100
15%
Value25.9 s
0/100
10%
1865 ms
86 ms
92 ms
324 ms
141 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 90% of them (92 requests) were addressed to the original Rollingstone.com.mx, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Rollingstone.com.mx.
Page size can be reduced by 4.2 MB (28%)
15.3 MB
11.1 MB
In fact, the total size of Rollingstone.com.mx main page is 15.3 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. 85% 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. Images take 14.7 MB which makes up the majority of the site volume.
Potential reduce by 132.1 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 43.1 kB, which is 29% 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 132.1 kB or 89% of the original size.
Potential reduce by 3.8 MB
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, Rolling Stone needs image optimization as it can save up to 3.8 MB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 125.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 125.1 kB or 61% of the original size.
Potential reduce by 118.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. Rollingstone.com.mx needs all CSS files to be minified and compressed as it can save up to 118.0 kB or 64% of the original size.
Number of requests can be reduced by 24 (26%)
94
70
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
rollingstone.com.mx
1865 ms
wp-emoji-release.min.js
86 ms
csbwfs.css
92 ms
admin-ajax.php
324 ms
dashicons.min.css
141 ms
font-awesome.min.css
97 ms
genericons.css
142 ms
css
77 ms
style.css
133 ms
jquery.js
224 ms
jquery-migrate.min.js
143 ms
sam-layout.min.js
179 ms
hoverIntent.min.js
184 ms
maxmegamenu.js
189 ms
searchbox.js
189 ms
jquery.raty.css
224 ms
jquery.raty.js
230 ms
labs.css
238 ms
custom-responsive.css
238 ms
labs.js
269 ms
scrollover.js
269 ms
navigation.js
244 ms
wp-embed.min.js
253 ms
scrollover.js
251 ms
custom.js
283 ms
ga.js
85 ms
_skin-seat.jpg
1161 ms
Captura-de-pantalla-2016-02-27-a-las-0.49.34.png
1167 ms
Captura-de-pantalla-2016-01-18-a-las-17.19.05.png
308 ms
Captura-de-pantalla-2016-02-08-a-las-17.24.36.png
1163 ms
Captura-de-pantalla-2016-02-28-a-las-22.41.43.png
1160 ms
Captura-de-pantalla-2016-02-29-a-las-10.22.53-a.m..png
1167 ms
Captura-de-pantalla-2016-02-23-a-las-10.21.22-a.m..png
1172 ms
tiger.jpg
1162 ms
ResidentEvil0HD_Trajes051.jpg
1187 ms
Captura-de-pantalla-2016-02-26-a-las-2.21.26-p.m..png
1164 ms
Lamb_of-god-300x3001-150x150.jpg
1163 ms
global-logo-rs.png
1195 ms
twitter.png
1167 ms
facebook.png
1167 ms
line.png
1168 ms
kgtnB-150x150.jpg
1171 ms
_leaderboard-seat.jpg
1178 ms
Captura-de-pantalla-2016-02-29-a-las-10.23.20-45x45.png
1172 ms
Captura-de-pantalla-2016-02-29-a-las-10.13.19-a.m.-45x45.png
1172 ms
6e0b906f-45x45.jpg
1173 ms
Captura-de-pantalla-2016-02-29-a-las-9.48.57-a.m.-45x45.png
1174 ms
Captura-de-pantalla-2016-02-29-a-las-9.35.47-45x45.png
1175 ms
Captura-de-pantalla-2016-02-28-a-las-22.41.43-45x45.png
1176 ms
Captura-de-pantalla-2016-02-27-a-las-0.49.34-45x45.png
1177 ms
screen-shot-2016-02-25-at-3-23-53-pm-45x45.png
1178 ms
Captura-de-pantalla-2016-02-26-a-las-2.21.26-p.m.-45x45.png
1179 ms
The-Strokes-45x45.jpg
1179 ms
banner_0274.jpg
1179 ms
leonardo-dicaprio-golden-globes-45x45.jpg
1180 ms
goldenglobes-45x45.jpg
1181 ms
AUNOJ-45x45.jpg
1181 ms
rlZL1-45x45.jpg
1184 ms
banner_0267.jpg
1185 ms
caprio_efe6.jpg
1186 ms
Captura-de-pantalla-2016-02-29-a-las-10.22.53-a.m.-624x358.png
1191 ms
quant.js
19 ms
Captura-de-pantalla-2016-02-29-a-las-10.23.20-624x348.png
1167 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
122 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
123 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
53 ms
pixel;r=1660195345;a=p-3-QtYPPfBVMQA;fpan=1;fpa=P0-60226916-1456764777544;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456764777544;tzo=-180;ref=;url=http%3A%2F%2Frollingstone.com.mx%2F;ogl=
60 ms
__utm.gif
20 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
16 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
61 ms
GothamNarrow-Medium.otf
111 ms
parkinson-roman-webfont.woff
85 ms
parkinson-medium-webfont.woff
53 ms
GarageGothic-Black.otf
84 ms
sam-ajax.php
617 ms
sam-ajax.php
633 ms
Captura-de-pantalla-2016-02-29-a-las-10.13.19-a.m.-624x385.png
192 ms
6e0b906f-624x398.jpg
81 ms
Captura-de-pantalla-2016-02-29-a-las-9.48.57-a.m.-624x388.png
182 ms
Captura-de-pantalla-2016-02-29-a-las-9.35.47-624x364.png
217 ms
Captura-de-pantalla-2016-02-28-a-las-22.41.43-624x357.png
175 ms
Captura-de-pantalla-2016-02-27-a-las-0.49.34-624x431.png
355 ms
screen-shot-2016-02-25-at-3-23-53-pm-624x416.png
290 ms
The-Strokes.jpg
204 ms
cash-624x469.jpg
220 ms
Captura-de-pantalla-2016-02-26-a-las-13.09.27.png
382 ms
grafico574FINAL.jpg
644 ms
tiger-150x150.jpg
265 ms
obama-150x150.jpg
273 ms
Captura-de-pantalla-2016-02-16-a-las-10.56.14-a.m.-150x150.png
324 ms
middle_vj_rec.jpg
335 ms
foo_twitter.jpg
351 ms
foo_facebook.jpg
384 ms
foo_line.jpg
395 ms
foo_google.jpg
408 ms
foo_instagram.jpg
413 ms
foo_vine.jpg
432 ms
foo_spotify.jpg
443 ms
foo_youtube.jpg
455 ms
1.jpg
463 ms
search.png
464 ms
arrow.png
479 ms
rollingstone.com.mx 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
Links do not have a discernible name
rollingstone.com.mx 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
rollingstone.com.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rollingstone.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Rollingstone.com.mx 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.
rollingstone.com.mx
Open Graph description is not detected on the main page of 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: