6.1 sec in total
862 ms
2.7 sec
2.6 sec
Click here to check amazing Current NYFA content for United States. Otherwise, check out these important facts you probably never knew about current.nyfa.org
New York Foundation for the Arts. Est. 1971, © 2014.
Visit current.nyfa.orgWe analyzed Current.nyfa.org page load time and found that the first response time was 862 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
current.nyfa.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value6.4 s
10/100
25%
Value5.2 s
60/100
10%
Value260 ms
83/100
30%
Value0.012
100/100
15%
Value6.7 s
56/100
10%
862 ms
16 ms
154 ms
34 ms
18 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Current.nyfa.org, 18% (21 requests) were made to Static.tumblr.com and 13% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 1.4 MB (31%)
4.5 MB
3.1 MB
In fact, the total size of Current.nyfa.org main page is 4.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 559.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 559.8 kB or 73% of the original size.
Potential reduce by 126.7 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. Current NYFA images are well optimized though.
Potential reduce by 671.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 671.9 kB or 63% of the original size.
Potential reduce by 56.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. Current.nyfa.org needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 58% of the original size.
Number of requests can be reduced by 38 (37%)
104
66
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Current NYFA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
current.nyfa.org
862 ms
pre_tumblelog.js
16 ms
piy3ezh.js
154 ms
font.css
34 ms
reset-min.css
18 ms
solaris_css_v1.2.1_nyfa_edit_v.1.css
21 ms
solaris-2x.css
223 ms
jquery.fancybox-1.3.1.tumblr.css
220 ms
nivo-slider.css
16 ms
custom-nivo-slider.css
19 ms
jquery-1.4.4.min.js
35 ms
jquery.blend-min.js
24 ms
jquery.timeago.js
25 ms
jquery.fancybox-1.3.1.pack.js
30 ms
jquery.jscrollpane-min.js
30 ms
jquery.nivo.slider.pack.js
34 ms
solaris-1.2.1.js
37 ms
tumblelog_post_message_queue.js
10 ms
stylesheet.css
13 ms
widgets.js
84 ms
addthis_widget.js
25 ms
tweets.js
419 ms
index.js
24 ms
analytics.js
14 ms
d
156 ms
collect
13 ms
divider.png
75 ms
tumblr_inline_o49b4uvUjq1s8x2z5_500.jpg
66 ms
tumblr_inline_o498zbd3gs1s8x2z5_500.jpg
519 ms
tumblr_inline_o47b58KwzR1s8x2z5_500.png
329 ms
tumblr_inline_o46x59wd2c1s8x2z5_500.jpg
365 ms
tumblr_inline_o44w6lx66q1s8x2z5_500.png
1016 ms
tumblr_inline_o43awg8KiW1s8x2z5_500.png
1013 ms
tumblr_inline_o43axn3g1N1s8x2z5_250.png
381 ms
tumblr_inline_o3w4qkeP1G1s8x2z5_500.jpg
487 ms
tumblr_inline_o41bzpG2k51s8x2z5_500.png
402 ms
tumblr_inline_o3qu9u85kq1s8x2z5_500.png
419 ms
tumblr_inline_o3oxchKfwF1s8x2z5_500.jpg
489 ms
tumblr_inline_o3opsgsWQe1s8x2z5_500.jpg
487 ms
tumblr_inline_o3j9vfYAth1s8x2z5_500.jpg
289 ms
search-go-2x.png
64 ms
top-nav.png
62 ms
top-media.png
61 ms
join_mailing.png
153 ms
tumblr_static_blog_logo_rev.png
62 ms
tumblr_inline_o496q443xz1s8x2z5_500.jpg
66 ms
tumblr_inline_o41qgzPKzf1s8x2z5_500.jpg
64 ms
tumblr_inline_o3w752ipCh1s8x2z5_500.jpg
62 ms
tumblr_inline_o3w9g0nBcZ1s8x2z5_500.png
63 ms
tumblr_inline_o3snajZc621s8x2z5_500.jpg
63 ms
tumblr_inline_o3hifmPOzc1s8x2z5_500.png
65 ms
p.gif
82 ms
O1r6eNRuer3T8BzdQwGk=
21 ms
d7b29azZ8Hyl4z9hjMBt
20 ms
Calluna-Regular-webfont.woff
20 ms
AQRXHOlAAAA
18 ms
fIw6w=
18 ms
Calluna-Black-webfont.woff
19 ms
Calluna-It-webfont.woff
18 ms
2BJLLbPcCiutstoaa62TZb0NNtpkc3Biq22222GnXXbbY6999jvgoEMOO+KoY4474aRTTjvjbHDqvAsuuuSyK64GY667Edy6Fcy546577nvgYZ5rjzyW64mnngUvX3jpldfeeOud9z78BBFcc6UAAAA=
16 ms
3yMOs
14 ms
Calluna-BoldIt-webfont.woff
64 ms
O1r6eNRuer3T8B1qMwGk=
13 ms
AdajMBp
12 ms
sprite.png
12 ms
like.php
190 ms
like.php
166 ms
like.php
244 ms
like.php
217 ms
like.php
215 ms
like.php
197 ms
like.php
196 ms
like.php
188 ms
like.php
593 ms
like.php
590 ms
qeKvIRsJabD.js
517 ms
LVx-xkvaJ0b.png
102 ms
like.php
527 ms
like.php
564 ms
like.php
478 ms
ga.js
442 ms
like.php
500 ms
impixu
512 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
488 ms
300lo.json
369 ms
counter.5524cceca805eb4b9b2b.js
282 ms
impixu
151 ms
like.php
145 ms
analytics.html
137 ms
login_check.html
55 ms
sh.8e5f85691f9aaa082472a194.html
84 ms
__utm.gif
109 ms
shares.json
41 ms
shares.json
39 ms
shares.json
39 ms
shares.json
37 ms
shares.json
39 ms
shares.json
39 ms
shares.json
37 ms
shares.json
88 ms
shares.json
36 ms
shares.json
86 ms
shares.json
83 ms
shares.json
81 ms
shares.json
79 ms
shares.json
79 ms
shares.json
79 ms
rapid-3.36.js
79 ms
rapidworker-1.2.js
82 ms
ga.js
71 ms
analytics.js
64 ms
cs.js
98 ms
yql
175 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
55 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
116 ms
__utm.gif
74 ms
cedexis.radar.js
8 ms
current.nyfa.org 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.
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
current.nyfa.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
current.nyfa.org SEO score
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 Current.nyfa.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 Current.nyfa.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.
current.nyfa.org
Open Graph data is detected on the main page of Current NYFA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: