Tools & Wizards About Us
midi.website screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

midi.website

MIDI Touchpad - Trackpad MIDI Controller

Page Load Speed

1.3 sec in total

First Response

41 ms

Resources Loaded

860 ms

Page Rendered

433 ms

midi.website screenshot

About Website

Click here to check amazing MIDI content. Otherwise, check out these important facts you probably never knew about midi.website

MIDI Touchpad transforms Trackpad into a MIDI controller

Visit midi.website

Key Findings

We analyzed Midi.website page load time and found that the first response time was 41 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

midi.website performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

midi.website

41 ms

midi.website

53 ms

js

90 ms

bootstrap.min.css

52 ms

font-awesome.min.css

68 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 38% of them (15 requests) were addressed to the original Midi.website, 31% (12 requests) were made to Fonts.gstatic.com and 13% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (328 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.4 kB (47%)

Content Size

596.8 kB

After Optimization

313.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Midi.website main page is 596.8 kB. 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 327.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 8.1 kB

  • Original 10.7 kB
  • After minification 6.8 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 36% 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 8.1 kB or 76% of the original size.

JavaScript Optimization

-34%

Potential reduce by 111.1 kB

  • Original 327.4 kB
  • After minification 327.4 kB
  • After compression 216.3 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 111.1 kB or 34% of the original size.

CSS Optimization

-63%

Potential reduce by 164.1 kB

  • Original 258.7 kB
  • After minification 254.8 kB
  • After compression 94.6 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. Midi.website needs all CSS files to be minified and compressed as it can save up to 164.1 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (68%)

Requests Now

25

After Optimization

8

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

midi.website

midi.website

41 ms

midi.website

midi.website

53 ms

js

js

90 ms

bootstrap.min.css

bootstrap.min.css

52 ms

font-awesome.min.css

font-awesome.min.css

68 ms

simple-line-icons.css

simple-line-icons.css

61 ms

css

css

74 ms

css

css

85 ms

css

css

109 ms

device-mockups.min.css

device-mockups.min.css

64 ms

new-age.css

new-age.css

57 ms

Krjvgq7UtBM

Krjvgq7UtBM

206 ms

jquery.min.js

jquery.min.js

71 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

71 ms

jquery.easing.min.js

jquery.easing.min.js

64 ms

new-age.min.js

new-age.min.js

64 ms

Get_MIDI_Trackpad_for_Mac.png

Get_MIDI_Trackpad_for_Mac.png

71 ms

midi_trackpad_controller.png

midi_trackpad_controller.png

197 ms

bg-pattern.png

bg-pattern.png

10 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd5a7dvg.ttf

84 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc5a7dvg.ttf

92 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd5a7dvg.ttf

108 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd5a7dvg.ttf

99 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd5a7dvg.ttf

108 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba5a7dvg.ttf

100 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a5a7dvg.ttf

108 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja5a7dvg.ttf

108 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa5a7dvg.ttf

111 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf

328 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

10 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

47 ms

base.js

base.js

106 ms

ad_status.js

ad_status.js

223 ms

62mh7a0fQTK9Uep7g0y3snI_COPB4Zut5ZKHWl7ffDc.js

62mh7a0fQTK9Uep7g0y3snI_COPB4Zut5ZKHWl7ffDc.js

149 ms

embed.js

embed.js

45 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

38 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

id

id

46 ms

Accessibility Review

midi.website accessibility score

93

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

midi.website 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

midi.website SEO score

100

Search Engine Optimization Advices

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

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 Midi.website 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 Midi.website 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

midi.website

Open Graph data is detected on the main page of MIDI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: