4.1 sec in total
369 ms
3.5 sec
247 ms
Visit elpoblado.com now to see the best up-to-date Elpoblado content and also check out these interesting facts you probably never knew about elpoblado.com
Todo sobre el Barrio Poblado de Medellín en el Periódigo Gente Poblado
Visit elpoblado.comWe analyzed Elpoblado.com page load time and found that the first response time was 369 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
elpoblado.com performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.8 s
56/100
25%
Value2.8 s
96/100
10%
Value300 ms
79/100
30%
Value0.008
100/100
15%
Value8.2 s
40/100
10%
369 ms
131 ms
275 ms
244 ms
381 ms
Our browser made a total of 216 requests to load all elements on the main page. We found that 15% of them (32 requests) were addressed to the original Elpoblado.com, 20% (43 requests) were made to Static.xx.fbcdn.net and 14% (30 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 932.8 kB (33%)
2.8 MB
1.9 MB
In fact, the total size of Elpoblado.com main page is 2.8 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 17.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 17.5 kB or 73% of the original size.
Potential reduce by 36.2 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. Elpoblado images are well optimized though.
Potential reduce by 804.9 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 804.9 kB or 68% of the original size.
Potential reduce by 74.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. Elpoblado.com needs all CSS files to be minified and compressed as it can save up to 74.2 kB or 82% of the original size.
Number of requests can be reduced by 98 (48%)
204
106
The browser has sent 204 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elpoblado. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
elpoblado.com
369 ms
styles.css
131 ms
camera.css
275 ms
tooltip.css
244 ms
jquery-ui-1.9.2.min.css
381 ms
css
26 ms
jquery.min.js
419 ms
jquery.mobile.customized.min.js
408 ms
jquery.easing.1.3.js
276 ms
camera.min.js
510 ms
jquery-ui-1.9.2.min.js
790 ms
googleanalytics.js
410 ms
eplv4.js
504 ms
home.js
536 ms
jquery.tabify.js
540 ms
ct.js
17 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
15 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
64 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
65 ms
ga.js
16 ms
all.js
14 ms
patter-header.png
165 ms
poblado-logo.png
162 ms
btn-suscripcion-boletin.png
163 ms
poblado-icon-facebook.png
162 ms
poblado-icon-twitter.png
163 ms
poblado-epaper.jpg
301 ms
pattern-title.png
289 ms
point-title.jpg
287 ms
bg-suscribete.png
307 ms
widgets.js
52 ms
gente-plan.jpg
458 ms
promociones-gente.jpg
459 ms
p2
50 ms
fpTVHK8qsXbIeTHTrnQH6Iue0YgdIF4L_q7PS4yTQOQ.ttf
50 ms
fpTVHK8qsXbIeTHTrnQH6BzYcsdbdSWRnnT3pSZS3xU.ttf
48 ms
epl-41.js
47 ms
1c4e
46 ms
HistoriasPoblado.aspx
386 ms
__utm.gif
61 ms
point-map.jpg
410 ms
bg-poblado.png
666 ms
161 ms
overlay1.png
377 ms
camera-loader.gif
378 ms
camera_skins.png
507 ms
poblado-1.jpg
1012 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
58 ms
xd_arbiter.php
39 ms
xd_arbiter.php
74 ms
embed
476 ms
syndication
99 ms
411604919959830528
183 ms
like_box.php
509 ms
Gente_El_Colombiano_1
79 ms
Gente_El_Colombiano_1
5 ms
multi-sync.js
23 ms
1f697.png
147 ms
2YN67sHI9-LhjZXz.jpg
147 ms
1f393.png
139 ms
1f467.png
139 ms
1f3a8.png
139 ms
1f3f0.png
141 ms
1f436.png
139 ms
1f340.png
141 ms
1f345.png
143 ms
1f33d.png
143 ms
1f3ad.png
143 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
34 ms
emily.html
132 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
76 ms
toastr.min.css
146 ms
gentestory.css
284 ms
jquery-1.9.1.min.js
719 ms
toastr.min.js
282 ms
gentestory.js
306 ms
cW44BYv1_normal.jpeg
96 ms
nfQfLoDm_normal.jpg
304 ms
QKAqzHTf_normal.jpeg
95 ms
J1HlDA_D_normal.jpeg
96 ms
0HqaOkY3_normal.jpeg
175 ms
Cd3g-BCW0AE7VaR.jpg:small
100 ms
Cd2-VY3XIAAfr3s.jpg:small
102 ms
Cd1pFW8VAAEldkP.jpg:small
102 ms
CdySx16WoAIYYDy.jpg:small
99 ms
CdwSQ1FWIAA0Avu.jpg:small
101 ms
CdwPEsDWAAAEObo.jpg:small
104 ms
CdsamJCXEAMY_PC.jpg:small
102 ms
Cdr01ghW0AEFK7y.jpg:small
102 ms
CdmSdtLWIAA3NrM.jpg:small
290 ms
CdmEGKNW8AETXN7.jpg:small
105 ms
Cdh-0spW4AQAHXU.jpg:small
106 ms
CdhAPfFWwAEKibB.jpg:small
105 ms
CdXt4MuXEAAa_7X.jpg:small
106 ms
CdXPsxIW4AADL3d.jpg:small
136 ms
CdXNmP_XIAAxwMz.jpg:small
105 ms
CdXLnwAWoAAi2N1.jpg:small
106 ms
CdWur2tWoAEtwGf.jpg:small
126 ms
rs=ABjfnFWG0j3zhtsZ1FCMy39vp-nQopMVGw
56 ms
css
153 ms
js
160 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
97 ms
hDvwL1_H7g-.css
67 ms
56WNbrUYLbL.css
69 ms
yZ--Yu0PDbV.css
88 ms
GN27K_co9Wc.css
86 ms
QD6_ejUFoCN.css
74 ms
xxJgcoj8mOR.css
87 ms
gbh6x73jsGH.css
78 ms
khX_DTDmaMU.css
70 ms
q68gy-v_YMF.js
85 ms
FJmpeSpHpjS.js
108 ms
0wM5s1Khldu.js
105 ms
1bNoFZUdlYZ.js
117 ms
njO1TPvGzoR.js
106 ms
OloiM1PZafe.js
116 ms
LTv6ZK-5zxz.js
203 ms
1FCa-btixu2.js
118 ms
Oagsvfb4VWi.js
202 ms
pObvZSrFc_4.js
222 ms
Kt4tkgSRvHH.js
227 ms
H3EKDTObx05.js
226 ms
eR-qA8bp1RM.js
225 ms
1QuX41zDRrx.js
226 ms
IjqSyiwKeaX.js
225 ms
rBxSIHk4zIe.js
234 ms
n6VgtouijQL.js
240 ms
7BE0CZr3HTs.js
241 ms
pQrUxxo5oQp.js
234 ms
_UYztdBNTjs.js
233 ms
-7JBD_ybv4q.js
246 ms
jot
195 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
229 ms
common.js
232 ms
map.js
284 ms
overlay.js
317 ms
1493-wht-blank_maps-4x.png&filter=ff7C3592&scale=1.0
372 ms
util.js
336 ms
marker.js
326 ms
poly.js
308 ms
geocoder.js
361 ms
controls.js
371 ms
places_impl.js
361 ms
selection_2x-000.png
215 ms
943861_1063091937067817_6677567851078469396_n.jpg
319 ms
safe_image.php
1332 ms
1528675_665546030155745_1817694176_n.jpg
350 ms
11822647_137848853220860_4189018314942386744_n.jpg
367 ms
1476018_10152036963893529_1948708133_n.jpg
396 ms
12249990_10153836283526209_4068298137869993032_n.jpg
376 ms
12654543_10153877643203618_9172635695012520125_n.jpg
374 ms
524827_10200543426123819_1360081961_n.jpg
374 ms
12794531_108547309540909_2464859168678026351_n.jpg
376 ms
12794534_460583184148394_6644143646749254244_n.jpg
396 ms
10599616_1063375847039426_3206822735760919062_n.jpg
408 ms
12365766_1063157157061295_1493829232_n.jpg
394 ms
943861_1063091937067817_6677567851078469396_n.jpg
384 ms
1488765_1063081460402198_415475559523673265_n.jpg
389 ms
wL6VQj7Ab77.png
215 ms
s7jcwEQH7Sx.png
214 ms
Qs-Ha2XZpNj.png
213 ms
QDwYpIaRyfG.png
214 ms
yDaBsYcc9pr.png
213 ms
l5aPruN9xMM.png
213 ms
b39fgpId85q.png
273 ms
sSwLTfB7PfP.png
272 ms
aeO1ik7i7-T.png
308 ms
K00K-UgnsKu.png
272 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
305 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
307 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
355 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
361 ms
gen204
222 ms
b8XhdWI9eAN.js
180 ms
gxbPuQdXIZP.png
159 ms
K_65vAc89SX.png
192 ms
poblado-2.jpg
265 ms
poblado-lo-que-contas.jpg
408 ms
poblado-title-historias.png
183 ms
send-poblado.png
183 ms
img-form.png
262 ms
onion.js
112 ms
ViewportInfoService.GetViewportInfo
90 ms
stats.js
90 ms
transparent.png
125 ms
undo_poly.png
112 ms
mapcnt6.png
55 ms
vt
37 ms
vt
76 ms
vt
99 ms
vt
37 ms
vt
34 ms
vt
81 ms
vt
56 ms
vt
46 ms
vt
47 ms
vt
78 ms
vt
82 ms
vt
84 ms
vt
88 ms
vt
100 ms
vt
105 ms
tmapctrl4.png
42 ms
vt
97 ms
um
19 ms
viewer-icons001.png
89 ms
star4.png
91 ms
1492-wht-polygon-blank.png&filter=ff7C3592&scale=1.0
74 ms
gen204
82 ms
AuthenticationService.Authenticate
37 ms
MyMaps_Icons003.png
19 ms
mymaps_32.png
22 ms
v1_4593b7d7.png
24 ms
google-my-maps-logo-small-001.png
23 ms
kh
67 ms
I6-MnjEovm5.js
5 ms
elpoblado.com 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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
elpoblado.com 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
elpoblado.com 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 doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elpoblado.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Elpoblado.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.
elpoblado.com
Open Graph description is not detected on the main page of Elpoblado. 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: