Tools & Wizards About Us
pollini.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

pollini.com

Pollini | Luxury Shoes and Bags with Unique and Precious Style since 1953 | Pollini

Page Load Speed

4.8 sec in total

First Response

311 ms

Resources Loaded

4.1 sec

Page Rendered

327 ms

pollini.com screenshot

About Website

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

Online sale of Luxury Shoes, Bags and Accessories for Men and Women. Sophisticated Italian style for every occasion ✓ Fast shipping and easy returns

Visit pollini.com

Key Findings

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

Performance Metrics

pollini.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value40.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value1.011

2/100

15%

TTI (Time to Interactive)

Value90.9 s

0/100

10%

Network Requests Diagram

pollini.com

311 ms

pollini.com

378 ms

www.pollini.com

186 ms

www.pollini.com

475 ms

en

279 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 45% of them (23 requests) were addressed to the original Pollini.com, 8% (4 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Pollini.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.4 kB (7%)

Content Size

4.2 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pollini.com main page is 4.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. 65% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 157.7 kB

  • Original 175.7 kB
  • After minification 95.8 kB
  • After compression 18.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 79.9 kB, which is 45% 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 157.7 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 132.0 kB

  • Original 3.6 MB
  • After minification 3.5 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. Pollini images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 459 B

  • Original 363.1 kB
  • After minification 363.1 kB
  • After compression 362.6 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

-0%

Potential reduce by 168 B

  • Original 96.6 kB
  • After minification 96.6 kB
  • After compression 96.4 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. Pollini.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (68%)

Requests Now

44

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pollini.com

pollini.com

311 ms

pollini.com

pollini.com

378 ms

www.pollini.com

www.pollini.com

186 ms

www.pollini.com

www.pollini.com

475 ms

en

en

279 ms

app.css

app.css

285 ms

api.js

api.js

55 ms

js

js

69 ms

9463.js

9463.js

412 ms

gift.js

gift.js

479 ms

stub.js

stub.js

38 ms

iubenda_cs.js

iubenda_cs.js

49 ms

new_nav.css

new_nav.css

409 ms

section_drawer.css

section_drawer.css

473 ms

section_images.css

section_images.css

473 ms

embed.js

embed.js

474 ms

instafeed.css

instafeed.css

655 ms

new_newsletter.css

new_newsletter.css

654 ms

new_footer.css

new_footer.css

679 ms

manifest.js

manifest.js

677 ms

vendor.js

vendor.js

853 ms

app.js

app.js

1034 ms

css

css

43 ms

mna1659517200000a1438.js

mna1659517200000a1438.js

603 ms

fbevents.js

fbevents.js

220 ms

bat.js

bat.js

224 ms

gtm.js

gtm.js

113 ms

analytics.js

analytics.js

183 ms

core.js

core.js

182 ms

hotjar-428237.js

hotjar-428237.js

400 ms

destination

destination

169 ms

js

js

160 ms

photo-1707249733200-cb5803d7d600

photo-1707249733200-cb5803d7d600

344 ms

menu_w.png

menu_w.png

1031 ms

banner_man.jpg

banner_man.jpg

539 ms

menu-heritage.jpg

menu-heritage.jpg

726 ms

banner_woman.jpg

banner_woman.jpg

819 ms

banner_heritage.jpg

banner_heritage.jpg

811 ms

company.gif

company.gif

2014 ms

CircularStd-Light.otf

CircularStd-Light.otf

879 ms

CircularStd-Book.otf

CircularStd-Book.otf

896 ms

collect

collect

184 ms

embed-272e13b221e78db10467.js

embed-272e13b221e78db10467.js

152 ms

343001990.js

343001990.js

113 ms

collect

collect

79 ms

modules.4d9dd1518dc89987e57a.js

modules.4d9dd1518dc89987e57a.js

62 ms

343001990

343001990

98 ms

ga-audiences

ga-audiences

718 ms

clarity.js

clarity.js

23 ms

loader.min.js

loader.min.js

154 ms

c.gif

c.gif

8 ms

Accessibility Review

pollini.com accessibility score

73

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

pollini.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

pollini.com

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