Tools & Wizards About Us
puroamore.eu screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

puroamore.eu

Abbigliamento ecosostenibile a Treviso - Made in Italy | PuroAmore

Page Load Speed

6.6 sec in total

First Response

1.2 sec

Resources Loaded

5.1 sec

Page Rendered

330 ms

puroamore.eu screenshot

About Website

Visit puroamore.eu now to see the best up-to-date Puro Amore content and also check out these interesting facts you probably never knew about puroamore.eu

Puro Amore è una linea di abbigliamento ecosostenibile a Treviso. Tutti i capi di abbigliamento sono pensati e realizzati a mano in atelier, con tessuti biologici certificati. Dai un'occhiata ai ...

Visit puroamore.eu

Key Findings

We analyzed Puroamore.eu page load time and found that the first response time was 1.2 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

puroamore.eu performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

1201 ms

webfont.js

47 ms

wp-emoji-release.min.js

221 ms

style.min.css

239 ms

style-legacy.css

241 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 98% of them (89 requests) were addressed to the original Puroamore.eu, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Puroamore.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 785.7 kB (15%)

Content Size

5.2 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puroamore.eu main page is 5.2 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. 70% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 94.9 kB

  • Original 115.0 kB
  • After minification 104.9 kB
  • After compression 20.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 94.9 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 447.1 kB

  • Original 4.5 MB
  • After minification 4.0 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. Puro Amore images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 73.6 kB

  • Original 305.0 kB
  • After minification 288.3 kB
  • After compression 231.4 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 73.6 kB or 24% of the original size.

CSS Optimization

-52%

Potential reduce by 170.0 kB

  • Original 324.2 kB
  • After minification 284.1 kB
  • After compression 154.2 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. Puroamore.eu needs all CSS files to be minified and compressed as it can save up to 170.0 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (82%)

Requests Now

88

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1201 ms

webfont.js

webfont.js

47 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

221 ms

style.min.css

style.min.css

239 ms

style-legacy.css

style-legacy.css

241 ms

styles.css

styles.css

249 ms

woocommerce-layout.css

woocommerce-layout.css

245 ms

woocommerce.css

woocommerce.css

256 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

339 ms

js_composer.min.css

js_composer.min.css

576 ms

Defaults.css

Defaults.css

360 ms

style.min.css

style.min.css

367 ms

app.css

app.css

379 ms

easyzoom.css

easyzoom.css

369 ms

woocommerce-overwrite.css

woocommerce-overwrite.css

452 ms

animate.min.css

animate.min.css

479 ms

animations-products-grid.css

animations-products-grid.css

485 ms

fresco.css

fresco.css

491 ms

swiper.min.css

swiper.min.css

488 ms

owl.carousel.css

owl.carousel.css

561 ms

owl.theme.css

owl.theme.css

601 ms

offcanvas.css

offcanvas.css

607 ms

nanoscroller.css

nanoscroller.css

597 ms

select2.css

select2.css

610 ms

defaults.css

defaults.css

678 ms

styles.css

styles.css

693 ms

responsive.css

responsive.css

716 ms

style.css

style.css

713 ms

font-awesome.min.css

font-awesome.min.css

723 ms

style.css

style.css

718 ms

jquery.js

jquery.js

806 ms

jquery-migrate.min.js

jquery-migrate.min.js

802 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

836 ms

add-to-cart.min.js

add-to-cart.min.js

834 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

829 ms

ultimate-params.min.js

ultimate-params.min.js

841 ms

modernizr.custom.js

modernizr.custom.js

907 ms

background-style.min.css

background-style.min.css

862 ms

flexslider.min.css

flexslider.min.css

737 ms

prettyPhoto.min.css

prettyPhoto.min.css

718 ms

scripts.js

scripts.js

717 ms

js.cookie.min.js

js.cookie.min.js

715 ms

woocommerce.min.js

woocommerce.min.js

776 ms

jquery.cookie.min.js

jquery.cookie.min.js

782 ms

Cart.min.js

Cart.min.js

728 ms

wpcf7r-fe.js

wpcf7r-fe.js

710 ms

foundation.min.js

foundation.min.js

808 ms

foundation.interchange.js

foundation.interchange.js

706 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

746 ms

imagesloaded.js

imagesloaded.js

707 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

702 ms

jquery.fitvids.js

jquery.fitvids.js

697 ms

swiper.min.js

swiper.min.js

812 ms

owl.carousel.min.js

owl.carousel.min.js

747 ms

fresco.js

fresco.js

718 ms

jquery.nanoscroller.min.js

jquery.nanoscroller.min.js

707 ms

select2.min.js

select2.min.js

702 ms

jquery.scroll_to.js

jquery.scroll_to.js

696 ms

jquery.stellar.min.js

jquery.stellar.min.js

743 ms

jquery.snapscroll.min.js

jquery.snapscroll.min.js

786 ms

easyzoom.js

easyzoom.js

724 ms

scripts.js

scripts.js

707 ms

wc-product-gallery.js

wc-product-gallery.js

692 ms

wc-counters.js

wc-counters.js

689 ms

style.css

style.css

735 ms

wp-embed.min.js

wp-embed.min.js

907 ms

js_composer_front.min.js

js_composer_front.min.js

831 ms

jquery-appear.min.js

jquery-appear.min.js

828 ms

ultimate_bg.min.js

ultimate_bg.min.js

804 ms

custom.min.js

custom.min.js

798 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

823 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

817 ms

frontend.js

frontend.js

752 ms

fbevents.js

fbevents.js

146 ms

arrow.svg

arrow.svg

337 ms

puroamore__oriz_sfondo-b.png

puroamore__oriz_sfondo-b.png

762 ms

puroamore__logo_or.png

puroamore__logo_or.png

737 ms

Abbigliamento-eco-sostenibile-treviso-1.png

Abbigliamento-eco-sostenibile-treviso-1.png

1266 ms

Untitled-design-4.png

Untitled-design-4.png

1078 ms

Untitled-design-3-1.png

Untitled-design-3-1.png

1189 ms

Untitled-design-6-2.png

Untitled-design-6-2.png

1087 ms

Caterina2.jpg

Caterina2.jpg

1261 ms

Caterina3.jpg

Caterina3.jpg

1262 ms

Caterina4.jpg

Caterina4.jpg

1422 ms

puroamore__logo_orizzontale_payoff_trasp.jpg

puroamore__logo_orizzontale_payoff_trasp.jpg

1304 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

259 ms

762 ms

Untitled-design-6-2.png

Untitled-design-6-2.png

963 ms

flexslider-icon.woff

flexslider-icon.woff

127 ms

empty_cart_offcanvas.png

empty_cart_offcanvas.png

110 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

117 ms

Accessibility Review

puroamore.eu accessibility score

80

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

Links do not have a discernible name

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

puroamore.eu best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

puroamore.eu SEO score

90

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

puroamore.eu

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