2.4 sec in total
367 ms
1.3 sec
713 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 367 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
pirelli.it performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value4.0 s
50/100
25%
Value11.5 s
5/100
10%
Value5,140 ms
0/100
30%
Value0.116
85/100
15%
Value22.6 s
1/100
10%
367 ms
261 ms
19 ms
22 ms
110 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pirelli.it, 78% (32 requests) were made to Pirelli.com and 20% (8 requests) were made to Tyre-assets.pirelli.com. The less responsive or slowest element that took the longest time to load (670 ms) relates to the external source Pirelli.com.
Page size can be reduced by 394.7 kB (82%)
482.3 kB
87.7 kB
In fact, the total size of Pirelli.it main page is 482.3 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. 70% of websites need less resources to load. HTML takes 448.7 kB which makes up the majority of the site volume.
Potential reduce by 369.4 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 369.4 kB or 82% of the original size.
Potential reduce by 14.1 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 14.1 kB or 71% of the original size.
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 82% of the original size.
Number of requests can be reduced by 29 (94%)
31
2
The browser has sent 31 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 22 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pirelli.it
367 ms
home
261 ms
cookies-gtm.min.js
19 ms
cookies-bar.min.css
22 ms
da83b2ff5344eb2c.css
110 ms
4039699ce0e30631.css
104 ms
eaad78398343595f.css
97 ms
b25f2732f99f57bb.css
102 ms
08271df1cc003302.css
99 ms
c7085edee1d674a2.css
242 ms
d2c0b7dcb7455e81.css
173 ms
445a5fabb9d3c922.css
200 ms
polyfills-c67a75d1b6f99dc8.js
181 ms
webpack-f656e26e7b4fe19d.js
321 ms
framework-09f3afa64952aba4.js
330 ms
main-13f55050fd1c2655.js
394 ms
_app-5d496b2185909040.js
670 ms
94726e6d-7f2b3b7a2ac48163.js
419 ms
fb7d5399-43f23ad5336d0ca0.js
391 ms
7790-1d1da3630ebfa319.js
417 ms
6137-4cbf55a942ed5ca3.js
419 ms
6269-b2969666f2b1d6f9.js
532 ms
3601-5e89fbb970e00ccc.js
529 ms
9778-b49a16f18bc349db.js
528 ms
6258-8f8fe7a4eab73ce6.js
530 ms
9676-57904ea05117091a.js
530 ms
5446-e93b0f206cc3fb0c.js
582 ms
5839-3fa674d75066b228.js
581 ms
5502-d5ccb886898acdba.js
588 ms
1984-42e862af1e6cf227.js
583 ms
genericPage-882d9f9db350181a.js
603 ms
_buildManifest.js
660 ms
_ssgManifest.js
657 ms
GothamW05-Medium.woff
139 ms
GothamW05-Book.woff
180 ms
GothamW05-Ultra.woff
213 ms
GothamW05-Light.woff
213 ms
GothamW05-ExtraLight.woff
213 ms
GothamW05-Thin.woff
211 ms
GothamW05-Bold.woff
212 ms
GothamW05-Black.woff
213 ms
pirelli.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
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
Tap targets are not sized appropriately
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: