2.7 sec in total
19 ms
2.3 sec
374 ms
Visit reporteindigo.com now to see the best up-to-date Reporte Indigo content for Mexico and also check out these interesting facts you probably never knew about reporteindigo.com
Reporte Índigo se publica de lunes a viernes en la CDMX, Guadalajara y Monterrey. Noticias, entrevistas, opinión, videos.
Visit reporteindigo.comWe analyzed Reporteindigo.com page load time and found that the first response time was 19 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.
reporteindigo.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value9.2 s
1/100
25%
Value6.5 s
39/100
10%
Value2,220 ms
6/100
30%
Value0
100/100
15%
Value13.9 s
10/100
10%
19 ms
5 ms
48 ms
67 ms
46 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 9% of them (16 requests) were addressed to the original Reporteindigo.com, 34% (61 requests) were made to Df3vgdkto12gv.cloudfront.net and 16% (29 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (645 ms) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 4.0 MB (48%)
8.4 MB
4.4 MB
In fact, the total size of Reporteindigo.com main page is 8.4 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. Javascripts take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 98.5 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 98.5 kB or 85% of the original size.
Potential reduce by 51.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. Reporte Indigo images are well optimized though.
Potential reduce by 3.4 MB
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 3.4 MB or 81% of the original size.
Potential reduce by 507.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. Reporteindigo.com needs all CSS files to be minified and compressed as it can save up to 507.0 kB or 84% of the original size.
Number of requests can be reduced by 67 (39%)
174
107
The browser has sent 174 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reporte Indigo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
reporteindigo.com
19 ms
type.css
5 ms
css_0b14602d6f6c936ddc897a426cc6009a_3110.css
48 ms
js_09e907a53e6a731628ef9ec9d9afd79d_3110.js
67 ms
thickbox_engine.js
46 ms
agile_carousel.alpha.js
7 ms
agile_carousel_home.js
8 ms
adsbygoogle.js
10 ms
ct.js
126 ms
gpt.js
5 ms
css_605a7081171a6f6480c7ebeded02e98c_70033.css
5 ms
pubads_impl_81.js
9 ms
container.html
54 ms
get_data
551 ms
atrk.js
105 ms
logo.png
45 ms
mail.jpeg
40 ms
90 ms
banner-sidebar-ideas.jpg
37 ms
Reporte_logo_gris.png
33 ms
comscore_logo_dark.bkg.png
34 ms
IE8.png
34 ms
bg-buscar.png
32 ms
920_oscar_35_3.jpg
51 ms
920_medioambiente_07_35.jpg
44 ms
920_cdmex_04_4.jpg
51 ms
920_senado_06_10.jpg
50 ms
920_durango_06_1.jpg
49 ms
920_irak_07_2.jpg
43 ms
920_eu_09_38.jpg
61 ms
920_marcadores_32_13.jpg
59 ms
920_fan_el_trabajo_943_1.jpg
66 ms
920_mty_promete_garcia_943_1.jpg
66 ms
920_independientes_18_3.jpg
65 ms
920_df_344.jpg
65 ms
920_mty_portada_943_0.jpg
79 ms
920_piensa_portada_943_0.jpg
79 ms
920_latitud_portada_943_0.jpg
95 ms
920_nomics_eu_28_1.jpg
112 ms
920_nomics_26_4.jpg
82 ms
920_mty_12.jpg
95 ms
ri_naclemus_920_0.jpg
245 ms
920_portada_963.jpg
113 ms
screen_shot_2016-02-26_at_7.39.59_am.png
112 ms
screen_shot_2016-02-26_at_7.39.57_am.png
111 ms
screen_shot_2016-02-26_at_7.39.53_am.png
110 ms
screen_shot_2016-02-25_at_7.32.03_am.png
165 ms
redes-de-poder.png
166 ms
redes-monterrey.png
165 ms
920_latitud_portada_943_0.jpg
167 ms
920_portada_963.jpg
167 ms
920_medioambiente_07_35.jpg
190 ms
920_irak_07_2.jpg
169 ms
920_mty_12.jpg
168 ms
920_oscar_35_3.jpg
193 ms
920_cdmex_04_4.jpg
195 ms
920_senado_06_10.jpg
192 ms
ca-pub-9078701942132883.js
70 ms
zrt_lookup.html
144 ms
show_ads_impl.js
100 ms
StagSansWeb-Book.woff
37 ms
StagSansWeb-Book.woff
173 ms
920_front_piden_descabezar_937_1.jpg
174 ms
920_fugachapo_06_13.jpg
163 ms
icon-type-taxonomia-gris.png
108 ms
StagSansWeb-Medium.woff
108 ms
StagSansWeb-Medium.woff
75 ms
atrk.gif
152 ms
89 ms
ads
190 ms
StagWeb-Medium.woff
40 ms
StagWeb-Medium.woff
37 ms
osd.js
35 ms
test.png
368 ms
ads
347 ms
ads
275 ms
circulo-gris-36px.png
64 ms
i-circulo-small.png
55 ms
all.js
88 ms
ga.js
35 ms
wFnm1sVhsrs
234 ms
loadingAnimation.gif
39 ms
afr.php
227 ms
StagWeb-Semibold.woff
44 ms
StagWeb-Semibold.woff
94 ms
StagSansWeb-Light.woff
146 ms
StagSansWeb-Light.woff
94 ms
__utm.gif
158 ms
306 ms
xd_arbiter.php
138 ms
xd_arbiter.php
221 ms
collect
149 ms
940_portada_194.jpg
60 ms
940_mty_9.jpg
62 ms
940_latitud_portada_943.jpg
58 ms
940_peinsa_portada_943.jpg
104 ms
940_oscar_35.jpg
105 ms
940_portada_194.jpg
54 ms
940_mty_9.jpg
103 ms
940_latitud_portada_943.jpg
103 ms
940_peinsa_portada_943.jpg
93 ms
940_oscar_35.jpg
101 ms
sprite_ac_normal.gif
105 ms
afr.php
81 ms
audi_t2_2017_q7_160x600.html
114 ms
www-embed-player-vflZsBgOl.css
109 ms
www-embed-player.js
160 ms
base.js
225 ms
ford_dealershipbrand_02_300x250.html
114 ms
like_box.php
384 ms
adUtils_v1.js
6 ms
edge.6.0.0.min.js
110 ms
adUtils_v1.js
36 ms
edge.6.0.0.min.js
197 ms
audi_t2_2017_q7_160x600_edge.js
124 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
61 ms
ad_status.js
48 ms
ford_dealershipbrand_02_300x250_edge.js
18 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
170 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
235 ms
audi_t2_2017_q7_160x600_edge.js
18 ms
roNeOY-tz5Y.css
235 ms
UHhaxo8Cs3k.css
254 ms
dbNRhrdsQao.css
282 ms
1ssvpqNRk1L.css
318 ms
O8DK6hTywHD.css
330 ms
Qz9nHTUX1Wv.css
305 ms
_rx8naC75Dy.js
330 ms
x5F9OMjKyLw.js
395 ms
ICDbTSzjQEg.js
303 ms
TTCre3391I0.js
371 ms
njO1TPvGzoR.js
371 ms
b_6HNn_J2BZ.js
370 ms
7cm7D75Y0Sf.js
415 ms
rFmE1g6Dkoz.js
422 ms
336JejShbZp.js
413 ms
C-h3nYPqETO.js
413 ms
oRoBXlHCpEy.js
412 ms
sj-JwAJi4AH.js
413 ms
DKRU1bYTkTw.js
449 ms
ZNPAadQNc33.js
419 ms
W0OV23mIOyO.js
452 ms
36TdwhIHusi.js
455 ms
ford_dealershipbrand_02_300x250_edge.js
11 ms
TweenMax.min.js
76 ms
TweenMax.min.js
77 ms
TweenMax.min.js
136 ms
TweenMax.min.js
136 ms
audiLogo.jpg
113 ms
heroImage.jpg
73 ms
audi_t2_2017_q7_160x600.html
96 ms
ctaArrow.png
106 ms
closeBtn.svg
104 ms
AudiType-ExtendedBold.woff
71 ms
webfont.woff
75 ms
10227_26.png
58 ms
bgGradient_mc.png
58 ms
Ford-Logo.png
27 ms
closeBtn.svg
26 ms
webfont.woff
34 ms
webfont.woff
34 ms
12311159_10153916042178900_917100054264766314_n.jpg
138 ms
safe_image.php
612 ms
safe_image.php
627 ms
safe_image.php
645 ms
10367177_10154058892498900_6872168800312179074_n.jpg
147 ms
12366249_519293968235638_184363204068478620_n.jpg
163 ms
10425507_833235800108805_9184675103453860057_n.jpg
182 ms
11079108_1435194766776294_5155808804500991215_n.jpg
184 ms
12791071_142342359487284_713306023744015942_n.jpg
188 ms
12744052_1301901629835520_5416473611313441306_n.jpg
186 ms
12187933_913019315439882_3136941299042636972_n.jpg
190 ms
10367177_10154058892498900_6872168800312179074_n.jpg
190 ms
12813922_10154092412438900_2810336918010409849_n.png
260 ms
wL6VQj7Ab77.png
90 ms
s7jcwEQH7Sx.png
92 ms
QDwYpIaRyfG.png
89 ms
a-ZN6WoEOje.png
91 ms
pUFVdPjIRct.png
58 ms
activeview
25 ms
I6-MnjEovm5.js
21 ms
vlXaquuXMrr.js
39 ms
reporteindigo.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
reporteindigo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
reporteindigo.com 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reporteindigo.com 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 Reporteindigo.com 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.
reporteindigo.com
Open Graph description is not detected on the main page of Reporte Indigo. 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: