5.2 sec in total
257 ms
4.4 sec
539 ms
Welcome to aya.go.cr homepage info - get ready to check Aya best content for Costa Rica right away, or after learning these important things about aya.go.cr
Noticas del AYA.
Visit aya.go.crWe analyzed Aya.go.cr page load time and found that the first response time was 257 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aya.go.cr performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value6.4 s
10/100
25%
Value23.1 s
0/100
10%
Value6,510 ms
0/100
30%
Value0.558
13/100
15%
Value41.5 s
0/100
10%
257 ms
380 ms
220 ms
97 ms
186 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 91% of them (110 requests) were addressed to the original Aya.go.cr, 2% (2 requests) were made to Ssl.google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Aya.go.cr.
Page size can be reduced by 1.1 MB (24%)
4.5 MB
3.4 MB
In fact, the total size of Aya.go.cr main page is 4.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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.1 kB or 74% of the original size.
Potential reduce by 92.3 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. Aya images are well optimized though.
Potential reduce by 421.8 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 421.8 kB or 65% of the original size.
Potential reduce by 519.4 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. Aya.go.cr needs all CSS files to be minified and compressed as it can save up to 519.4 kB or 90% of the original size.
Number of requests can be reduced by 36 (31%)
117
81
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aya. 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 12 to 1 for CSS and as a result speed up the page load time.
aya.go.cr
257 ms
aya.go.cr
380 ms
Principal.aspx
220 ms
controls.css
97 ms
search.css
186 ms
corev4.css
518 ms
jupiter_ayaMenuSecundarioAppi.css
354 ms
jupiter_ayaCarruselNoticias.css
266 ms
nightandday.css
361 ms
Jup_Home.css
273 ms
Jup_default.css
277 ms
jupiter_ayaMainAppi.css
470 ms
jquery.min.js
70 ms
WebResource.axd
364 ms
blank.js
364 ms
init.js
177 ms
ScriptResource.axd
189 ms
ScriptResource.axd
89 ms
aya_1920_1080_bg_blur.jpg
228 ms
gosearch15.png
96 ms
nd_logo.png
98 ms
fgimg.png
95 ms
blank.gif
97 ms
ga.js
68 ms
sdk.js
262 ms
aya_loading_icon.gif
94 ms
home_btn_hover.svg
146 ms
home_btn.svg
151 ms
bgximg.png
149 ms
aya-logo.svg
241 ms
consulte_su_recibo_icon_hover_960.svg
184 ms
consulte_su_recibo_icon_960.svg
238 ms
contrataciones_icon_hover_960.svg
252 ms
contrataciones_icon_960.svg
253 ms
puntos_de_atencion_icon_hover_960.svg
275 ms
puntos_de_atencion_icon_960.svg
283 ms
reporte_de_averias_icon_hover_960.svg
334 ms
reporte_de_averias_icon_960.svg
337 ms
directorio_interno_icon_hover_960.svg
339 ms
directorio_interno_icon_960.svg
342 ms
mensajeria_icon_hover_960.svg
365 ms
mensajeria_icon_960.svg
375 ms
colaboracion_internacional_icon_hover_960.svg
429 ms
colaboracion_internacional_icon_960.svg
431 ms
place_holder_icon_hover_960.svg
432 ms
place_holder_icon_960.svg
437 ms
aya_bandera.png
455 ms
jupiter_ayaMainAppi.css
471 ms
close_panel_icon_hover.svg
527 ms
close_panel_icon.svg
528 ms
selbg.png
508 ms
index.html
526 ms
informacion_general_icon_hover_960.svg
548 ms
informacion_general_icon_960.svg
553 ms
programas_ambientales_icon_hover_960.svg
594 ms
programas_ambientales_icon_960.svg
601 ms
__utm.gif
12 ms
jquery-1.8.3.min.js
652 ms
tweenmax.min.js
575 ms
scrolltoplugin.js
597 ms
ayamainappi.js
601 ms
ayamenusecundarioappi.js
615 ms
servicio_al_cliente_icon_hover_960.svg
629 ms
servicio_al_cliente_icon_960.svg
630 ms
proyectos_icon_hover_960.svg
632 ms
proyectos_icon_960.svg
600 ms
asadas_icon_hover_960.svg
609 ms
asadas_icon_960.svg
564 ms
proveduria_icon_hover_960.svg
555 ms
proveduria_icon_960.svg
572 ms
centro_de_documentos_icon_hover_960.svg
566 ms
171 ms
centro_de_documentos_icon_960.svg
568 ms
xd_arbiter.php
261 ms
conozcanos_icon_hover_960.svg
611 ms
conozcanos_icon_960.svg
562 ms
2.png
562 ms
1.png
578 ms
noticias_icon_hover_960.svg
595 ms
noticias_icon_960.svg
573 ms
logo_800_960.svg
610 ms
logo_transparencia_960.svg
564 ms
logo_meic_960.svg
566 ms
logo_digital_960.svg
580 ms
logo_cnfl_960.png
592 ms
sugerencias_hover.png
578 ms
sugerencias.png
608 ms
email_interno_icon_hover.svg
564 ms
email_interno_icon.svg
556 ms
intranet_icon_hover.svg
577 ms
style.css
580 ms
jquery.js
562 ms
ayaCarruselAppi.js
599 ms
wowslider.js
564 ms
intranet_icon.svg
563 ms
user_login_icon_hover.svg
568 ms
user_login_icon.svg
555 ms
consulte_su_recibo_icon_960.svg
465 ms
contrataciones_icon_960.svg
501 ms
like.php
120 ms
puntos_de_atencion_icon_960.svg
496 ms
reporte_de_averias_icon_960.svg
493 ms
directorio_interno_icon_960.svg
514 ms
mensajeria_icon_960.svg
518 ms
colaboracion_internacional_icon_960.svg
532 ms
place_holder_icon_960.svg
560 ms
consulte_su_recibo_icon_960.png
935 ms
lupa_btn.svg
1775 ms
user_panel_logo.svg
1759 ms
qbEHJxuVK5u.js
300 ms
LVx-xkvaJ0b.png
330 ms
css
23 ms
comunicados%201.jpg
1457 ms
Banner%20nuevo%20reglamento.jpg
1454 ms
bullet.png
1416 ms
comunicados%201_jpg.jpg
1415 ms
Banner%20nuevo%20reglamento_jpg.jpg
1415 ms
script.js
1410 ms
arrows.png
95 ms
pause.png
96 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
27 ms
aya.go.cr 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
aya.go.cr 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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
aya.go.cr SEO score
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 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 Aya.go.cr 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 Aya.go.cr 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.
aya.go.cr
Open Graph data is detected on the main page of Aya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: