2.6 sec in total
92 ms
2 sec
478 ms
Welcome to telmex.com homepage info - get ready to check Telmex best content for Mexico right away, or after learning these important things about telmex.com
Contrata Infinitum para tu hogar; el mejor servicio de internet y telefonía en México. Obtén Claro video, antivirus y compra con cargo a tu Recibo Telmex.
Visit telmex.comWe analyzed Telmex.com page load time and found that the first response time was 92 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
telmex.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value12.1 s
0/100
25%
Value6.5 s
39/100
10%
Value4,010 ms
1/100
30%
Value0.315
37/100
15%
Value20.7 s
2/100
10%
92 ms
481 ms
173 ms
229 ms
221 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 86% of them (70 requests) were addressed to the original Telmex.com, 9% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (679 ms) belongs to the original domain Telmex.com.
Page size can be reduced by 7.5 MB (85%)
8.8 MB
1.3 MB
In fact, the total size of Telmex.com main page is 8.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. 75% 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. HTML takes 7.6 MB which makes up the majority of the site volume.
Potential reduce by 7.4 MB
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 7.4 MB or 97% of the original size.
Potential reduce by 13.7 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. Telmex images are well optimized though.
Potential reduce by 67.3 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 67.3 kB or 16% of the original size.
Potential reduce by 19.0 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. Telmex.com needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 22% of the original size.
Number of requests can be reduced by 29 (41%)
71
42
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Telmex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
telmex.com
92 ms
telmex.com
481 ms
aui.css
173 ms
main.css
229 ms
main.css
221 ms
main.css
227 ms
barebone.jsp
383 ms
main.css
361 ms
css
185 ms
css2
186 ms
libraries.js
262 ms
portal_normal.js
297 ms
223f8a93-98f1-3ab9-f346-99eb45f0d80c
307 ms
af3cd3af-8cf1-726f-4002-f5d0fbc508d6
306 ms
85e83dc5-88ce-b3e5-7e3d-316e84abf204
341 ms
functions-ui.min.js
557 ms
main.js
208 ms
main.js
403 ms
stormcaster.js
200 ms
fd1183b3-c08d-7c40-86f0-cec5dd75c6d7
210 ms
85cf9615-c098-7621-9436-3342a446ce63
206 ms
7489bc1c-2077-3574-e040-417977b3579f
204 ms
d9140559-41b7-7063-4da6-87e2a688a159
207 ms
760190cc-ea05-9c53-a254-8558b58be176
201 ms
97389232-7aef-a185-9d02-ee26330900c5
212 ms
b6f42c38-1fcf-ae96-333f-5ab0d9150c8e
268 ms
107b4475-8a62-9d42-ba59-7aedf2e944eb
268 ms
957009c4-1dd1-6b0c-9cdb-6e93e53d2382
272 ms
4ad35e22-5359-fabc-15b9-5d3d3377c2bb
271 ms
95733d36-db17-2b11-7896-709ea7f3cfb0
270 ms
037dea09-70f2-f72c-1283-5074b51f8e25
284 ms
194d8950-7433-0a34-f290-eaae7be1bb1e
384 ms
c508b8b3-2b90-0b94-56cb-ca42b513a14d
288 ms
8bcf0422-eaae-cf9a-1379-2f2b785e470a
381 ms
d283cf3d-bdc7-2629-1240-f45152919b13
385 ms
b9616ba0-4410-5916-5b62-1b83b139d761
388 ms
45bb4d60-2cae-a8ef-c5cf-1622bfe1317d
390 ms
2233d357-e6ac-7114-cc94-0b52b6d92b06
390 ms
65fe43d8-1513-ed3e-7b40-29b2497edc67
393 ms
4761e934-acac-a30a-12a0-8eca99d6f15b
393 ms
36d63c92-b344-74a6-160a-05d4f20c7ab4
390 ms
3d0ae184-ea8d-b1ca-1695-b48a66afe86f
396 ms
548f84d1-7030-30f9-4fe4-db9492c71163
480 ms
7bed5682-33dc-3c71-a899-ea1d6770d0f2
482 ms
1e2d51e3-a286-1c96-ea94-6897c5edbc90
484 ms
96ab3c62-0141-196e-18c4-dc246aef212e
485 ms
4b8114c2-b9d6-692a-ec18-3b861baf33c7
483 ms
608ef0be-6abd-4c4e-2e09-d90dd6860469
486 ms
e1b35bc7-1aa6-aec7-a482-8988e5f5018c
529 ms
2379a9a2-50d5-f997-99c8-d42990a78aab
530 ms
6da3e9ee-b647-6dc1-337b-22fc19efaf74
531 ms
eba975ae-b9cb-63dc-9543-ffd004c9c659
539 ms
7982f7d5-0bdb-d99e-b9a6-ada78c822041
514 ms
KFOmCnqEu92Fr1Mu4mxM.woff
148 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
148 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
150 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
149 ms
f66fa20c-fabc-1fab-8e76-9b115d380870
525 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBK.woff
139 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBK.woff
139 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBK.woff
139 ms
4e98269d-98f9-f89e-87b7-9d55029c4de5
407 ms
53fdcced-9559-9674-2564-5cf585652183
435 ms
6dc14eb6-2242-cdab-b3ba-9c13c2d2fdbb
435 ms
eb7c3493-8782-664e-bbe2-bb556b93b1d7
437 ms
3719eca2-6569-e8c3-30b4-9fc3dcb3d863
437 ms
5bd685e1-07a7-269b-cc14-d8de747d5054
439 ms
iconos.woff
454 ms
d30daa61-83b3-96e8-a7c8-591234d83094
570 ms
right_arrow.svg
679 ms
96f21b1c-917d-7920-347e-5599291ade3b
571 ms
10dc4e98-a7c6-66a7-89a8-85688ef11ab8
676 ms
72cbe7fb-fd10-3dc0-ddc1-5aa636544680
665 ms
5a1dd06a-c8c6-602b-c8c0-37ec4cb2489a
664 ms
ajax-loader.gif
565 ms
a7a4a35b-0da1-e4a3-ab0f-4bc64f1526e3
560 ms
9ba69778-4a9e-a308-2acc-16c5e6d96a60
565 ms
e73ad7cb-cbec-dfa9-52c3-d7d79f941206
569 ms
255f1c65-1322-f60e-751f-a93839e029ae
355 ms
285 ms
gtm.js
277 ms
telmex.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
telmex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
telmex.com 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 doesn't use 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 Telmex.com 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 Telmex.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.
telmex.com
Open Graph data is detected on the main page of Telmex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: