Tools & Wizards About Us
forte-notation.eu screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

forte-notation.eu

Music Notation Software FORTE - Smart Music Writing Software

Page Load Speed

7.6 sec in total

First Response

264 ms

Resources Loaded

6.6 sec

Page Rendered

715 ms

forte-notation.eu screenshot

About Website

Visit forte-notation.eu now to see the best up-to-date FORTE Notation content and also check out these interesting facts you probably never knew about forte-notation.eu

With FORTE music notation software, you get a smart music writing software for sheet music. ✅easy to use ✅ free trial download

Visit forte-notation.eu

Key Findings

We analyzed Forte-notation.eu page load time and found that the first response time was 264 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

forte-notation.eu performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

forte-notation.eu

264 ms

index.php

252 ms

316 ms

gtm.js

27 ms

dbdd1b3ff471.09cf4f18c404.google-font.css

235 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Forte-notation.eu, 96% (97 requests) were made to Fortenotation.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Fortenotation.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.0 kB (18%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forte-notation.eu main page is 1.7 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. 50% of websites need less resources to load. Images take 751.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 192.9 kB

  • Original 225.6 kB
  • After minification 200.7 kB
  • After compression 32.7 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 24.9 kB, which is 11% 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 192.9 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 24 B

  • Original 751.7 kB
  • After minification 751.7 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. FORTE Notation images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 60.3 kB

  • Original 431.7 kB
  • After minification 431.7 kB
  • After compression 371.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 60.3 kB or 14% of the original size.

CSS Optimization

-19%

Potential reduce by 57.8 kB

  • Original 308.7 kB
  • After minification 308.7 kB
  • After compression 250.9 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. Forte-notation.eu needs all CSS files to be minified and compressed as it can save up to 57.8 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (85%)

Requests Now

94

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forte-notation.eu

forte-notation.eu

264 ms

index.php

index.php

252 ms

316 ms

gtm.js

gtm.js

27 ms

dbdd1b3ff471.09cf4f18c404.google-font.css

dbdd1b3ff471.09cf4f18c404.google-font.css

235 ms

a0b14e168bee.thrive_flat.css

a0b14e168bee.thrive_flat.css

821 ms

2b0dd7eecea0.mediaelementplayer-legacy.min.css

2b0dd7eecea0.mediaelementplayer-legacy.min.css

319 ms

ea958276b7de.wp-mediaelement.min.css

ea958276b7de.wp-mediaelement.min.css

324 ms

a516ac271a73.grid.css

a516ac271a73.grid.css

335 ms

6130a15f074b.base.css

6130a15f074b.base.css

335 ms

70266b6e1c44.layout.css

70266b6e1c44.layout.css

398 ms

19946d5f4bff.shortcodes.css

19946d5f4bff.shortcodes.css

544 ms

30b593b71d76.magnific-popup.css

30b593b71d76.magnific-popup.css

439 ms

2054ae900334.enfold_child.css

2054ae900334.enfold_child.css

568 ms

1877fc72c3a2.custom.css

1877fc72c3a2.custom.css

449 ms

e737b31fbbd1.style.css

e737b31fbbd1.style.css

526 ms

a78d70c58103.borlabs-cookie_1_en.css

a78d70c58103.borlabs-cookie_1_en.css

554 ms

88416f9f90df.avia-merged-styles-9d9b4a6c09c7fc369ac25b1d35e95edc.css

88416f9f90df.avia-merged-styles-9d9b4a6c09c7fc369ac25b1d35e95edc.css

575 ms

jquery.min.js

jquery.min.js

705 ms

jquery-migrate.min.js

jquery-migrate.min.js

656 ms

imagesloaded.min.js

imagesloaded.min.js

669 ms

masonry.min.js

masonry.min.js

702 ms

jquery.masonry.min.js

jquery.masonry.min.js

686 ms

general.min.js

general.min.js

888 ms

moxie.min.js

moxie.min.js

892 ms

avia-compat.js

avia-compat.js

799 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

888 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

889 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

920 ms

vimeo.min.js

vimeo.min.js

929 ms

9c2490ee969e.public.js

9c2490ee969e.public.js

998 ms

si_captcha.js

si_captcha.js

932 ms

preload.min.js

preload.min.js

843 ms

acf-dynamic-elements.min.js

acf-dynamic-elements.min.js

976 ms

audio.min.js

audio.min.js

976 ms

carousel-libs.min.js

carousel-libs.min.js

978 ms

carousel.min.js

carousel.min.js

977 ms

contact-form-compat.min.js

contact-form-compat.min.js

978 ms

content-reveal.min.js

content-reveal.min.js

1008 ms

client

client

52 ms

api.js

api.js

31 ms

countdown.min.js

countdown.min.js

1034 ms

conditional-display.min.js

conditional-display.min.js

938 ms

search-form.min.js

search-form.min.js

846 ms

dropdown.min.js

dropdown.min.js

842 ms

divider.min.js

divider.min.js

853 ms

plupload.min.js

plupload.min.js

910 ms

file-upload.min.js

file-upload.min.js

862 ms

avatar-picker.min.js

avatar-picker.min.js

844 ms

fill-counter.min.js

fill-counter.min.js

827 ms

number-counter.min.js

number-counter.min.js

770 ms

image-gallery-libs.min.js

image-gallery-libs.min.js

783 ms

image-gallery.min.js

image-gallery.min.js

813 ms

lead-generation.min.js

lead-generation.min.js

852 ms

login.min.js

login.min.js

827 ms

menu.min.js

menu.min.js

770 ms

number-counter-compat.min.js

number-counter-compat.min.js

765 ms

post-grid-compat.min.js

post-grid-compat.min.js

763 ms

pagination.min.js

pagination.min.js

789 ms

post-list.min.js

post-list.min.js

820 ms

post-list-filter.min.js

post-list-filter.min.js

741 ms

pricing-table.min.js

pricing-table.min.js

649 ms

progress-bar.min.js

progress-bar.min.js

666 ms

social-share.min.js

social-share.min.js

676 ms

table.min.js

table.min.js

721 ms

tabs.min.js

tabs.min.js

746 ms

timer.min.js

timer.min.js

762 ms

toc.min.js

toc.min.js

754 ms

toggle.min.js

toggle.min.js

753 ms

twitter.min.js

twitter.min.js

740 ms

user-profile.min.js

user-profile.min.js

651 ms

video.min.js

video.min.js

680 ms

google-api.min.js

google-api.min.js

716 ms

facebook-api.min.js

facebook-api.min.js

721 ms

modal.min.js

modal.min.js

719 ms

131d2717ef56.avia.js

131d2717ef56.avia.js

779 ms

3a161bcfd1a7.shortcodes.js

3a161bcfd1a7.shortcodes.js

786 ms

F12_3Versio_EN_breit.png

F12_3Versio_EN_breit.png

1315 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

772 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

883 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

779 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

800 ms

comment-reply.min.js

comment-reply.min.js

778 ms

frontend.min.js

frontend.min.js

775 ms

new-tab.js

new-tab.js

810 ms

avia-footer-scripts-c8fc904331f0321fbdba896cfedb73ae.js

avia-footer-scripts-c8fc904331f0321fbdba896cfedb73ae.js

824 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

852 ms

gothambold.ttf

gothambold.ttf

936 ms

new_logo_forte-1.png

new_logo_forte-1.png

821 ms

background-black-coffee-compose-1262973-e1567071606516.jpg

background-black-coffee-compose-1262973-e1567071606516.jpg

1087 ms

classical-music-1838390_640-300x200.jpg

classical-music-1838390_640-300x200.jpg

845 ms

F12Pre_EN_Web-220x300.png

F12Pre_EN_Web-220x300.png

883 ms

chorus-515897_640-300x199.jpg

chorus-515897_640-300x199.jpg

874 ms

F12Hom_EN_Web-220x300.png

F12Hom_EN_Web-220x300.png

909 ms

background-black-coffee-compose-1262973-1-e1566474333457-300x203.jpg

background-black-coffee-compose-1262973-1-e1566474333457-300x203.jpg

885 ms

F12Bas_EN_Web-220x300.png

F12Bas_EN_Web-220x300.png

881 ms

admin-ajax.php

admin-ajax.php

1410 ms

logo_gruen.png

logo_gruen.png

227 ms

borlabs-cookie-icon-black.svg

borlabs-cookie-icon-black.svg

293 ms

entypo-fontello.woff

entypo-fontello.woff

389 ms

f082e197d60a.print.css

f082e197d60a.print.css

149 ms

Accessibility Review

forte-notation.eu accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

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

forte-notation.eu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

forte-notation.eu SEO score

96

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

High

Tap targets are not sized appropriately

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 Forte-notation.eu 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 Forte-notation.eu 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

forte-notation.eu

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