11.5 sec in total
297 ms
5.8 sec
5.5 sec
Visit fdb.es now to see the best up-to-date Fdb content for Spain and also check out these interesting facts you probably never knew about fdb.es
Benito constituye uno de los mayores grupos industriales del sector de la iluminación y el mobiliario urbano. Fabrica todo tipo de productos para el espacio público. Consulta el catálogo online.
Visit fdb.esWe analyzed Fdb.es page load time and found that the first response time was 297 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fdb.es performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value9.7 s
0/100
25%
Value11.6 s
5/100
10%
Value9,740 ms
0/100
30%
Value0.616
10/100
15%
Value18.1 s
3/100
10%
297 ms
2030 ms
171 ms
529 ms
782 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 71% of them (55 requests) were addressed to the original Fdb.es, 5% (4 requests) were made to Google.com and 5% (4 requests) were made to Benito.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Benito.com.
Page size can be reduced by 589.0 kB (10%)
5.7 MB
5.1 MB
In fact, the total size of Fdb.es main page is 5.7 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 4.9 MB which makes up the majority of the site volume.
Potential reduce by 154.2 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 154.2 kB or 84% of the original size.
Potential reduce by 93.5 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. Fdb images are well optimized though.
Potential reduce by 218.6 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 218.6 kB or 64% of the original size.
Potential reduce by 122.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. Fdb.es needs all CSS files to be minified and compressed as it can save up to 122.6 kB or 65% of the original size.
Number of requests can be reduced by 41 (57%)
72
31
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fdb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fdb.es
297 ms
www.fdb.es
2030 ms
gtm.js
171 ms
normalize.min.css
529 ms
bootstrap.min.css
782 ms
all.min.css
655 ms
select2.min.css
521 ms
select2-bootstrap.min.css
595 ms
general.min.css
823 ms
app.css
596 ms
jquery-3.3.1.min.js
796 ms
jquery.countdown.min.js
409 ms
api.js
409 ms
owl.carousel.min.css
680 ms
owl.theme.default.min.css
680 ms
conversion_async.js
162 ms
cookies.js
381 ms
cookie.js
440 ms
popper.min.js
439 ms
bootstrap.min.js
905 ms
bootbox.min.js
523 ms
bootbox.locales.min.js
522 ms
owl.carousel.js
907 ms
select2.min.js
906 ms
modalAnuncis.js
903 ms
respostaFormularis.js
905 ms
barraMenuModalCistella.js
903 ms
login.js
927 ms
sha512.js
928 ms
menuWeb.js
931 ms
mGeneral.js
931 ms
principalBuida.js
931 ms
64 ms
98 ms
18 ms
20 ms
css
65 ms
recaptcha__en.js
580 ms
movilidad.jpg
2638 ms
movilidad2222.jpg
2367 ms
light_HOME_ES.gif
2602 ms
HORMIGON.jpg
2482 ms
LINIES_MENU.svg
694 ms
logo_benito1.svg
629 ms
LUPA.svg
669 ms
PERFIL_USUARI.svg
667 ms
TEL.svg
665 ms
carrito.svg
691 ms
iconcheckbox.png
850 ms
light6.jpg
1761 ms
urban9.jpg
851 ms
play5.jpg
1791 ms
covers1.jpg
1328 ms
jaen_1.jpg
1325 ms
alps1.jpg
1384 ms
515.jpg
1363 ms
ulldecona2.jpg
2096 ms
Trescantons_MADRID_8.jpg
1792 ms
parqueigualdo_2_1.jpg
1791 ms
Castellbisbal_2.jpg
2001 ms
Tenerife_3.jpg
2333 ms
Alcala1.jpg
2094 ms
icono_fletxa.svg
1980 ms
info_arroba.svg
2017 ms
info_telf.svg
2037 ms
info_config.svg
2057 ms
sib-conversations.js
796 ms
sa.js
1253 ms
iconaEnviar.svg
1615 ms
doofinder-classic.7.latest.min.js
474 ms
fa-solid-900.woff
1220 ms
fa-regular-400.woff
1233 ms
analytics.js
871 ms
js
450 ms
collect
213 ms
collect
244 ms
ga-audiences
24 ms
fdb.es 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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
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 IDs are not unique
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.
fdb.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fdb.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Fdb.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 Fdb.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.
fdb.es
Open Graph description is not detected on the main page of Fdb. 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: