6.8 sec in total
1.2 sec
4.7 sec
873 ms
Visit afme.es now to see the best up-to-date AFME content and also check out these interesting facts you probably never knew about afme.es
AFME es una organización profesional sin ánimo de lucro, de carácter nacional, que abarca los diferentes subsectores de la industria de material eléctrico.
Visit afme.esWe analyzed Afme.es page load time and found that the first response time was 1.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
afme.es performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value12.9 s
0/100
25%
Value16.8 s
0/100
10%
Value1,320 ms
17/100
30%
Value0.059
98/100
15%
Value29.7 s
0/100
10%
1182 ms
328 ms
333 ms
575 ms
351 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 81% of them (116 requests) were addressed to the original Afme.es, 8% (11 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Afme.es.
Page size can be reduced by 3.0 MB (48%)
6.3 MB
3.2 MB
In fact, the total size of Afme.es main page is 6.3 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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 125.4 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 125.4 kB or 82% of the original size.
Potential reduce by 1.1 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. Obviously, AFME needs image optimization as it can save up to 1.1 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 952.7 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 952.7 kB or 60% of the original size.
Potential reduce by 866.6 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. Afme.es needs all CSS files to be minified and compressed as it can save up to 866.6 kB or 83% of the original size.
Number of requests can be reduced by 84 (69%)
122
38
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AFME. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
afme.es
1182 ms
slickmap.css
328 ms
simplelightbox.min.css
333 ms
powerfolio_css.css
575 ms
owl.carousel.css
351 ms
owl.theme.default.min.css
363 ms
pwrgrids_css.css
438 ms
all.css
25 ms
styles.css
331 ms
all.min.css
345 ms
bootstrap.min.css
585 ms
front.css
613 ms
cookieblocker.min.css
437 ms
team.min.css
547 ms
frontend.css
460 ms
style.min.css
868 ms
style.css
580 ms
all.min.css
692 ms
simple-line-icons.min.css
656 ms
css
30 ms
css
35 ms
elementor-icons.min.css
697 ms
frontend-lite.min.css
1036 ms
swiper.min.css
734 ms
post-18.css
766 ms
frontend-lite.min.css
806 ms
post-1956.css
813 ms
post-71.css
857 ms
default.css
875 ms
style.min.css
921 ms
css
33 ms
fontawesome.min.css
929 ms
solid.min.css
978 ms
jquery.min.js
976 ms
jquery-migrate.min.js
984 ms
popper.min.js
1054 ms
bootstrap.min.js
1056 ms
front.js
1088 ms
frontend.js
1100 ms
widget-posts.min.css
989 ms
widget-icon-list.min.css
985 ms
jquery.min.js
22 ms
estadisticas-form.js
984 ms
api.js
42 ms
409 ms
animations.min.css
991 ms
imagesloaded.min.js
980 ms
isotope.pkgd.min.js
1080 ms
packery-mode.pkgd.min.js
933 ms
simple-lightbox.min.js
1006 ms
custom-portfolio-lightbox.js
987 ms
custom-portfolio.js
898 ms
owl.carousel.min.js
873 ms
pwrgrids-custom-js.js
910 ms
hooks.min.js
893 ms
i18n.min.js
858 ms
index.js
856 ms
index.js
833 ms
FZfMXhsUOOYW1dTg0c79aG-8109.js
105 ms
jquery.form.min.js
786 ms
team.min.js
798 ms
theme.min.js
851 ms
drop-down-mobile-menu.min.js
814 ms
drop-down-search.min.js
789 ms
magnific-popup.min.js
752 ms
ow-lightbox.min.js
747 ms
flickity.pkgd.min.js
876 ms
ow-slider.min.js
783 ms
scroll-effect.min.js
784 ms
scroll-top.min.js
747 ms
select.min.js
742 ms
wp-polyfill.min.js
698 ms
index.js
819 ms
main.min.js
813 ms
complianz.min.js
744 ms
webpack-pro.runtime.min.js
739 ms
webpack.runtime.min.js
738 ms
frontend-modules.min.js
884 ms
frontend.min.js
782 ms
waypoints.min.js
680 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff
89 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
106 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
123 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
122 ms
fa-solid-900.woff
51 ms
fa-regular-400.woff
60 ms
S6u9w4BMUTPHh50XSwiPHw.woff
126 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
126 ms
S6uyw4BMUTPHjx4wWA.woff
125 ms
S6u9w4BMUTPHh7USSwiPHw.woff
143 ms
S6u8w4BMUTPHh30AXC-s.woff
141 ms
core.min.js
688 ms
frontend.min.js
696 ms
preloaded-elements-handlers.min.js
699 ms
fa-solid-900.woff
791 ms
embed
255 ms
fa-solid-900.ttf
1101 ms
embed
329 ms
fa-solid-900.ttf
941 ms
fa-regular-400.ttf
731 ms
fa-regular-400.ttf
721 ms
Simple-Line-Icons.ttf
787 ms
eicons.woff
809 ms
cropped-image001.gif
802 ms
Banner-con-logos-Post-de-Twitter.jpg
743 ms
Banner-MATELEC-990x180-esp-e1726146230396.gif
809 ms
Vector_2640-scaled.jpg
975 ms
5-NL281-MATELEC-AFME.jpg
846 ms
2-NL281-Logo-Congreso-Industria-e1725968907753.png
851 ms
3-NL281-foto-e1725968366938.jpg
880 ms
js
38 ms
4-NL281-Estadisticas-e1725947406483.png
840 ms
geometry.js
4 ms
search.js
7 ms
main.js
9 ms
1-NL281-Imagen-e1722330863396.png
852 ms
4-NL280-Imagen-e1721822184567.png
859 ms
plataformaE475x76.jpeg
909 ms
ETIM-Espana_2023.png
932 ms
banner_publi1.jpg
847 ms
banner_publi2.jpg
860 ms
Video-3-1024x562.jpg
854 ms
Video-2-1024x587.jpg
856 ms
Video-1-1024x647.jpg
904 ms
recaptcha__en.js
23 ms
Logos_Entidades_2021-11-18-1.jpg
995 ms
Banner_AENOR.gif
821 ms
CAPIEL_SmartGrids.jpg
836 ms
Guia_AFME_ADIME_FENIE.png
835 ms
Banner-Toma_de_corriente.png
1074 ms
banner-ambiafme.jpg
889 ms
Banner-AFME-enero-23.jpg
857 ms
WIDGET-20-AFME-2023.jpg
989 ms
Aenor_BANNER_395x120.gif
848 ms
Widget_Dtos.-AENOR-formacion_2021.jpg
891 ms
AF_UNE_logotipo_lv_rgb_pos-1024x853.png
945 ms
capiel.jpeg
859 ms
CecapiRGB-1024x193.png
821 ms
confemetal800x262.jpeg
854 ms
orgalim480x144.jpeg
898 ms
icex970x487.jpeg
855 ms
AFME-1024x196.png
809 ms
afme.es 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-hidden="true"] elements contain focusable descendents
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
afme.es 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
Page has valid source maps
afme.es 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afme.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Afme.es 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.
afme.es
Open Graph description is not detected on the main page of AFME. 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: