Tools & Wizards About Us
fabeitaly.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

fabeitaly.com

Fabeshop.com | Vendita Zoccoli, Plantari Podomed

Page Load Speed

2.2 sec in total

First Response

349 ms

Resources Loaded

1.7 sec

Page Rendered

177 ms

fabeitaly.com screenshot

About Website

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

Default Description

Visit fabeitaly.com

Key Findings

We analyzed Fabeitaly.com page load time and found that the first response time was 349 ms 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 40% of websites can load faster.

Performance Metrics

fabeitaly.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value19.1 s

0/100

10%

TBT (Total Blocking Time)

Value35,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value48.2 s

0/100

10%

Network Requests Diagram

fabeitaly.com

349 ms

www.fabeitaly.com

500 ms

mod_jflanguageselection.css

81 ms

mootools.js

241 ms

caption.js

157 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 Fabeitaly.com, 4% (1 request) were made to Fabeshop.com. The less responsive or slowest element that took the longest time to load (587 ms) relates to the external source Fabeshop.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.8 kB (35%)

Content Size

340.3 kB

After Optimization

219.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fabeitaly.com main page is 340.3 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. 15% of websites need less resources to load. Images take 176.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.0 kB

  • Original 15.2 kB
  • After minification 12.0 kB
  • After compression 3.2 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 3.2 kB, which is 21% 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 12.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 131 B

  • Original 176.0 kB
  • After minification 175.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. Fabeitaly images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 75.8 kB

  • Original 110.4 kB
  • After minification 109.4 kB
  • After compression 34.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 75.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 32.8 kB

  • Original 38.7 kB
  • After minification 29.5 kB
  • After compression 5.9 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. Fabeitaly.com needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (55%)

Requests Now

22

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fabeitaly.com

fabeitaly.com

349 ms

www.fabeitaly.com

www.fabeitaly.com

500 ms

mod_jflanguageselection.css

mod_jflanguageselection.css

81 ms

mootools.js

mootools.js

241 ms

caption.js

caption.js

157 ms

cufon-yui.js

cufon-yui.js

159 ms

Futura_BdCn_BT_400.font.js

Futura_BdCn_BT_400.font.js

159 ms

cufon-replace.js

cufon-replace.js

160 ms

maxheight.js

maxheight.js

160 ms

constant.css

constant.css

233 ms

template.css

template.css

272 ms

slider_img.jpg

slider_img.jpg

587 ms

fabeitaly-logo.png

fabeitaly-logo.png

84 ms

it.gif

it.gif

82 ms

en.gif

en.gif

82 ms

dettagli-fuxia.gif

dettagli-fuxia.gif

82 ms

menu-bg.gif

menu-bg.gif

84 ms

ver.gif

ver.gif

80 ms

search_bg.gif

search_bg.gif

150 ms

bg-1.gif

bg-1.gif

148 ms

dot_line.gif

dot_line.gif

150 ms

top_left_bg.gif

top_left_bg.gif

150 ms

bottom_left_bg.gif

bottom_left_bg.gif

156 ms

arrow.gif

arrow.gif

159 ms

Accessibility Review

fabeitaly.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Best Practices

fabeitaly.com 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

High

Page has valid source maps

SEO Factors

fabeitaly.com SEO score

87

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

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

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

fabeitaly.com

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