4.6 sec in total
337 ms
3.6 sec
627 ms
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
Italian shoes, bags and accessories on Pollini store. Collection for men and women. Shipping wordwide and free Return Italian shoes, bags and accessories on Pollini store. Collection for men and women...
Visit pollini.comWe analyzed Pollini.com page load time and found that the first response time was 337 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pollini.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value19.4 s
0/100
25%
Value14.1 s
1/100
10%
Value19,570 ms
0/100
30%
Value0.522
15/100
15%
Value30.4 s
0/100
10%
337 ms
1787 ms
215 ms
200 ms
201 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 64% of them (38 requests) were addressed to the original Pollini.com, 5% (3 requests) were made to Staticxx.facebook.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Pollini.com.
Page size can be reduced by 400.2 kB (34%)
1.2 MB
773.8 kB
In fact, the total size of Pollini.com main page is 1.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. 55% of websites need less resources to load. Images take 656.3 kB which makes up the majority of the site volume.
Potential reduce by 75.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. This page needs HTML code to be minified as it can gain 19.7 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 75.1 kB or 81% of the original size.
Potential reduce by 3.0 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. POLLINI images are well optimized though.
Potential reduce by 61.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 61.5 kB or 52% of the original size.
Potential reduce by 260.6 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 needs all CSS files to be minified and compressed as it can save up to 260.6 kB or 85% of the original size.
Number of requests can be reduced by 32 (62%)
52
20
The browser has sent 52 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 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pollini.com
337 ms
www.pollini.com
1787 ms
panZoomer.css
215 ms
jquery.gritter.css
200 ms
simple_thumbs.css
201 ms
jquery.fancybox-1.3.4.css
202 ms
help.css
202 ms
jquery.jqzoom.css
203 ms
venobox.css
301 ms
styles_1456752744-blessed1.css
507 ms
styles_1456752744.css
299 ms
piwik.js
402 ms
piwik_request.js
398 ms
conversion.js
18 ms
jquery.min.js
30 ms
jquery.fancybox-1.3.4.pack.js
303 ms
jquery.jcarousel.min.js
302 ms
venobox.min.js
307 ms
jquery-ui.js
10 ms
jquery.history.js
396 ms
jquery.mousewheel.js
396 ms
jquery.gritter.min.js
398 ms
jquery.validate.js
402 ms
jquery.scrollIntoView.min.js
407 ms
jquery.scrollTo.js
496 ms
help.js
495 ms
jquery.jqzoom-core.js
498 ms
jquery.isotope.min.js
540 ms
venocarousel.js
540 ms
scripts_1456333794.js
33 ms
logo.jpg
107 ms
logo-mini.jpg
108 ms
return-instruct_en.gif
107 ms
freccione.jpg
107 ms
gtm.js
89 ms
80 ms
62918.jpg
853 ms
glyphicons-halflings.png
188 ms
58358.jpg
576 ms
60814.jpg
379 ms
gender-uomo.jpg
572 ms
edelsans_regular-webfont.woff
167 ms
fontawesome-webfont.woff
424 ms
century_schoolbook_italic-webfont.woff
349 ms
helveticaneue-lightcond-webfont.woff
445 ms
all.js
224 ms
123 ms
zanox.js
262 ms
analytics.js
77 ms
520 ms
ec.js
46 ms
collect
29 ms
collect
63 ms
102 ms
xd_arbiter.php
151 ms
xd_arbiter.php
279 ms
3F328B2F3F64619CB82E
220 ms
pixel
18 ms
xd_arbiter.php
83 ms
pollini.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
pollini.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pollini.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
EN
EN
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.
pollini.com
Open Graph description is not detected on the main page of POLLINI. 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: