Tools & Wizards About Us
status.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

status.net

Status.net Business Templates

Page Load Speed

28.6 sec in total

First Response

139 ms

Resources Loaded

18.1 sec

Page Rendered

10.4 sec

status.net screenshot

About Website

Click here to check amazing Status content for India. Otherwise, check out these important facts you probably never knew about status.net

Resources

Visit status.net

Key Findings

We analyzed Status.net page load time and found that the first response time was 139 ms and then it took 28.5 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

status.net performance score

0

Network Requests Diagram

status.net

139 ms

status.net

965 ms

css

2206 ms

css

2317 ms

font-awesome.min.css

2207 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 58% of them (21 requests) were addressed to the original Status.net, 22% (8 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.0 kB (77%)

Content Size

582.0 kB

After Optimization

135.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Status.net main page is 582.0 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. 50% of websites need less resources to load. Javascripts take 258.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 59.4 kB

  • Original 81.3 kB
  • After minification 80.8 kB
  • After compression 21.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. 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 59.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 10.9 kB
  • After minification 10.9 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. Status images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 187.5 kB

  • Original 258.5 kB
  • After minification 256.9 kB
  • After compression 71.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 187.5 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 200.1 kB

  • Original 231.4 kB
  • After minification 229.2 kB
  • After compression 31.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. Status.net needs all CSS files to be minified and compressed as it can save up to 200.1 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

status.net

status.net

139 ms

status.net

status.net

965 ms

css

css

2206 ms

css

css

2317 ms

font-awesome.min.css

font-awesome.min.css

2207 ms

animate.min.css

animate.min.css

2144 ms

style.css

style.css

1713 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

2143 ms

anime.min.js

anime.min.js

2036 ms

index.js

index.js

2035 ms

segment.js

segment.js

1480 ms

logo.svg

logo.svg

2009 ms

telescope.svg

telescope.svg

2157 ms

moonwalker.svg

moonwalker.svg

2252 ms

satellite.svg

satellite.svg

2306 ms

icon_1.svg

icon_1.svg

3306 ms

hand_plus.jpg

hand_plus.jpg

3295 ms

icon_2.svg

icon_2.svg

3294 ms

rocket.jpg

rocket.jpg

3293 ms

icon_3.svg

icon_3.svg

3295 ms

tada.jpg

tada.jpg

3458 ms

astro.svg

astro.svg

3797 ms

e.svg

e.svg

3419 ms

arrow-right.svg

arrow-right.svg

3643 ms

stars1.svg

stars1.svg

3643 ms

stars2.svg

stars2.svg

3640 ms

v6y1Ig2gA2GS6CCEzu_YLA.woff

v6y1Ig2gA2GS6CCEzu_YLA.woff

3055 ms

aJq3s1gF0cfda4RFyoB5YQ.woff

aJq3s1gF0cfda4RFyoB5YQ.woff

3928 ms

kU4XYdV4jtS72BIidPtqyw.woff

kU4XYdV4jtS72BIidPtqyw.woff

4164 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

4407 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

4406 ms

BVtM30trf7q_jfqYeHfjtA.woff

BVtM30trf7q_jfqYeHfjtA.woff

4407 ms

oUan5VrEkpzIazlUe5ieaA.woff

oUan5VrEkpzIazlUe5ieaA.woff

4406 ms

HkF_qI1x_noxlxhrhMQYED8E0i7KZn-EPnyo3HZu7kw.woff

HkF_qI1x_noxlxhrhMQYED8E0i7KZn-EPnyo3HZu7kw.woff

4163 ms

djtflbt20bdde.cloudfront.net

djtflbt20bdde.cloudfront.net

2394 ms

analytics.min.js

analytics.min.js

3838 ms

SEO Factors

status.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Status.net 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

status.net

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