Tools & Wizards About Us
blog.1thingapp.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.1thingapp.com

域名已过期,无法正常使用

Page Load Speed

1.7 sec in total

First Response

280 ms

Resources Loaded

903 ms

Page Rendered

494 ms

blog.1thingapp.com screenshot

About Website

Welcome to blog.1thingapp.com homepage info - get ready to check Blog 1 Thingapp best content right away, or after learning these important things about blog.1thingapp.com

The shared gratitude journal that helps you tell the happy story of your life. Sign up and start...

Visit blog.1thingapp.com

Key Findings

We analyzed Blog.1thingapp.com page load time and found that the first response time was 280 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

blog.1thingapp.com performance score

0

Network Requests Diagram

blog.1thingapp.com

280 ms

pre_tumblelog.js

19 ms

tumblelog_post_message_queue.js

22 ms

stylesheet.css

22 ms

tweets.js

337 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Blog.1thingapp.com, 24% (8 requests) were made to Assets.tumblr.com and 18% (6 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (532 ms) relates to the external source 41.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 380.9 kB (34%)

Content Size

1.1 MB

After Optimization

740.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.1thingapp.com main page is 1.1 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. 45% of websites need less resources to load. Images take 558.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 46.0 kB

  • Original 55.2 kB
  • After minification 44.3 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 10.9 kB, which is 20% 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 46.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 16.0 kB

  • Original 558.4 kB
  • After minification 542.4 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. Blog 1 Thingapp images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 318.5 kB

  • Original 507.2 kB
  • After minification 507.2 kB
  • After compression 188.8 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 318.5 kB or 63% of the original size.

CSS Optimization

-59%

Potential reduce by 384 B

  • Original 655 B
  • After minification 655 B
  • After compression 271 B

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.1thingapp.com needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (28%)

Requests Now

32

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.1thingapp.com

blog.1thingapp.com

280 ms

pre_tumblelog.js

pre_tumblelog.js

19 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

22 ms

stylesheet.css

stylesheet.css

22 ms

tweets.js

tweets.js

337 ms

index.js

index.js

33 ms

tumblr_static_1thingillustrated_logo-01.jpg

tumblr_static_1thingillustrated_logo-01.jpg

57 ms

tumblr_mx3dd3PAm61r763xlo1_500.jpg

tumblr_mx3dd3PAm61r763xlo1_500.jpg

458 ms

tumblr_mwy6z8SLDL1r763xlo1_500.jpg

tumblr_mwy6z8SLDL1r763xlo1_500.jpg

247 ms

tumblr_mwq59hdzAV1r763xlo1_500.jpg

tumblr_mwq59hdzAV1r763xlo1_500.jpg

113 ms

avatar_c9fd1b09bd7d_64.png

avatar_c9fd1b09bd7d_64.png

7 ms

tumblr_mwlb45mC811r763xlo1_500.jpg

tumblr_mwlb45mC811r763xlo1_500.jpg

168 ms

tumblr_mwjdqiJ5Rr1r763xlo1_500.jpg

tumblr_mwjdqiJ5Rr1r763xlo1_500.jpg

232 ms

tumblr_mwwc6rM0141r763xlo1_500.jpg

tumblr_mwwc6rM0141r763xlo1_500.jpg

532 ms

tumblr_mwuj0asmAv1r763xlo1_500.jpg

tumblr_mwuj0asmAv1r763xlo1_500.jpg

248 ms

tumblr_mwq57xfh2t1r763xlo1_500.jpg

tumblr_mwq57xfh2t1r763xlo1_500.jpg

249 ms

tumblr_mwhgpnm10A1r763xlo1_500.jpg

tumblr_mwhgpnm10A1r763xlo1_500.jpg

250 ms

tumblr_mwffelpNkQ1r763xlo1_500.jpg

tumblr_mwffelpNkQ1r763xlo1_500.jpg

252 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

49 ms

impixu

impixu

119 ms

impixu

impixu

87 ms

analytics.html

analytics.html

81 ms

login_check.html

login_check.html

2 ms

avatar_c9fd1b09bd7d_40.png

avatar_c9fd1b09bd7d_40.png

69 ms

iframe_logo.png

iframe_logo.png

36 ms

rapid-3.33.js

rapid-3.33.js

33 ms

rapidworker-1.2.js

rapidworker-1.2.js

37 ms

ga.js

ga.js

49 ms

analytics.js

analytics.js

33 ms

cs.js

cs.js

59 ms

__utm.gif

__utm.gif

11 ms

cedexis.radar.js

cedexis.radar.js

8 ms

SEO Factors

blog.1thingapp.com 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.1thingapp.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 Blog.1thingapp.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

blog.1thingapp.com

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