5.5 sec in total
441 ms
4.4 sec
599 ms
Welcome to cap.cl homepage info - get ready to check CAP best content for Chile right away, or after learning these important things about cap.cl
Grupo CAP - Es el principal productor de minerales de hierro y pellets en la costa americana del Pacífico, el mayor productor siderúrgico en Chile y el más importante procesador de acero del país.
Visit cap.clWe analyzed Cap.cl page load time and found that the first response time was 441 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cap.cl performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value17.3 s
0/100
25%
Value10.8 s
6/100
10%
Value1,070 ms
25/100
30%
Value0.96
2/100
15%
Value21.8 s
1/100
10%
441 ms
811 ms
79 ms
378 ms
412 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 68% of them (57 requests) were addressed to the original Cap.cl, 13% (11 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cap.cl.
Page size can be reduced by 832.3 kB (21%)
4.0 MB
3.2 MB
In fact, the total size of Cap.cl main page is 4.0 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. 85% 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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 74.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 35.3 kB, which is 42% 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 74.7 kB or 89% of the original size.
Potential reduce by 402.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. Obviously, CAP needs image optimization as it can save up to 402.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 72.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 72.0 kB or 34% of the original size.
Potential reduce by 283.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. Cap.cl needs all CSS files to be minified and compressed as it can save up to 283.1 kB or 85% of the original size.
Number of requests can be reduced by 36 (46%)
78
42
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
cap.cl
441 ms
www.cap.cl
811 ms
gtm.js
79 ms
bootstrap.min.css
378 ms
slick.css
412 ms
slick-theme.css
420 ms
style.css
813 ms
style_menu_responsive.css
422 ms
style-modal.css
418 ms
ionicons.min.css
133 ms
css
111 ms
Vistas.class.js
493 ms
jquery.min.js
109 ms
jquery-ui.min.js
110 ms
main-modal.js
520 ms
bootstrap.min.js
652 ms
jquery.simple-sidebar.min.js
529 ms
slick.min.js
664 ms
main.js
613 ms
analytics.js
47 ms
collect
33 ms
collect
52 ms
ga-audiences
39 ms
stylescampos.css
127 ms
fran.css
139 ms
estilos_iversionistas.css
140 ms
responsive.css
131 ms
foto_0000000220160810164500.png
163 ms
nav.png
165 ms
foto_0000001520160628084004.jpg
521 ms
foto_0000001720160628084004.jpg
412 ms
foto_0000001820160628084004.jpg
612 ms
foto_0000001620160628084004.jpg
761 ms
foto_0000000920220805205604.jpg
548 ms
foto_0000000520220805183240.jpg
320 ms
icon-reportes-2.png
444 ms
icon-reportes-2-mob.png
507 ms
foto_0000001320220805205604.jpg
568 ms
foto_0000000420220805183240.jpg
636 ms
div-lineas.svg
658 ms
div-lineas-white.svg
672 ms
mapa_mundo_chile.svg
1090 ms
mapa_chile.svg
731 ms
btn-mapa.png
757 ms
foto_0000001120160628161649.png
782 ms
foto_0000001620160628161649.png
799 ms
diag-map-operac.svg
856 ms
foto_0000003120160628161649.png
887 ms
foto_0000002820160628161649.png
1508 ms
foto_0000002920160628161649.png
913 ms
foto_0000003220160628161649.jpg
924 ms
map-internacional.svg
1320 ms
map-internacional-pais2.svg
1508 ms
map-internacional-pais3.svg
1692 ms
map-internacional-pais7.svg
1784 ms
map-internacional-pais8.svg
1932 ms
foto_0000001720160628161649.png
1926 ms
foto_0000002520160628161649.png
2108 ms
foto_0000002720160628161649.png
1927 ms
foto_0000002620160628161649.png
1927 ms
foto_0000000620160810164500.png
1928 ms
foto_0000000320160810164500.png
2088 ms
foto_0000002420160810164500.jpg
1955 ms
foto_0000002120160810164500.jpg
1955 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
128 ms
S6uyw4BMUTPHjx4wWw.ttf
155 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
157 ms
ionicons.ttf
52 ms
foto_0000000420160810164500.png
1953 ms
widgets.js
199 ms
ajax-loader.gif
1800 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
96 ms
settings
90 ms
horizon_timeline.a7991bb824d62c8d5038ddd875db8389.js
26 ms
embeds
39 ms
CAP_CL
1289 ms
polyfills-57d3feabe8bfd4ee389c.js
207 ms
runtime-eb61dff4a84b8f906e6b.js
195 ms
modules.c7def0268c66f6a548ed.js
200 ms
main-e9db78f5e7b3d83edd5e.js
228 ms
_app-446fb4a338b215deec8c.js
228 ms
%5BscreenName%5D-c8b4c96951cf24f547b4.js
226 ms
_buildManifest.js
250 ms
_ssgManifest.js
252 ms
cap.cl 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 input fields do not have accessible names
ARIA IDs are not unique
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
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
Links do not have a discernible name
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.
cap.cl 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
Page has valid source maps
cap.cl SEO score
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 Cap.cl 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 Cap.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.
cap.cl
Open Graph data is detected on the main page of CAP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: