Tools & Wizards About Us
tomato.it screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

tomato.it

Contactlab leader in soluzioni di digital marketing multicanale

Page Load Speed

3.1 sec in total

First Response

1.2 sec

Resources Loaded

1.8 sec

Page Rendered

118 ms

tomato.it screenshot

About Website

Welcome to tomato.it homepage info - get ready to check Tomato best content for France right away, or after learning these important things about tomato.it

Contactlab offre soluzioni di digital marketing multicanale personalizzato, gestione campagne marketing online e consulenze per la strategia digitale di aziende e Brand.

Visit tomato.it

Key Findings

We analyzed Tomato.it page load time and found that the first response time was 1.2 sec and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

tomato.it performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

tomato.it

1222 ms

tomato.css

107 ms

logo_cl.gif

221 ms

entra_blue.gif

227 ms

cerchiamo_it.gif

223 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 82% of them (9 requests) were addressed to the original Tomato.it, 18% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Tomato.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.5 kB (5%)

Content Size

67.4 kB

After Optimization

63.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomato.it main page is 67.4 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 44.9 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 1.3 kB

  • Original 2.4 kB
  • After minification 2.3 kB
  • After compression 1.1 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 1.3 kB or 54% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 44.9 kB
  • After minification 44.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. Tomato images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 2.2 kB

  • Original 2.9 kB
  • After minification 2.3 kB
  • After compression 719 B

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. Tomato.it needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 75% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomato. According to our analytics all requests are already optimized.

Network Requests Diagram

tomato.it

tomato.it

1222 ms

tomato.css

tomato.css

107 ms

logo_cl.gif

logo_cl.gif

221 ms

entra_blue.gif

entra_blue.gif

227 ms

cerchiamo_it.gif

cerchiamo_it.gif

223 ms

banner_newsletter.jpg

banner_newsletter.jpg

536 ms

ga.js

ga.js

30 ms

sfumatura.gif

sfumatura.gif

127 ms

bg_content.gif

bg_content.gif

197 ms

bg_ombra.gif

bg_ombra.gif

238 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

tomato.it accessibility score

82

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tomato.it best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tomato.it SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    IT

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomato.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Tomato.it 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.

Social Sharing Optimization

tomato.it

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