Tools & Wizards About Us
everyonepiano.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

everyonepiano.com

Everyone Piano - Forever Free Piano Software, Download Numerous Music Scores, Stave and Numbered Musical Notation, and EOP File.

Page Load Speed

17.4 sec in total

First Response

128 ms

Resources Loaded

17 sec

Page Rendered

232 ms

everyonepiano.com screenshot

About Website

Visit everyonepiano.com now to see the best up-to-date Everyone Piano content for Taiwan and also check out these interesting facts you probably never knew about everyonepiano.com

Everyone Piano is the best free computer keyboard piano software, which supports downloading 3 types of music score formats like stave, right and left hand numbered musical notation and EOP file. Furt...

Visit everyonepiano.com

Key Findings

We analyzed Everyonepiano.com page load time and found that the first response time was 128 ms and then it took 17.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

everyonepiano.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

everyonepiano.com

128 ms

www.everyonepiano.com

144 ms

www.everyonepiano.com

14616 ms

2016bootstrap3.3.4.css

164 ms

font-awesome.min.css

138 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 61% of them (51 requests) were addressed to the original Everyonepiano.com, 11% (9 requests) were made to Tpc.googlesyndication.com and 10% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (14.6 sec) belongs to the original domain Everyonepiano.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 785.7 kB (25%)

Content Size

3.1 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Everyonepiano.com main page is 3.1 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 54.5 kB

  • Original 66.2 kB
  • After minification 61.3 kB
  • After compression 11.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. 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 54.5 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 104.6 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Everyone Piano images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 625.4 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 539.1 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 625.4 kB or 54% of the original size.

CSS Optimization

-4%

Potential reduce by 1.2 kB

  • Original 31.6 kB
  • After minification 31.6 kB
  • After compression 30.4 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. Everyonepiano.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (39%)

Requests Now

77

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

everyonepiano.com

everyonepiano.com

128 ms

www.everyonepiano.com

www.everyonepiano.com

144 ms

www.everyonepiano.com

www.everyonepiano.com

14616 ms

2016bootstrap3.3.4.css

2016bootstrap3.3.4.css

164 ms

font-awesome.min.css

font-awesome.min.css

138 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

207 ms

2019global-0626.css

2019global-0626.css

144 ms

marquee2016.js

marquee2016.js

144 ms

adsbygoogle.js

adsbygoogle.js

171 ms

bootstrap3.3.4.min.js

bootstrap3.3.4.min.js

173 ms

eop2016.js

eop2016.js

141 ms

en_comment.js

en_comment.js

150 ms

index20181109.js

index20181109.js

151 ms

vip.png

vip.png

87 ms

rbutton.png

rbutton.png

122 ms

logobg.jpg

logobg.jpg

87 ms

logoen.png

logoen.png

87 ms

logosmall.png

logosmall.png

85 ms

menunew-en.png

menunew-en.png

87 ms

en.png

en.png

106 ms

jp.png

jp.png

161 ms

tw.png

tw.png

236 ms

cn.png

cn.png

124 ms

laba.png

laba.png

157 ms

vip-en.jpg

vip-en.jpg

351 ms

005-en.jpg

005-en.jpg

436 ms

006-en.jpg

006-en.jpg

371 ms

eop02en.jpg

eop02en.jpg

493 ms

eop03en.jpg

eop03en.jpg

672 ms

0017039-small.jpg

0017039-small.jpg

423 ms

0015856-small.jpg

0015856-small.jpg

560 ms

0017044-small.jpg

0017044-small.jpg

436 ms

0017038-small.jpg

0017038-small.jpg

627 ms

0015169-small.jpg

0015169-small.jpg

565 ms

0017035-small.jpg

0017035-small.jpg

488 ms

0017025-small.jpg

0017025-small.jpg

533 ms

0017036-small.jpg

0017036-small.jpg

546 ms

0017032-small.jpg

0017032-small.jpg

576 ms

0017040-small.jpg

0017040-small.jpg

653 ms

0017043-small.jpg

0017043-small.jpg

682 ms

0017041-small.jpg

0017041-small.jpg

676 ms

0016669-small.jpg

0016669-small.jpg

685 ms

0017027-small.jpg

0017027-small.jpg

848 ms

0017028-small.jpg

0017028-small.jpg

701 ms

0017048-small.jpg

0017048-small.jpg

788 ms

new.png

new.png

764 ms

0009247-small.jpg

0009247-small.jpg

787 ms

hot.png

hot.png

736 ms

show_ads_impl.js

show_ads_impl.js

259 ms

0000031-small.jpg

0000031-small.jpg

682 ms

boxen.jpg

boxen.jpg

700 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

765 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

745 ms

zrt_lookup.html

zrt_lookup.html

41 ms

ads

ads

541 ms

ads

ads

685 ms

faf71a0e8da85c808301846dcd34a748.js

faf71a0e8da85c808301846dcd34a748.js

25 ms

load_preloaded_resource.js

load_preloaded_resource.js

23 ms

4a5cba740e22a750e003929b84bc8a1f.js

4a5cba740e22a750e003929b84bc8a1f.js

20 ms

abg_lite.js

abg_lite.js

50 ms

window_focus.js

window_focus.js

56 ms

qs_click_protection.js

qs_click_protection.js

56 ms

ufs_web_display.js

ufs_web_display.js

14 ms

60efddb729a951d3495fe79f6eb41a86.js

60efddb729a951d3495fe79f6eb41a86.js

49 ms

s

s

8 ms

icon.png

icon.png

111 ms

css

css

100 ms

reactive_library.js

reactive_library.js

210 ms

ca-pub-2655776593187108

ca-pub-2655776593187108

122 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

19 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

24 ms

activeview

activeview

207 ms

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

35 ms

ads

ads

372 ms

ads

ads

410 ms

ads

ads

361 ms

12984118184795248095

12984118184795248095

74 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

7 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

73 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

78 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

79 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

74 ms

42838078324111336

42838078324111336

37 ms

activeview

activeview

222 ms

Accessibility Review

everyonepiano.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

everyonepiano.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

everyonepiano.com SEO score

92

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Everyonepiano.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Everyonepiano.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

everyonepiano.com

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