6.1 sec in total
1.7 sec
4 sec
372 ms
Welcome to provesa.com homepage info - get ready to check PROVESA best content right away, or after learning these important things about provesa.com
Tienda creada con PrestaShop
Visit provesa.comWe analyzed Provesa.com page load time and found that the first response time was 1.7 sec 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.
provesa.com performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value14.2 s
0/100
25%
Value16.1 s
0/100
10%
Value100 ms
98/100
30%
Value0.223
56/100
15%
Value12.4 s
15/100
10%
1672 ms
220 ms
192 ms
196 ms
205 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 86% of them (95 requests) were addressed to the original Provesa.com, 6% (7 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Provesa.com.
Page size can be reduced by 121.0 kB (11%)
1.1 MB
978.2 kB
In fact, the total size of Provesa.com main page is 1.1 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. 60% of websites need less resources to load. Images take 753.1 kB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 16% 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 47.6 kB or 82% of the original size.
Potential reduce by 1.8 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. PROVESA images are well optimized though.
Potential reduce by 60.5 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 60.5 kB or 29% of the original size.
Potential reduce by 11.1 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. Provesa.com needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 14% of the original size.
Number of requests can be reduced by 70 (69%)
101
31
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROVESA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
provesa.com
1672 ms
global.css
220 ms
highdpi.css
192 ms
responsive-tables.css
196 ms
uniform.default.css
205 ms
css
56 ms
css
89 ms
responsive.css
192 ms
responsive-md.css
256 ms
responsive-1.css
282 ms
animate.min.css
286 ms
jquery.fancybox.css
289 ms
jquery.ui.core.css
300 ms
jquery.ui.slider.css
310 ms
jquery.ui.theme.css
330 ms
blockcategories.css
369 ms
blocknewsletter.css
372 ms
blocksearch.css
373 ms
jquery.autocomplete.css
394 ms
blocktags.css
401 ms
blockuserinfo.css
436 ms
blockviewed.css
463 ms
blockwishlist.css
467 ms
productcomments.css
467 ms
stmegamenu.css
498 ms
iosslider.css
500 ms
camera.css
545 ms
custom.css
554 ms
stsocial.css
558 ms
stblog.css
562 ms
stblogfeaturedarticles.css
596 ms
stblogcomments.css
604 ms
css
69 ms
stfeaturedcategories.css
654 ms
customer-s1.css
642 ms
jquery-1.11.0.min.js
734 ms
jquery-migrate-1.2.1.min.js
650 ms
jquery.easing.js
683 ms
tools.js
685 ms
css
47 ms
styles.css
706 ms
custom.css
640 ms
global.js
632 ms
10-bootstrap.min.js
641 ms
15-jquery.total-storage.min.js
626 ms
15-jquery.uniform-modified.js
613 ms
products-comparison.js
603 ms
global.js
591 ms
owl.carousel.js
622 ms
jquery.hoverIntent.js
630 ms
jquery.fancybox.js
623 ms
treeManagement.js
655 ms
blocknewsletter.js
635 ms
jquery.autocomplete.js
593 ms
blocksearch.js
635 ms
ajax-wishlist.js
636 ms
stmegamenu.js
623 ms
jquery.iosslider.min.js
633 ms
camera.js
604 ms
jquery.ui.widget.min.js
585 ms
jquery.mobile.customized.min.js
644 ms
steasytabs.js
638 ms
jquery.fitvids.js
652 ms
stblog.js
655 ms
stblogcomments.js
610 ms
jquery.parallax-1.1.3.js
602 ms
GoogleAnalyticActionLib.js
650 ms
index.js
651 ms
jquery.elevatezoom.min.js
637 ms
main.js
627 ms
analytics.js
28 ms
css
95 ms
ec.js
49 ms
provesa-logo-1450715607.jpg
168 ms
acuicultura.jpg
168 ms
avicultura.jpg
163 ms
bovino.jpg
163 ms
ovino-caprino.jpg
162 ms
cunicultura.jpg
164 ms
equino.jpg
501 ms
gato.jpg
500 ms
perro.jpg
496 ms
porcino.jpg
498 ms
otros.jpg
492 ms
3-manufacturer_default.jpg
484 ms
9-manufacturer_default.jpg
491 ms
7-manufacturer_default.jpg
499 ms
6-manufacturer_default.jpg
499 ms
1-manufacturer_default.jpg
500 ms
4-manufacturer_default.jpg
500 ms
2-manufacturer_default.jpg
500 ms
5-manufacturer_default.jpg
501 ms
10-manufacturer_default.jpg
501 ms
8-manufacturer_default.jpg
502 ms
provesa-logo-positivo.png
503 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
124 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
24 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
420 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
423 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
424 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
423 ms
fontello.woff
403 ms
3b0ecf35f3ce65711741d24b7434db9f.jpg
417 ms
b4339804051fb3fe02d58dfb6f0b0a32.jpg
565 ms
8d714423eba14126c190ba90dc6c0b5d.jpg
471 ms
opener.png
350 ms
Yq6R-LCAWCX3-6Ky7FAFrOF6lw.ttf
276 ms
collect
352 ms
6277c5215ffcefe8178a49849c70ebf3.jpg
302 ms
37cd719e1af5330af755d0f2076dfe2e.jpg
215 ms
provesa.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
provesa.com 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
General
Impact
Issue
Detected JavaScript libraries
provesa.com 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
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 Provesa.com 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 Provesa.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.
provesa.com
Open Graph description is not detected on the main page of PROVESA. 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: