Tools & Wizards About Us
flat.io screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

flat.io

Online collaborative music notation software - Flat

Page Load Speed

1.1 sec in total

First Response

29 ms

Resources Loaded

666 ms

Page Rendered

448 ms

flat.io screenshot

About Website

Welcome to flat.io homepage info - get ready to check Flat best content for United States right away, or after learning these important things about flat.io

Create, compose, collaborate, play, and print your sheet music using the world's most simple and intuitive web-based music writing and composition software.

Visit flat.io

Key Findings

We analyzed Flat.io page load time and found that the first response time was 29 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

flat.io performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

flat.io

29 ms

flat.io

64 ms

en

73 ms

flat.min.css

45 ms

logo-white.svg

101 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 82% of them (31 requests) were addressed to the original Flat.io, 11% (4 requests) were made to Pbs.twimg.com and 8% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 861.6 kB (72%)

Content Size

1.2 MB

After Optimization

342.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flat.io main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 738.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 14.3 kB

  • Original 19.9 kB
  • After minification 17.6 kB
  • After compression 5.5 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 2.2 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 14.3 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 472 B

  • Original 15.1 kB
  • After minification 14.6 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. Flat images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 482.3 kB

  • Original 738.2 kB
  • After minification 738.2 kB
  • After compression 255.9 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 482.3 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 364.4 kB

  • Original 430.6 kB
  • After minification 430.3 kB
  • After compression 66.1 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. Flat.io needs all CSS files to be minified and compressed as it can save up to 364.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (19%)

Requests Now

26

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flat.io

flat.io

29 ms

flat.io

flat.io

64 ms

en

en

73 ms

flat.min.css

flat.min.css

45 ms

logo-white.svg

logo-white.svg

101 ms

logo-flat.svg

logo-flat.svg

105 ms

logo-f-white.svg

logo-f-white.svg

104 ms

logo-f.svg

logo-f.svg

111 ms

icon_home_collaboration.svg

icon_home_collaboration.svg

116 ms

icon_home_history.svg

icon_home_history.svg

114 ms

icon_home_standard.svg

icon_home_standard.svg

121 ms

icon_home_instruments.svg

icon_home_instruments.svg

118 ms

icon_home_midi.png

icon_home_midi.png

122 ms

icon_drive.svg

icon_drive.svg

122 ms

icon_hangouts.svg

icon_hangouts.svg

124 ms

h1HMIGNL_bigger.jpg

h1HMIGNL_bigger.jpg

99 ms

api.js

api.js

144 ms

raven.min.js

raven.min.js

119 ms

vendor.min.js

vendor.min.js

163 ms

flat.common.min.js

flat.common.min.js

161 ms

flat.site-home.min.js

flat.site-home.min.js

161 ms

school_bag.svg

school_bag.svg

119 ms

kyTkOkYG_bigger.jpg

kyTkOkYG_bigger.jpg

104 ms

JSHgTH5z_bigger.jpg

JSHgTH5z_bigger.jpg

103 ms

mSYcIqtD_bigger.jpg

mSYcIqtD_bigger.jpg

121 ms

bg_notes.svg

bg_notes.svg

84 ms

analytics.js

analytics.js

275 ms

raleway-81ab5403b1be0080c299234cfa5018d5bc984e56.woff

raleway-81ab5403b1be0080c299234cfa5018d5bc984e56.woff

89 ms

raleway-e634977bfabc20ed15fe7ed03d3876cf68834b93.woff

raleway-e634977bfabc20ed15fe7ed03d3876cf68834b93.woff

88 ms

raleway-c97d4772fbb5c5637d466b5f991bc7ec28830b32.woff

raleway-c97d4772fbb5c5637d466b5f991bc7ec28830b32.woff

87 ms

raleway-bb071565f82907d117b0732dca8013409162c67d.woff

raleway-bb071565f82907d117b0732dca8013409162c67d.woff

88 ms

flat-icons.woff

flat-icons.woff

90 ms

opensans-4bd3f3f26f7a8eb357a09da8636390a28a21f826.woff

opensans-4bd3f3f26f7a8eb357a09da8636390a28a21f826.woff

89 ms

opensans-adb2daec48669c7b205edfad36830a0ed8201225.woff

opensans-adb2daec48669c7b205edfad36830a0ed8201225.woff

88 ms

opensans-84f97fc997632d2fffb788cd07c92241f178a9a1.woff

opensans-84f97fc997632d2fffb788cd07c92241f178a9a1.woff

89 ms

opensans-845bbcd4bd3d110360a1994e213f709ef73ac6e8.woff

opensans-845bbcd4bd3d110360a1994e213f709ef73ac6e8.woff

89 ms

twitter.svg

twitter.svg

19 ms

collect

collect

14 ms

Accessibility Review

flat.io accessibility score

96

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

Heading elements are not in a sequentially-descending order

Best Practices

flat.io 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

flat.io SEO score

93

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flat.io 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 Flat.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

flat.io

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