13.5 sec in total
3.1 sec
10.1 sec
341 ms
Click here to check amazing Elo Utfsm content for Chile. Otherwise, check out these important facts you probably never knew about elo.utfsm.cl
Bienvenido al Sitio Web del Departamento de Electrónica de la Universidad Técnica Federico Santa María. Ingeniero Electrónicos e Ingenieros Temáticos al servicio de Chile y el mundo.
Visit elo.utfsm.clWe analyzed Elo.utfsm.cl page load time and found that the first response time was 3.1 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
elo.utfsm.cl performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value20.6 s
0/100
25%
Value19.4 s
0/100
10%
Value300 ms
79/100
30%
Value0.098
90/100
15%
Value15.2 s
7/100
10%
3090 ms
310 ms
517 ms
387 ms
622 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Elo.utfsm.cl, 16% (24 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Electronica.usm.cl.
Page size can be reduced by 182.2 kB (8%)
2.4 MB
2.2 MB
In fact, the total size of Elo.utfsm.cl main page is 2.4 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 124.9 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 124.9 kB or 84% of the original size.
Potential reduce by 51.2 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. Elo Utfsm images are well optimized though.
Potential reduce by 4.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.
Potential reduce by 2.2 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. Elo.utfsm.cl has all CSS files already compressed.
Number of requests can be reduced by 78 (80%)
98
20
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elo Utfsm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 43 to 1 for CSS and as a result speed up the page load time.
electronica.usm.cl
3090 ms
formidableforms.css
310 ms
bdt-uikit.css
517 ms
prime-slider-site.css
387 ms
style.min.css
622 ms
fonts.css
463 ms
sumoselect.min.css
470 ms
jquery.mCustomScrollbar.min.css
550 ms
css
31 ms
styles.min.css
521 ms
style.min.css
629 ms
style.css
626 ms
frontend.min.css
655 ms
post-26.css
645 ms
style.min.css
733 ms
all.min.css
778 ms
post-101.css
783 ms
simple-line-icons.min.css
785 ms
aa4cd108caefe67bed556707fc45a33f.css
773 ms
240e3834173594b415b78ead4c875dcc.css
783 ms
cherry-handler-styles.min.css
915 ms
jet-widgets.css
905 ms
jet-widgets-skin.css
931 ms
juxtapose.css
937 ms
elementor-icons.min.css
910 ms
swiper.min.css
938 ms
post-27.css
1034 ms
frontend.min.css
1047 ms
all.min.css
1101 ms
v4-shims.min.css
1087 ms
global.css
1094 ms
post-37.css
1096 ms
general.min.css
1161 ms
slick.css
1175 ms
slick-theme.css
1242 ms
ha-37.css
1250 ms
widgets.css
1251 ms
css
31 ms
style.min.css
1144 ms
fontawesome.min.css
993 ms
brands.min.css
926 ms
solid.min.css
942 ms
ps-blog.css
946 ms
animations.min.css
897 ms
jquery.min.js
1144 ms
jquery-migrate.min.js
881 ms
jquery.sumoselect.min.js
816 ms
tocca.min.js
934 ms
jquery.mCustomScrollbar.concat.min.js
934 ms
jquery.fullscreen.min.js
927 ms
scripts.min.js
1039 ms
v4-shims.min.js
835 ms
cherry-js-core.min.js
1054 ms
happy-addons.min.js
1045 ms
imagesloaded.min.js
1045 ms
theme.min.js
1046 ms
full-screen-mobile-menu.min.js
1079 ms
drop-down-search.min.js
938 ms
equal-height-elements.min.js
935 ms
magnific-popup.min.js
957 ms
ow-lightbox.min.js
974 ms
flickity.pkgd.min.js
970 ms
ow-slider.min.js
1062 ms
scroll-effect.min.js
968 ms
scroll-top.min.js
989 ms
select.min.js
953 ms
ow-infinite-scroll.min.js
945 ms
cherry-handler.min.js
949 ms
general.min.js
982 ms
slick.min.js
933 ms
social.js
1009 ms
slick.min.js
962 ms
anime.min.js
980 ms
bdt-uikit.min.js
964 ms
webpack.runtime.min.js
932 ms
frontend-modules.min.js
926 ms
waypoints.min.js
1036 ms
core.min.js
956 ms
frontend.min.js
942 ms
prime-slider-site.min.js
967 ms
jet-widgets.js
929 ms
Logo-Departamento-Blanco-150px-24.png
652 ms
Multimedia.jpg
1339 ms
Matias_Za%C3%B1artu.jpg
3527 ms
WhatsApp-Image-2024-04-18-at-6.57.23-AM-002.jpeg
1097 ms
Logo-Electronica.jpg
911 ms
33.jpg
769 ms
20.jpg
958 ms
29.jpg
865 ms
5.jpg
1010 ms
4.jpg
1020 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
45 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
69 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
68 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
69 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
69 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
71 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
73 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyDPA-9a6Vc.ttf
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyCjA-9a6Vc.ttf
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9A-9a6Vc.ttf
128 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9Au9a6Vc.ttf
129 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9a6Vc.ttf
76 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf
73 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9BO9a6Vc.ttf
170 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyBUBO9a6Vc.ttf
75 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
76 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
76 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
76 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
124 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
125 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
125 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
1161 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
1181 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
1166 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1306 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
1272 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
1242 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1209 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1271 ms
fa-solid-900.woff
1260 ms
fa-solid-900.woff
1436 ms
fa-regular-400.woff
1337 ms
fa-regular-400.woff
1304 ms
fa-brands-400.woff
1510 ms
fa-brands-400.woff
1329 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf
1326 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyDPA-9a6Vc.ttf
1345 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyCjA-9a6Vc.ttf
1358 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9A-9a6Vc.ttf
1426 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9Au9a6Vc.ttf
1451 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAjBO9a6Vc.ttf
1495 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6Vc.ttf
1357 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyB9BO9a6Vc.ttf
1417 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyBUBO9a6Vc.ttf
1455 ms
7.png
1924 ms
8.jpg
1428 ms
Entrevista_Marcelo_Perez-Tb.jpg
1509 ms
Acatec-Home.jpg
1533 ms
banner-primer.jpg
1445 ms
banner-acatec.jpg
1263 ms
admision-2023-2.jpg
1510 ms
banner-arte.jpg
1253 ms
sello-acreditacion-2028-1-e1700074821166.png
1379 ms
elo.utfsm.cl accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
elo.utfsm.cl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
elo.utfsm.cl SEO score
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 Elo.utfsm.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 Elo.utfsm.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.
elo.utfsm.cl
Open Graph description is not detected on the main page of Elo Utfsm. 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: