7.1 sec in total
1.2 sec
4.8 sec
1.1 sec
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.9 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.8 s
0/100
25%
Value17.5 s
0/100
10%
Value1,350 ms
17/100
30%
Value0.059
98/100
15%
Value30.6 s
0/100
10%
1166 ms
346 ms
349 ms
573 ms
359 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 82% of them (114 requests) were addressed to the original Afme.es, 8% (11 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Afme.es.
Page size can be reduced by 2.8 MB (43%)
6.5 MB
3.7 MB
In fact, the total size of Afme.es main page is 6.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. 65% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 113.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. 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 113.7 kB or 83% of the original size.
Potential reduce by 1.3 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.3 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 633.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 633.7 kB or 53% of the original size.
Potential reduce by 775.9 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 775.9 kB or 83% of the original size.
Number of requests can be reduced by 79 (68%)
117
38
The browser has sent 117 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 48 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
afme.es
1166 ms
slickmap.css
346 ms
simplelightbox.min.css
349 ms
powerfolio_css.css
573 ms
owl.carousel.css
359 ms
owl.theme.default.min.css
360 ms
pwrgrids_css.css
424 ms
all.css
461 ms
styles.css
359 ms
all.min.css
698 ms
bootstrap.min.css
619 ms
front.css
616 ms
team.min.css
432 ms
style.min.css
923 ms
style.css
542 ms
all.min.css
702 ms
simple-line-icons.min.css
658 ms
css
28 ms
css
29 ms
elementor-icons.min.css
738 ms
frontend-lite.min.css
974 ms
swiper.min.css
768 ms
post-18.css
811 ms
frontend-lite.min.css
814 ms
post-1956.css
861 ms
post-71.css
881 ms
default.css
930 ms
style.min.css
930 ms
css
30 ms
fontawesome.min.css
1102 ms
solid.min.css
992 ms
jquery.min.js
1036 ms
jquery-migrate.min.js
1040 ms
popper.min.js
1043 ms
bootstrap.min.js
1093 ms
front.js
1100 ms
widget-posts.min.css
1083 ms
widget-icon-list.min.css
978 ms
jquery.min.js
20 ms
estadisticas-form.js
989 ms
animations.min.css
1031 ms
api.js
46 ms
412 ms
imagesloaded.min.js
1029 ms
isotope.pkgd.min.js
1011 ms
packery-mode.pkgd.min.js
1053 ms
simple-lightbox.min.js
1043 ms
custom-portfolio-lightbox.js
1044 ms
custom-portfolio.js
1037 ms
owl.carousel.min.js
1004 ms
pwrgrids-custom-js.js
929 ms
index.js
944 ms
index.js
872 ms
wp-polyfill-inert.min.js
796 ms
regenerator-runtime.min.js
834 ms
FZfMXhsUOOYW1dTg0c79aG-8109.js
108 ms
wp-polyfill.min.js
942 ms
hooks.min.js
778 ms
i18n.min.js
824 ms
jquery.form.min.js
792 ms
team.min.js
763 ms
theme.min.js
751 ms
drop-down-mobile-menu.min.js
801 ms
drop-down-search.min.js
782 ms
magnific-popup.min.js
766 ms
ow-lightbox.min.js
720 ms
flickity.pkgd.min.js
850 ms
ow-slider.min.js
790 ms
scroll-effect.min.js
749 ms
scroll-top.min.js
769 ms
select.min.js
726 ms
index.js
722 ms
main.min.js
807 ms
webpack-pro.runtime.min.js
757 ms
webpack.runtime.min.js
775 ms
frontend-modules.min.js
694 ms
frontend.min.js
682 ms
waypoints.min.js
692 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
53 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
75 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
101 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
118 ms
core.min.js
766 ms
fa-solid-900.woff
133 ms
fa-regular-400.woff
158 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
119 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
118 ms
S6uyw4BMUTPHjx4wWw.ttf
119 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
132 ms
S6u8w4BMUTPHh30AXC-v.ttf
119 ms
embed
252 ms
frontend.min.js
718 ms
elements-handlers.min.js
743 ms
embed
339 ms
fa-solid-900.woff
762 ms
fa-solid-900.ttf
866 ms
fa-solid-900.ttf
1190 ms
fa-regular-400.ttf
835 ms
fa-regular-400.ttf
787 ms
Simple-Line-Icons.ttf
801 ms
eicons.woff
834 ms
cropped-image001.gif
846 ms
Banner-con-logos-Post-de-Twitter.jpg
853 ms
HIGH_banner_fondos_next.png
1009 ms
Vector_2640-scaled.jpg
1374 ms
2-NL269-LOGO-ELECTRONET.jpg
844 ms
js
48 ms
1-NL269-Imagen-webinar-e1705662554113.png
858 ms
8-NL268-FOTO1-e1705568041530.jpg
859 ms
7-NL268-ETIM-e1705481517500.png
912 ms
6-NL268-1-e1705396198574.png
953 ms
4-NL265-alta-e1699343049849.jpg
896 ms
plataformaE475x76.jpeg
926 ms
ETIM-Espana_2023.png
916 ms
banner_publi1.jpg
954 ms
banner_publi2.jpg
986 ms
Video-3-1024x562.jpg
918 ms
Video-2-1024x587.jpg
934 ms
Video-1-1024x647.jpg
916 ms
Logos_Entidades_2021-11-18-1.jpg
965 ms
Banner_AENOR.gif
1025 ms
recaptcha__en.js
22 ms
CAPIEL_SmartGrids.jpg
974 ms
Guia_AFME_ADIME_FENIE.png
978 ms
Banner-Toma_de_corriente.png
1263 ms
banner-ambiafme.jpg
961 ms
Banner-AFME-enero-23.jpg
1006 ms
WIDGET-20-AFME-2023.jpg
1239 ms
Aenor_BANNER_395x120.gif
1128 ms
Widget_Dtos.-AENOR-formacion_2021.jpg
979 ms
AF_UNE_logotipo_lv_rgb_pos-1024x853.png
979 ms
capiel.jpeg
1006 ms
CecapiRGB-1024x193.png
1042 ms
confemetal800x262.jpeg
915 ms
orgalim480x144.jpeg
980 ms
icex970x487.jpeg
974 ms
AFME-1024x196.png
995 ms
afme.es 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.
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
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 uses 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: