11.3 sec in total
630 ms
10.3 sec
359 ms
Click here to check amazing Grifoso content. Otherwise, check out these important facts you probably never knew about grifoso.com
Descuento el grifo, baño, cocina,tap cañada de baño y ducha, líder del equipo.La opción más garantías de bajo precio y envío gratis.
Visit grifoso.comWe analyzed Grifoso.com page load time and found that the first response time was 630 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
grifoso.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value3.1 s
74/100
25%
Value13.7 s
2/100
10%
Value3,140 ms
2/100
30%
Value0.169
70/100
15%
Value14.9 s
8/100
10%
630 ms
347 ms
349 ms
345 ms
343 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Grifoso.com, 5% (3 requests) were made to V2.zopim.com and 3% (2 requests) were made to C.statcounter.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Pcookie.cnzz.com.
Page size can be reduced by 259.3 kB (12%)
2.2 MB
1.9 MB
In fact, the total size of Grifoso.com main page is 2.2 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 23.5 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 23.5 kB or 81% of the original size.
Potential reduce by 32.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. Grifoso images are well optimized though.
Potential reduce by 116.8 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 116.8 kB or 61% of the original size.
Potential reduce by 86.4 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. Grifoso.com needs all CSS files to be minified and compressed as it can save up to 86.4 kB or 85% of the original size.
Number of requests can be reduced by 39 (68%)
57
18
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grifoso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
grifoso.com
630 ms
stylesheet.css
347 ms
stylesheet_boxes.css
349 ms
stylesheet_css_buttons.css
345 ms
stylesheet_ezpages_footer_columns.css
343 ms
stylesheet_header_menu.css
350 ms
stylesheet_lightbox-0.css
348 ms
stylesheet_lrtk.css
418 ms
stylesheet_main.css
424 ms
stylesheet_news.css
411 ms
stylesheet_news_sidebox_archive.css
418 ms
stylesheet_social_media_icons.css
427 ms
stylesheet_tm.css
420 ms
stylesheet_z.css
479 ms
stylesheet_zzz.css
485 ms
jscript_jquery-1.7.1.min.js
613 ms
jscript_jquery.js
557 ms
jscript_jquery.nivo.slider.pack.js
492 ms
jscript_script.js
490 ms
jscript_scrolltop.js
544 ms
jscript_xdropdown_menu.js
549 ms
stat.php
2111 ms
body-bg.jpg
71 ms
logo.jpg
74 ms
icon.gif
73 ms
banner1.jpg
431 ms
banner2.jpg
430 ms
banner3.jpg
427 ms
banner4.jpg
428 ms
0510F.jpg
274 ms
0784-4.jpg
233 ms
0828F.jpg
340 ms
8014.jpg
427 ms
SC006.jpg
984 ms
SA007.jpg
534 ms
0818.jpg
538 ms
7042AF.jpg
576 ms
rss.gif
512 ms
lanren_top.jpg
511 ms
counter.js
8 ms
t.php
213 ms
header-line.gif
554 ms
cart.png
552 ms
btn1-bg.png
930 ms
hor-cat.png
600 ms
cat-line.png
623 ms
loading.gif
1014 ms
title-marker.png
614 ms
add-to-cart.png
655 ms
footer-bg.png
1424 ms
widget_v2.134.js
14 ms
__$$__stringtable_lang_es.js
23 ms
avatar_simple_visitor.png
103 ms
print_stylesheet.css
70 ms
stat.htm
162 ms
core.php
1622 ms
aL63HcygAAVYuCCsAAA==
1 ms
9.gif
1145 ms
t.php
134 ms
app.gif
4354 ms
www.grifoso.com
399 ms
default-arrows.png
86 ms
default-bullets.png
91 ms
grifoso.com 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
grifoso.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
grifoso.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grifoso.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Spanish. Our system also found out that Grifoso.com 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.
grifoso.com
Open Graph description is not detected on the main page of Grifoso. 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: