Tools & Wizards About Us
appiani.it screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

appiani.it

Appiani - Ceramiche dal 1873 | Gruppo Bardelli

Page Load Speed

3.8 sec in total

First Response

389 ms

Resources Loaded

2.7 sec

Page Rendered

642 ms

appiani.it screenshot

About Website

Visit appiani.it now to see the best up-to-date Appiani content for Russia and also check out these interesting facts you probably never knew about appiani.it

Quasi 150 anni di storia rendono Appiani uno dei brand più autorevoli e longevi del panorama ceramico italiano e internazionale | Scopri le novità

Visit appiani.it

Key Findings

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

Performance Metrics

appiani.it performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value3,490 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

appiani.it

389 ms

668 ms

styles.css

177 ms

style.css

267 ms

style.css

359 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Appiani.it, 97% (71 requests) were made to Gruppobardelli.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Gruppobardelli.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.7 kB (28%)

Content Size

774.4 kB

After Optimization

560.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Appiani.it main page is 774.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. 50% of websites need less resources to load. Javascripts take 408.9 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 209.8 kB

  • Original 230.1 kB
  • After minification 168.9 kB
  • After compression 20.3 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 61.2 kB, which is 27% 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 209.8 kB or 91% of the original size.

Image Optimization

-24%

Potential reduce by 1.5 kB

  • Original 6.4 kB
  • After minification 4.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. Obviously, Appiani needs image optimization as it can save up to 1.5 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 537 B

  • Original 408.9 kB
  • After minification 408.9 kB
  • After compression 408.3 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

-1%

Potential reduce by 1.8 kB

  • Original 129.0 kB
  • After minification 128.7 kB
  • After compression 127.3 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. Appiani.it has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (88%)

Requests Now

68

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

appiani.it

appiani.it

389 ms

668 ms

styles.css

styles.css

177 ms

style.css

style.css

267 ms

style.css

style.css

359 ms

tailwind.css

tailwind.css

368 ms

um-modal.min.css

um-modal.min.css

272 ms

jquery-ui.min.css

jquery-ui.min.css

283 ms

tipsy.min.css

tipsy.min.css

285 ms

um-raty.min.css

um-raty.min.css

355 ms

select2.min.css

select2.min.css

377 ms

um-fileupload.min.css

um-fileupload.min.css

379 ms

um-confirm.min.css

um-confirm.min.css

378 ms

default.min.css

default.min.css

444 ms

default.date.min.css

default.date.min.css

445 ms

default.time.min.css

default.time.min.css

450 ms

fonticons-ii.min.css

fonticons-ii.min.css

450 ms

fonticons-fa.min.css

fonticons-fa.min.css

470 ms

um-fontawesome.min.css

um-fontawesome.min.css

562 ms

common.min.css

common.min.css

532 ms

um-responsive.min.css

um-responsive.min.css

533 ms

um-styles.min.css

um-styles.min.css

540 ms

cropper.min.css

cropper.min.css

541 ms

um-profile.min.css

um-profile.min.css

581 ms

um-account.min.css

um-account.min.css

622 ms

um-misc.min.css

um-misc.min.css

621 ms

um-old-default.min.css

um-old-default.min.css

630 ms

language-cookie.js

language-cookie.js

644 ms

xdomain-data.js

xdomain-data.js

656 ms

jquery.min.js

jquery.min.js

749 ms

um-gdpr.min.js

um-gdpr.min.js

709 ms

manifest.js

manifest.js

629 ms

vendor.js

vendor.js

1075 ms

mymix-vendors.js

mymix-vendors.js

895 ms

index.js

index.js

889 ms

underscore.min.js

underscore.min.js

894 ms

wp-util.min.js

wp-util.min.js

895 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

893 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

803 ms

wp-polyfill.min.js

wp-polyfill.min.js

807 ms

hooks.min.js

hooks.min.js

805 ms

i18n.min.js

i18n.min.js

788 ms

tipsy.min.js

tipsy.min.js

791 ms

um-confirm.min.js

um-confirm.min.js

718 ms

picker.min.js

picker.min.js

808 ms

picker.date.min.js

picker.date.min.js

796 ms

picker.time.min.js

picker.time.min.js

799 ms

it_IT.min.js

it_IT.min.js

798 ms

common.min.js

common.min.js

798 ms

cropper.min.js

cropper.min.js

807 ms

common-frontend.min.js

common-frontend.min.js

805 ms

um-modal.min.js

um-modal.min.js

800 ms

jquery-form.min.js

jquery-form.min.js

803 ms

fileupload.js

fileupload.js

791 ms

um-functions.min.js

um-functions.min.js

731 ms

um-responsive.min.js

um-responsive.min.js

803 ms

um-conditional.min.js

um-conditional.min.js

795 ms

select2.full.min.js

select2.full.min.js

797 ms

it.js

it.js

765 ms

um-raty.min.js

um-raty.min.js

774 ms

um-scripts.min.js

um-scripts.min.js

734 ms

um-profile.min.js

um-profile.min.js

802 ms

um-account.min.js

um-account.min.js

782 ms

gtm.js

gtm.js

240 ms

logo_ceramicabardelli.png

logo_ceramicabardelli.png

656 ms

logo_vogue_2024.svg

logo_vogue_2024.svg

656 ms

logo_appiani.svg

logo_appiani.svg

660 ms

logo_appiani_w.svg

logo_appiani_w.svg

658 ms

logo_vogue_2024_w.svg

logo_vogue_2024_w.svg

542 ms

NexaLight.woff

NexaLight.woff

545 ms

NexaBold.woff

NexaBold.woff

576 ms

bootstrap-icons.woff

bootstrap-icons.woff

724 ms

logo_ceramicabardelli_w.png

logo_ceramicabardelli_w.png

576 ms

Accessibility Review

appiani.it accessibility score

71

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

appiani.it best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

appiani.it SEO score

86

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 Appiani.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 Appiani.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

appiani.it

Open Graph data is detected on the main page of Appiani. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: