3.1 sec in total
43 ms
2.4 sec
652 ms
Visit notinfomex.co now to see the best up-to-date Notinfomex content for Mexico and also check out these interesting facts you probably never knew about notinfomex.co
Notinfomex. Espacio de noticias relevantes del narcotráfico, política y sociales de México y EU
Visit notinfomex.coWe analyzed Notinfomex.co page load time and found that the first response time was 43 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
notinfomex.co performance score
43 ms
140 ms
80 ms
304 ms
45 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Notinfomex.co, 7% (10 requests) were made to Apis.google.com and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Msnoticias.com.
Page size can be reduced by 502.0 kB (40%)
1.3 MB
762.0 kB
In fact, the total size of Notinfomex.co main page is 1.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. 80% 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 541.2 kB which makes up the majority of the site volume.
Potential reduce by 177.2 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 177.2 kB or 79% of the original size.
Potential reduce by 15.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. Notinfomex images are well optimized though.
Potential reduce by 309.7 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 309.7 kB or 57% of the original size.
Potential reduce by 9 B
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. Notinfomex.co has all CSS files already compressed.
Number of requests can be reduced by 79 (60%)
132
53
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Notinfomex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
notinfomex.co
43 ms
www.notinfomex.co
140 ms
3645911276-widget_css_bundle.css
80 ms
authorization.css
304 ms
mootools-yui-compressed.js
45 ms
jsapi
23 ms
brand
36 ms
adsbygoogle.js
17 ms
plusone.js
53 ms
addthis_widget.js
23 ms
show.jsp
228 ms
66512.js
21 ms
3731899860-widgets.js
76 ms
t13n
58 ms
brand
71 ms
background.png
33 ms
Sin+2.png
36 ms
icon18_wrench_allbkg.png
60 ms
Notinfomex-Narcoviolencia.jpg
32 ms
proxy
126 ms
taxista%20(4)_0.jpg
709 ms
veracruz3-650x400.jpg
343 ms
Cceuz73UMAATWGN.jpg
341 ms
twitter.png
28 ms
facebook.png
55 ms
favorites.png
67 ms
eL%2BKINO1.png
119 ms
Cceu0x3UMAAgZcX.jpg
403 ms
Cceu0rkUMAAU65N.jpg
405 ms
taxista%20(3).jpg
774 ms
taxista%20(5).jpg
782 ms
taxista%20(1)_0.jpg
1058 ms
folder.png
53 ms
stumbleupon.png
52 ms
rss.png
51 ms
twitter.png
50 ms
Screen%2BShot%2B2016-02-29%2Bat%2B05.59.36%2Bcopia.png
115 ms
JOVENCITA%2BESCALPELADA%2BEN%2BEDOMEX%2BNOTINFOMEX.png
116 ms
SEDENA%2BOPERATIVOS%2BANITNARCO%2BNOTINFOMEX.jpg
115 ms
more.png
32 ms
date.png
48 ms
comments.png
58 ms
BALACERA%2BTECOMAN%2BCOL%2BNOTINFOMEX.png
113 ms
delicious.png
48 ms
digg.png
47 ms
proxy
143 ms
proxy
194 ms
proxy
334 ms
proxy
334 ms
proxy
330 ms
pagenav-backgr.png
101 ms
32 ms
transliteration.css
4 ms
transliteration.I.js
8 ms
38 ms
mainnav-sep.gif
86 ms
nav-backgr-hover.png
35 ms
google_custom_search_watermark.gif
221 ms
ca-pub-1956006214007973.js
211 ms
zrt_lookup.html
209 ms
show_ads_impl.js
70 ms
share_buttons_20_3.png
48 ms
inputtools.js
46 ms
bullet.gif
149 ms
ads
324 ms
cb=gapi.loaded_0
26 ms
cb=gapi.loaded_1
26 ms
google_top_exp.js
24 ms
osd.js
25 ms
ads
248 ms
ads
219 ms
blank.html
65 ms
navbar.g
252 ms
emb.js
571 ms
likebox.php
112 ms
script.js
108 ms
main.js
105 ms
beacon.js
18 ms
sync
6 ms
8361415091744328133
77 ms
abg.js
77 ms
m_js_controller.js
85 ms
googlelogo_color_112x36dp.png
74 ms
3849684925742746547
125 ms
BdmCbeqDF1M.css
459 ms
34E4j2xurGO.css
546 ms
_rx8naC75Dy.js
697 ms
b94UUzHjapV.js
852 ms
0wM5s1Khldu.js
851 ms
TTCre3391I0.js
851 ms
ads
436 ms
summary
117 ms
s
57 ms
x_button_blue2.png
58 ms
favicon
295 ms
nessie_icon_tiamat_white.png
74 ms
icons_peach.png
340 ms
platform:gapi.iframes.style.common.js
336 ms
arrows-light.png
338 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
51 ms
min-inimage.js
16 ms
min-intextualv2.js
19 ms
66512.js
171 ms
kwServe
353 ms
300lo.json
193 ms
sh.7c7179124ea24ac6ba46caac.html
86 ms
66512.js
137 ms
kwServe
309 ms
mobile_unified_button_icon_white.png
118 ms
favicon
503 ms
cb=gapi.loaded_0
316 ms
cb=gapi.loaded_1
312 ms
fastbutton
406 ms
adServe
257 ms
base.js
303 ms
306723_445063002195288_1132132606_n.jpg
280 ms
12734159_986082938094280_5405611779602697808_n.jpg
310 ms
1379841_10150004552801901_469209496895221757_n.jpg
351 ms
12417685_1010475888991600_6881258555936822990_n.jpg
389 ms
12661924_10153950320196204_5674002466214654881_n.jpg
390 ms
11222475_102383856766410_1346174273351670902_n.jpg
393 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
84 ms
postmessageRelay
96 ms
cb=gapi.loaded_0
37 ms
cb=gapi.loaded_1
40 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
133 ms
api.js
102 ms
core:rpc:shindig.random:shindig.sha1.js
160 ms
2536007149-postmessagerelay.js
128 ms
inimage-close.png
97 ms
b
26 ms
bounce
15 ms
b
18 ms
sync
64 ms
activeview
14 ms
__tt.gif
7 ms
__tt.gif
7 ms
__tt.gif
8 ms
I6-MnjEovm5.js
42 ms
f6T91Deal_q.js
80 ms
ui
14 ms
notinfomex.co SEO score
N/A
N/A
\
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notinfomex.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Notinfomex.co main page’s claimed encoding is \. 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.
notinfomex.co
Open Graph description is not detected on the main page of Notinfomex. 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: