Tools & Wizards About Us
ccrma.stanford.edu screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

ccrma.stanford.edu

Center for Computer Research in Music and Acoustics | CCRMA

Page Load Speed

3.2 sec in total

First Response

251 ms

Resources Loaded

2.5 sec

Page Rendered

417 ms

ccrma.stanford.edu screenshot

About Website

Visit ccrma.stanford.edu now to see the best up-to-date CCRMA Stanford content for United States and also check out these interesting facts you probably never knew about ccrma.stanford.edu

Multi-disciplinary facility where composers and researchers use computer-based technology as an artistic medium and as a research tool.

Visit ccrma.stanford.edu

Key Findings

We analyzed Ccrma.stanford.edu page load time and found that the first response time was 251 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ccrma.stanford.edu performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

ccrma.stanford.edu

251 ms

ccrma.stanford.edu

374 ms

d8cb3486c453b26bfaebd5cc8164a287.css

252 ms

css_4b08a8c10decc0e819152aa066e9a82a.css

420 ms

js_156b71be8de411b5d89ce56e0ea65929.js

440 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 96% of them (26 requests) were addressed to the original Ccrma.stanford.edu, 4% (1 request) were made to Blog.leapmotion.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ccrma.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.1 kB (13%)

Content Size

1.1 MB

After Optimization

976.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ccrma.stanford.edu main page is 1.1 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. 25% of websites need less resources to load. Images take 983.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.7 kB

  • Original 42.9 kB
  • After minification 37.5 kB
  • After compression 9.2 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 5.3 kB, which is 12% 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 33.7 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 44.8 kB

  • Original 983.1 kB
  • After minification 938.3 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. CCRMA Stanford images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 27.4 kB

  • Original 45.0 kB
  • After minification 37.2 kB
  • After compression 17.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 27.4 kB or 61% of the original size.

CSS Optimization

-79%

Potential reduce by 43.2 kB

  • Original 54.6 kB
  • After minification 50.9 kB
  • After compression 11.4 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. Ccrma.stanford.edu needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (24%)

Requests Now

25

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CCRMA Stanford. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

ccrma.stanford.edu

ccrma.stanford.edu

251 ms

ccrma.stanford.edu

ccrma.stanford.edu

374 ms

d8cb3486c453b26bfaebd5cc8164a287.css

d8cb3486c453b26bfaebd5cc8164a287.css

252 ms

css_4b08a8c10decc0e819152aa066e9a82a.css

css_4b08a8c10decc0e819152aa066e9a82a.css

420 ms

js_156b71be8de411b5d89ce56e0ea65929.js

js_156b71be8de411b5d89ce56e0ea65929.js

440 ms

slork-bing-800.jpg

slork-bing-800.jpg

352 ms

background.png

background.png

985 ms

karma_logo.png

karma_logo.png

334 ms

shadow-t.png

shadow-t.png

251 ms

corner-bits.png

corner-bits.png

252 ms

shadow-l.png

shadow-l.png

253 ms

shadow-r.png

shadow-r.png

258 ms

shadow-b.png

shadow-b.png

497 ms

bischoff-5.jpg

bischoff-5.jpg

665 ms

roger_linnstrument.jpg

roger_linnstrument.jpg

670 ms

surface_tension_ripples.jpg

surface_tension_ripples.jpg

598 ms

feed.png

feed.png

584 ms

decorr_pic.jpg

decorr_pic.jpg

743 ms

untitled1.jpg

untitled1.jpg

847 ms

jean.jpg

jean.jpg

844 ms

doug.jpg

doug.jpg

910 ms

background-block1.png

background-block1.png

1340 ms

plus.png

plus.png

994 ms

stanford_logo.gif

stanford_logo.gif

1092 ms

facebook_icon.jpg

facebook_icon.jpg

1102 ms

music_logo.gif

music_logo.gif

1163 ms

css_7fd52246dd4c2ef1ec8a4da00fb246c3.css

css_7fd52246dd4c2ef1ec8a4da00fb246c3.css

84 ms

Accessibility Review

ccrma.stanford.edu accessibility score

82

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ccrma.stanford.edu best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ccrma.stanford.edu SEO score

71

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ccrma.stanford.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 Ccrma.stanford.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.

Social Sharing Optimization

ccrma.stanford.edu

Open Graph description is not detected on the main page of CCRMA Stanford. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: