Tools & Wizards About Us
pipilando.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pipilando.com.br

Pipilando

Page Load Speed

3.8 sec in total

First Response

281 ms

Resources Loaded

2.9 sec

Page Rendered

635 ms

pipilando.com.br screenshot

About Website

Visit pipilando.com.br now to see the best up-to-date Pipilando content and also check out these interesting facts you probably never knew about pipilando.com.br

Blog com contos infantis, infanto-juvenis e diversas histórias, além de textos sobre séries, livros e filmes.

Visit pipilando.com.br

Key Findings

We analyzed Pipilando.com.br page load time and found that the first response time was 281 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

pipilando.com.br performance score

0

Network Requests Diagram

pipilando.com.br

281 ms

www.pipilando.com.br

345 ms

3375562265-css_bundle_v2.css

72 ms

gsearch.css

32 ms

authorization.css

111 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Pipilando.com.br, 19% (20 requests) were made to Um.simpli.fi and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (835 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 545.4 kB (26%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pipilando.com.br main page is 2.1 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 62.9 kB

  • Original 81.0 kB
  • After minification 80.5 kB
  • After compression 18.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 62.9 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 87.7 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. Pipilando images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 151.5 kB

  • Original 343.0 kB
  • After minification 340.8 kB
  • After compression 191.4 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 151.5 kB or 44% of the original size.

CSS Optimization

-81%

Potential reduce by 243.2 kB

  • Original 298.8 kB
  • After minification 283.2 kB
  • After compression 55.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. Pipilando.com.br needs all CSS files to be minified and compressed as it can save up to 243.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (78%)

Requests Now

81

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pipilando. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pipilando.com.br

pipilando.com.br

281 ms

www.pipilando.com.br

www.pipilando.com.br

345 ms

3375562265-css_bundle_v2.css

3375562265-css_bundle_v2.css

72 ms

gsearch.css

gsearch.css

32 ms

authorization.css

authorization.css

111 ms

small.js

small.js

158 ms

3226477086-widgets.js

3226477086-widgets.js

71 ms

plusone.js

plusone.js

97 ms

jsapi

jsapi

54 ms

back.png

back.png

108 ms

gradients_light.png

gradients_light.png

32 ms

icon18_wrench_allbkg.png

icon18_wrench_allbkg.png

30 ms

i_oXD2vxqLU

i_oXD2vxqLU

112 ms

curta.png

curta.png

101 ms

banner.png

banner.png

81 ms

Sem%2BTi%25CC%2581tulo-1.png

Sem%2BTi%25CC%2581tulo-1.png

91 ms

fear.png

fear.png

82 ms

procrastinacao%2Bda%2Bvida.png

procrastinacao%2Bda%2Bvida.png

83 ms

blogger_index.js

blogger_index.js

74 ms

60 ms

71 ms

ga.js

ga.js

59 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

76 ms

clear.gif

clear.gif

72 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

83 ms

www-embed-player.js

www-embed-player.js

144 ms

base.js

base.js

184 ms

dpx.js

dpx.js

53 ms

__utm.gif

__utm.gif

35 ms

count.js

count.js

89 ms

tc.js

tc.js

53 ms

likebox.php

likebox.php

428 ms

tpid=1EE7044565ABEE5627035F360203DEEC

tpid=1EE7044565ABEE5627035F360203DEEC

31 ms

default+pt_BR.css

default+pt_BR.css

7 ms

default+pt_BR.I.js

default+pt_BR.I.js

31 ms

p

p

11 ms

dpx

dpx

65 ms

p

p

252 ms

count-data.js

count-data.js

222 ms

async-ads.js

async-ads.js

175 ms

small-logo.png

small-logo.png

46 ms

aol

aol

37 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

87 ms

ad_status.js

ad_status.js

149 ms

mapuser

mapuser

14 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

38 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

41 ms

v2

v2

89 ms

y_match

y_match

4 ms

dpx

dpx

3 ms

match_redirect

match_redirect

4 ms

29931

29931

22 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

282 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

350 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

487 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

617 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

509 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

510 ms

xrefid.xgi

xrefid.xgi

9 ms

ca.png

ca.png

167 ms

match_redirect

match_redirect

4 ms

tpid=C629559E65ABEE56D223DFAD025D1653

tpid=C629559E65ABEE56D223DFAD025D1653

4 ms

lr

lr

5 ms

52154.gif

52154.gif

15 ms

lr.gif

lr.gif

6 ms

match_redirect

match_redirect

4 ms

sync

sync

40 ms

match_redirect

match_redirect

5 ms

C629559E65ABEE56D223DFAD025D1653

C629559E65ABEE56D223DFAD025D1653

34 ms

match_redirect

match_redirect

4 ms

ProfilesEngineServlet

ProfilesEngineServlet

9 ms

ProfilesEngineServlet

ProfilesEngineServlet

18 ms

tap.php

tap.php

7 ms

exelate

exelate

4 ms

138 ms

17 ms

18 ms

spotx_match

spotx_match

4 ms

fb_match

fb_match

4 ms

u.php

u.php

57 ms

an

an

5 ms

lj_match

lj_match

5 ms

merge

merge

6 ms

cw_match

cw_match

4 ms

rtset

rtset

19 ms

rb_match

rb_match

4 ms

tap.php

tap.php

6 ms

ox_match

ox_match

9 ms

pm_match

pm_match

9 ms

Pug

Pug

119 ms

485158_529667727091990_1995104580_n.png

485158_529667727091990_1995104580_n.png

452 ms

150417_529667317092031_530625236_n.png

150417_529667317092031_530625236_n.png

601 ms

12688253_1005567319529581_3914202543062525311_n.jpg

12688253_1005567319529581_3914202543062525311_n.jpg

715 ms

12743668_832215950239455_958972091187312975_n.jpg

12743668_832215950239455_958972091187312975_n.jpg

835 ms

11391493_636657666465304_8973329841107246978_n.jpg

11391493_636657666465304_8973329841107246978_n.jpg

654 ms

12310487_416813138509223_549749292829618_n.jpg

12310487_416813138509223_549749292829618_n.jpg

747 ms

1934777_628616240630260_8701559195915507031_n.jpg

1934777_628616240630260_8701559195915507031_n.jpg

710 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

157 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

159 ms

pixel

pixel

23 ms

g_match

g_match

4 ms

match_redirect

match_redirect

4 ms

pixel

pixel

33 ms

aa_px

aa_px

7 ms

sd

sd

78 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

70 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

72 ms

SEO Factors

pipilando.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pipilando.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 Pipilando.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.

Social Sharing Optimization

pipilando.com.br

Open Graph description is not detected on the main page of Pipilando. 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: