6.7 sec in total
282 ms
2.9 sec
3.5 sec
Click here to check amazing TDF content for United States. Otherwise, check out these important facts you probably never knew about tdf.org
Theatre Development Fund (TDF) is a Not-For-Profit Organization for the Performing Arts which works to make theatre affordable and accessible to all.
Visit tdf.orgWe analyzed Tdf.org page load time and found that the first response time was 282 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tdf.org performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value9.2 s
1/100
25%
Value13.6 s
2/100
10%
Value2,140 ms
6/100
30%
Value0.043
99/100
15%
Value23.3 s
1/100
10%
282 ms
901 ms
213 ms
239 ms
227 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 94% of them (63 requests) were addressed to the original Tdf.org, 4% (3 requests) were made to Ssl.google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (917 ms) belongs to the original domain Tdf.org.
Page size can be reduced by 901.2 kB (38%)
2.4 MB
1.5 MB
In fact, the total size of Tdf.org main page is 2.4 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 75.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 75.1 kB or 76% of the original size.
Potential reduce by 47.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. TDF images are well optimized though.
Potential reduce by 540.3 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 540.3 kB or 81% of the original size.
Potential reduce by 238.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. Tdf.org needs all CSS files to be minified and compressed as it can save up to 238.7 kB or 90% of the original size.
Number of requests can be reduced by 26 (40%)
65
39
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TDF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
tdf.org
282 ms
www.tdf.org
901 ms
css
213 ms
site.css
239 ms
cmsCustom.css
227 ms
bootstrap.css
246 ms
widgets.css
385 ms
jquery-ui-1.10.3.custom.css
262 ms
widgetTutorial.css
275 ms
jquery-1.10.2.js
464 ms
jquery-ui-1.10.3.custom.js
592 ms
jquery.easing.js
424 ms
best.js
332 ms
best.utility.js
364 ms
Site.Master.js
398 ms
site.js
534 ms
widgetTutorial.js
534 ms
twitterpf.js
534 ms
FBUtils.js
534 ms
widgetFX.js
534 ms
jquery.fitvids.js
533 ms
firefitvids.js
533 ms
TDF_Mods.js
571 ms
page-default.js
577 ms
WebResource.axd
526 ms
ScriptResource.axd
513 ms
Telerik.Web.UI.WebResource.axd
579 ms
jquery.bxslider.css
474 ms
jquery.bxslider.js
564 ms
ga.js
109 ms
logo_white.png
83 ms
contentimage85.jpg
452 ms
contentimage31.jpg
314 ms
contentimage86.jpg
419 ms
contentimage33.jpg
314 ms
stages_button.png
84 ms
contentimage35.jpg
264 ms
contentimage34.png
539 ms
contentimage36.jpg
559 ms
contentimage37.jpg
916 ms
contentimage3.jpg
917 ms
contentimage4.jpg
917 ms
contentimage57.png
559 ms
title-pager_btn_right.png
917 ms
__utm.gif
170 ms
ico_sprite.png
654 ms
www.tdf.org
657 ms
learn_more.png
606 ms
widget-frame-2.png
606 ms
widget-frame-2-over.png
606 ms
go-flag.png
607 ms
go-flag-over.png
606 ms
btn_toTop.png
394 ms
ico_social_sprite.png
341 ms
overlay.png
342 ms
__utm.gif
303 ms
GetStageArticlesWp
69 ms
ui-bg_flat_75_ffffff_40x100.png
23 ms
stages-article-thumbnail-image-1380.jpg
52 ms
stages-article-thumbnail-image-1381.jpg
174 ms
stages-article-thumbnail-image-1379.jpg
76 ms
stages-article-thumbnail-image-1378.jpg
189 ms
stages-article-thumbnail-image-1377.jpg
201 ms
bx_loader.gif
108 ms
dotOff.png
165 ms
controls.png
169 ms
dotOn.png
135 ms
tdf.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tdf.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tdf.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tdf.org 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 Tdf.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.
tdf.org
Open Graph description is not detected on the main page of TDF. 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: