Tools & Wizards About Us
ponsi.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

ponsi.com

Home page | Ercos - Bathroom experience

Page Load Speed

8 sec in total

First Response

445 ms

Resources Loaded

6.2 sec

Page Rendered

1.4 sec

ponsi.com screenshot

About Website

Welcome to ponsi.com homepage info - get ready to check Ponsi best content right away, or after learning these important things about ponsi.com

Offriamo soluzioni sostenibili di comfort ed estetica nel mondo del riscaldamento e del bagno per ogni ambiente domestico e professionale.

Visit ponsi.com

Key Findings

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

Performance Metrics

ponsi.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value27.3 s

0/100

25%

SI (Speed Index)

Value24.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value32.8 s

0/100

10%

Network Requests Diagram

ponsi.com

445 ms

it

1198 ms

frontend.css

350 ms

main.css

660 ms

js

257 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ponsi.com, 64% (30 requests) were made to Ercosponsi.com and 17% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ercosponsi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 457.1 kB (3%)

Content Size

14.9 MB

After Optimization

14.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ponsi.com main page is 14.9 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. Only a small number of websites need less resources to load. Images take 14.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 88.1 kB

  • Original 110.9 kB
  • After minification 100.9 kB
  • After compression 22.8 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 88.1 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 367.8 kB

  • Original 14.6 MB
  • After minification 14.2 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. Ponsi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 769 B

  • Original 59.0 kB
  • After minification 59.0 kB
  • After compression 58.2 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 468 B

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 76.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. Ponsi.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

37

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ponsi.com

ponsi.com

445 ms

it

it

1198 ms

frontend.css

frontend.css

350 ms

main.css

main.css

660 ms

js

js

257 ms

evelean_analytics.js

evelean_analytics.js

460 ms

evelean_cookiemanager.js

evelean_cookiemanager.js

375 ms

async.js

async.js

443 ms

libs.js

libs.js

759 ms

api.js

api.js

297 ms

main.js

main.js

864 ms

gtm.js

gtm.js

191 ms

logo.svg

logo.svg

176 ms

ico-nuova-configurazione.png

ico-nuova-configurazione.png

729 ms

ico-riprendi-configurazione.png

ico-riprendi-configurazione.png

336 ms

ico-riprendi-eden.png

ico-riprendi-eden.png

622 ms

ico-configuratore-installatore.png

ico-configuratore-installatore.png

333 ms

en.svg

en.svg

246 ms

ico-chisiamo.svg

ico-chisiamo.svg

199 ms

ico-configurator.svg

ico-configurator.svg

262 ms

ico-download.svg

ico-download.svg

265 ms

img-cover.jpg

img-cover.jpg

931 ms

perche-scegliere-box-doccia-walk-in.jpg

perche-scegliere-box-doccia-walk-in.jpg

665 ms

come-scegliere-sanitari-bagno.jpg

come-scegliere-sanitari-bagno.jpg

1754 ms

scaldasalviette-cosa-sapere.jpg

scaldasalviette-cosa-sapere.jpg

661 ms

realta-virtuale-arredo-bagno.jpg

realta-virtuale-arredo-bagno.jpg

1018 ms

pattern-small.svg

pattern-small.svg

681 ms

Bagno_Cover.png

Bagno_Cover.png

1293 ms

ico-cta.svg

ico-cta.svg

932 ms

Caldo_Cover.png

Caldo_Cover.png

1427 ms

pattern.svg

pattern.svg

1014 ms

iubenda_cs.js

iubenda_cs.js

294 ms

gen_204

gen_204

85 ms

newsletter-img.jpg

newsletter-img.jpg

487 ms

css2

css2

49 ms

core-it.js

core-it.js

253 ms

recaptcha__en.js

recaptcha__en.js

320 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

352 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

350 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

351 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

349 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UbtY.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UbtY.ttf

330 ms

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUbtY.ttf

nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUbtY.ttf

349 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDQ.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiukDQ.ttf

379 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsukDQ.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsukDQ.ttf

377 ms

fontawesome.css

fontawesome.css

106 ms

fontawesome.css

fontawesome.css

103 ms

Accessibility Review

ponsi.com accessibility score

77

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

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

ponsi.com SEO score

82

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

    UTF-8

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

ponsi.com

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