Tools & Wizards About Us
emedcal.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

emedcal.com.br

Page Load Speed

3.5 sec in total

First Response

312 ms

Resources Loaded

2.2 sec

Page Rendered

975 ms

emedcal.com.br screenshot

About Website

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

Visit emedcal.com.br

Key Findings

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

Performance Metrics

emedcal.com.br performance score

0

Network Requests Diagram

emedcal.com.br

312 ms

green.css

74 ms

medicom.css

157 ms

bootstrap.css

199 ms

jquery-ui-1.10.3.custom.css

90 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 65% of them (90 requests) were addressed to the original Emedcal.com.br, 11% (15 requests) were made to Google.com and 9% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Emedcal.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (19%)

Content Size

11.0 MB

After Optimization

8.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 109.5 kB

  • Original 121.3 kB
  • After minification 55.0 kB
  • After compression 11.9 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 66.3 kB, which is 55% 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 109.5 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 170.0 kB

  • Original 8.6 MB
  • After minification 8.4 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. Emedcal images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 1.4 MB

  • Original 1.8 MB
  • After minification 1.5 MB
  • After compression 434.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 1.4 MB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 442.9 kB

  • Original 528.4 kB
  • After minification 476.7 kB
  • After compression 85.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. Emedcal.com.br needs all CSS files to be minified and compressed as it can save up to 442.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (35%)

Requests Now

129

After Optimization

84

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

emedcal.com.br

emedcal.com.br

312 ms

green.css

green.css

74 ms

medicom.css

medicom.css

157 ms

bootstrap.css

bootstrap.css

199 ms

jquery-ui-1.10.3.custom.css

jquery-ui-1.10.3.custom.css

90 ms

owl.carousel.css

owl.carousel.css

106 ms

uniform.default.css

uniform.default.css

99 ms

revolution_style.css

revolution_style.css

108 ms

settings.css

settings.css

125 ms

light.css

light.css

131 ms

modal.css

modal.css

170 ms

jquery.js

jquery.js

288 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

270 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

347 ms

bootstrap.min.js

bootstrap.min.js

214 ms

carousel.js

carousel.js

176 ms

jquery.stellar.js

jquery.stellar.js

153 ms

jquery-ui-1.10.3.custom.js

jquery-ui-1.10.3.custom.js

266 ms

owl.carousel.js

owl.carousel.js

446 ms

counter.js

counter.js

228 ms

waypoints.js

waypoints.js

238 ms

jquery.uniform.js

jquery.uniform.js

291 ms

forms-validation.js

forms-validation.js

258 ms

fonts.css

fonts.css

157 ms

font-awesome.css

font-awesome.css

179 ms

embed

embed

281 ms

toggle-btn.png

toggle-btn.png

104 ms

slide01.png

slide01.png

618 ms

LOGO.svg

LOGO.svg

265 ms

blank.png

blank.png

103 ms

06.png

06.png

239 ms

slider2-img-bg.png

slider2-img-bg.png

99 ms

05.png

05.png

242 ms

02.png

02.png

545 ms

04.png

04.png

399 ms

01.png

01.png

258 ms

slider2-girl-img.png

slider2-girl-img.png

258 ms

03.png

03.png

398 ms

01.png

01.png

395 ms

02.png

02.png

397 ms

lines-bg-white.jpg

lines-bg-white.jpg

612 ms

app-available-img.jpg

app-available-img.jpg

553 ms

mobile-hand.png

mobile-hand.png

414 ms

app-store-btn.png

app-store-btn.png

545 ms

google-play-btn.png

google-play-btn.png

552 ms

heading-border.png

heading-border.png

551 ms

1.png

1.png

1188 ms

1.png

1.png

733 ms

1.png

1.png

1332 ms

1.png

1.png

868 ms

1.png

1.png

867 ms

01.png

01.png

736 ms

02.png

02.png

870 ms

03.png

03.png

899 ms

04.png

04.png

870 ms

04.png

04.png

871 ms

01.jpg

01.jpg

899 ms

02.jpg

02.jpg

953 ms

03.jpg

03.jpg

978 ms

3.png

3.png

1002 ms

5.png

5.png

944 ms

lato-regular.woff

lato-regular.woff

947 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

999 ms

lato-light.woff

lato-light.woff

961 ms

QKmXyiJ5Zi8

QKmXyiJ5Zi8

283 ms

icomoon.woff

icomoon.woff

823 ms

OpFirHe7Gx8

OpFirHe7Gx8

158 ms

ClCUzFw4vPc

ClCUzFw4vPc

169 ms

Lato-Semibold.woff

Lato-Semibold.woff

955 ms

lato-bold.woff

lato-bold.woff

881 ms

js

js

248 ms

init_embed.js

init_embed.js

156 ms

XWr7tU54_zE

XWr7tU54_zE

142 ms

2.png

2.png

900 ms

4.png

4.png

951 ms

3.png

3.png

965 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

38 ms

www-embed-player.js

www-embed-player.js

57 ms

5.png

5.png

842 ms

2.png

2.png

910 ms

4.png

4.png

894 ms

6.png

6.png

869 ms

3.png

3.png

912 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

77 ms

ad_status.js

ad_status.js

142 ms

5.png

5.png

791 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

171 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

172 ms

7.png

7.png

793 ms

2.png

2.png

807 ms

3.png

3.png

834 ms

4.png

4.png

848 ms

2.png

2.png

879 ms

3.png

3.png

749 ms

common.js

common.js

59 ms

map.js

map.js

59 ms

google4.png

google4.png

154 ms

overlay.js

overlay.js

22 ms

util.js

util.js

19 ms

onion.js

onion.js

15 ms

search_impl.js

search_impl.js

18 ms

4.png

4.png

688 ms

5.png

5.png

691 ms

stats.js

stats.js

81 ms

openhand_8_8.cur

openhand_8_8.cur

44 ms

colourfull-line.jpg

colourfull-line.jpg

590 ms

loader.gif

loader.gif

586 ms

arrow_left.png

arrow_left.png

560 ms

arrow_right.png

arrow_right.png

580 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

103 ms

controls.js

controls.js

30 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

68 ms

kh

kh

115 ms

select-bg.png

select-bg.png

603 ms

transparent.png

transparent.png

82 ms

sprite.png

sprite.png

552 ms

backtop.png

backtop.png

628 ms

css

css

154 ms

entity11.png

entity11.png

52 ms

mapcnt6.png

mapcnt6.png

78 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

48 ms

tmapctrl.png

tmapctrl.png

53 ms

vt

vt

164 ms

vt

vt

187 ms

vt

vt

157 ms

vt

vt

153 ms

vt

vt

156 ms

vt

vt

154 ms

vt

vt

190 ms

vt

vt

189 ms

vt

vt

202 ms

vt

vt

198 ms

vt

vt

189 ms

vt

vt

203 ms

vt

vt

206 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

10 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

11 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

17 ms

SEO Factors

emedcal.com.br SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

emedcal.com.br

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