8.5 sec in total
546 ms
7.5 sec
495 ms
Visit pitu.com.br now to see the best up-to-date Pitu content for Brazil and also check out these interesting facts you probably never knew about pitu.com.br
Visit pitu.com.brWe analyzed Pitu.com.br page load time and found that the first response time was 546 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pitu.com.br performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value26.7 s
0/100
25%
Value7.5 s
27/100
10%
Value110 ms
98/100
30%
Value0.851
4/100
15%
Value6.9 s
53/100
10%
546 ms
1294 ms
566 ms
699 ms
283 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 42% of them (63 requests) were addressed to the original Pitu.com.br, 26% (39 requests) were made to Facebook.com and 22% (33 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Pitu.com.br.
Page size can be reduced by 528.0 kB (11%)
4.8 MB
4.3 MB
In fact, the total size of Pitu.com.br main page is 4.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 61.3 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 8.8 kB, which is 12% 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 61.3 kB or 87% of the original size.
Potential reduce by 143.2 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. Pitu images are well optimized though.
Potential reduce by 276.0 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 276.0 kB or 66% of the original size.
Potential reduce by 47.5 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. Pitu.com.br needs all CSS files to be minified and compressed as it can save up to 47.5 kB or 85% of the original size.
Number of requests can be reduced by 46 (31%)
149
103
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pitu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and as a result speed up the page load time.
pitu.com.br
546 ms
www.pitu.com.br
1294 ms
screen.css
566 ms
jquery-1.8.2.min.js
699 ms
cookie.jquery.js
283 ms
plugins.js
571 ms
TweenLite.min.js
8 ms
CSSPlugin.min.js
12 ms
util.js
572 ms
all.js
55 ms
pattern.png
172 ms
sprite-language.png
172 ms
logo-pitu.png
299 ms
ico-loja.png
306 ms
fb.png
303 ms
tw.png
2805 ms
bt-search.png
2804 ms
destaque-vitoriosa.png
2853 ms
titulo-vitoriosa.png
2812 ms
bg-loja.jpg
2834 ms
destaque-caipirinha.png
2849 ms
sprite-bts.png
2810 ms
ft-destaque-products.png
2808 ms
bt-mais.png
2831 ms
ft-destaque-stuff.png
2832 ms
ft-destaque-drinks.png
2848 ms
01122014190911_823385264.png
2855 ms
01122014190639_565285074.png
2856 ms
01122014190737_2093877992.png
2852 ms
26122014170517_1660562300.png
2852 ms
04122014153930_819071772.png
2859 ms
01122014191000_1737817157.png
2863 ms
04122014154148_1788534623.png
2860 ms
05122014110015_2001283368.png
2864 ms
ipego.png
2855 ms
13082013095606_927475537.png
2865 ms
13082013095645_351308726.png
2864 ms
13082013095724_1994852370.png
2865 ms
13082013095748_1579407077.png
2867 ms
13082013095839_1585344738.png
2866 ms
13082013095924_665714999.png
2867 ms
13082013100010_465281356.png
2868 ms
widgets.js
78 ms
13082013095518_1533203778.png
2843 ms
141 ms
xd_arbiter.php
57 ms
xd_arbiter.php
73 ms
gotham_light-webfont.woff
2707 ms
gotham_bold-webfont.woff
2708 ms
gotham_ultra_italic-webfont.woff
2615 ms
gotham_light_italic-webfont.woff
2614 ms
gotham_ultra-webfont.woff
2581 ms
gotham-book-webfont.woff
2577 ms
gotham_book_italic-webfont.woff
2576 ms
ga.js
2377 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
2285 ms
13082013100055_341780446.png
2328 ms
ping
2245 ms
ga.js
2203 ms
widgets.js
2200 ms
all.js
2205 ms
TweenLite.min.js
656 ms
CSSPlugin.min.js
657 ms
13082013100125_922631952.png
803 ms
thumb-13082013095606_927475537.png
290 ms
thumb-13082013095645_351308726.png
240 ms
thumb-13082013095724_1994852370.png
344 ms
thumb-13082013095748_1579407077.png
337 ms
like.php
228 ms
like.php
272 ms
like.php
316 ms
like.php
281 ms
like.php
296 ms
like.php
302 ms
like.php
286 ms
thumb-13082013095839_1585344738.png
331 ms
thumb-13082013095924_665714999.png
364 ms
like.php
338 ms
like.php
360 ms
like.php
350 ms
like.php
380 ms
like.php
387 ms
like.php
368 ms
like.php
502 ms
like.php
610 ms
like.php
606 ms
like.php
598 ms
like.php
602 ms
thumb-13082013100010_465281356.png
496 ms
thumb-13082013095518_1533203778.png
594 ms
thumb-13082013100055_341780446.png
602 ms
thumb-13082013100125_922631952.png
600 ms
marca.png
595 ms
bg-idade.png
750 ms
bg-idade-produtos-blur.png
1477 ms
bg-idade-produtos.png
1771 ms
__utm.gif
100 ms
__utm.gif
49 ms
jJhqmvSAXq3.js
46 ms
LVx-xkvaJ0b.png
41 ms
jJhqmvSAXq3.js
53 ms
jJhqmvSAXq3.js
264 ms
jJhqmvSAXq3.js
264 ms
jJhqmvSAXq3.js
265 ms
jJhqmvSAXq3.js
255 ms
jJhqmvSAXq3.js
250 ms
jJhqmvSAXq3.js
246 ms
jJhqmvSAXq3.js
250 ms
jJhqmvSAXq3.js
246 ms
jJhqmvSAXq3.js
150 ms
jJhqmvSAXq3.js
134 ms
jJhqmvSAXq3.js
120 ms
jJhqmvSAXq3.js
159 ms
jot.html
59 ms
ping
55 ms
like.php
82 ms
like.php
133 ms
like.php
115 ms
like.php
95 ms
like.php
103 ms
like.php
117 ms
like.php
102 ms
like.php
108 ms
like.php
118 ms
like.php
242 ms
like.php
124 ms
like.php
139 ms
jJhqmvSAXq3.js
59 ms
like.php
174 ms
like.php
182 ms
like.php
189 ms
like.php
253 ms
like.php
252 ms
like.php
273 ms
jJhqmvSAXq3.js
40 ms
jJhqmvSAXq3.js
39 ms
jJhqmvSAXq3.js
32 ms
jJhqmvSAXq3.js
122 ms
jJhqmvSAXq3.js
117 ms
jJhqmvSAXq3.js
144 ms
jJhqmvSAXq3.js
113 ms
jJhqmvSAXq3.js
186 ms
jJhqmvSAXq3.js
178 ms
jJhqmvSAXq3.js
178 ms
jJhqmvSAXq3.js
169 ms
jJhqmvSAXq3.js
166 ms
jJhqmvSAXq3.js
162 ms
jJhqmvSAXq3.js
113 ms
jJhqmvSAXq3.js
103 ms
jJhqmvSAXq3.js
86 ms
jJhqmvSAXq3.js
83 ms
pitu.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pitu.com.br 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pitu.com.br SEO score
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 doesn't use legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pitu.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Pitu.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.
pitu.com.br
Open Graph description is not detected on the main page of Pitu. 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: