1.3 sec in total
35 ms
1.1 sec
181 ms
Click here to check amazing Main W GBH content for United States. Otherwise, check out these important facts you probably never knew about main.wgbh.org
Learn more about WGBH's mission and leadership as well as corporate reports and the latest news and events, plus a behind-the-scenes look at our people, places and programs.
Visit main.wgbh.orgWe analyzed Main.wgbh.org page load time and found that the first response time was 35 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.
main.wgbh.org performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.9 s
29/100
25%
Value5.7 s
52/100
10%
Value3,030 ms
2/100
30%
Value0.011
100/100
15%
Value19.6 s
2/100
10%
35 ms
28 ms
128 ms
56 ms
70 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Main.wgbh.org, 40% (45 requests) were made to Wgbh.org and 7% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (369 ms) relates to the external source Cs.gssprt.jp.
Page size can be reduced by 1.1 MB (63%)
1.7 MB
610.5 kB
In fact, the total size of Main.wgbh.org main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 77.1 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 77.1 kB or 73% of the original size.
Potential reduce by 5.0 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. Main W GBH images are well optimized though.
Potential reduce by 813.9 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 813.9 kB or 68% of the original size.
Potential reduce by 162.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. Main.wgbh.org needs all CSS files to be minified and compressed as it can save up to 162.1 kB or 62% of the original size.
Number of requests can be reduced by 77 (79%)
97
20
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Main W GBH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
main.wgbh.org
35 ms
28 ms
index.cfm
128 ms
cfmessage.js
56 ms
cfajax.js
70 ms
cfform.js
39 ms
masks.js
40 ms
cfformhistory.js
45 ms
118070054.js
195 ms
style.css
76 ms
style-v2.css
98 ms
header-footer.css
57 ms
styleBfs.css
65 ms
subModal.css
70 ms
common.js
76 ms
subModal.js
85 ms
jquery.min.js
108 ms
hoverIntent.min.js
86 ms
js.js
95 ms
flash_detect.js
92 ms
mouseover-tracker.js
103 ms
javascript.js
103 ms
dw_event.js
104 ms
dw_viewport.js
109 ms
dw_tooltip.js
111 ms
dw_tooltip_aux.js
121 ms
addthis_widget.js
10 ms
quant.js
13 ms
fonts.css
61 ms
gpt.js
7 ms
bg_field_search2.gif
78 ms
butGoSignin.gif
78 ms
but_search.gif
79 ms
signin_x.gif
79 ms
bgSubscribe.gif
79 ms
logo.png
81 ms
membership.png
81 ms
sustainer.jpg
81 ms
corner_top_bar.gif
82 ms
modal_close.png
83 ms
pbs-logo.gif
82 ms
npr-logo.gif
82 ms
pri-logo.gif
83 ms
fbds.js
10 ms
analytics.js
8 ms
pubads_impl_82.js
70 ms
nav-arrow.gif
75 ms
wgbh-header-sprite.png
75 ms
collect
45 ms
107 ms
container.html
21 ms
collect
66 ms
PEyJxOSjH0epS9XB1v8G71HvLF4noCFJ9dyPxfCkX6iFcExwQq5n6W32sZNPaw4SSv3pAtDA1l8PDk4lBOoKsldWXQf4fgcE89od1Ma14Dp1lmdN62Tnoh+UDHJ0X6mPW4mPH5LU9bPD3+W8rf02ZCuA==
12 ms
A7KwQrA=
11 ms
TZkK4
12 ms
A7KwQrA=
11 ms
DC0K0
10 ms
Q3C4p57QbqY1r4HTLDM6b1snvZB8oOOTIn3MelzM+PyWpy2eHv8t5W9QkkKY
9 ms
DC0K0
8 ms
LeVvUJJCmA==
8 ms
ads
96 ms
popup_bg.png
19 ms
footer-bg-pattern.gif
21 ms
back_to.gif
18 ms
tc.min.js
18 ms
pixel;r=14988272;a=p-d9rZqRcDHtMDo;fpan=1;fpa=P0-1924690562-1458255501853;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458255501853;tzo=-180;ref=;url=http%3A%2F%2Fwww.wgbh.org%2Fabout%2Findex.cfm;ogl=image.http%3A%2F%2Fwww%252Ewgbh%252Eorg%2FwgbhLogo%252Epng
15 ms
piwik.js
157 ms
102 ms
97 ms
pixel;r=604198616;a=p-jENtKzreN1buT;labels=_fp.event.__about__index_cfm;fpan=0;fpa=P0-1924690562-1458255501853;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458255501855;tzo=-180;ref=;url=http%3A%2F%2Fwww.wgbh.org%2Fabout%2Findex.cfm;ogl=image.http%3A%2F%2Fwww%252Ewgbh%252Eorg%2FwgbhLogo%252Epng
9 ms
7158.js
12 ms
ca.html
17 ms
pixel
65 ms
Pug
63 ms
rum
59 ms
adb.gif
51 ms
1
61 ms
cs
369 ms
sync
67 ms
cx
52 ms
2596963438253068707
58 ms
osd.js
28 ms
16654787934992117479
59 ms
demconf.jpg
18 ms
cm
26 ms
rum
44 ms
xrefid.xgi
22 ms
360947.gif
22 ms
pixel
39 ms
37 ms
mapuid
35 ms
cm
28 ms
cm
26 ms
cx
28 ms
sd
46 ms
cx
23 ms
cm
13 ms
362378.gif
14 ms
xrefid.xgi
14 ms
14 ms
tap.php
76 ms
lr.gif
15 ms
piwik.php
119 ms
pixel.gif
22 ms
pixel.gif
45 ms
btn_close2.gif
17 ms
loading.html
18 ms
s
46 ms
22 ms
21 ms
maskBG.png
18 ms
u
43 ms
main.wgbh.org accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
main.wgbh.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
main.wgbh.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Main.wgbh.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 Main.wgbh.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.
main.wgbh.org
Open Graph description is not detected on the main page of Main W GBH. 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: