3.6 sec in total
219 ms
3.1 sec
297 ms
Welcome to pirelli.com.br homepage info - get ready to check Pirelli best content right away, or after learning these important things about pirelli.com.br
A Pirelli oferece uma grande variedade de pneus para carros, SUVs e vans com qualidade confiável. Descubra agora!
Visit pirelli.com.brWe analyzed Pirelli.com.br page load time and found that the first response time was 219 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pirelli.com.br performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value3.5 s
65/100
25%
Value8.4 s
18/100
10%
Value1,410 ms
15/100
30%
Value0.002
100/100
15%
Value11.6 s
18/100
10%
219 ms
734 ms
107 ms
323 ms
271 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pirelli.com.br, 84% (46 requests) were made to Pirelli.com and 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Pirelli.com.
Page size can be reduced by 682.6 kB (39%)
1.7 MB
1.0 MB
In fact, the total size of Pirelli.com.br main page is 1.7 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 24% 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 37.4 kB or 82% of the original size.
Potential reduce by 135.5 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. Obviously, Pirelli needs image optimization as it can save up to 135.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 27 B
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.
Potential reduce by 509.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. Pirelli.com.br needs all CSS files to be minified and compressed as it can save up to 509.6 kB or 92% of the original size.
Number of requests can be reduced by 11 (31%)
36
25
The browser has sent 36 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 12 to 1 for CSS and as a result speed up the page load time.
pirelli.com.br
219 ms
index
734 ms
provide.js
107 ms
modernizr-latest.min.js
323 ms
fonts.css
271 ms
webfonts.css
216 ms
common.css
218 ms
chinese.css
214 ms
tools.css
222 ms
header.css
318 ms
footer.css
349 ms
css.php
424 ms
require.js
421 ms
46AFC3FAEBD89E12D.css
105 ms
myPirelliSprite.css
116 ms
gtm.js
71 ms
pirelli-logo-section.gif
125 ms
pirelli-logo-section-mobile.gif
125 ms
pirelli-logo-section-ar.gif
125 ms
pirelli-logo-section-mobile-ar.gif
124 ms
pirelli-logo-splash.gif
124 ms
pirelli-logo-splash-ar.gif
125 ms
index.php
235 ms
index.php
230 ms
index.php
454 ms
index.php
235 ms
index.php
230 ms
index.php
232 ms
country-selector-tpl.html
347 ms
index.php
1443 ms
sprite-common.png
806 ms
Gotham-Book.woff
472 ms
Gotham-Bold.woff
575 ms
Gotham-Light.woff
678 ms
Gotham-Medium.woff
592 ms
dc.js
39 ms
conversion_async.js
16 ms
config.js
565 ms
51 ms
__utm.gif
14 ms
ga-audiences
34 ms
48 ms
webfonts.css
423 ms
common.css
559 ms
normalize.css
435 ms
cms.spr.css
517 ms
main.css
523 ms
bootstrap.css
543 ms
jquery.jscrollpane.css
594 ms
common.css
625 ms
cms.css
632 ms
country-selector.css
648 ms
jquery-1.11.1.min.js
873 ms
country-selector.js
693 ms
libs.min.js
922 ms
pirelli.com.br 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.com.br 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.com.br 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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pirelli.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pirelli.com.br 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.com.br
Open Graph description is not detected on the main page of Pirelli. 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: