4.1 sec in total
843 ms
3.1 sec
164 ms
Click here to check amazing Great Scores content for Italy. Otherwise, check out these important facts you probably never knew about greatscores.com
Online sheet music from £1.50, €2, $3. Over 100,000 original and arranged scores for piano, guitar, saxophone, clarinet and much more
Visit greatscores.comWe analyzed Greatscores.com page load time and found that the first response time was 843 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
greatscores.com performance score
name
value
score
weighting
Value1.8 s
91/100
10%
Value4.9 s
29/100
25%
Value2.6 s
97/100
10%
Value330 ms
75/100
30%
Value0.025
100/100
15%
Value3.7 s
90/100
10%
843 ms
98 ms
176 ms
48 ms
62 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 21% of them (18 requests) were addressed to the original Greatscores.com, 11% (9 requests) were made to Images.greatscores.com and 8% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Web.greatscores.com.
Page size can be reduced by 635.4 kB (50%)
1.3 MB
628.8 kB
In fact, the total size of Greatscores.com main page is 1.3 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. 60% of websites need less resources to load. Images take 512.7 kB which makes up the majority of the site volume.
Potential reduce by 59.6 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 59.6 kB or 78% of the original size.
Potential reduce by 66.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. Obviously, Great Scores needs image optimization as it can save up to 66.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 298.7 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 298.7 kB or 71% of the original size.
Potential reduce by 210.3 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. Greatscores.com needs all CSS files to be minified and compressed as it can save up to 210.3 kB or 83% of the original size.
Number of requests can be reduced by 43 (55%)
78
35
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Great Scores. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
greatscores.com
843 ms
jquery-ui.min.css
98 ms
jquery-ui.theme.min.css
176 ms
jquery.qtip.css
48 ms
bootstrap.min.css
62 ms
bootstrap-theme.min.css
78 ms
gs.css
193 ms
jquery.min.js
80 ms
bootstrap.min.js
78 ms
jquery-ui.min.js
108 ms
jquery.qtip.min.js
78 ms
hoverIntent.js
236 ms
jquery.truncator.js
231 ms
jquery.swfobject.1-1-1.min.js
231 ms
gs.js
230 ms
avid.js
248 ms
buttons.js
69 ms
plusone.js
111 ms
widgets.js
43 ms
ga.js
160 ms
English.gif
1142 ms
gplus-16.png
159 ms
youtube_24x24.png
156 ms
pvg.png
432 ms
logo.png
190 ms
banner.png
223 ms
3748635.ThinkingOutLoud.88
190 ms
2553600.JarOfHearts.png
193 ms
3919531.Hello.88
189 ms
3761752.TakeMeToChurch.88
189 ms
2362714.GetLucky.88
261 ms
piano.png
1237 ms
string-quartet.png
1239 ms
guitar-tab.png
1240 ms
PayPalWithCreditCards.gif
1152 ms
alto-saxophone.png
440 ms
logo-small.png
352 ms
Avid_a_22x21_gs.png
440 ms
Avid_a_22x21_bright.png
440 ms
smdScoreIcon.png
356 ms
gsScoreIcon.png
440 ms
faberScoreIcon.png
462 ms
gsFaberScoreIcon.png
495 ms
all.js
357 ms
cb=gapi.loaded_0
205 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
107 ms
getAllAppDefault.esi
119 ms
cb=gapi.loaded_1
78 ms
fastbutton
133 ms
homeVideo.png
1096 ms
home_main.png
366 ms
big_caslon_medium-webfont.woff
178 ms
__utm.gif
41 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
19 ms
postmessageRelay
48 ms
getSegment.php
22 ms
checkOAuth.esi
54 ms
cb=gapi.loaded_0
21 ms
cb=gapi.loaded_1
23 ms
t.dhj
63 ms
api.js
96 ms
core:rpc:shindig.random:shindig.sha1.js
94 ms
2536007149-postmessagerelay.js
5 ms
t.dhj
56 ms
cm
27 ms
jot
129 ms
153 ms
196 ms
xd_arbiter.php
220 ms
xd_arbiter.php
429 ms
s-3271.xgi
26 ms
10 ms
hbpix
32 ms
5 ms
xrefid.xgi
8 ms
pixel
27 ms
2981
20 ms
ping
56 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
13 ms
buttons.ab966a004186897711de4a5ed256c924.css
12 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
12 ms
st.1188278743c14064d5e8ae56c8ada29c.js
22 ms
like.php
89 ms
vpc6VNjRPXV.js
480 ms
LVx-xkvaJ0b.png
542 ms
greatscores.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greatscores.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
greatscores.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greatscores.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 Greatscores.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.
greatscores.com
Open Graph description is not detected on the main page of Great Scores. 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: