Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

resonic.at

Resonic - A fast audio player and sample manager

Page Load Speed

2.5 sec in total

First Response

361 ms

Resources Loaded

2 sec

Page Rendered

157 ms

resonic.at screenshot

About Website

Click here to check amazing Resonic content for Russia. Otherwise, check out these important facts you probably never knew about resonic.at

Resonic is the planet's fastest audio and music player, browser, and sample manager, built around a big waveform view and a frequency analyzer.

Visit resonic.at

Key Findings

We analyzed Resonic.at page load time and found that the first response time was 361 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

resonic.at performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.083

94/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

resonic.at

361 ms

resonic.at

640 ms

bootstrap.min.css

30 ms

jquery-3.4.1.min.js

27 ms

site.min.css

112 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 85% of them (29 requests) were addressed to the original Resonic.at, 6% (2 requests) were made to Stackpath.bootstrapcdn.com and 3% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (674 ms) relates to the external source Matomo.liqube.com.

Page Optimization Overview & Recommendations

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

Content Size

59.1 kB

After Optimization

44.1 kB

In fact, the total size of Resonic.at main page is 59.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. 20% of websites need less resources to load. Javascripts take 26.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.8 kB

  • Original 18.8 kB
  • After minification 15.8 kB
  • After compression 5.0 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 2.9 kB, which is 16% 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 13.8 kB or 74% of the original size.

Image Optimization

-16%

Potential reduce by 492 B

  • Original 3.0 kB
  • After minification 2.5 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, Resonic needs image optimization as it can save up to 492 B or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 522 B

  • Original 26.8 kB
  • After minification 26.8 kB
  • After compression 26.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 167 B

  • Original 10.5 kB
  • After minification 10.5 kB
  • After compression 10.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. Resonic.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (35%)

Requests Now

31

After Optimization

20

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

Accessibility Review

resonic.at accessibility score

85

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.

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

Best Practices

resonic.at best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

resonic.at SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Resonic.at 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 Resonic.at 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

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