6.1 sec in total
384 ms
5.2 sec
477 ms
Welcome to pian.com.br homepage info - get ready to check Pian best content right away, or after learning these important things about pian.com.br
Rações Premium para Cães e Gatos.
Visit pian.com.brWe analyzed Pian.com.br page load time and found that the first response time was 384 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pian.com.br performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.3 s
21/100
25%
Value13.5 s
2/100
10%
Value570 ms
52/100
30%
Value0.63
9/100
15%
Value51.1 s
0/100
10%
384 ms
64 ms
105 ms
74 ms
77 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 77% of them (114 requests) were addressed to the original Pian.com.br, 7% (10 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Facebook.com.
Page size can be reduced by 1.2 MB (20%)
6.2 MB
5.0 MB
In fact, the total size of Pian.com.br main page is 6.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. 80% 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.5 MB which makes up the majority of the site volume.
Potential reduce by 51.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. 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 51.3 kB or 81% of the original size.
Potential reduce by 31.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. Pian images are well optimized though.
Potential reduce by 701.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 701.5 kB or 65% of the original size.
Potential reduce by 465.0 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. Pian.com.br needs all CSS files to be minified and compressed as it can save up to 465.0 kB or 86% of the original size.
Number of requests can be reduced by 105 (74%)
141
36
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
pian.com.br
384 ms
wp-emoji-release.min.js
64 ms
fblb.css
105 ms
lionbars.css
74 ms
toolbar.css
77 ms
style.css
169 ms
layerslider.css
87 ms
styles.css
144 ms
jquery.qtip.min.css
112 ms
default.css
148 ms
rounded.css
172 ms
prettyPhoto.css
139 ms
jquery.fancybox.css
149 ms
jquery.fancybox-buttons.css
182 ms
jquery.fancybox-thumbs.css
188 ms
jquery.fancygallery.css
180 ms
settings.css
216 ms
dynamic-captions.css
210 ms
static-captions.css
211 ms
bootstrap.css
313 ms
style.css
329 ms
responsive.css
230 ms
flexslider.css
253 ms
jquery.bxslider.css
254 ms
magnific-popup.css
250 ms
font-awesome.min.css
275 ms
jplayer.pink.flag.css
292 ms
dynamic-styles.php
940 ms
css
25 ms
jquery.js
420 ms
jquery-migrate.min.js
333 ms
userscripts.js
335 ms
jquery.lionbars.0.3.min.js
347 ms
flags.js
352 ms
toolbar.js
362 ms
load-toolbar.js
365 ms
layerslider.kreaturamedia.jquery-min.js
385 ms
element.js
33 ms
js_composer_front.css
386 ms
isotope.css
346 ms
jquery-easing-1.3.js
370 ms
iphorm.js
350 ms
swfupload.js
392 ms
swfobject.js
346 ms
swfupload.swfobject.js
334 ms
swfupload.queue.js
327 ms
jquery.prettyPhoto.js
334 ms
jquery.fancybox.pack.js
353 ms
jquery.fancybox-media.js
499 ms
jquery.fancybox-buttons.js
345 ms
jquery.fancybox-thumbs.js
339 ms
jquery.fancygallery.min.js
361 ms
jquery.themepunch.plugins.min.js
428 ms
jquery.themepunch.revolution.min.js
392 ms
modernizr.js
344 ms
bootstrap.js
371 ms
jquery.carouFredSel-6.2.0-packed.js
360 ms
comment-reply.min.js
431 ms
jquery.iphorm.js
375 ms
jquery.form.min.js
390 ms
jquery.smooth-scroll.min.js
372 ms
jquery.qtip.min.js
394 ms
jquery.uniform.js
431 ms
jquery.infieldlabel.min.js
352 ms
rounded.js
367 ms
jquery.isotope.min.js
392 ms
jquery.jplayer.min.js
410 ms
jquery.flexslider.js
373 ms
jquery.bxslider.min.js
376 ms
retina-1.1.0.min.js
405 ms
jquery.magnific-popup.min.js
385 ms
raphael-min.js
419 ms
DevSolutionSkill.min.js
392 ms
jflickrfeed.min.js
407 ms
jquery.validate.min.js
387 ms
script.js
390 ms
js_composer_front.js
409 ms
core.min.js
400 ms
widget.min.js
389 ms
accordion.min.js
393 ms
brickwall.png
660 ms
pian.png
119 ms
BANNER_01.jpg
331 ms
BANNER_04.jpg
333 ms
BANNER_02.jpg
332 ms
BANNER_03.jpg
331 ms
05.jpg
337 ms
BANNER_08.jpg
338 ms
BANNER_10.jpg
336 ms
BANNER_12.jpg
418 ms
BANNER_11.jpg
417 ms
BANNER_05.jpg
415 ms
BANNER_09.jpg
564 ms
BANNER_07.jpg
429 ms
ProdutosEmDestaque2.jpg
456 ms
banho-400x179.jpg
411 ms
old-400x179.jpg
410 ms
noticia-1-400x179.jpg
435 ms
FOOTER.jpg
583 ms
flags20.png
446 ms
analytics.js
8 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
40 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
40 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
41 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
41 ms
fontawesome-webfont.woff
469 ms
translateelement.css
55 ms
main.js
244 ms
collect
18 ms
flags.png
194 ms
timer.png
234 ms
loader.gif
234 ms
likebox.php
1848 ms
element_main.js
35 ms
translate_24dp.png
27 ms
l
42 ms
googlelogo_color_42x16dp.png
19 ms
large_left.png
65 ms
large_right.png
58 ms
kyEKgjk51ZE.css
285 ms
xgj7bXhJNEH.css
353 ms
q68gy-v_YMF.js
487 ms
FJmpeSpHpjS.js
621 ms
0wM5s1Khldu.js
517 ms
1bNoFZUdlYZ.js
516 ms
10590422_328626020642030_5575385366278841959_n.jpg
464 ms
1920149_328622807309018_7038127483114008026_n.jpg
591 ms
1001086_1019396564794485_1800266074403909982_n.jpg
732 ms
11986372_1456930931304167_2039174652056800678_n.jpg
732 ms
1549389_659658830840184_3207710613733000493_n.jpg
674 ms
12742578_555204041320549_4168553729656056475_n.jpg
708 ms
12794534_498588130333841_6831070226810294272_n.jpg
874 ms
12744289_841557705954861_8065865878418179253_n.jpg
744 ms
12552974_921962684583472_7384089496134888240_n.jpg
800 ms
wL6VQj7Ab77.png
80 ms
s7jcwEQH7Sx.png
80 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
72 ms
file-upload-tick.png
56 ms
captcha-refresh-icon.png
67 ms
default-loading.gif
48 ms
error.png
46 ms
success.png
40 ms
input-active-bg-rep.png
48 ms
file-upload-progress-area.png
78 ms
file-progress-bar-bg.png
98 ms
file-close.png
85 ms
button-active-bg-rep.png
86 ms
pian.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
pian.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pian.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
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pian.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Pian.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.
pian.com.br
Open Graph data is detected on the main page of Pian. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: