4.9 sec in total
504 ms
4.1 sec
287 ms
Click here to check amazing FEV content for Spain. Otherwise, check out these important facts you probably never knew about fev.es
F.E.V. es la Federación Española del Vino, organización privada más representativa del sector bodeguero español, agrupa a elaboradores y comercializadores vitivinícolas.
Visit fev.esWe analyzed Fev.es page load time and found that the first response time was 504 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fev.es performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value15.9 s
0/100
25%
Value10.6 s
7/100
10%
Value280 ms
80/100
30%
Value0.851
4/100
15%
Value11.4 s
19/100
10%
504 ms
1102 ms
831 ms
206 ms
424 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 56% of them (55 requests) were addressed to the original Fev.es, 34% (33 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fev.es.
Page size can be reduced by 298.0 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Fev.es main page is 1.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. 50% of websites need less resources to load. Images take 969.9 kB which makes up the majority of the site volume.
Potential reduce by 32.6 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 32.6 kB or 80% of the original size.
Potential reduce by 21.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. FEV images are well optimized though.
Potential reduce by 183.1 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 183.1 kB or 79% of the original size.
Potential reduce by 60.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. Fev.es needs all CSS files to be minified and compressed as it can save up to 60.6 kB or 86% of the original size.
Number of requests can be reduced by 36 (38%)
96
60
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEV. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.fev.es
504 ms
apartado.asp
1102 ms
prototype.js
831 ms
scriptaculous.js
206 ms
carousel.js
424 ms
verflash.js
420 ms
jquery.min.js
49 ms
1.5.js
437 ms
esencia_load.js
306 ms
estilos.asp
808 ms
cabecera.js
336 ms
plugs.js
320 ms
antispam.js
201 ms
effects.js
120 ms
widgets.js
18 ms
fnd_web.png
133 ms
logo_sup_wfcp.jpg
218 ms
imagen.asp
101 ms
ic_c_facebook_white.png
127 ms
ic_c_twitter_white.png
126 ms
ic_c_youtube_white.png
128 ms
ic_c_linkedin_white.png
206 ms
imagen.asp
339 ms
imagen.asp
238 ms
imagen.asp
359 ms
imagen.asp
281 ms
ic_page_off.png
304 ms
imagen.asp
328 ms
imagen.asp
350 ms
imagen.asp
400 ms
imagen.asp
434 ms
flecha_cal_ant.gif
440 ms
flecha_cal_sgte.gif
442 ms
boton.gif
442 ms
imagen.asp
462 ms
imagen.asp
518 ms
imagen.asp
532 ms
logo_fev.jpg
549 ms
logo_wine_moderation.jpg
574 ms
fnd_menu.png
573 ms
fnd_primera_noticia.jpg
559 ms
linea_noticias.jpg
609 ms
fnd_noticia.png
621 ms
fnd_pie_noticias.jpg
658 ms
fnd_recibir_noticias.png
694 ms
icono_recibir_noticias.gif
701 ms
fnd_mes_calendario.jpg
702 ms
fnd_destacados_eventos.jpg
764 ms
fnd_pie_calendario.jpg
765 ms
icono_registrar_evento.gif
805 ms
fnd_ver_todos.gif
848 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
26 ms
fnd_destacados_pie.jpg
830 ms
syndication
84 ms
581503066341511169
221 ms
fnd_logos_pie.png
829 ms
fnd_foot.jpg
920 ms
logo_sci_pie.gif
891 ms
1f377.png
30 ms
proxy.jpg
112 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
10 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
16 ms
C03lXrhy_normal.jpg
126 ms
8z8m2XgG_normal.png
148 ms
LogoALTA_jpg_normal.jpg
189 ms
QNr6zNaM_normal.jpg
218 ms
wKPCD0B7_normal.jpg
234 ms
R_M4lFrA_normal.png
235 ms
ByQTZhfW_normal.jpg
246 ms
Mv4fgDci_normal.jpg
243 ms
ziF_QkN3_normal.jpg
244 ms
CdQzHw4W8AAQ7ip.jpg:large
288 ms
CdQXhVkWwAAOYw8.jpg
260 ms
CdM6A6lW0AAAchM.jpg
284 ms
CdHtusrWwAA75_d.jpg
319 ms
CdHsnW8W0AE_oHE.jpg
298 ms
CdG348VXIAAo069.jpg
320 ms
CdG0Q23XEAE3Q3e.jpg
400 ms
CdGyDYZXEAAb-4X.jpg
361 ms
CdGv47lXEAAXBIz.jpg
313 ms
CdGvLG6W0AAIV6M.jpg
361 ms
CcuCjKwWIAEdNub.jpg:large
339 ms
Ccn8nL4WEAAtVE7.jpg:small
346 ms
CdRHsXvW4AA3OgI.jpg:small
343 ms
CdRHsbBW4AATmfp.jpg:small
366 ms
CdRHsV8W8AABeQr.jpg:small
371 ms
CdRHsUzW0AAvE0X.jpg:small
373 ms
CdQ4BCBUEAAygB1.jpg:small
409 ms
CdQ4BJIUAAAyIzJ.jpg:small
553 ms
CdQ4BJuVIAA9dNN.jpg:small
414 ms
CdQ4BIUUMAAjQjW.jpg:small
491 ms
CcZaWJHW8AEj7hk.jpg:small
400 ms
CcZaU8rWoAEs3lB.jpg:small
424 ms
CcZaV4NW8AAgjlP.jpg:small
428 ms
CcZaWk9WwAA1yi_.jpg:small
435 ms
jot
24 ms
estilosprint.asp
205 ms
ic_page_on.png
111 ms
fev.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 input fields do not have accessible names
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fev.es 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fev.es 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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fev.es 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 Fev.es main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
fev.es
Open Graph description is not detected on the main page of FEV. 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: