Tools & Wizards About Us
support.weta.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

support.weta.org

WETA | Public Television and Classical Music for Greater Washington

Page Load Speed

1000 ms in total

First Response

123 ms

Resources Loaded

691 ms

Page Rendered

186 ms

support.weta.org screenshot

About Website

Welcome to support.weta.org homepage info - get ready to check Support WETA best content for United States right away, or after learning these important things about support.weta.org

WETA is the leading public broadcasting station in the nation’s capital, serving Virginia, Maryland and the District of Columbia with educational, cultural, news and public affairs programs and servic...

Visit support.weta.org

Key Findings

We analyzed Support.weta.org page load time and found that the first response time was 123 ms and then it took 877 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

support.weta.org performance score

0

Network Requests Diagram

support.weta.org

123 ms

subscribers

66 ms

yui-min.js

109 ms

modules.js

115 ms

utils.js

215 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 75% of them (15 requests) were addressed to the original Support.weta.org, 15% (3 requests) were made to Weta.org and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (215 ms) belongs to the original domain Support.weta.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.5 kB (54%)

Content Size

254.8 kB

After Optimization

117.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Support.weta.org main page is 254.8 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. 20% of websites need less resources to load. Javascripts take 97.8 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 4.5 kB

  • Original 7.2 kB
  • After minification 7.0 kB
  • After compression 2.7 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 4.5 kB or 63% of the original size.

Image Optimization

-23%

Potential reduce by 20.1 kB

  • Original 86.0 kB
  • After minification 65.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. Obviously, Support WETA needs image optimization as it can save up to 20.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 58.8 kB

  • Original 97.8 kB
  • After minification 94.7 kB
  • After compression 39.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 58.8 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 54.2 kB

  • Original 63.8 kB
  • After minification 41.3 kB
  • After compression 9.7 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. Support.weta.org needs all CSS files to be minified and compressed as it can save up to 54.2 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

18

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support WETA. 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

support.weta.org

support.weta.org

123 ms

subscribers

subscribers

66 ms

yui-min.js

yui-min.js

109 ms

modules.js

modules.js

115 ms

utils.js

utils.js

215 ms

obs_comp_rollup.js

obs_comp_rollup.js

111 ms

default.css

default.css

112 ms

alphacube.css

alphacube.css

121 ms

UserGlobalStyle.css

UserGlobalStyle.css

159 ms

CustomStyle.css

CustomStyle.css

160 ms

CustomWysiwygStyle.css

CustomWysiwygStyle.css

165 ms

global.js

global.js

162 ms

ga.js

ga.js

16 ms

body1.jpg

body1.jpg

17 ms

Convio_Top2c.jpg

Convio_Top2c.jpg

212 ms

Convio_Bottom2c.jpg

Convio_Bottom2c.jpg

58 ms

poweredbyconvio.gif

poweredbyconvio.gif

56 ms

swoosh2.gif

swoosh2.gif

36 ms

divider1.gif

divider1.gif

34 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

support.weta.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.weta.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Support.weta.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

support.weta.org

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