Tools & Wizards About Us
sm.blog.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sm.blog.br

Social Media Blog Brasil | Conteúdo para Social Media

Page Load Speed

7.8 sec in total

First Response

1.8 sec

Resources Loaded

5.4 sec

Page Rendered

586 ms

sm.blog.br screenshot

About Website

Visit sm.blog.br now to see the best up-to-date Sm Blog content for Brazil and also check out these interesting facts you probably never knew about sm.blog.br

Conteúdo para Social Media

Visit sm.blog.br

Key Findings

We analyzed Sm.blog.br page load time and found that the first response time was 1.8 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

sm.blog.br performance score

0

Network Requests Diagram

sm.blog.br

1764 ms

analytics.js

31 ms

wp-emoji-release.min.js

172 ms

mediaelementplayer.min.css

294 ms

wp-mediaelement.css

292 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 33% of them (28 requests) were addressed to the original Sm.blog.br, 31% (27 requests) were made to Static.xx.fbcdn.net and 12% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source External.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.8 kB (38%)

Content Size

1.2 MB

After Optimization

717.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sm.blog.br main page is 1.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. 65% of websites need less resources to load. Images take 590.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 30.8 kB

  • Original 41.3 kB
  • After minification 39.7 kB
  • After compression 10.5 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 30.8 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 18.7 kB

  • Original 590.0 kB
  • After minification 571.3 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. Sm Blog images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 263.9 kB

  • Original 375.2 kB
  • After minification 338.5 kB
  • After compression 111.3 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 263.9 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 121.4 kB

  • Original 146.3 kB
  • After minification 128.8 kB
  • After compression 24.9 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. Sm.blog.br needs all CSS files to be minified and compressed as it can save up to 121.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (59%)

Requests Now

80

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sm.blog.br

sm.blog.br

1764 ms

analytics.js

analytics.js

31 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

172 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

294 ms

wp-mediaelement.css

wp-mediaelement.css

292 ms

style.css

style.css

300 ms

css

css

70 ms

font-awesome.css

font-awesome.css

295 ms

jetpack.css

jetpack.css

285 ms

jquery.js

jquery.js

467 ms

jquery-migrate.min.js

jquery-migrate.min.js

456 ms

spin.js

spin.js

453 ms

jquery.spin.js

jquery.spin.js

447 ms

infinity.js

infinity.js

448 ms

jquery.cycle.js

jquery.cycle.js

455 ms

slideshow-shortcode.js

slideshow-shortcode.js

614 ms

devicepx-jetpack.js

devicepx-jetpack.js

21 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

741 ms

wp-mediaelement.js

wp-mediaelement.js

605 ms

navigation.js

navigation.js

614 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

732 ms

wp-embed.min.js

wp-embed.min.js

635 ms

e-201611.js

e-201611.js

19 ms

collect

collect

21 ms

header.png

header.png

395 ms

34615.53366-FACEBOOK-900x300.jpg

34615.53366-FACEBOOK-900x300.jpg

577 ms

twitternewphotos_625-625x300.jpg

twitternewphotos_625-625x300.jpg

582 ms

face-900x300.jpg

face-900x300.jpg

476 ms

TwitterHeartStar-900x300.jpeg

TwitterHeartStar-900x300.jpeg

529 ms

fb-900x300.jpg

fb-900x300.jpg

970 ms

telegram-vs-whatsapp-1728x800-900x300.png

telegram-vs-whatsapp-1728x800-900x300.png

1199 ms

instagram-900x300.jpg

instagram-900x300.jpg

787 ms

sdk.js

sdk.js

21 ms

_ddpdtd1ofP9Ocd2RnhWXA.woff

_ddpdtd1ofP9Ocd2RnhWXA.woff

71 ms

69xcvahA6o9RE5_Tmt9HT_esZW2xOQ-xsNqO47m55DA.woff

69xcvahA6o9RE5_Tmt9HT_esZW2xOQ-xsNqO47m55DA.woff

94 ms

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

103 ms

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

106 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

966 ms

76 ms

xd_arbiter.php

xd_arbiter.php

43 ms

xd_arbiter.php

xd_arbiter.php

56 ms

g.gif

g.gif

6 ms

page.php

page.php

313 ms

LUdypCgtRlc.css

LUdypCgtRlc.css

50 ms

46icGyCHNkx.css

46icGyCHNkx.css

57 ms

7UFpPvIym7D.css

7UFpPvIym7D.css

60 ms

6fhPFsydUm0.css

6fhPFsydUm0.css

58 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

55 ms

XoqZARH4OJa.js

XoqZARH4OJa.js

58 ms

ihptErjAmMX.js

ihptErjAmMX.js

89 ms

3So47A9WcrL.js

3So47A9WcrL.js

95 ms

cUsKAwzqrQw.js

cUsKAwzqrQw.js

92 ms

_mImxO4mCU1.js

_mImxO4mCU1.js

93 ms

QjJ5QeyKyW9.js

QjJ5QeyKyW9.js

90 ms

6PDLJFN-l6_.js

6PDLJFN-l6_.js

93 ms

12190838_984444614948865_4908815999134352451_n.png

12190838_984444614948865_4908815999134352451_n.png

214 ms

safe_image.php

safe_image.php

2008 ms

vErY8zngADX.js

vErY8zngADX.js

63 ms

FzGTmhgBEqv.js

FzGTmhgBEqv.js

59 ms

b8XhdWI9eAN.js

b8XhdWI9eAN.js

59 ms

lRyN50VcaFW.js

lRyN50VcaFW.js

56 ms

css;base64,

css;base64,

16 ms

AQCoNaHeh00.css

AQCoNaHeh00.css

50 ms

safe_image.php

safe_image.php

1377 ms

safe_image.php

safe_image.php

2175 ms

safe_image.php

safe_image.php

1814 ms

safe_image.php

safe_image.php

112 ms

12208605_984442281615765_2794925765579637378_n.png

12208605_984442281615765_2794925765579637378_n.png

107 ms

10620768_566320963522575_8263923079949506604_n.jpg

10620768_566320963522575_8263923079949506604_n.jpg

59 ms

944960_1745192562375918_8551721844569896359_n.jpg

944960_1745192562375918_8551721844569896359_n.jpg

59 ms

12417641_535328009978568_8910143952455400657_n.jpg

12417641_535328009978568_8910143952455400657_n.jpg

59 ms

1479177_1532005230428981_5775895043895935452_n.jpg

1479177_1532005230428981_5775895043895935452_n.jpg

59 ms

1913703_119991968375650_3309696342829607952_n.jpg

1913703_119991968375650_3309696342829607952_n.jpg

148 ms

10014681_600463746705845_740677011_n.jpg

10014681_600463746705845_740677011_n.jpg

108 ms

12573135_813077938802233_2207270532242604854_n.jpg

12573135_813077938802233_2207270532242604854_n.jpg

112 ms

12798868_1107145085972375_7820919161375876206_n.jpg

12798868_1107145085972375_7820919161375876206_n.jpg

111 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

24 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

58 ms

GtIpNnEyqq_.png

GtIpNnEyqq_.png

105 ms

YzFEFmGRSUa.png

YzFEFmGRSUa.png

106 ms

JNPO3NqYHEj.png

JNPO3NqYHEj.png

19 ms

QijIVO3ZIrO.png

QijIVO3ZIrO.png

19 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

5 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

4 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

5 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

6 ms

SEO Factors

sm.blog.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

sm.blog.br

Open Graph data is detected on the main page of Sm Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: