Tools & Wizards About Us
saxophone.org screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

saxophone.org

Saxophone Museum, Saxophone Serial Numbers, Audio, Videos, and Reviews

Page Load Speed

1.8 sec in total

First Response

75 ms

Resources Loaded

1.5 sec

Page Rendered

209 ms

saxophone.org screenshot

About Website

Click here to check amazing Saxophone content for United States. Otherwise, check out these important facts you probably never knew about saxophone.org

Saxophone.org - created by saxophone players for saxophone players. Features an active saxophone forum, buy sell trade your sax, saxophone museum, sax teachers and more.

Visit saxophone.org

Key Findings

We analyzed Saxophone.org page load time and found that the first response time was 75 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

saxophone.org performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

saxophone.org

75 ms

www.saxophone.org

304 ms

gtm.js

78 ms

jquery.js

20 ms

combined.css

35 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 62% of them (24 requests) were addressed to the original Saxophone.org, 13% (5 requests) were made to Youtube.com and 5% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (671 ms) belongs to the original domain Saxophone.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.8 kB (14%)

Content Size

686.1 kB

After Optimization

589.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saxophone.org main page is 686.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 444.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 18.9 kB

  • Original 25.3 kB
  • After minification 20.9 kB
  • After compression 6.4 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 4.4 kB, which is 17% 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 18.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.7 kB

  • Original 134.8 kB
  • After minification 133.2 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. Saxophone images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 72.0 kB

  • Original 444.0 kB
  • After minification 444.0 kB
  • After compression 372.0 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 72.0 kB or 16% of the original size.

CSS Optimization

-5%

Potential reduce by 4.3 kB

  • Original 82.0 kB
  • After minification 82.0 kB
  • After compression 77.8 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. Saxophone.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (40%)

Requests Now

35

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

saxophone.org

saxophone.org

75 ms

www.saxophone.org

www.saxophone.org

304 ms

gtm.js

gtm.js

78 ms

jquery.js

jquery.js

20 ms

combined.css

combined.css

35 ms

tiny_mce_src.js

tiny_mce_src.js

32 ms

jquery.tinymce.js

jquery.tinymce.js

57 ms

js

js

104 ms

flowplayer-3.2.2.js

flowplayer-3.2.2.js

77 ms

jquery.simplemodal-1.4.1.js

jquery.simplemodal-1.4.1.js

31 ms

plugins.js

plugins.js

31 ms

app_defer.js

app_defer.js

74 ms

ga.js

ga.js

46 ms

CGK_9AzWwvc

CGK_9AzWwvc

188 ms

main_bg.jpg

main_bg.jpg

96 ms

header_logo.gif

header_logo.gif

95 ms

header_button.gif

header_button.gif

95 ms

nav_bg.gif

nav_bg.gif

95 ms

nav_sub.gif

nav_sub.gif

95 ms

virtual_museum.jpg

virtual_museum.jpg

94 ms

arrow.gif

arrow.gif

179 ms

14_82_82.jpg

14_82_82.jpg

219 ms

4787_120_120.jpg

4787_120_120.jpg

671 ms

1444_120_83.jpg

1444_120_83.jpg

251 ms

footer_border.gif

footer_border.gif

95 ms

dark-overlay.png

dark-overlay.png

123 ms

loader.gif

loader.gif

160 ms

__utm.gif

__utm.gif

14 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

36 ms

base.js

base.js

73 ms

ad_status.js

ad_status.js

292 ms

8bwowYG5RNtA9FhY8KreTMIyRq72TB8rCtAEZTTrOhQ.js

8bwowYG5RNtA9FhY8KreTMIyRq72TB8rCtAEZTTrOhQ.js

191 ms

embed.js

embed.js

52 ms

print.css

print.css

51 ms

id

id

56 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

216 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

217 ms

Create

Create

162 ms

Accessibility Review

saxophone.org accessibility score

51

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

saxophone.org best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

saxophone.org SEO score

75

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Saxophone.org 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 Saxophone.org 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

saxophone.org

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