Tools & Wizards About Us
carolina-da-rocha-resende.catalogo.med.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

carolina-da-rocha-resende.catalogo.med.br

Buscar: carolina da rocha resende | CatalogoMed

Page Load Speed

5.4 sec in total

First Response

978 ms

Resources Loaded

4.2 sec

Page Rendered

192 ms

carolina-da-rocha-resende.catalogo.med.br screenshot

About Website

Welcome to carolina-da-rocha-resende.catalogo.med.br homepage info - get ready to check Carolina Da Rocha Resende Catalogo best content for Brazil right away, or after learning these important things about carolina-da-rocha-resende.catalogo.med.br

Resultados da pesquisa carolina da rocha resende

Visit carolina-da-rocha-resende.catalogo.med.br

Key Findings

We analyzed Carolina-da-rocha-resende.catalogo.med.br page load time and found that the first response time was 978 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

carolina-da-rocha-resende.catalogo.med.br performance score

0

Network Requests Diagram

idalcy+pinheiro+da+silva+pinto+1407974.htm

978 ms

Catalogo_Desktop.css

193 ms

Catalogo_Desktop_ptBR.js

574 ms

platform.js

60 ms

male.png

130 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Carolina-da-rocha-resende.catalogo.med.br, 13% (13 requests) were made to Apis.google.com and 12% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (978 ms) relates to the external source Catalogo.med.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (66%)

Content Size

1.5 MB

After Optimization

516.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Carolina-da-rocha-resende.catalogo.med.br main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 42.6 kB

  • Original 55.6 kB
  • After minification 55.4 kB
  • After compression 13.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 42.6 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 8.9 kB

  • Original 120.5 kB
  • After minification 111.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. Carolina Da Rocha Resende Catalogo images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 845.7 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 370.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 845.7 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 108.7 kB

  • Original 130.3 kB
  • After minification 130.3 kB
  • After compression 21.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. Carolina-da-rocha-resende.catalogo.med.br needs all CSS files to be minified and compressed as it can save up to 108.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (60%)

Requests Now

97

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carolina Da Rocha Resende Catalogo. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

idalcy+pinheiro+da+silva+pinto+1407974.htm

idalcy+pinheiro+da+silva+pinto+1407974.htm

978 ms

Catalogo_Desktop.css

Catalogo_Desktop.css

193 ms

Catalogo_Desktop_ptBR.js

Catalogo_Desktop_ptBR.js

574 ms

platform.js

platform.js

60 ms

male.png

male.png

130 ms

share-24-c.png

share-24-c.png

132 ms

message-24-c.png

message-24-c.png

133 ms

blank.png

blank.png

133 ms

star-24-c.png

star-24-c.png

208 ms

logo_small.png

logo_small.png

209 ms

warn.gif

warn.gif

208 ms

search.gif

search.gif

208 ms

like.php

like.php

61 ms

likebox.php

likebox.php

69 ms

L70CG02Crze.js

L70CG02Crze.js

485 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

569 ms

xYm_UD1pmAz.css

xYm_UD1pmAz.css

688 ms

TGpOWuX6Pv8.css

TGpOWuX6Pv8.css

779 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

828 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

949 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

775 ms

TTCre3391I0.js

TTCre3391I0.js

774 ms

bg_results.png

bg_results.png

70 ms

simple_brasil.png

simple_brasil.png

131 ms

frame.png

frame.png

71 ms

favorite_disabled_24.png

favorite_disabled_24.png

72 ms

star-off.png

star-off.png

70 ms

frame_logo_small.png

frame_logo_small.png

136 ms

windows.png

windows.png

139 ms

android.png

android.png

137 ms

apple.png

apple.png

146 ms

enderecos.png

enderecos.png

200 ms

telefone.png

telefone.png

208 ms

convenios.png

convenios.png

206 ms

pont_2.gif

pont_2.gif

206 ms

open.gif

open.gif

212 ms

close.gif

close.gif

266 ms

bg_footer.png

bg_footer.png

274 ms

piwik.js

piwik.js

392 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

67 ms

__utm.gif

__utm.gif

89 ms

__utm.gif

__utm.gif

70 ms

__utm.gif

__utm.gif

90 ms

widgets.js

widgets.js

87 ms

all.js

all.js

401 ms

facebook-48.png

facebook-48.png

136 ms

blank.png

blank.png

216 ms

mac.js

mac.js

360 ms

google-48.png

google-48.png

111 ms

twitter-48.png

twitter-48.png

119 ms

linkedin-48.png

linkedin-48.png

110 ms

pinterest-48.png

pinterest-48.png

113 ms

tumblr-48.png

tumblr-48.png

113 ms

en_us_24.gif

en_us_24.gif

180 ms

es_24.gif

es_24.gif

193 ms

fr_24.gif

fr_24.gif

181 ms

pt_br_24.gif

pt_br_24.gif

205 ms

centralxbar.png

centralxbar.png

180 ms

close.gif

close.gif

179 ms

passport_icon24.gif

passport_icon24.gif

301 ms

bar_up.gif

bar_up.gif

301 ms

favorite_bar.png

favorite_bar.png

283 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

41 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

41 ms

fastbutton

fastbutton

99 ms

page

page

164 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

70 ms

postmessageRelay

postmessageRelay

81 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

24 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

12 ms

tweet_button.6a78875565a912489e9aef879c881358.pt.html

tweet_button.6a78875565a912489e9aef879c881358.pt.html

20 ms

api.js

api.js

106 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

179 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

143 ms

rs=AGLTcCMOpby8iouOYcERfvdCv7RXI3hi_g

rs=AGLTcCMOpby8iouOYcERfvdCv7RXI3hi_g

17 ms

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

29 ms

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

46 ms

photo.jpg

photo.jpg

253 ms

gplus-dd4b38-20.png

gplus-dd4b38-20.png

139 ms

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

66 ms

601527_516122715124146_1251335693_n.png

601527_516122715124146_1251335693_n.png

447 ms

1239837_516124078457343_510948491_n.png

1239837_516124078457343_510948491_n.png

514 ms

11224056_830237293763565_4660192292362273015_n.jpg

11224056_830237293763565_4660192292362273015_n.jpg

583 ms

12548965_118908131822574_6116603909926949710_n.jpg

12548965_118908131822574_6116603909926949710_n.jpg

649 ms

944080_933475593397198_2221121663830426181_n.jpg

944080_933475593397198_2221121663830426181_n.jpg

647 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

175 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

174 ms

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

rs=AGLTcCNYboMAS4AqgOBf1QOL1ZSBE0_GhA

87 ms

27 ms

mac.pl

mac.pl

457 ms

jot.html

jot.html

2 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

73 ms

xd_arbiter.php

xd_arbiter.php

209 ms

xd_arbiter.php

xd_arbiter.php

424 ms

ping

ping

25 ms

SEO Factors

carolina-da-rocha-resende.catalogo.med.br SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carolina-da-rocha-resende.catalogo.med.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Carolina-da-rocha-resende.catalogo.med.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

carolina-da-rocha-resende.catalogo.med.br

Open Graph data is detected on the main page of Carolina Da Rocha Resende Catalogo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: