4.4 sec in total
460 ms
3.8 sec
131 ms
Visit 123.cl now to see the best up-to-date 123 content for Chile and also check out these interesting facts you probably never knew about 123.cl
Disfruta de los mejores planes en telefonía móvil, conoce el catálogo de equipos, recarga en línea y aprovecha los beneficios que Entel tiene para ti.
Visit 123.clWe analyzed 123.cl page load time and found that the first response time was 460 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
123.cl performance score
460 ms
575 ms
262 ms
263 ms
1040 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 41% of them (35 requests) were addressed to the original 123.cl, 14% (12 requests) were made to Static.xx.fbcdn.net and 13% (11 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 123.cl.
Page size can be reduced by 621.9 kB (47%)
1.3 MB
697.8 kB
In fact, the total size of 123.cl 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. 55% of websites need less resources to load. Javascripts take 709.7 kB which makes up the majority of the site volume.
Potential reduce by 15.0 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 3.7 kB, which is 19% 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 15.0 kB or 76% of the original size.
Potential reduce by 13.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. 123 images are well optimized though.
Potential reduce by 498.2 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 498.2 kB or 70% of the original size.
Potential reduce by 95.1 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. 123.cl needs all CSS files to be minified and compressed as it can save up to 95.1 kB or 85% of the original size.
Number of requests can be reduced by 42 (51%)
82
40
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
123.cl
460 ms
www.123.cl
575 ms
style.css
262 ms
carrousel.css
263 ms
jquery.min.js
1040 ms
jquery-ui.min.js
1330 ms
jquery-1.4.2.min.js
704 ms
jquery.pngFix.js
391 ms
jquery.jcarousel.min.js
659 ms
jquery.mousewheel.js
522 ms
jScrollPane.js
791 ms
base.js
795 ms
funcionesTwitter.js
917 ms
cookies.js
963 ms
activex.js
1055 ms
home123_smtp.js
1066 ms
funciones-entelchile.js
1188 ms
jquery.carouFredSel-6.2.1-packed.js
1356 ms
jquery.fancybox-1.2.5.css
1310 ms
jquery.fancybox-1.2.5.js
1446 ms
logo-123.png
261 ms
logo-entel.png
393 ms
PERSONAS-123-PUNTO-CE-ELE-BANNER--DISEnO.jpg
1066 ms
banner_cuanto-pesan-App.jpg
1352 ms
facebook.jpg
677 ms
ico-calendario.png
269 ms
des2.jpg
1311 ms
uso_aplicaciones.jpg
943 ms
peso_apps.jpg
1052 ms
btn-youtube.jpg
949 ms
btn-twitter.jpg
1212 ms
btn-facebook.jpg
1219 ms
gtm.js
64 ms
bg-login.png
1308 ms
widgets.js
32 ms
btn_carouselHomeLiquidoSeleccionado.png
1290 ms
btn_carouselHomeLiquido.png
1438 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
24 ms
analytics.js
24 ms
likebox.php
191 ms
syndication
106 ms
357490420923650048
279 ms
collect
19 ms
collect
70 ms
ga-audiences
47 ms
roNeOY-tz5Y.css
29 ms
UHhaxo8Cs3k.css
44 ms
O8DK6hTywHD.css
35 ms
_rx8naC75Dy.js
48 ms
x5F9OMjKyLw.js
59 ms
ICDbTSzjQEg.js
59 ms
TTCre3391I0.js
47 ms
10437665_10152542585311125_6745668722453038513_n.jpg
54 ms
10351172_10152392571121125_8216536121963217957_n.png
42 ms
67737_10200189129872798_619333541_n.jpg
29 ms
12573822_966363646778196_7419126813759801092_n.jpg
76 ms
12141577_1510584465927125_8017955423507259586_n.jpg
42 ms
12208778_1635638523390865_8969624761194821855_n.jpg
43 ms
10354686_10150004552801856_220367501106153455_n.jpg
42 ms
HEyyDkPknAC.png
23 ms
wL6VQj7Ab77.png
22 ms
s7jcwEQH7Sx.png
22 ms
1f47d.png
130 ms
1f499.png
154 ms
1f44a.png
183 ms
1f609.png
210 ms
1f525.png
237 ms
1f602.png
241 ms
1f3b6.png
241 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
13 ms
cPcWXQ0t_normal.png
129 ms
CcV-fkmWEAE89AW.jpg:small
160 ms
CcT3RdHW4AErZHD.jpg:small
208 ms
CcR33buUcAALakX.jpg:small
237 ms
CcRsDwAW4AAUXrI.jpg:small
251 ms
CcRc_EwWEAIJFT4.jpg:small
256 ms
CcRJSI_W4AAqkOp.jpg:small
265 ms
CcRA54XWIAE3m3Q.jpg:small
269 ms
CcQw4VsUcAEtwBg.jpg:small
271 ms
CcMxKmRXEAAQQtg.jpg:small
270 ms
CcMjo7iW4AAzqfo.jpg:small
278 ms
I6-MnjEovm5.js
13 ms
vlXaquuXMrr.js
13 ms
jot
25 ms
123.cl SEO score
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123.cl 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 123.cl 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.
123.cl
Open Graph description is not detected on the main page of 123. 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: