10.3 sec in total
341 ms
9.6 sec
351 ms
Click here to check amazing Bri Cor content for Spain. Otherwise, check out these important facts you probably never knew about bricor.es
Encuentra las herramientas de trabajo y el material que necesitas para tus tareas en la tienda de bricolaje, carpintería, jardinería, reforma del hogar y mucho más.
Visit bricor.esWe analyzed Bricor.es page load time and found that the first response time was 341 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
bricor.es performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value32.5 s
0/100
25%
Value35.7 s
0/100
10%
Value32,830 ms
0/100
30%
Value0.062
97/100
15%
Value47.7 s
0/100
10%
341 ms
347 ms
482 ms
211 ms
544 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 61% of them (52 requests) were addressed to the original Bricor.es, 13% (11 requests) were made to Info.bricor.es and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Info.bricor.es.
Page size can be reduced by 4.4 MB (68%)
6.4 MB
2.0 MB
In fact, the total size of Bricor.es main page is 6.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. 35% of websites need less resources to load. Images take 5.0 MB which makes up the majority of the site volume.
Potential reduce by 56.0 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. This page needs HTML code to be minified as it can gain 12.7 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.0 kB or 83% of the original size.
Potential reduce by 3.2 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, Bri Cor needs image optimization as it can save up to 3.2 MB or 65% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 868.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 868.6 kB or 79% of the original size.
Potential reduce by 223.5 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. Bricor.es needs all CSS files to be minified and compressed as it can save up to 223.5 kB or 85% of the original size.
Number of requests can be reduced by 47 (61%)
77
30
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bri Cor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
bricor.es
341 ms
www.bricor.es
347 ms
index.action
482 ms
border-radius.htc
211 ms
border-radius.js
544 ms
confianza_online.css
347 ms
bricor_fonts.css
239 ms
bricor_general.css
374 ms
bricor_styles.css
619 ms
bricor_header_footer_styles.css
475 ms
bricor_slider_styles.css
451 ms
bricor_tabs_styles.css
462 ms
bricor_formularios.css
623 ms
bootstrap.css
1853 ms
bootstrap-theme.css
691 ms
flexslider.css
593 ms
jquery-1.9.1.js
2932 ms
jquery-1.10.3.tabs.js
2294 ms
funciones.js
719 ms
funciones-Cesta.js
1368 ms
jquery.jFrame.js
805 ms
jquery.aviaSlider.js
1331 ms
jquery.aviaSlider.custom.js
922 ms
jquery.jcarousel.js
1381 ms
jcarousel.connected-carousels.js
1434 ms
jquery.tinyscrollbar.min.js
1615 ms
bootstrap.js
2579 ms
jquery.flexslider.js
2054 ms
geci.bricor.min.js
2239 ms
jquery.ui.spinner.css
1953 ms
jquery.ui.widget.js
2162 ms
jquery.ui.button.js
2075 ms
jquery.ui.spinner.js
2179 ms
bootstrap.min.js
25 ms
gtm.js
45 ms
Bootstrap.js
169 ms
close_popup.png
165 ms
arrow_right_white.png
166 ms
basket2_white.png
161 ms
logo_facebook.png
163 ms
logo_twitter.png
161 ms
logo_google.png
159 ms
logo_youtube.png
221 ms
bricor_logo.png
1597 ms
basket.png
208 ms
arrow_down_white.png
238 ms
bg_triangulo_cesta.png
230 ms
basket2.png
258 ms
OpenSans-Regular.ttf
1254 ms
pontecomodo.jpg
1326 ms
bg_bottom_banner_second.gif
302 ms
banner_newsletter.jpg
498 ms
prepararjardin.jpg
1589 ms
elegir.jpg
1148 ms
slider_pintura.jpg
1596 ms
muebles_bano.jpg
919 ms
plantar.jpg
1216 ms
oportunidades.jpg
1399 ms
todojardin.jpg
5548 ms
puertahoga[5].jpg
1468 ms
alfombras.jpg
3491 ms
iluminacion_dic.jpg
3760 ms
dist-confianza-100.png
554 ms
sello-confianza-100.png
576 ms
analytics.js
71 ms
conversion_async.js
69 ms
hotjar-25555.js
108 ms
anyadeCesta.action
232 ms
moonshine-font.woff
602 ms
43 ms
linkid.js
21 ms
ec.js
35 ms
52 ms
serverComponent.php
46 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
71 ms
77 ms
collect
25 ms
collect
82 ms
54 ms
collect
50 ms
ga-audiences
17 ms
ga-audiences
17 ms
arrow_left_banner.png
108 ms
cookies-policy.css
135 ms
arrow_right_banner.png
111 ms
bricor.es accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
bricor.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
Missing source maps for large first-party JavaScript
bricor.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
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
ES
ES
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bricor.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 Bricor.es main page’s claimed encoding is . 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.
bricor.es
Open Graph description is not detected on the main page of Bri Cor. 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: