Access claro.com.co. ¡Descubre por qué con Claro lo puedes todo!

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value24.5 s

0/100

25%

SI (Speed Index)

Value24.1 s

0/100

10%

TBT (Total Blocking Time)

Value5,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.269

45/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

claro.com.co

238 ms

209 ms

gtm.js

96 ms

gtm.js

204 ms

bk-coretag.js

140 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 74% of them (79 requests) were addressed to the original Claro.com.co, 7% (7 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source Wsa1.byside.com.

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Claro.com.co main page is 2.5 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. 80% 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 558.6 kB

Original 672.2 kB
After minification 672.2 kB
After compression 113.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 558.6 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 10.4 kB

Original 1.4 MB
After minification 1.4 MB

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. Claro images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 13.6 kB

Original 343.6 kB
After minification 343.6 kB
After compression 330.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-68%

Potential reduce by 73.1 kB

Original 107.9 kB
After minification 107.4 kB
After compression 34.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. Claro.com.co needs all CSS files to be minified and compressed as it can save up to 73.1 kB or 68% of the original size.

Requests Now

After Optimization

The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Claro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Claro.com.co 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 Claro.com.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.

Social Sharing Optimization

claro.com.co

Open Graph data is detected on the main page of Claro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

¡Descubre por qué con Claro lo puedes todo! | Claro Colombia

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

claro.com.co

gtm.js

gtm.js

bk-coretag.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

claro.com.co

gtm.js

gtm.js

bk-coretag.js

bwc_sa1.js

font-claro.css

css2

api.js

jquery-2.2.4.min.js

animate.min.css

slick.js

lazysizes.min.js

ls.parent-fit.min.js

jquery.fancybox.min.css

jquery.fancybox.min.js

wow.min.js

logo-appMiClaro.png

logo-MiClaro.png

flag-argentina.svg

flag-brasil.svg

flag-chile.svg

flag-colombia.svg

flag-costa-rica.svg

flag-ecuador.svg

flag-el-salvador.svg

flag-estados-unidos.svg

flag-guatemala.svg

flag-honduras.svg

flag-nicaragua.svg

flag-panama.svg

flag-paraguay.svg

flag-peru.svg

flag-puerto-rico.svg

flag-dominicana.svg

flag-uruguay.svg

1644860549715-logo-claro.png

logo-claro-blanco.svg

1712863378290-ico-whatsapp.webp

1712863402513-ico-mi-claro.webp

1713215588684-carrito-icon.webp

1712863454441-ico-autogestion.webp

ico-celulares-con-plan.svg

ico-servicios-hogar.svg

ico-videojuegos.svg