3.1 sec in total
355 ms
2.3 sec
459 ms
Click here to check amazing Pirelli content for Italy. Otherwise, check out these important facts you probably never knew about pirelli.it
Tradizione e innovazione Pirelli al servizio degli automobilisti per una guida più sicura e prestazioni sempre più elevate.
Visit pirelli.itWe analyzed Pirelli.it page load time and found that the first response time was 355 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pirelli.it performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value7.4 s
4/100
25%
Value8.5 s
18/100
10%
Value2,310 ms
5/100
30%
Value0
100/100
15%
Value13.1 s
12/100
10%
355 ms
114 ms
390 ms
195 ms
17 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pirelli.it, 71% (30 requests) were made to Pirelli.com and 24% (10 requests) were made to D3nv2arudvw7ln.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Pirelli.com.
Page size can be reduced by 169.0 kB (31%)
536.9 kB
367.9 kB
In fact, the total size of Pirelli.it main page is 536.9 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. 55% of websites need less resources to load. Images take 368.7 kB which makes up the majority of the site volume.
Potential reduce by 127.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. 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 127.0 kB or 83% of the original size.
Potential reduce by 30.8 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. Pirelli images are well optimized though.
Potential reduce by 11.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. Pirelli.it needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 77% of the original size.
Number of requests can be reduced by 25 (86%)
29
4
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pirelli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pirelli.it
355 ms
index
114 ms
index
390 ms
home
195 ms
cookies-bar.min.css
17 ms
dynamic-commons.min.css
26 ms
f9c8dbce04841382.css
313 ms
af16e0fa0c206764.css
343 ms
0627e4fdce74ae73.css
237 ms
1a4803d9fb2aa0d6.css
225 ms
b85f7ff1031ba7dc.css
232 ms
e77b3b86d58857ad.css
411 ms
polyfills-c67a75d1b6f99dc8.js
523 ms
webpack-da945e3d49a508bf.js
543 ms
framework-bb5c596eafb42b22.js
608 ms
main-fe0cff67096da68d.js
663 ms
_app-44b1095247d26fd9.js
823 ms
7d0bf13e-8544b9e1d9903f3e.js
570 ms
324-63d9f2fc6f8463c8.js
628 ms
386-116c521c4925fa9e.js
806 ms
539-e73f3292e75bc138.js
646 ms
584-54dd378765350388.js
802 ms
26-ba4dd1cd4a755ec4.js
853 ms
275-64c227665164a73f.js
734 ms
69-14fc224226415e0d.js
743 ms
558-2f642153e9e0db62.js
1008 ms
190-ec9b013a8a87db65.js
851 ms
genericPage-d870f9d88446a6c1.js
1078 ms
_buildManifest.js
885 ms
_ssgManifest.js
1035 ms
image
1255 ms
sprite-country.png
128 ms
GothamW05-Book.woff
28 ms
GothamW05-Medium.woff
58 ms
GothamW05-Light.woff
51 ms
GothamW05-ExtraLight.woff
51 ms
GothamW05-Thin.woff
50 ms
GothamW05-Bold.woff
57 ms
GothamW05-Black.woff
88 ms
GothamW05-Ultra.woff
59 ms
icomoon.ttf
58 ms
_error-effe22be6ff34abe.js
76 ms
pirelli.it accessibility score
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
Form elements do not have associated labels
pirelli.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pirelli.it SEO score
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
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pirelli.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 Pirelli.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.
pirelli.it
Open Graph data is detected on the main page of Pirelli. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: