Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

jellynote.com

Farewell, Musicians | Jellynote

Page Load Speed

1.1 sec in total

First Response

75 ms

Resources Loaded

819 ms

Page Rendered

254 ms

jellynote.com screenshot

About Website

Visit jellynote.com now to see the best up-to-date Jellynote content for Sweden and also check out these interesting facts you probably never knew about jellynote.com

Jouez, imprimez et téléchargez les partitions de vos morceaux préférés sur Jellynote. Avec une bibliothèque de 400.000 tablatures de guitare et basse, partitions de piano, violon et plus, devenez le m...

Visit jellynote.com

Key Findings

We analyzed Jellynote.com page load time and found that the first response time was 75 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.

Performance Metrics

jellynote.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value27.1 s

0/100

10%

TBT (Total Blocking Time)

Value25,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

jellynote.com

75 ms

47 ms

46e6e67a98be.css

136 ms

db8d789f3078.js

102 ms

e4b740162e36.js

116 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Jellynote.com, 57% (34 requests) were made to D5lxao33c2vqc.cloudfront.net and 10% (6 requests) were made to D1gfnm0lm0sn6t.cloudfront.net. The less responsive or slowest element that took the longest time to load (439 ms) relates to the external source D5lxao33c2vqc.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.8 kB (51%)

Content Size

812.6 kB

After Optimization

396.7 kB

In fact, the total size of Jellynote.com main page is 812.6 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. CSS take 537.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 24.5 kB

  • Original 30.2 kB
  • After minification 30.2 kB
  • After compression 5.8 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 24.5 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 5.6 kB

  • Original 124.1 kB
  • After minification 118.5 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. Jellynote images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 518 B

  • Original 121.0 kB
  • After minification 120.9 kB
  • After compression 120.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-72%

Potential reduce by 385.3 kB

  • Original 537.3 kB
  • After minification 444.7 kB
  • After compression 152.0 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. Jellynote.com needs all CSS files to be minified and compressed as it can save up to 385.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (32%)

Requests Now

25

After Optimization

17

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

Accessibility Review

jellynote.com accessibility score

78

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

Buttons do not have an accessible name

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.

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

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

jellynote.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

jellynote.com 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 Jellynote.com 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 Jellynote.com 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

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