Tools & Wizards About Us
contenttrends.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

contenttrends.com.br

Rock Content: Content Experiences your audience will love

Page Load Speed

2.7 sec in total

First Response

208 ms

Resources Loaded

2.2 sec

Page Rendered

259 ms

contenttrends.com.br screenshot

About Website

Visit contenttrends.com.br now to see the best up-to-date Content Trends content for Brazil and also check out these interesting facts you probably never knew about contenttrends.com.br

Rock Content empowers brands to launch the best content experiences using our best in class products and services.

Visit contenttrends.com.br

Key Findings

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

Performance Metrics

contenttrends.com.br performance score

0

Network Requests Diagram

contenttrends.com.br

208 ms

bootstrap.min.css

37 ms

css

57 ms

animate.min.css

30 ms

font-awesome.min.css

8 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 29% of them (23 requests) were addressed to the original Contenttrends.com.br, 10% (8 requests) were made to Apis.google.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Js.hs-analytics.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 572.9 kB (64%)

Content Size

895.5 kB

After Optimization

322.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Contenttrends.com.br main page is 895.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 414.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 32.5 kB

  • Original 39.4 kB
  • After minification 30.6 kB
  • After compression 6.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 8.8 kB, which is 22% 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 32.5 kB or 83% of the original size.

Image Optimization

-38%

Potential reduce by 78.7 kB

  • Original 205.0 kB
  • After minification 126.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. Obviously, Content Trends needs image optimization as it can save up to 78.7 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 259.7 kB

  • Original 414.0 kB
  • After minification 413.9 kB
  • After compression 154.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 259.7 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 201.9 kB

  • Original 237.1 kB
  • After minification 233.3 kB
  • After compression 35.2 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. Contenttrends.com.br needs all CSS files to be minified and compressed as it can save up to 201.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (61%)

Requests Now

72

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Content Trends. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

contenttrends.com.br

contenttrends.com.br

208 ms

bootstrap.min.css

bootstrap.min.css

37 ms

css

css

57 ms

animate.min.css

animate.min.css

30 ms

font-awesome.min.css

font-awesome.min.css

8 ms

creative.css

creative.css

64 ms

platform.js

platform.js

105 ms

in.js

in.js

54 ms

conversion.js

conversion.js

55 ms

jquery.min.js

jquery.min.js

59 ms

bootstrap.min.js

bootstrap.min.js

51 ms

jquery.easing.min.js

jquery.easing.min.js

51 ms

jquery.fittext.js

jquery.fittext.js

101 ms

wow.min.js

wow.min.js

100 ms

buttons.js

buttons.js

53 ms

creative.js

creative.js

48 ms

rock.js

rock.js

57 ms

sdk.js

sdk.js

205 ms

widgets.js

widgets.js

82 ms

secureAnonymousFramework

secureAnonymousFramework

163 ms

fbevents.js

fbevents.js

215 ms

analytics.js

analytics.js

71 ms

355484.js

355484.js

1899 ms

dots.png

dots.png

57 ms

logoTMC-2015.svg

logoTMC-2015.svg

80 ms

01.png

01.png

79 ms

02.png

02.png

82 ms

logo.png

logo.png

81 ms

aberje.png

aberje.png

82 ms

resultados-digitais.png

resultados-digitais.png

79 ms

mundo-do-marketing.png

mundo-do-marketing.png

130 ms

hsm.png

hsm.png

129 ms

dna-digital.png

dna-digital.png

139 ms

webinsider.png

webinsider.png

138 ms

digitalks.png

digitalks.png

139 ms

matilde-filmes.png

matilde-filmes.png

138 ms

getAllAppDefault.esi

getAllAppDefault.esi

154 ms

154 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

48 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

89 ms

sharebutton

sharebutton

156 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

76 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

120 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

144 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

141 ms

collect

collect

54 ms

192 ms

share

share

177 ms

sprite_connect_v14.png

sprite_connect_v14.png

173 ms

postmessageRelay

postmessageRelay

164 ms

135 ms

rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA

rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA

72 ms

rs=AGLTcCOUMF44lxC2EamPesvNXMSDxGgUfQ

rs=AGLTcCOUMF44lxC2EamPesvNXMSDxGgUfQ

71 ms

190 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

126 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

140 ms

getSegment.php

getSegment.php

201 ms

checkOAuth.esi

checkOAuth.esi

96 ms

xd_arbiter.php

xd_arbiter.php

163 ms

xd_arbiter.php

xd_arbiter.php

313 ms

178 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

35 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

29 ms

rpc:shindig_random.js

rpc:shindig_random.js

48 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

jot

jot

106 ms

t.dhj

t.dhj

9 ms

t.dhj

t.dhj

14 ms

cm

cm

32 ms

x35248

x35248

119 ms

s-3271.xgi

s-3271.xgi

13 ms

hbpix

hbpix

40 ms

14 ms

22 ms

xrefid.xgi

xrefid.xgi

17 ms

pixel

pixel

23 ms

2981

2981

23 ms

index.a8fc48294ca4cc10eb440189d9f22d7c.html

index.a8fc48294ca4cc10eb440189d9f22d7c.html

17 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

11 ms

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

st.125da8bfe70ad3e00a35a6e4c65d8bc5.js

6 ms

SEO Factors

contenttrends.com.br SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contenttrends.com.br can be misinterpreted by Google and other search engines. Our service has detected that English 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 Contenttrends.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

contenttrends.com.br

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