Tools & Wizards About Us
contentbuddy.com screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    75% of websites

contentbuddy.com

Page Load Speed

33.9 sec in total

First Response

6.5 sec

Resources Loaded

21 sec

Page Rendered

6.4 sec

contentbuddy.com screenshot

About Website

Welcome to contentbuddy.com homepage info - get ready to check Contentbuddy best content right away, or after learning these important things about contentbuddy.com

Become the expert on any niche on your blog by using Content Buddy to drag and drop keyword rich SEO content straight to your WordPress editor to curate content. WIth the new WordPress content plugin.

Visit contentbuddy.com

Key Findings

We analyzed Contentbuddy.com page load time and found that the first response time was 6.5 sec and then it took 27.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

contentbuddy.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

contentbuddy.com

6501 ms

css

36 ms

style.css

362 ms

modernizr-2.0.6.min.js

174 ms

jquery.js

353 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 35% of them (17 requests) were addressed to the original Contentbuddy.com, 12% (6 requests) were made to 0 and 12% (6 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Contentbuddy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.1 kB (50%)

Content Size

568.3 kB

After Optimization

282.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Contentbuddy.com main page is 568.3 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 218.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 18.2 kB

  • Original 25.6 kB
  • After minification 23.8 kB
  • After compression 7.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 18.2 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 141 B

  • Original 142.8 kB
  • After minification 142.6 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. Contentbuddy images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 109.6 kB

  • Original 218.1 kB
  • After minification 213.3 kB
  • After compression 108.6 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 109.6 kB or 50% of the original size.

CSS Optimization

-87%

Potential reduce by 158.2 kB

  • Original 181.8 kB
  • After minification 166.9 kB
  • After compression 23.5 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. Contentbuddy.com needs all CSS files to be minified and compressed as it can save up to 158.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (40%)

Requests Now

43

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

contentbuddy.com

contentbuddy.com

6501 ms

css

css

36 ms

style.css

style.css

362 ms

modernizr-2.0.6.min.js

modernizr-2.0.6.min.js

174 ms

jquery.js

jquery.js

353 ms

jquery-migrate.min.js

jquery-migrate.min.js

140 ms

jquery.min.js

jquery.min.js

3611 ms

plugins.js

plugins.js

3610 ms

script.js

script.js

3609 ms

all.js

all.js

3610 ms

plusone.js

plusone.js

5926 ms

wp_super_faq.js

wp_super_faq.js

3607 ms

click_handler.js

click_handler.js

3606 ms

widgets.js

widgets.js

3608 ms

logo.png

logo.png

3729 ms

slider-bg.png

slider-bg.png

3755 ms

slider-vid.png

slider-vid.png

3757 ms

main-bg.png

main-bg.png

3755 ms

twitter.png

twitter.png

3530 ms

facebook.png

facebook.png

3755 ms

email.png

email.png

3681 ms

33231233

33231233

1216 ms

404.html

404.html

933 ms

404.html

404.html

954 ms

404.html

404.html

901 ms

404.html

404.html

902 ms

404.html

404.html

903 ms

3048 ms

player.js

player.js

1164 ms

player.css

player.css

1087 ms

ga.js

ga.js

1086 ms

vuid.min.js

vuid.min.js

1087 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

2454 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

2974 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

2365 ms

js

js

2719 ms

ping

ping

1685 ms

loading.gif

loading.gif

1953 ms

like.php

like.php

1212 ms

404.html

404.html

130 ms

33231233

33231233

623 ms

in.php

in.php

650 ms

player.js

player.js

1599 ms

player.css

player.css

334 ms

ga.js

ga.js

911 ms

vuid.min.js

vuid.min.js

247 ms

4qFiRLLPSF7.js

4qFiRLLPSF7.js

3185 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

3098 ms

__utm.gif

__utm.gif

1800 ms

Accessibility Review

contentbuddy.com accessibility score

68

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

SEO Factors

contentbuddy.com SEO score

92

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contentbuddy.com 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), while the claimed language is English. Our system also found out that Contentbuddy.com 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

contentbuddy.com

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