Tools & Wizards About Us
fruticoles.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fruticoles.com

Fruticoles - Programa Escolar de Consumo de Frutas y Hortalizas de la Unión Europea, en la Comunidad de Madrid

Page Load Speed

3.4 sec in total

First Response

449 ms

Resources Loaded

2.6 sec

Page Rendered

320 ms

fruticoles.com screenshot

About Website

Visit fruticoles.com now to see the best up-to-date Fruticoles content and also check out these interesting facts you probably never knew about fruticoles.com

Programa Escolar de Consumo de Frutas y Hortalizas de la Unión Europea, en la Comunidad de Madrid

Visit fruticoles.com

Key Findings

We analyzed Fruticoles.com page load time and found that the first response time was 449 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fruticoles.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.517

15/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

Index.aspx

449 ms

dw.js

281 ms

estilo.css

266 ms

swfobject_modified.js

418 ms

style.css

284 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 96% of them (23 requests) were addressed to the original Fruticoles.com, 4% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fruticoles.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.5 kB (12%)

Content Size

934.6 kB

After Optimization

827.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fruticoles.com main page is 934.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 839.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 27.0 kB

  • Original 30.6 kB
  • After minification 15.6 kB
  • After compression 3.7 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 15.1 kB, which is 49% 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 27.0 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 37.5 kB

  • Original 839.4 kB
  • After minification 801.9 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. Fruticoles images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 34.6 kB

  • Original 54.6 kB
  • After minification 45.0 kB
  • After compression 20.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 34.6 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 8.5 kB

  • Original 10.0 kB
  • After minification 8.2 kB
  • After compression 1.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. Fruticoles.com needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fruticoles. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

Index.aspx

Index.aspx

449 ms

dw.js

dw.js

281 ms

estilo.css

estilo.css

266 ms

swfobject_modified.js

swfobject_modified.js

418 ms

style.css

style.css

284 ms

jquery-latest.pack.js

jquery-latest.pack.js

565 ms

jcarousellite_1.0.1c4.js

jcarousellite_1.0.1c4.js

426 ms

get_flash_player.gif

get_flash_player.gif

49 ms

zjxwvo30.advolive-oil-968657_1920.jpg

zjxwvo30.advolive-oil-968657_1920.jpg

1160 ms

fondo.jpg

fondo.jpg

889 ms

top.png

top.png

421 ms

banner_Recetario.jpg

banner_Recetario.jpg

582 ms

banner_encuesta.jpg

banner_encuesta.jpg

430 ms

TIT_NOTICIAS.png

TIT_NOTICIAS.png

136 ms

linea.png

linea.png

140 ms

banner_quehace.jpg

banner_quehace.jpg

426 ms

banner_juegos.jpg

banner_juegos.jpg

469 ms

banner_fruta.jpg

banner_fruta.jpg

595 ms

banner_tematicos.jpg

banner_tematicos.jpg

604 ms

banners_tira.png

banners_tira.png

718 ms

bottom.png

bottom.png

604 ms

pxbenfke.hc1fruits-and-vegetables-805797_1280.jpg

pxbenfke.hc1fruits-and-vegetables-805797_1280.jpg

1252 ms

Cuprum-webfont.woff

Cuprum-webfont.woff

704 ms

playtime-webfont.woff

playtime-webfont.woff

869 ms

Accessibility Review

fruticoles.com accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

fruticoles.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fruticoles.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fruticoles.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fruticoles.com main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

fruticoles.com

Open Graph description is not detected on the main page of Fruticoles. 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: