midi-ld.github.io

Midi-ld.github.io

#1,734,212 Global
MIDI Linked Data
Last Updated 225 days ago
     
This can take up to 60 seconds. Please wait...

Domain Summary

What is the traffic rank for Midi-ld.github.io?

Midi-ld.github.io ranks #1,734,212 globally on HypeStat.

What percent of global Internet users visit Midi-ld.github.io?

<0.000001% of global Internet users visit Midi-ld.github.io

How many people visit Midi-ld.github.io each day?

Midi-ld.github.io receives approximately 20 visitors and 21 page impressions per day.

Which countries does Midi-ld.github.io receive most of its visitors from?

Midi-ld.github.io is mostly visited by people located in Australia.

How much Midi-ld.github.io can earn?

Midi-ld.github.io should earn about $0.08/day from advertising revenue.

What is Midi-ld.github.io estimated value?

Estimated value of Midi-ld.github.io is $73.44.

What IP addresses does Midi-ld.github.io resolve to?

Midi-ld.github.io resolves to the IP addresses 2606:50c0:8001::153, 185.199.108.153.

Where are Midi-ld.github.io servers located in?

Midi-ld.github.io has servers located in United States.

midi-ld.github.io Profile

Title
MIDI Linked Data
The website midi-ld.github.io serves as a platform for exploring and visualizing MIDI files through the use of a lightweight web-based application designed for educational and analytical purposes. Its primary features include the ability to upload MIDI files, view their structural components such as tracks and notes, and play back the music in a user-friendly interface that emphasizes clarity and accessibility. The site employs a minimalist design, focusing on functionality with intuitive navigation that facilitates ease of use for both novice and experienced users. Overall, midi-ld.github.io aims to enhance understanding of MIDI data and its applications in music composition and analysis.
Edit Site Info

What technologies does midi-ld.github.io use?

These are the technologies used at midi-ld.github.io. midi-ld.github.io has a total of 7 technologies installed in 6 different categories.

midi-ld.github.io Traffic Analysis

Midi-ld.github.io is ranked #1,734,212 in the world. This website is viewed by an estimated 20 visitors daily, generating a total of 21 pageviews. This equates to about 606 monthly visitors. Midi-ld.github.io traffic has decreased by 96.29% compared to last month.

Daily Visitors
20
20 unique
▼ 96.29%
Monthly Visits
606
▼ 96.29%
Pages per Visit
1.06
Visit Duration
n/a
Bounce Rate
33.82%
Is this your site?Verify your site's metrics.
Daily Unique Visitors
20
Monthly Visits
606
Pages per Visit
1.06
Daily Pageviews
21
Avg. Visit Duration
n/a
Bounce Rate
33.82%
Global Reach
<0.000001%
Monthly Visits (SEMrush)
13
Monthly Unique Visitors (SEMrush)
13
Monthly Visits (SimilarWeb)
583
HypeRank
1,734,212
SEMrush Rank
10,373,652

*All traffic values are estimates only.

Traffic Sources

Direct
0%
Referral
0%
Search
100.00%
Social
0%
Paid
0%

Desktop vs Mobile

Desktop
100.00%
Mobile
0%

Total Visits Last 3 Months

38
NOV
16.3K
DEC
606
JAN

Visitors by Country

CountryUsers %
Australia 100.00%
SEO

midi-ld.github.io SEMrush Overview

SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.

SemRushSemRush
Domain
midi-ld.github.io
RankBased on keywords, cost and organic traffic
10,373,652
Organic KeywordsKeywords in top 20 Google SERP
3
Organic TrafficVisitors coming from top 20 search results
3
Organic CostEquivalent Google Ads spend for the same traffic
$0.00
Full SEMrush Report →
Monetization

Revenue Report

midi-ld.github.io would generate approximately $0.1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $2.4 and annual gross revenue of approximately $29.2. Based on these figures, the site's net worth is estimated at around $73.4.

How much would midi-ld.github.io make?

Daily Revenue
$0.08
Monthly Revenue
$2.40
Yearly Revenue
$29.20

How much is midi-ld.github.io worth?

Website Value
$73.4

*All earnings values are estimates only.

Daily Earning by Country

CountryPageviewsEarning
Australia 21 $0.08

Daily Revenue Loss by Country

CountryBlockedLost
Australia 4 $0.02

Impact of Ad Blockers

Daily Revenue Loss
$0.02
Monthly Revenue Loss
$0.61
Yearly Revenue Loss
$7.39
Daily Pageviews Blocked
4
Monthly Pageviews Blocked
126
Yearly Pageviews Blocked
1,533

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to midi-ld.github.io, per platform.

Mobile Summary

Root Domain
midi-ld.github.io
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
midi-ld.github.io
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
midi-ld.github.io
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is midi-ld.github.io hosted?

Midi-ld.github.io may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

ASN
AS54113
ISP
Fastly, Inc.
Server Location

United States, US

Other sites hosted on 185.199.108.153

How fast does midi-ld.github.io load?

The average loading time of midi-ld.github.io is 126 ms. The Desktop speed index is 96 and mobile speed index is 80.

96
Good
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
126 ms

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report. We are showing the 90th percentile of FCP and the 95th percentile of FID.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report over the last 30 days. To view suggestions tailored to each page, analyze individual page URLs.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP
First Contentful Paint0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Speed Index0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Total Blocking Time80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
80
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
126 ms

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report. We are showing the 90th percentile of FCP and the 95th percentile of FID.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report over the last 30 days. To view suggestions tailored to each page, analyze individual page URLs.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow
Speed Index2.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint2.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive4.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP
Total Blocking Time60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP

Does midi-ld.github.io use compression?

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on midi-ld.github.io are reduced by 61%.

61%
Reduced
Original
11.26 KB
Compressed
4.36 KB

Saved 6.9 KB off the original size

midi-ld.github.io use gzip compression.

Google Safe Browsing

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.

This site is not currently listed as suspicious

WOT MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.

Status
SAFE

SSL Checker SSL Certificate Verify

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. midi-ld.github.io supports HTTPS.

midi-ld.github.io supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.github.io
Organization:
Location:
Issuer: R12
Valid from: Feb 6 21:41:53 2026 GMT
Valid until: May 7 21:41:52 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R12
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 & HTTP/3 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

midi-ld.github.io supports HTTP/2
midi-ld.github.io does not support HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

Http Header

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.

HTTP/1.1
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Fri, 19 Mar 2021 10:14:25 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"60547981-2d0b"
expires: Fri, 06 Mar 2026 16:38:39 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: EAEA:144B:14A8C89:14E1D94:69AB00B4
accept-ranges: bytes
age: 0
date: Fri, 06 Mar 2026 16:48:31 GMT
via: 1.1 varnish
x-served-by: cache-fra-eddf8230218-FRA
x-cache: HIT
x-cache-hits: 0
x-timer: S1772815711.399479,VS0,VE102
vary: Accept-Encoding
x-fastly-request-id: 2047a5ac2872d53969f4ed51daef088627c53be1
content-length: 4462

DNS Lookup

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.

TypeIPTarget / TXTTTL
A 185.199.109.153 3600
A 185.199.110.153 3600
A 185.199.108.153 3600
A 185.199.111.153 3600
AAAA 2606:50c0:8000::153 3600
AAAA 2606:50c0:8003::153 3600
AAAA 2606:50c0:8002::153 3600
AAAA 2606:50c0:8001::153 3600
CAA letsencrypt.org 3600
CAA sectigo.com 3600
CAA digicert.com 3600
CAA letsencrypt.org 3600
CAA sectigo.com 3600
CAA digicert.com 3600

Whois Lookup

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.

WHOIS
Malformed request.
>>> Last update of WHOIS database: 2026-03-06T16:49:12Z 
More on HypeStat
Activity

Recently Analyzed Sites

mgkomik.cc
HTTP/3 supportedHTTPS supported 14 secs
ticketmaster.ph
HTTP/2 supportedHTTPS supported 1 min
gudfast.com
HTTP/3 supportedHTTPS supported 1 min
anichin.moe
HTTP/3 supportedHTTPS supported 2 mins
prmovies.futbol
HTTP/3 supportedHTTPS supported 2 mins
moviesmod.zone
HTTP/3 supportedHTTPS supported 3 mins
applicable-coffee-sjktmm5e-dpqgn1fbkxqv.edgeone.dev
HTTP/2 not supportedHTTPS not supported 3 mins
saktya.com
HTTP/3 supportedHTTPS supported 3 mins
071kk.com
HTTP/2 supportedHTTPS supported 4 mins
klipmalam.store
HTTP/3 supportedHTTPS supported 4 mins
kaunggyi.com
HTTP/3 supportedHTTPS supported 5 mins
mdkjewellers.com
HTTP/2 supportedHTTPS supported 5 mins
tnlive.sk
HTTP/3 supportedHTTPS supported 5 mins
pinaypie.ch
HTTP/3 supportedHTTPS supported 6 mins
market-qx.info
HTTP/2 supportedHTTPS supported 6 mins
Resources

Custom Widget

midi-ld.github.io
Daily Visitors 20
Monthly Visits 606
Pages / Visit 1.06
HypeRank #1,734,212
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.