3.6 sec in total
734 ms
2.7 sec
173 ms
Visit aia.cl now to see the best up-to-date AIA content for Chile and also check out these interesting facts you probably never knew about aia.cl
Visit aia.clWe analyzed Aia.cl page load time and found that the first response time was 734 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
aia.cl performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value22.1 s
0/100
25%
Value15.7 s
0/100
10%
Value1,320 ms
17/100
30%
Value0
100/100
15%
Value19.6 s
2/100
10%
734 ms
43 ms
121 ms
43 ms
42 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 52% of them (57 requests) were addressed to the original Aia.cl, 23% (25 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (734 ms) belongs to the original domain Aia.cl.
Page size can be reduced by 746.0 kB (47%)
1.6 MB
851.3 kB
In fact, the total size of Aia.cl main page is 1.6 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 691.8 kB which makes up the majority of the site volume.
Potential reduce by 48.1 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 48.1 kB or 80% of the original size.
Potential reduce by 37.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. AIA images are well optimized though.
Potential reduce by 433.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 433.2 kB or 63% of the original size.
Potential reduce by 227.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. Aia.cl needs all CSS files to be minified and compressed as it can save up to 227.1 kB or 82% of the original size.
Number of requests can be reduced by 57 (54%)
105
48
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AIA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
aia.cl
734 ms
slimbox.css
43 ms
template.css.php
121 ms
modstyle.css
43 ms
jmod_tweetdisplay.css
42 ms
default_icemegamenu.css
44 ms
mootools-core.js
104 ms
core.js
63 ms
caption.js
64 ms
mootools-more.js
195 ms
slimbox.js
64 ms
jquery.min.js
5 ms
jquery.fpss.js
84 ms
icemegamenu.js
136 ms
template.css
108 ms
template.js
105 ms
jquery.bpopup.min.js
136 ms
element.js
31 ms
translateelement.css
58 ms
main.js
82 ms
b46c4895dd6a07faa2d619cf559b2c5a_normal.png
187 ms
logo_aia.gif
22 ms
banner_expo2017_2.gif
179 ms
ift.png
60 ms
home.gif
34 ms
mail.gif
34 ms
mapa.gif
33 ms
separador1.gif
43 ms
facebook.gif
78 ms
twitter.gif
77 ms
blank.png
78 ms
separador2.gif
78 ms
division_segmentada_columnaizq.jpg
79 ms
01.jpg
80 ms
02.jpg
80 ms
03.jpg
154 ms
04.jpg
154 ms
05.jpg
158 ms
06.png
158 ms
382_e561084e9220383c7204eb40f9bc13f1_m.jpg
158 ms
381_84c42b9986b8cecdea81ed6abb66c108_m.jpg
178 ms
380_8b0dca3b357fcee94cf1b8a6c08994ea_m.jpg
176 ms
379_eb9b7452cdc806568d2312ea5614a301_m.jpg
223 ms
378_24051f1a73d7ccf80aa0e781a6178da9_m.jpg
222 ms
377_a28321ba8f3530fc856783a3123dd44c_m.jpg
232 ms
division_segmentada.jpg
223 ms
division_vertical.jpg
234 ms
250x129-equal_images_noticias_articulos_2015_diciembre_lanza_web.jpg
231 ms
250x160-equal_images_noticias_articulos_2015_diciembre_Donbosco1.jpg
232 ms
250x167-equal_images_noticias_articulos_2015_diciembre_IMG_3241.jpg
239 ms
swiss_721_condensed_bt-webfont.woff
285 ms
16a.png
231 ms
point.png
229 ms
all.js
240 ms
twitter-icon.png
232 ms
loading.gif
231 ms
readmore.png
231 ms
382_e561084e9220383c7204eb40f9bc13f1_t.jpg
232 ms
381_84c42b9986b8cecdea81ed6abb66c108_t.jpg
232 ms
380_8b0dca3b357fcee94cf1b8a6c08994ea_t.jpg
233 ms
379_eb9b7452cdc806568d2312ea5614a301_t.jpg
234 ms
378_24051f1a73d7ccf80aa0e781a6178da9_t.jpg
233 ms
377_a28321ba8f3530fc856783a3123dd44c_t.jpg
234 ms
element_main.js
38 ms
EMzrVQiKdHE
73 ms
translate_24dp.png
19 ms
l
82 ms
www-embed-player-vfl-z2BtK.css
17 ms
www-embed-player.js
32 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
56 ms
ad_status.js
56 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
112 ms
xd_arbiter.php
131 ms
xd_arbiter.php
242 ms
like_box.php
304 ms
E6teJbut7Oz.css
168 ms
KJtsWU0X327.css
211 ms
SjGvcmqWmCE.css
253 ms
tpDFPbDykHB.css
326 ms
EWhhEkcBPae.css
333 ms
6bIl72b-rkY.js
364 ms
TkV0upu1GVq.js
378 ms
mn6tHWuLI-Y.js
290 ms
x8BMxYCqTb9.js
292 ms
QKy94bWvcbp.js
342 ms
5paioeCYCa7.js
342 ms
wRXOQ26LQ1k.js
407 ms
UMeIUxuSxxa.js
485 ms
50Trs1RKgUY.js
390 ms
942130_446538655435909_1286924066_n.jpg
167 ms
safe_image.php
171 ms
1467190_537922086297565_2119848322_n.jpg
199 ms
12821573_1013146665441769_8499533286874175918_n.jpg
238 ms
12799024_896570110459576_49367829670049575_n.jpg
314 ms
20908_735618003221455_5831511378498436271_n.png
277 ms
10291_975279072561862_4480350539860949048_n.jpg
317 ms
wL6VQj7Ab77.png
51 ms
s7jcwEQH7Sx.png
50 ms
mbF8ssTVP_5.png
52 ms
Fe6g47SXw-8.png
54 ms
L5AOQ9vzKfo.png
54 ms
oULnqcel5Nm.png
50 ms
q2ibvFgTxmh.png
79 ms
A2JLtDOGyCJ.png
81 ms
pimRBh7B6ER.png
80 ms
Fy3hs8lKW0M.png
82 ms
VXcANLwwL5J.js
40 ms
aia.cl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
aia.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aia.cl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Aia.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 Aia.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.
aia.cl
Open Graph description is not detected on the main page of AIA. 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: