7.4 sec in total
2.5 sec
4.8 sec
118 ms
Click here to check amazing Support Gracenote content for United States. Otherwise, check out these important facts you probably never knew about support.gracenote.com
Visit support.gracenote.comWe analyzed Support.gracenote.com page load time and found that the first response time was 2.5 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
support.gracenote.com performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.7 s
1/100
25%
Value9.7 s
11/100
10%
Value70 ms
99/100
30%
Value0.203
61/100
15%
Value8.1 s
42/100
10%
2548 ms
191 ms
194 ms
226 ms
43 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 51% of them (33 requests) were addressed to the original Support.gracenote.com, 35% (23 requests) were made to Gracenote.com and 5% (3 requests) were made to Themes.googleusercontent.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Support.gracenote.com.
Page size can be reduced by 405.2 kB (24%)
1.7 MB
1.3 MB
In fact, the total size of Support.gracenote.com 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 122.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 122.7 kB or 68% of the original size.
Potential reduce by 24.1 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. Support Gracenote images are well optimized though.
Potential reduce by 136.2 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 136.2 kB or 66% of the original size.
Potential reduce by 122.2 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. Support.gracenote.com needs all CSS files to be minified and compressed as it can save up to 122.2 kB or 83% of the original size.
Number of requests can be reduced by 32 (55%)
58
26
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Gracenote. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
support.gracenote.com
2548 ms
stub.js
191 ms
3_3_3.Finalorg.ajax4jsf.javascript.AjaxScript
194 ms
eAEz2rRkV-jyGdIAEoQD8g__
226 ms
SfdcCore.js
43 ms
pkb_jquery_1_6_2
43 ms
pkb_jquery_simplemodal_1_4_1
63 ms
picklist.js
55 ms
VFState.js
55 ms
bootstrap.min.css
44 ms
css
74 ms
css
85 ms
font-awesome.mind7b7.css
64 ms
footer-credits14b6.css
217 ms
frontdc8c.css
89 ms
gt.public.bootstrap.mind7b7.css
75 ms
gt-shortcodes.mind7b7.css
89 ms
style4b94.css
99 ms
styled7b7.css
121 ms
trans_black_hoverd7b7.css
121 ms
ubermenu.min.css
130 ms
support_portal
124 ms
font-awesome.min.css
31 ms
jquery.min.js
51 ms
jquery-migrate.min.js
55 ms
applicationd7b7.js
137 ms
css3-animate-itd7b7.js
300 ms
custom4b94.js
149 ms
jquery.fitvids4b94.js
172 ms
core.mine899.js
190 ms
jquery.magnific-popup4b94.js
188 ms
ubermenu.min7f18.js
300 ms
waypoints.min4b94.js
202 ms
waypoints.mind7b7.js
197 ms
tooltip.mine899.js
293 ms
megamenu-music-recognition-300x150.png
807 ms
Gracenote_logo_30pxw.png
27 ms
pkb_loadingdots
27 ms
loading.gif
52 ms
pkb_search_icon
25 ms
megamenu-music-discovery-300x1501.png
816 ms
megamenu-customers-300x150.png
824 ms
megamenu-tv-listings-300x150.png
824 ms
megamenu-international-tv-300x150.png
823 ms
megamenu-studio-celebrity-300x150.png
830 ms
megamenu-music-recognition-auto-300x150.png
1024 ms
megamenu-connected-music-300x150.png
1040 ms
megamenu-radio-recommendations-auto-300x150.png
1049 ms
megamenu-sports-data-300x150.png
975 ms
megamenu-covers-300x150.png
1051 ms
megamenu-about-us-300x150.png
1058 ms
megamenu-leadership-300x150.png
1372 ms
megamenu-press-300x150.png
1241 ms
megamenu-careers-300x150.png
1188 ms
megamenu-support-300x150.png
1275 ms
megamenu-contact-us-300x150.png
1201 ms
support-all.jpg
1441 ms
icon-support-consumer.png
1263 ms
icon-support-artist.png
1278 ms
icon-support-developer.png
1315 ms
icon-facebook-footer.png
1916 ms
icon-twitter-footer.png
1634 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
47 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
47 ms
support.gracenote.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
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
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.
support.gracenote.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
support.gracenote.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.gracenote.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 Support.gracenote.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.
support.gracenote.com
Open Graph description is not detected on the main page of Support Gracenote. 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: