3.2 sec in total
155 ms
2.8 sec
267 ms
Visit movistar.co now to see the best up-to-date Movistar content for Colombia and also check out these interesting facts you probably never knew about movistar.co
Contrata tu plan de Internet Hogar con Fibra Óptica, lleva tu celular favorito con un Plan Pospago y recibe todos los beneficios que Movistar tiene para ti.
Visit movistar.coWe analyzed Movistar.co page load time and found that the first response time was 155 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.
movistar.co performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value8.3 s
2/100
25%
Value32.2 s
0/100
10%
Value28,140 ms
0/100
30%
Value0.727
6/100
15%
Value54.4 s
0/100
10%
155 ms
228 ms
1294 ms
109 ms
132 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 74% of them (101 requests) were addressed to the original Movistar.co, 8% (11 requests) were made to Mi.movistar.co and 3% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Www5.smartadserver.com.
Page size can be reduced by 2.5 MB (65%)
3.8 MB
1.3 MB
In fact, the total size of Movistar.co main page is 3.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. 65% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 184.7 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 50.0 kB, which is 24% 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 184.7 kB or 87% of the original size.
Potential reduce by 15.6 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. Movistar images are well optimized though.
Potential reduce by 1.0 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 1.0 MB or 70% of the original size.
Potential reduce by 1.2 MB
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. Movistar.co needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 88% of the original size.
Number of requests can be reduced by 76 (63%)
121
45
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Movistar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
movistar.co
155 ms
www.movistar.co
228 ms
config.js
1294 ms
aui.css
109 ms
main.css
132 ms
main.css
72 ms
main.css
77 ms
main.css
74 ms
main.css
112 ms
main.css
110 ms
main.css
114 ms
main.css
112 ms
main.css
132 ms
main.css
145 ms
barebone.jsp
253 ms
main.js
149 ms
navigation.js
150 ms
main.js
160 ms
main.js
157 ms
main.css
328 ms
jquery-1.10.1.min.js
255 ms
bootstrap.min.js
183 ms
jssor.js
185 ms
jssor.slider.min.js
191 ms
general.js
219 ms
jquery.jcarousel-0.2.8.min.js
211 ms
jcarousel-pagination.js
222 ms
hammer.min.js
239 ms
jquery.hammer.js
258 ms
jquery.validate.js
257 ms
jquery.zaccordion.min.js
267 ms
jquery.carouFredSel-6.2.1-packed.js
283 ms
banners.js
286 ms
preventDefaultSearch.js
144 ms
login-popup.js
269 ms
skype-uri.js
271 ms
0a74e587-b7ca-46ec-9cef-4fdebb21856a
268 ms
9c089a32-3a3e-4d0d-b2c8-578664bb13b0
297 ms
f30b536f-579a-4224-9acd-e3541ca48d46
267 ms
main.js
266 ms
main.js
260 ms
main.js
268 ms
main.js
281 ms
main.js
259 ms
smart.js
49 ms
company_logo
37 ms
layout_icon
34 ms
layout_icon
37 ms
layout_icon
30 ms
layout_icon
38 ms
layout_icon
37 ms
ico_mimovistar_bco.png
54 ms
6a0e5262-7d06-465b-966c-ae4b088c2bd5
67 ms
339a3c25-83db-449d-a208-b611d8ef1167
71 ms
0ee2900b-8433-4610-a0bf-7632219718bf
186 ms
09fc7054-e621-46fd-a840-a60b41b16a17
71 ms
Alcatel-1534-0.png
72 ms
ico_carrito.png
79 ms
Huawei-1621-0.png
99 ms
Huawei-1687-0.png
106 ms
Apple-1645-0.png
107 ms
Xiaomi-1685-0.png
145 ms
Motorola-1668-0.png
104 ms
ver_mas.png
139 ms
4ae1cbc5-bfea-42cc-95e4-a926055a5751
138 ms
0ad25d50-d86d-4daa-a4e6-b4ba20b5a932
144 ms
abfff708-13ee-4671-a684-b463e40d8678
145 ms
c2c12793-6cfe-44a1-a598-77ccf4a64f95
233 ms
3575441a-1552-4448-8f41-98ffcaea3f5d
177 ms
9dd1dc2a-5644-4a61-ac9e-eb2642a8a823
189 ms
5b0543ba-d931-4fc8-a357-04caa49850fd
188 ms
2aa628d9-a281-48ff-a056-7d0235a1ec69
187 ms
93a3dd16-4a9b-4f07-9361-fffad9322934
214 ms
439f8a84-241a-4f53-9b91-3f60e45b1163
203 ms
d9409d8f-1658-49f2-8754-4b9b4ad21262
226 ms
35aaef8a-8246-4fde-bfd7-df29f371f05a
270 ms
3ee336c1-7fb6-4f00-a6ef-5d95b0af456a
226 ms
layout_icon
230 ms
layout_icon
250 ms
layout_icon
270 ms
layout_icon
292 ms
gtm.js
31 ms
241 ms
movistartext-regular-webfont.woff
267 ms
movistartext-bold-webfont.woff
267 ms
logo_telefonica.png
265 ms
ico_separador_blue.png
292 ms
oct.js
75 ms
activityi;src=4626130;type=colom0;cat=lpg_m0;u1=%2C%2C;u2=%2C%2C;ord=6079243558599;~oref=http%3A%2F%2Fwww.movistar.co%2F
48 ms
ebOneTag.js
37 ms
conversion.js
44 ms
adsct
102 ms
adsct
62 ms
Serving
67 ms
59 ms
67 ms
78 ms
81 ms
pixel
21 ms
33 ms
25 ms
21 ms
49 ms
skype-analytics.js
27 ms
ico_mimovistar.png
58 ms
ico_movil.png
57 ms
55 ms
mi.movistar.co
214 ms
ico_arrow_blue3.png
59 ms
ico_separador_white.png
38 ms
ico_search.png
60 ms
movistarheadline-regular-webfont.woff
39 ms
fontawesome-alloy.woff
38 ms
51 ms
1cdc5591-d14d-4b73-a706-bafa9b0f6619
59 ms
fd2909ce-3391-4ce2-8ae2-a14edf955189
57 ms
dotmovistar-font.woff
56 ms
movistarheadline-bold-webfont.woff
78 ms
4a40058f-c89f-472c-8a6d-7f481f0930fd
104 ms
estilos_login.min.css
33 ms
google-analyticsM.min.js
35 ms
jquery-1.10.2.min.js
205 ms
jquery.validate.js
80 ms
jquery.validate.unobtrusive.js
80 ms
modernizr-2.6.2.js
81 ms
jquery.fancybox.js
129 ms
jquery.fancybox.pack.js
129 ms
Login.js
128 ms
dc.js
145 ms
__utm.gif
45 ms
Login_Social.png
36 ms
movistartext-bold-webfont.woff
12 ms
94f21d8a-bcda-4f47-a9d6-e2ea28fd587b
51 ms
4fbb2fb1-8a74-4606-b823-c49a930ccdd8
35 ms
41 ms
86 ms
movistar.co 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible 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.
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.
movistar.co 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
movistar.co SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 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 Movistar.co 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 Movistar.co 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.
movistar.co
Open Graph description is not detected on the main page of Movistar. 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: