3.1 sec in total
243 ms
2.3 sec
562 ms
Click here to check amazing ThINKingDANCE content. Otherwise, check out these important facts you probably never knew about thinkingdance.net
thINKingDANCE was started to catalyze conversation about dance and to develop the skills of dance writers in the Philadelphia area. Our initial year-long training scheme, funded by The Pew Center for ...
Visit thinkingdance.netWe analyzed Thinkingdance.net page load time and found that the first response time was 243 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
thinkingdance.net performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value7.0 s
6/100
25%
Value3.2 s
92/100
10%
Value400 ms
67/100
30%
Value0.684
7/100
15%
Value5.9 s
65/100
10%
243 ms
428 ms
113 ms
219 ms
262 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 76% of them (37 requests) were addressed to the original Thinkingdance.net, 4% (2 requests) were made to S7.addthis.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain Thinkingdance.net.
Page size can be reduced by 444.2 kB (53%)
845.8 kB
401.6 kB
In fact, the total size of Thinkingdance.net main page is 845.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. 55% of websites need less resources to load. Javascripts take 508.1 kB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 22% 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 38.7 kB or 76% of the original size.
Potential reduce by 5.8 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. ThINKingDANCE images are well optimized though.
Potential reduce by 353.5 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 353.5 kB or 70% of the original size.
Potential reduce by 46.3 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. Thinkingdance.net needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 84% of the original size.
Number of requests can be reduced by 21 (48%)
44
23
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ThINKingDANCE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
thinkingdance.net
243 ms
thinkingdance.net
428 ms
jquery-ui-1.8.9.custom.css
113 ms
overlay_style.css
219 ms
layout.css
262 ms
common.js
275 ms
jquery.min.js
38 ms
jquery-ui-1.8.14.custom.min.js
432 ms
jquery.scrollTo-1.4.2-min.js
377 ms
overlay.js
375 ms
AC_RunActiveContent.js
393 ms
easySlider.js
394 ms
jquery.colorbox.js
420 ms
addthis_widget.js
149 ms
classic-10_7.css
132 ms
mc-validate.js
149 ms
aller_rg-webfont.woff
273 ms
ga.js
312 ms
btn_donateCC_LG.gif
676 ms
social-media-facebook.png
187 ms
older.gif
186 ms
newer.gif
623 ms
84675742-4FF5-4FF5-9DBE-65E158DB00B1.jpeg
622 ms
transBlack-50.png
623 ms
20200929_CC_AquiferoftheDucts_Photo_courtesy_of_FringeArts_1.png
641 ms
F4892225-8FEF-4462-8487-4A7D990C2063.jpeg
621 ms
TemporaryOccupancy_KS_review_10-3-20.jpg
621 ms
6D4AF544-24E6-4EE3-B127-72184DAF32BB.png
907 ms
IHearaDistantSong_WW.jpg
870 ms
E4E07001-9FE5-46A1-899A-06B44E605C9B.jpeg
640 ms
20201015_CC_Pam_Tanowitz_AnnenbergCenter_2.jpg
870 ms
Event2-EL-10_15-2.jpg
868 ms
101520_DG_MargoTamize_OlivierTarpaga58.png
870 ms
Screen_Shot_2020-10-22_at_11.39.27_PM.png
905 ms
102520_RamonObusanFolkloricGroup-Kuratsa.png
994 ms
PCF.jpg
871 ms
PCA_logo.jpg
870 ms
Subscribe.png
905 ms
101920_Thinking-Dance.jpg
994 ms
Rocky%20Awards%202020%20TD%20Ad.png
908 ms
pixel.gif
620 ms
dot.gif
807 ms
Moms_typewriter-webfont.woff
957 ms
aller_bd-webfont.woff
872 ms
moatframe.js
392 ms
__utm.gif
278 ms
_ate.track.config_resp
257 ms
300lo.json
224 ms
sh.f48a1a04fe8dbf021b4cda1d.html
85 ms
thinkingdance.net accessibility score
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
thinkingdance.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
thinkingdance.net 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
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 Thinkingdance.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 Thinkingdance.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.
thinkingdance.net
Open Graph data is detected on the main page of ThINKingDANCE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: