Tools & Wizards About Us
ftsupport.it screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

ftsupport.it

FT MERCATI

Page Load Speed

4.3 sec in total

First Response

522 ms

Resources Loaded

2.5 sec

Page Rendered

1.2 sec

ftsupport.it screenshot

About Website

Visit ftsupport.it now to see the best up-to-date FT Support content and also check out these interesting facts you probably never knew about ftsupport.it

Visit ftsupport.it

Key Findings

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

Performance Metrics

ftsupport.it performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

ftsupport.it

522 ms

www.ftmercati.com

354 ms

index.html

95 ms

css2

36 ms

swiper-bundle.min.css

84 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ftsupport.it, 97% (70 requests) were made to Ftmercati.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (857 ms) relates to the external source Ftmercati.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.5 kB (9%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ftsupport.it main page is 1.7 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 23.9 kB

  • Original 28.9 kB
  • After minification 19.2 kB
  • After compression 5.0 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.7 kB, which is 34% 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 23.9 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 132.3 kB

  • Original 1.5 MB
  • After minification 1.3 MB

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. FT Support images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 211.7 kB
  • After minification 211.7 kB
  • After compression 210.7 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

-37%

Potential reduce by 6.3 kB

  • Original 17.1 kB
  • After minification 17.1 kB
  • After compression 10.8 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. Ftsupport.it needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (10%)

Requests Now

69

After Optimization

62

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ftsupport.it

ftsupport.it

522 ms

www.ftmercati.com

www.ftmercati.com

354 ms

index.html

index.html

95 ms

css2

css2

36 ms

swiper-bundle.min.css

swiper-bundle.min.css

84 ms

style.css

style.css

169 ms

login.svg

login.svg

286 ms

FT-Mercati.png

FT-Mercati.png

367 ms

carousel-03.jpg

carousel-03.jpg

533 ms

carousel-01.jpg

carousel-01.jpg

611 ms

carousel-02.jpg

carousel-02.jpg

609 ms

arrow-right.svg

arrow-right.svg

367 ms

athena.png

athena.png

370 ms

raffmetal.png

raffmetal.png

448 ms

cimbali.png

cimbali.png

449 ms

ifi.png

ifi.png

452 ms

alpewa.png

alpewa.png

529 ms

rfi.png

rfi.png

530 ms

iseo.png

iseo.png

533 ms

stiga.png

stiga.png

612 ms

finder.png

finder.png

611 ms

recuperator.png

recuperator.png

615 ms

oldrati.png

oldrati.png

616 ms

arvedi.png

arvedi.png

689 ms

amiat.png

amiat.png

691 ms

delonghi.png

delonghi.png

693 ms

calligaris.png

calligaris.png

693 ms

valbruna.png

valbruna.png

695 ms

ansaldoenergia.png

ansaldoenergia.png

697 ms

a2a.png

a2a.png

771 ms

gewiss.png

gewiss.png

772 ms

caleffi.png

caleffi.png

773 ms

trenitalia.png

trenitalia.png

775 ms

pietrofiorentini.png

pietrofiorentini.png

777 ms

fantinicosmi.png

fantinicosmi.png

778 ms

sanlorenzo.png

sanlorenzo.png

851 ms

artemide.png

artemide.png

854 ms

ama.png

ama.png

853 ms

nice.png

nice.png

856 ms

dmAdvancedHeader-min.js

dmAdvancedHeader-min.js

857 ms

swiper-bundle.min.js

swiper-bundle.min.js

784 ms

marquee3k.js

marquee3k.js

760 ms

hc-sticky.js

hc-sticky.js

655 ms

site-min.js

site-min.js

574 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

575 ms

dx.chartjs.js

dx.chartjs.js

738 ms

index.js

index.js

504 ms

enel.png

enel.png

569 ms

zoppas.png

zoppas.png

570 ms

camozzi.png

camozzi.png

492 ms

carel.png

carel.png

494 ms

acea.png

acea.png

500 ms

aristoncavi.png

aristoncavi.png

568 ms

scrigno.png

scrigno.png

496 ms

pichler.png

pichler.png

497 ms

monchieri.png

monchieri.png

495 ms

bonfiglioli.png

bonfiglioli.png

528 ms

fincantieri.png

fincantieri.png

572 ms

voestalpine.png

voestalpine.png

572 ms

scavolini.png

scavolini.png

501 ms

electrolux.png

electrolux.png

503 ms

sanremo.png

sanremo.png

498 ms

arcansas.png

arcansas.png

502 ms

brembo.png

brembo.png

573 ms

eventi-large.jpg

eventi-large.jpg

734 ms

download.svg

download.svg

501 ms

google-play.png

google-play.png

501 ms

app-store.png

app-store.png

502 ms

phone_app.png

phone_app.png

749 ms

youtube.svg

youtube.svg

573 ms

linkedin.svg

linkedin.svg

574 ms

ft-mercati-large.png

ft-mercati-large.png

587 ms

Accessibility Review

ftsupport.it accessibility score

74

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.

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ftsupport.it best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ftsupport.it SEO score

75

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ftsupport.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 Ftsupport.it 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.

Social Sharing Optimization

ftsupport.it

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