1.1 sec in total
55 ms
750 ms
315 ms
Visit music.yale.edu now to see the best up-to-date Music Yale content for United States and also check out these interesting facts you probably never knew about music.yale.edu
admissions
Visit music.yale.eduWe analyzed Music.yale.edu page load time and found that the first response time was 55 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
music.yale.edu performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value12.9 s
0/100
25%
Value5.4 s
57/100
10%
Value680 ms
43/100
30%
Value0
100/100
15%
Value12.1 s
16/100
10%
55 ms
19 ms
24 ms
22 ms
23 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 78% of them (70 requests) were addressed to the original Music.yale.edu, 6% (5 requests) were made to Match.adsrvr.org and 3% (3 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (210 ms) relates to the external source Ysm.wpengine.com.
Page size can be reduced by 402.1 kB (24%)
1.7 MB
1.3 MB
In fact, the total size of Music.yale.edu main page is 1.7 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 51.6 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 51.6 kB or 83% of the original size.
Potential reduce by 23.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. Music Yale images are well optimized though.
Potential reduce by 207.7 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 207.7 kB or 64% of the original size.
Potential reduce by 119.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. Music.yale.edu needs all CSS files to be minified and compressed as it can save up to 119.7 kB or 84% of the original size.
Number of requests can be reduced by 41 (55%)
75
34
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Music Yale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
music.yale.edu
55 ms
style.css
19 ms
stylesheet.css
24 ms
jquery.fancybox.css
22 ms
jquery.fancybox-buttons.css
23 ms
jquery.fancybox-thumbs.css
26 ms
flashblock.css
26 ms
player.css
24 ms
toggle-box.css
26 ms
bbpress.css
27 ms
twitter.css
29 ms
editor-styles.css
29 ms
quick-chat.css
28 ms
basic.css
29 ms
custom.css
32 ms
jquery.js
42 ms
jquery-migrate.min.js
37 ms
twitter.js
38 ms
jquery.carouFredSel-5.5.0-packed.js
58 ms
jquery.isotope.min.js
38 ms
jquery.countdown.min.js
40 ms
jquery.fancybox.js
78 ms
jquery.fancybox-buttons.js
74 ms
jquery.fancybox-thumbs.js
76 ms
jquery.fancybox-media.js
81 ms
soundmanager2-nodebug-jsmin.js
81 ms
toggle-box.js
86 ms
Bootstrap.js
13 ms
hoverIntent.js
174 ms
ubermenu.min.js
176 ms
comment-reply.min.js
178 ms
editor.js
179 ms
jquery.c00kie.js
181 ms
quick-chat-load.js
181 ms
piano-jazz-h.jpg
210 ms
blocker-horizontal.jpg
147 ms
theofanidis-vees-h.jpg
150 ms
homepage-logo-350x28.png
130 ms
icn-search.gif
131 ms
top-gradient.png
132 ms
bg-nav-transparent.png
133 ms
nav-seperator.png
132 ms
YSM-app-128x128.png
135 ms
video-nav.jpg
133 ms
collection-nav.jpg
133 ms
gig-nav.jpg
133 ms
audio-tour-home-1200x550.jpg
135 ms
iPad-splash-1200x550-1445366311.jpg
140 ms
midsummer-home-1200x550.jpg
137 ms
music-makers-home.jpg-1200x550.jpeg
137 ms
brentano-home-1200x550-1410548783.jpg
137 ms
sterling-library-home-1200x550.jpg
140 ms
icn-arrow-left.png
135 ms
icn-arrow-right.png
138 ms
bg-content.jpg
139 ms
chamber-music-practice-300x170.jpg
140 ms
bg-cal-blue.jpg
141 ms
gene-kimball-nhregister-web-300x170-1442336924.jpg
142 ms
rathey-300x170.jpg
142 ms
interchange-300x170.jpg
141 ms
bg-gold.png
144 ms
icn-camera-white.png
143 ms
video-button.png
143 ms
bg-footer.jpg
144 ms
social-icons.png
145 ms
logo-yale.png
144 ms
ga.js
118 ms
serverComponent.php
48 ms
proximanova-reg-webfont.woff
47 ms
proximanova-sbold-webfont.woff
48 ms
proximanova-bold-webfont.woff
48 ms
yaledesign-medium-webfont.woff
48 ms
yaledesign-bold-webfont.woff
48 ms
yaledesign-italic-webfont.woff
49 ms
yaledesign-bolditalic-webfont.woff
48 ms
yaledessmacap-webfont.woff
41 ms
__utm.gif
14 ms
ed5d2f872e0d9bff5d55168e04c11d43.js
8 ms
collect
82 ms
fbds.js
156 ms
activityi;src=4353631;type=invmedia;cat=luitlfps;ord=8482324066571.892
83 ms
80 ms
generic
33 ms
pixel
41 ms
generic
4 ms
8 ms
match
24 ms
generic
5 ms
generic
4 ms
24 ms
music.yale.edu accessibility score
music.yale.edu 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
music.yale.edu 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
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 Music.yale.edu 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 Music.yale.edu 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.
music.yale.edu
Open Graph data is detected on the main page of Music Yale. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: