7.3 sec in total
1.6 sec
4.4 sec
1.3 sec
Click here to check amazing Agrogenia content. Otherwise, check out these important facts you probably never knew about agrogenia.es
Somos una empresa con más de 10 años de experiencia en la investigación y la producción de biofertilizantes respetuosos con el suelo.
Visit agrogenia.esWe analyzed Agrogenia.es page load time and found that the first response time was 1.6 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
agrogenia.es performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value13.1 s
0/100
25%
Value8.2 s
20/100
10%
Value940 ms
30/100
30%
Value0
100/100
15%
Value12.8 s
13/100
10%
1622 ms
193 ms
133 ms
229 ms
236 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 28% of them (28 requests) were addressed to the original Agrogenia.es, 26% (26 requests) were made to Cdn.website-start.de and 8% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Agrogenia.es.
Page size can be reduced by 712.0 kB (34%)
2.1 MB
1.4 MB
In fact, the total size of Agrogenia.es main page is 2.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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 99.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 99.6 kB or 84% of the original size.
Potential reduce by 22.4 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. Agrogenia images are well optimized though.
Potential reduce by 501.0 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 501.0 kB or 69% of the original size.
Potential reduce by 89.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. Agrogenia.es needs all CSS files to be minified and compressed as it can save up to 89.1 kB or 85% of the original size.
Number of requests can be reduced by 46 (49%)
94
48
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Agrogenia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.agrogenia.es
1622 ms
style.css
193 ms
theming.css
133 ms
web.css
229 ms
common,counter,socialbookmark,shoppingbasket
236 ms
mobilenavigation.css
223 ms
logstate2-css.php
482 ms
logstate-js.php
497 ms
web.js
542 ms
web.bundle.js
229 ms
mobilenavigation.js
326 ms
common,counter,socialbookmark,shoppingbasket
532 ms
589 ms
pfcsupport.js
375 ms
basic.css
537 ms
web.css
604 ms
jsapi
20 ms
8214.js
222 ms
analytics.js
31 ms
logo.png
125 ms
emotionheader5798814073.jpg
411 ms
QeBG_XeF_normal.png
172 ms
background.jpg
389 ms
cache_2459992001.jpg
202 ms
cache_2448989244.png
436 ms
cache_2448989248.png
321 ms
cache_2458216010.png
231 ms
cache_2458218227.jpg
302 ms
cache_2458218210.jpg
349 ms
cache_2453692693.jpg
434 ms
cache_2459080642.jpg
656 ms
cache_2453692760.jpg
483 ms
cache_2459409868.jpg
656 ms
cache_2453692823.jpg
587 ms
cache_2462882818.jpg
731 ms
cache_2448974380.png
685 ms
cache_2459992137.jpg
631 ms
cache_2448974386.png
695 ms
cache_2457938678.jpg
876 ms
cache_2459329444.jpg
742 ms
cache_2457938778.jpg
876 ms
cache_2457939154.jpg
778 ms
cache_2457938969.jpg
900 ms
printer.gif
102 ms
mail.gif
103 ms
Cd7EcCgWoAAEQTj.jpg
321 ms
dIIeZCM6_normal.jpg
250 ms
collect
14 ms
16 ms
collect
105 ms
default+es.css
9 ms
espresso.css
21 ms
default+es.I.js
14 ms
espresso.css
25 ms
print.css
103 ms
embed.php
433 ms
basic.css
282 ms
web.css
270 ms
order.js
105 ms
ga-audiences
34 ms
twitterNG.js
363 ms
es_ES
425 ms
twitter_bird_logo.png
290 ms
widgets.js
107 ms
icon_reply_base.png
374 ms
icon_retweet_base.png
422 ms
icon_favorite_base.png
435 ms
icon_retweet_small.png
523 ms
jquery.min.js
65 ms
embed.jScrollPane.js,embed.jquery.mousewheel.3.0.4.pack.js,embed.soundmanager2.js,hulkembed2.js,embed_detector.js
272 ms
hsPlayer.js.php
306 ms
default
458 ms
playful_05d.png
113 ms
facebook.png
430 ms
twitter.png
499 ms
googleplus.png
569 ms
async-ads.js
87 ms
google_custom_search_watermark.gif
80 ms
small-logo.png
33 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
11 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
28 ms
mx_v2_gradients.png
97 ms
ga.js
31 ms
embed_detector.php
282 ms
flConfig_hsPlayerLight.php
244 ms
__utm.gif
14 ms
__utm.gif
13 ms
8bcda29bc80494bec2e5011bd748ad23.png
277 ms
icons.png
98 ms
default.png
290 ms
e10306c6f67a5e8cf439ece871e8e9c5_f.png
311 ms
032821573ddea4a0f4d7fe6e44495f5e.jpg
285 ms
1458482408525
334 ms
jot.html
3 ms
nr-885.min.js
19 ms
258 ms
cb21ff2afc
86 ms
ajax-loader-3.gif
56 ms
174 ms
agrogenia.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
agrogenia.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
Page has valid source maps
agrogenia.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Agrogenia.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 Agrogenia.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.
agrogenia.es
Open Graph data is detected on the main page of Agrogenia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: