Tools & Wizards About Us
sonic-pi.net screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 32

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

sonic-pi.net

Sonic Pi - The Live Coding Music Synth for Everyone

Page Load Speed

6.8 sec in total

First Response

174 ms

Resources Loaded

3.5 sec

Page Rendered

3.1 sec

sonic-pi.net screenshot

About Website

Visit sonic-pi.net now to see the best up-to-date Sonic Pi content for United States and also check out these interesting facts you probably never knew about sonic-pi.net

Sonic Pi is a new kind of instrument for a new generation of musicians. It is simple to learn, powerful enough for live performances and free to download.

Visit sonic-pi.net

Key Findings

We analyzed Sonic-pi.net page load time and found that the first response time was 174 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

sonic-pi.net performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value13,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.94

3/100

15%

TTI (Time to Interactive)

Value21.9 s

1/100

10%

Network Requests Diagram

sonic-pi.net

174 ms

sonic-pi.net

443 ms

not.the.skin.css

78 ms

circle.player.css

154 ms

skel.css

227 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 71% of them (60 requests) were addressed to the original Sonic-pi.net, 13% (11 requests) were made to Youtube.com and 8% (7 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Sonic-pi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (25%)

Content Size

5.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sonic-pi.net main page is 5.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. Only a small number of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 67.7 kB

  • Original 78.6 kB
  • After minification 62.8 kB
  • After compression 10.9 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 15.8 kB, which is 20% 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 67.7 kB or 86% of the original size.

Image Optimization

-22%

Potential reduce by 1.0 MB

  • Original 4.5 MB
  • After minification 3.5 MB

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, Sonic Pi needs image optimization as it can save up to 1.0 MB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 145.7 kB

  • Original 393.6 kB
  • After minification 382.3 kB
  • After compression 248.0 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 145.7 kB or 37% of the original size.

CSS Optimization

-46%

Potential reduce by 63.2 kB

  • Original 136.5 kB
  • After minification 116.4 kB
  • After compression 73.3 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. Sonic-pi.net needs all CSS files to be minified and compressed as it can save up to 63.2 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (27%)

Requests Now

79

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sonic Pi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

sonic-pi.net

sonic-pi.net

174 ms

sonic-pi.net

sonic-pi.net

443 ms

not.the.skin.css

not.the.skin.css

78 ms

circle.player.css

circle.player.css

154 ms

skel.css

skel.css

227 ms

style2.css

style2.css

300 ms

style-desktop.css

style-desktop.css

227 ms

jquery.min.js

jquery.min.js

379 ms

jquery.scrolly.min.js

jquery.scrolly.min.js

227 ms

skel.min.js

skel.min.js

230 ms

init.js

init.js

301 ms

jquery.transform2d.js

jquery.transform2d.js

375 ms

jquery.grab.js

jquery.grab.js

302 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

383 ms

mod.csstransforms.min.js

mod.csstransforms.min.js

373 ms

circle.player.js

circle.player.js

374 ms

font-awesome.min.css

font-awesome.min.css

155 ms

style.css

style.css

78 ms

w2s1DK1w3WI

w2s1DK1w3WI

262 ms

zdc94RAX9UY

zdc94RAX9UY

372 ms

oDHumac84aw

oDHumac84aw

266 ms

cydH_JAgSfg

cydH_JAgSfg

258 ms

7sEMKXrRaAs

7sEMKXrRaAs

257 ms

TK1mBqKvIyU

TK1mBqKvIyU

262 ms

OLLwG_SN8oo

OLLwG_SN8oo

943 ms

logo.png

logo.png

128 ms

bg.png

bg.png

124 ms

sonic-pi-connectivity.svg

sonic-pi-connectivity.svg

772 ms

dashbit.png

dashbit.png

89 ms

alembic-logo.svg

alembic-logo.svg

123 ms

Wyeworks-Logo-Black-Red.png

Wyeworks-Logo-Black-Red.png

772 ms

patreon-fierycoral.png

patreon-fierycoral.png

784 ms

github-sponsors.png

github-sponsors.png

784 ms

in_thread_screen.png

in_thread_screen.png

1136 ms

live-coding-education.png

live-coding-education.png

787 ms

music_note.png

music_note.png

881 ms

blackboard.png

blackboard.png

785 ms

code-border.png

code-border.png

882 ms

book.png

book.png

882 ms

bgr.png

bgr.png

881 ms

controls.jpg

controls.jpg

882 ms

music_commission.jpg

music_commission.jpg

1009 ms

naked_scientists.png

naked_scientists.png

1136 ms

big_bang.jpg

big_bang.jpg

1136 ms

mehackit_kokoa.png

mehackit_kokoa.png

1137 ms

convo.jpg

convo.jpg

1135 ms

codebus.png

codebus.png

1136 ms

google.png

google.png

1208 ms

mt-awardlogo.png

mt-awardlogo.png

1908 ms

rollingstone.png

rollingstone.png

1207 ms

iss.jpg

iss.jpg

1574 ms

mistajam.jpg

mistajam.jpg

1208 ms

Red_daft_punk.PNG

Red_daft_punk.PNG

1208 ms

newsround.png

newsround.png

1576 ms

sonic-dreams.png

sonic-dreams.png

1575 ms

summerschool.jpg

summerschool.jpg

1573 ms

rpi-logo.png

rpi-logo.png

1573 ms

arm64-chip.png

arm64-chip.png

1691 ms

box3.png

box3.png

1691 ms

unibody_windows.png

unibody_windows.png

1691 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1692 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

48 ms

base.js

base.js

116 ms

intel-cpu.png

intel-cpu.png

1602 ms

windows.png

windows.png

1782 ms

apple-cpu.png

apple-cpu.png

1783 ms

apple.png

apple.png

1727 ms

ad_status.js

ad_status.js

662 ms

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

jDVVIT4ZwDHfBiET8TcWj790JrYgF6qU1g_sOcBWI_w.js

490 ms

embed.js

embed.js

301 ms

buffer.png

buffer.png

1127 ms

progress.png

progress.png

1123 ms

id

id

131 ms

Create

Create

553 ms

Create

Create

554 ms

Create

Create

554 ms

Create

Create

552 ms

Create

Create

769 ms

Create

Create

808 ms

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

37 ms

Create

Create

743 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

632 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

634 ms

Accessibility Review

sonic-pi.net accessibility score

32

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

sonic-pi.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sonic-pi.net SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sonic-pi.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sonic-pi.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.

Social Sharing Optimization

sonic-pi.net

Open Graph description is not detected on the main page of Sonic Pi. 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: