1.9 sec in total
163 ms
1.6 sec
157 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 163 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
thinkingdance.net performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value8.7 s
1/100
25%
Value3.0 s
94/100
10%
Value230 ms
87/100
30%
Value0.534
14/100
15%
Value4.3 s
84/100
10%
163 ms
412 ms
150 ms
228 ms
228 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 88% of them (38 requests) were addressed to the original Thinkingdance.net, 5% (2 requests) were made to Paypalobjects.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (522 ms) belongs to the original domain Thinkingdance.net.
Page size can be reduced by 114.6 kB (12%)
922.3 kB
807.7 kB
In fact, the total size of Thinkingdance.net main page is 922.3 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. 35% of websites need less resources to load. Images take 792.4 kB which makes up the majority of the site volume.
Potential reduce by 14.8 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 14.8 kB or 69% of the original size.
Potential reduce by 89.1 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, ThINKingDANCE needs image optimization as it can save up to 89.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.8 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 2.8 kB or 27% of the original size.
Number of requests can be reduced by 8 (22%)
37
29
The browser has sent 37 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 9 to 1 for JavaScripts and as a result speed up the page load time.
thinkingdance.net
163 ms
thinkingdance.net
412 ms
jquery-ui-1.8.9.custom.css
150 ms
overlay_style.css
228 ms
layout.css
228 ms
common.js
301 ms
jquery.min.js
21 ms
jquery-ui-1.8.14.custom.min.js
449 ms
jquery.scrollTo-1.4.2-min.js
229 ms
overlay.js
225 ms
AC_RunActiveContent.js
301 ms
easySlider.js
316 ms
jquery.colorbox.js
315 ms
js
70 ms
addthis_widget.js
139 ms
aller_rg-webfont.woff
76 ms
btn_donateCC_LG.gif
50 ms
social-media-facebook.png
76 ms
older.gif
79 ms
newer.gif
79 ms
The_cast_of_Poor_Judge_by_Pig_Iron_Theatre_Company_Photo_by_Eli_Eisenstein.jpg
149 ms
transBlack-50.png
77 ms
HomepageImage_RushJohnston_09.19.24.jpg
76 ms
clapping_3.png
224 ms
ZOEMAY-8_copy.jpg
152 ms
After_Yes.jpeg
225 ms
IMG_3749.jpg
152 ms
Pic_466.jpg
152 ms
P1166056_edit1.jpg
224 ms
FutureJam94-1.png
228 ms
Zoe_Rabinowitz_photo_Sara_Radin_performance_9-20-24_IMG_579737.jpg
226 ms
complexions-contemporary-ballet.jpeg
228 ms
photo_1_by_Jano_Cohen48.jpg
298 ms
PCF.jpg
300 ms
PCA_logo.jpg
300 ms
102124_ThinkingDance_Limon.jpg
447 ms
300x200_thinkingdance.jpg
301 ms
Catja%20social%20media%20drafts%20(1).png
522 ms
Subscribe.png
373 ms
pixel.gif
45 ms
dot.gif
342 ms
Moms_typewriter-webfont.woff
415 ms
aller_bd-webfont.woff
344 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
Browser errors were logged to the console
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
Tap targets are not sized appropriately
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: