8.7 sec in total
1.4 sec
7 sec
287 ms
Visit somoscali.com now to see the best up-to-date Somoscali content and also check out these interesting facts you probably never knew about somoscali.com
somoscali.com directorio comercial zonificado, con geolocalizador exclusivo para Santiago de Cali, todos los lugares y eventos en un solo lugar somoscali.com
Visit somoscali.comWe analyzed Somoscali.com page load time and found that the first response time was 1.4 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
somoscali.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value1.114
1/100
15%
Value0
0/100
10%
1421 ms
22 ms
48 ms
301 ms
199 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 48% of them (68 requests) were addressed to the original Somoscali.com, 19% (27 requests) were made to Maps.google.com and 6% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Somoscali.com.
Page size can be reduced by 1.1 MB (49%)
2.2 MB
1.1 MB
In fact, the total size of Somoscali.com main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 123.6 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 123.6 kB or 80% of the original size.
Potential reduce by 49.5 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. Somoscali images are well optimized though.
Potential reduce by 710.6 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 710.6 kB or 61% of the original size.
Potential reduce by 174.8 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. Somoscali.com needs all CSS files to be minified and compressed as it can save up to 174.8 kB or 84% of the original size.
Number of requests can be reduced by 74 (54%)
136
62
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Somoscali. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.somoscali.com
1421 ms
js
22 ms
geometa.js
48 ms
style.css
301 ms
6-skyblue.css
199 ms
wprhe_qrcode_style.css
1517 ms
style.css
172 ms
styles.css
183 ms
jetpack.css
393 ms
jquery.js
524 ms
jquery-migrate.min.js
301 ms
custom.js
449 ms
js
23 ms
mailchimp-widget-min.js
391 ms
plusone.js
78 ms
map.js
566 ms
widgets.js
4 ms
addthis_widget.js
12 ms
jquery.form.min.js
508 ms
scripts.js
551 ms
devicepx-jetpack.js
4 ms
gprofiles.js
56 ms
wpgroho.js
516 ms
add-divs-to-coded-excerpts.js
578 ms
e-201611.js
4 ms
reset.css
423 ms
1-default.css
547 ms
ga.js
28 ms
wp-emoji-release.min.js
147 ms
__utm.gif
11 ms
analytics.js
18 ms
cb=gapi.loaded_0
33 ms
s2.jpg
352 ms
b634dd2f3a0cc7f4aacd1c25306386b3
93 ms
s4.jpg
352 ms
s5.jpg
351 ms
s1.jpg
351 ms
s3.jpg
352 ms
logo.png
381 ms
pin.png
143 ms
thumb.php
1362 ms
rating_off.png
194 ms
thumb.php
351 ms
thumb.php
378 ms
thumb.php
447 ms
thumb.php
455 ms
thumb.php
528 ms
rating_on.png
498 ms
thumb.php
571 ms
thumb.php
566 ms
thumb.php
600 ms
thumb.php
650 ms
thumb.php
684 ms
thumb.php
719 ms
thumb.php
739 ms
app_somoscali3.png
760 ms
rss.png
738 ms
top_nav_sepretor.png
801 ms
search_forbg.png
806 ms
nearmebg.png
833 ms
b_search.png
828 ms
common.js
15 ms
util.js
16 ms
geocoder.js
15 ms
collect
54 ms
category_stripbg.png
832 ms
cat_nav_h.png
889 ms
cat_nav_n.png
909 ms
shadow_bg.png
872 ms
fullscreen.png
872 ms
loading2.gif
1888 ms
minus-white-icon.png
1004 ms
new.png
1030 ms
featured.png
1095 ms
i_comment2.png
1102 ms
i_more.png
1241 ms
gravatar2.png
373 ms
gravatar2.png
503 ms
fastbutton
85 ms
i_comment.png
1268 ms
like.php
83 ms
i_image.png
1356 ms
bullet_b.png
1292 ms
rs=AGLTcCMAwxoRoD2FCk39OgVvopwW4qkyyw
136 ms
footerbg.png
1557 ms
fy8tT2klpgR.js
330 ms
LVx-xkvaJ0b.png
365 ms
hovercard.css
75 ms
services.css
124 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
72 ms
boost
32 ms
300lo.json
53 ms
cb=gapi.loaded_0
52 ms
cb=gapi.loaded_1
106 ms
sepretor.png
1489 ms
sh.07f0d9bf220d07a763adad1e.html
72 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
114 ms
g.gif
65 ms
previous.png
1479 ms
next.png
1669 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
29 ms
dot_h2.png
1606 ms
dot_n2.png
1933 ms
jot
91 ms
print.css
359 ms
map.js
4 ms
onion.js
14 ms
openhand_8_8.cur
23 ms
ViewportInfoService.GetViewportInfo
51 ms
stats.js
15 ms
controls.js
9 ms
transparent.png
17 ms
css
45 ms
google4.png
44 ms
marker.js
23 ms
mapcnt6.png
45 ms
sv5.png
49 ms
infowindow.js
19 ms
tmapctrl.png
21 ms
cb_scout5.png
27 ms
tmapctrl4.png
22 ms
imgs8.png
22 ms
vt
80 ms
vt
97 ms
vt
82 ms
vt
156 ms
vt
78 ms
vt
74 ms
vt
157 ms
vt
164 ms
vt
168 ms
vt
144 ms
vt
189 ms
vt
191 ms
vt
226 ms
vt
225 ms
vt
247 ms
vt
318 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
20 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
29 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
48 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
48 ms
AuthenticationService.Authenticate
148 ms
somoscali.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
somoscali.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
somoscali.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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Somoscali.com 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 Somoscali.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.
somoscali.com
Open Graph description is not detected on the main page of Somoscali. 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: