2.8 sec in total
66 ms
2.5 sec
226 ms
Welcome to aileyextension.com homepage info - get ready to check Ailey Extension best content for United States right away, or after learning these important things about aileyextension.com
Ailey Extension from Alvin Ailey. Learn about our in-studio dance classes in New York City or sign up for an online class. All levels, ages, and styles.
Visit aileyextension.comWe analyzed Aileyextension.com page load time and found that the first response time was 66 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
aileyextension.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value31.0 s
0/100
25%
Value25.4 s
0/100
10%
Value22,480 ms
0/100
30%
Value0.094
91/100
15%
Value57.4 s
0/100
10%
66 ms
726 ms
46 ms
30 ms
24 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 30% of them (42 requests) were addressed to the original Aileyextension.com, 22% (31 requests) were made to S3.amazonaws.com and 7% (9 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (735 ms) relates to the external source Widgets.healcode.com.
Page size can be reduced by 761.4 kB (49%)
1.6 MB
800.9 kB
In fact, the total size of Aileyextension.com main page is 1.6 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 777.9 kB which makes up the majority of the site volume.
Potential reduce by 46.4 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 7.9 kB, which is 13% 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 46.4 kB or 79% of the original size.
Potential reduce by 62.5 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. Ailey Extension images are well optimized though.
Potential reduce by 571.1 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 571.1 kB or 73% of the original size.
Potential reduce by 81.5 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. Aileyextension.com needs all CSS files to be minified and compressed as it can save up to 81.5 kB or 87% of the original size.
Number of requests can be reduced by 80 (70%)
114
34
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ailey Extension. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
aileyextension.com
66 ms
www.aileyextension.com
726 ms
css_f75122c16883697651bb785d5afd8be7.css
46 ms
jquery.min.js
30 ms
drupal.js
24 ms
ajax_load.js
17 ms
jquery.colorbox-min.js
24 ms
colorbox.js
18 ms
colorbox_default_style.js
25 ms
colorbox_load.js
26 ms
colorbox_inline.js
29 ms
ailey_mobile_tweaks.js
32 ms
breaking_news.js
32 ms
env_highlight.js
34 ms
performance_links.js
33 ms
panels.js
39 ms
aaadt.lightbox.js
69 ms
jquery.validate.js
71 ms
global.js
73 ms
jquery.ga.js
69 ms
mobile-response.js
71 ms
froogaloop2.min.js
5 ms
all.js
265 ms
conversion.js
17 ms
analytics.js
7 ms
app.v1.js
52 ms
0h9g50.js
27 ms
fbds.js
88 ms
facebook-label.png
30 ms
at
49 ms
btn_back_to_theater.png
17 ms
header-kick-noglow_000_000.png
16 ms
sign-up-button.png
23 ms
blog-label.png
17 ms
blog-icon.png
17 ms
EXT_Homepage_2015Sept.jpg
117 ms
linkid.js
9 ms
collect
4 ms
collect
56 ms
23 ms
1458407251
14 ms
at
119 ms
ep
21 ms
19 ms
ecc
19 ms
16 ms
pixel
24 ms
pixel
16 ms
css_d62ffe2d1e4f5e42317e0d64a2e0b81e.css
11 ms
cm
22 ms
ua
67 ms
extension-logo-w-sub.png
18 ms
border_header.png
14 ms
bg_home_cbg.png
14 ms
22 ms
hc_widget.js
35 ms
ermcm
23 ms
xd_arbiter.php
161 ms
xd_arbiter.php
288 ms
healcode-573bc1f0a94b46097b195ab0f19d05eecbdb448fe9a89c0716bc72e507c8b644.js
120 ms
ajax-loader-c1cf81bef2ea82eaa43265a5ff786b7cd74e7d5f4f2de104b586f092ca0fb886.gif
102 ms
bg_footer.png
21 ms
bg_search.png
18 ms
89 ms
81 ms
bounce
52 ms
loading_animation.gif
53 ms
jquery.hoverIntent.minified.js
39 ms
jquery.cycle.all.min.js
43 ms
jquery.easing.v13.js
24 ms
jquery.cycle.all.min.js
31 ms
jquery-ui-1.7.2.custom.min.js
29 ms
ping
51 ms
33 ms
controls.png
18 ms
45 ms
30 ms
42 ms
jquery.hoverIntent.minified.js
15 ms
jquery.atooltip.js
14 ms
like.php
72 ms
24 ms
roundtrip.js
8 ms
x-tag-components-7eabff25536a3b3f89f97b68df54a72673ca74cebb915fb4af19255dc5e88616.js
31 ms
healcode.yepnope-23af02e66170f2455f54b54cf8bbb19d15a2446cd81dfcbb9c4390c5a0ef4a4a.js
40 ms
qeKvIRsJabD.js
347 ms
LVx-xkvaJ0b.png
396 ms
jquery.min.js
76 ms
jquery-ui.widget-396bc6c8cc9d453826cb92486c1bd89b30bc0b10d7eeff3fefbcd2ebccafe857.js
43 ms
jquery_ujs-95e05b917009519148c662c7fb1d60ad2437530ec915c2189ed2ab13275307c8.js
25 ms
jquery-ui.widget-9ce3f9262a1193451327715095bfeefd7def930a01eef7cff0065aa48f9af0f1.css
141 ms
hcjq-3048c2ae28d04f1d340fc1b26b53a810d585b42adf06aa441935884b32e085b9.js
40 ms
filter_sessions-b4977882c514f721e38eaaf9a2536ae81110216e232f550065331e558a447fa9.js
44 ms
jquery-ui-datepicker-localization-9a5cb64022f344501b9d003093b0409dc66baaa82a7d5ccc7b3e5167771b49f4.js
43 ms
schedule-ee35e88573593ba1a20ce1dc46b950e71a544335cf4fcee5ced5e2c9cc7e7a8c.js
40 ms
widget-d46590d6bf0d3239be65144558fc4bba5ff86113f8d72be3abf5e72c0faed30f.js
45 ms
application-edb4f8603e739a9e01a5fae56cb0325ec8331bbe7433dc506f80fdaeb3470cff.js
46 ms
AUNAU57OWFFXTEUMOIW3PZ.js
137 ms
jquery.min.js
55 ms
jquery-ui.widget-396bc6c8cc9d453826cb92486c1bd89b30bc0b10d7eeff3fefbcd2ebccafe857.js
15 ms
jquery_ujs-95e05b917009519148c662c7fb1d60ad2437530ec915c2189ed2ab13275307c8.js
12 ms
jquery-ui.widget-9ce3f9262a1193451327715095bfeefd7def930a01eef7cff0065aa48f9af0f1.css
12 ms
hcjq-3048c2ae28d04f1d340fc1b26b53a810d585b42adf06aa441935884b32e085b9.js
19 ms
out
16 ms
26 ms
out
13 ms
out
14 ms
out
14 ms
out
17 ms
out
19 ms
out
18 ms
adsct
81 ms
pxj
30 ms
u.php
29 ms
pixel
49 ms
41 ms
filter_sessions-b4977882c514f721e38eaaf9a2536ae81110216e232f550065331e558a447fa9.js
83 ms
377928.gif
10 ms
Pug
21 ms
sd
4 ms
in
8 ms
in
5 ms
jquery-ui-datepicker-localization-9a5cb64022f344501b9d003093b0409dc66baaa82a7d5ccc7b3e5167771b49f4.js
7 ms
schedule-ee35e88573593ba1a20ce1dc46b950e71a544335cf4fcee5ced5e2c9cc7e7a8c.js
8 ms
widget-d46590d6bf0d3239be65144558fc4bba5ff86113f8d72be3abf5e72c0faed30f.js
12 ms
application-edb4f8603e739a9e01a5fae56cb0325ec8331bbe7433dc506f80fdaeb3470cff.js
8 ms
store_deploy_url.json
52 ms
55212485f69.js
19 ms
print-d1759857cb4b677716a25434a84a7c954fb6ca0f44cabdb5a88b9873128e337e.png
28 ms
healcode-b5160abe8d8ca68c088fa96236522ff97c2d688ffedd6491e62357e0efbbd55f.css
25 ms
55212485f69.availability
735 ms
spinner-5f564ddf940c9fc6373138d8a3970897a7ef7f6b4bee5e463c77a56ba63485ec.gif
16 ms
calendar-20px-0b54dc182795843e199994c790cb47151cd0fe9ab659d4a8150df70e48948540.png
16 ms
healcode-powered-by-mini-bc4cc9736724a0164d544df54eaf3152fa8750a86a72512e7d1d7bbe4966c00b.png
16 ms
modal-b2576b077b1b4b60ccca6383b38b7aedca70a9162b5f9f66e25ad4a1bf1a048e.js
8 ms
modal-03a190afcb53a41a4a0d390840683d7642e5e1d61b645d08bb1db46e2ff1fafd.css
12 ms
modal-b2576b077b1b4b60ccca6383b38b7aedca70a9162b5f9f66e25ad4a1bf1a048e.js
10 ms
modal-03a190afcb53a41a4a0d390840683d7642e5e1d61b645d08bb1db46e2ff1fafd.css
7 ms
aileyextension.com 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
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
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
aileyextension.com 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
Browser errors were logged to the console
aileyextension.com 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
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 Aileyextension.com 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 Aileyextension.com 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.
aileyextension.com
Open Graph data is detected on the main page of Ailey Extension. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: