Tools & Wizards About Us
audio.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

audio.com

audio.com - a better way to upload and share audio online

Page Load Speed

908 ms in total

First Response

120 ms

Resources Loaded

684 ms

Page Rendered

104 ms

audio.com screenshot

About Website

Click here to check amazing Audio content for United States. Otherwise, check out these important facts you probably never knew about audio.com

audio.com is a free audio-sharing platform designed to empower audio creatives and musicians

Visit audio.com

Key Findings

We analyzed Audio.com page load time and found that the first response time was 120 ms and then it took 788 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

audio.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

Network Requests Diagram

audio.com

120 ms

basscss.min.css

11 ms

css

64 ms

main1.css

27 ms

main.css

135 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 34% of them (10 requests) were addressed to the original Audio.com, 10% (3 requests) were made to Platform.twitter.com and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (232 ms) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.0 kB (45%)

Content Size

605.4 kB

After Optimization

333.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Audio.com main page is 605.4 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. 50% of websites need less resources to load. Images take 470.3 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 17.6 kB

  • Original 24.9 kB
  • After minification 22.7 kB
  • After compression 7.3 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 17.6 kB or 71% of the original size.

Image Optimization

-41%

Potential reduce by 193.4 kB

  • Original 470.3 kB
  • After minification 276.9 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, Audio needs image optimization as it can save up to 193.4 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 12.0 kB

  • Original 48.2 kB
  • After minification 41.1 kB
  • After compression 36.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 12.0 kB or 25% of the original size.

CSS Optimization

-79%

Potential reduce by 48.9 kB

  • Original 62.1 kB
  • After minification 55.7 kB
  • After compression 13.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. Audio.com needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (48%)

Requests Now

25

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

audio.com

audio.com

120 ms

basscss.min.css

basscss.min.css

11 ms

css

css

64 ms

main1.css

main1.css

27 ms

main.css

main.css

135 ms

styles.css

styles.css

148 ms

jquery.min.js

jquery.min.js

5 ms

main.js

main.js

51 ms

counter.js

counter.js

7 ms

font-awesome.min.css

font-awesome.min.css

64 ms

css

css

27 ms

sdk.js

sdk.js

65 ms

widgets.js

widgets.js

56 ms

analytics.js

analytics.js

38 ms

t.php

t.php

161 ms

screen-1.png

screen-1.png

130 ms

screen-2.png

screen-2.png

68 ms

screen-3.png

screen-3.png

106 ms

cd-arrow.svg

cd-arrow.svg

54 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

52 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

52 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

53 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

42 ms

collect

collect

30 ms

232 ms

xd_arbiter.php

xd_arbiter.php

24 ms

xd_arbiter.php

xd_arbiter.php

67 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

21 ms

jot

jot

97 ms

Accessibility Review

audio.com accessibility score

91

Accessibility Issues

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

Document doesn't have a <title> element

Best Practices

audio.com 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

Page has valid source maps

SEO Factors

audio.com SEO score

55

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

Document doesn't have a <title> element

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 Audio.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 Audio.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

audio.com

Open Graph data is detected on the main page of Audio. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: