Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.onbeing.org

The On Being Project Tumblr

Page Load Speed

4.4 sec in total

First Response

673 ms

Resources Loaded

2 sec

Page Rendered

1.7 sec

blog.onbeing.org screenshot

About Website

Welcome to blog.onbeing.org homepage info - get ready to check Blog Onbeing best content for United States right away, or after learning these important things about blog.onbeing.org

Groundbreaking Peabody Award-winning conversation about the big questions of meaning — spiritual inquiry, science, social healing, and the arts. Each week a new discovery about the immensity of our...

Visit blog.onbeing.org

Key Findings

We analyzed Blog.onbeing.org page load time and found that the first response time was 673 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

blog.onbeing.org performance score

0

Network Requests Diagram

blog.onbeing.org

673 ms

pre_tumblelog.js

29 ms

css

34 ms

modernizr.js

25 ms

precrafted-social.css

21 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Blog.onbeing.org, 13% (8 requests) were made to Assets.tumblr.com and 11% (7 requests) were made to Static.tumblr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 40.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (16%)

Content Size

7.4 MB

After Optimization

6.3 MB

In fact, the total size of Blog.onbeing.org main page is 7.4 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. 70% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 119.1 kB

  • Original 141.3 kB
  • After minification 133.2 kB
  • After compression 22.2 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 119.1 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 9.1 kB

  • Original 5.8 MB
  • After minification 5.8 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. Blog Onbeing images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 716.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 377.0 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 716.7 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 338.4 kB

  • Original 420.5 kB
  • After minification 415.3 kB
  • After compression 82.1 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. Blog.onbeing.org needs all CSS files to be minified and compressed as it can save up to 338.4 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

22

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

SEO Factors

blog.onbeing.org SEO score

0

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 Blog.onbeing.org 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 Blog.onbeing.org 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

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