Tools & Wizards About Us
upstreamdownstream.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

upstreamdownstream.org

Page Load Speed

1.7 sec in total

First Response

378 ms

Resources Loaded

861 ms

Page Rendered

426 ms

upstreamdownstream.org screenshot

About Website

Visit upstreamdownstream.org now to see the best up-to-date Upstreamdownstream content for India and also check out these interesting facts you probably never knew about upstreamdownstream.org

Visit upstreamdownstream.org

Key Findings

We analyzed Upstreamdownstream.org page load time and found that the first response time was 378 ms and then it took 1.3 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

upstreamdownstream.org performance score

0

Network Requests Diagram

upstreamdownstream.org

378 ms

style.css

11 ms

jquery.js

62 ms

jquery-migrate.min.js

18 ms

superfish.js

20 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 81% of them (48 requests) were addressed to the original Upstreamdownstream.org, 5% (3 requests) were made to Intensedebate.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (378 ms) belongs to the original domain Upstreamdownstream.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.4 kB (36%)

Content Size

666.7 kB

After Optimization

429.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Upstreamdownstream.org main page is 666.7 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. 45% of websites need less resources to load. Images take 395.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 47.4 kB

  • Original 55.9 kB
  • After minification 46.9 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 16% 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 47.4 kB or 85% of the original size.

Image Optimization

-12%

Potential reduce by 46.3 kB

  • Original 395.9 kB
  • After minification 349.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. Obviously, Upstreamdownstream needs image optimization as it can save up to 46.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 86.2 kB

  • Original 147.1 kB
  • After minification 143.4 kB
  • After compression 60.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 86.2 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 57.4 kB

  • Original 67.8 kB
  • After minification 49.6 kB
  • After compression 10.4 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. Upstreamdownstream.org needs all CSS files to be minified and compressed as it can save up to 57.4 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

upstreamdownstream.org

upstreamdownstream.org

378 ms

style.css

style.css

11 ms

jquery.js

jquery.js

62 ms

jquery-migrate.min.js

jquery-migrate.min.js

18 ms

superfish.js

superfish.js

20 ms

jquery.easing.min.js

jquery.easing.min.js

21 ms

woo-jcarousellite.js

woo-jcarousellite.js

21 ms

general.js

general.js

22 ms

default.css

default.css

25 ms

shortcodes.css

shortcodes.css

26 ms

custom.css

custom.css

25 ms

css

css

24 ms

style.css

style.css

20 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

116 ms

widgets.js

widgets.js

174 ms

wordpressTemplateLinkWrapper2.php

wordpressTemplateLinkWrapper2.php

201 ms

ga.js

ga.js

75 ms

top-bg.png

top-bg.png

117 ms

Final-Logo_v7.png

Final-Logo_v7.png

112 ms

nav-bg.png

nav-bg.png

19 ms

icon-bg.png

icon-bg.png

19 ms

ico-rssfeed.png

ico-rssfeed.png

19 ms

ico-twitter.png

ico-twitter.png

19 ms

ico-facebook.png

ico-facebook.png

112 ms

bg-catnav.png

bg-catnav.png

115 ms

slider-bg.png

slider-bg.png

111 ms

slider-scanlines.png

slider-scanlines.png

115 ms

four-leaf-clover-216x86.png

four-leaf-clover-216x86.png

116 ms

HDR_in_Sheep_Meadow_Jul_2009_-_03-216x86.jpg

HDR_in_Sheep_Meadow_Jul_2009_-_03-216x86.jpg

118 ms

lypmammovan_0060-216x86.jpg

lypmammovan_0060-216x86.jpg

120 ms

Pie-216x86.jpeg

Pie-216x86.jpeg

117 ms

Kidney_Cross_Section-216x86.png

Kidney_Cross_Section-216x86.png

124 ms

mockup-865115_960_720-216x86.jpg

mockup-865115_960_720-216x86.jpg

117 ms

AAEAAQAAAAAAAAOYAAAAJDNkMjc5MzcxLWQ5NjUtNDJkYi1hY2FiLTNhYTExNzUxZjQyOQ.jpg

AAEAAQAAAAAAAAOYAAAAJDNkMjc5MzcxLWQ5NjUtNDJkYi1hY2FiLTNhYTExNzUxZjQyOQ.jpg

117 ms

Reproductive-rights-216x86.jpeg

Reproductive-rights-216x86.jpeg

122 ms

next.png

next.png

118 ms

previous.png

previous.png

119 ms

bg-scanlines.png

bg-scanlines.png

119 ms

four-leaf-clover-150x100.png

four-leaf-clover-150x100.png

120 ms

HDR_in_Sheep_Meadow_Jul_2009_-_03-150x100.jpg

HDR_in_Sheep_Meadow_Jul_2009_-_03-150x100.jpg

122 ms

lypmammovan_0060-150x100.jpg

lypmammovan_0060-150x100.jpg

123 ms

Pie-150x100.jpeg

Pie-150x100.jpeg

123 ms

Eye-drops-150x100.png

Eye-drops-150x100.png

124 ms

Kidney_Cross_Section-150x100.png

Kidney_Cross_Section-150x100.png

126 ms

mockup-865115_960_720-150x100.jpg

mockup-865115_960_720-150x100.jpg

123 ms

AAEAAQAAAAAAAAOYAAAAJDNkMjc5MzcxLWQ5NjUtNDJkYi1hY2FiLTNhYTExNzUxZjQyOQ-150x100.jpg

AAEAAQAAAAAAAAOYAAAAJDNkMjc5MzcxLWQ5NjUtNDJkYi1hY2FiLTNhYTExNzUxZjQyOQ-150x100.jpg

124 ms

Reproductive-rights-150x100.jpeg

Reproductive-rights-150x100.jpeg

124 ms

Untitled-150x100.png

Untitled-150x100.png

127 ms

ico-search.png

ico-search.png

124 ms

footer-widgets-bg.png

footer-widgets-bg.png

125 ms

woothemes.png

woothemes.png

127 ms

0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf

0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf

103 ms

G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf

G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf

105 ms

slider-img-bg.png

slider-img-bg.png

126 ms

__utm.gif

__utm.gif

63 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

141 ms

remoteVisit.php

remoteVisit.php

66 ms

getCommentCounts.php

getCommentCounts.php

129 ms

collect

collect

72 ms

SEO Factors

upstreamdownstream.org SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Upstreamdownstream.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Upstreamdownstream.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

upstreamdownstream.org

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