Tools & Wizards About Us
cubic.fm screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

cubic.fm

Loading...

Page Load Speed

2.7 sec in total

First Response

196 ms

Resources Loaded

2.4 sec

Page Rendered

137 ms

cubic.fm screenshot

About Website

Visit cubic.fm now to see the best up-to-date Cubic content for United States and also check out these interesting facts you probably never knew about cubic.fm

Save any sound you come across, stream all on the same player.

Visit cubic.fm

Key Findings

We analyzed Cubic.fm page load time and found that the first response time was 196 ms and then it took 2.5 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

cubic.fm performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

cubic.fm

196 ms

cubic.fm

444 ms

please-wait.css

480 ms

styles.min.css

1037 ms

font-awesome.min.css

662 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 22% of them (2 requests) were addressed to the original Cubic.fm, 67% (6 requests) were made to Cdn.cubic.fm and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.cubic.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 799.9 kB (77%)

Content Size

1.0 MB

After Optimization

237.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Cubic.fm main page is 1.0 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. Only 5% of websites need less resources to load. Javascripts take 732.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 12.7 kB

  • Original 16.8 kB
  • After minification 15.1 kB
  • After compression 4.2 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 12.7 kB or 75% of the original size.

JavaScript Optimization

-73%

Potential reduce by 532.7 kB

  • Original 732.3 kB
  • After minification 732.3 kB
  • After compression 199.6 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 532.7 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 254.5 kB

  • Original 287.8 kB
  • After minification 286.2 kB
  • After compression 33.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. Cubic.fm needs all CSS files to be minified and compressed as it can save up to 254.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (71%)

Requests Now

7

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

cubic.fm

cubic.fm

196 ms

cubic.fm

cubic.fm

444 ms

please-wait.css

please-wait.css

480 ms

styles.min.css

styles.min.css

1037 ms

font-awesome.min.css

font-awesome.min.css

662 ms

styles.css

styles.css

137 ms

emptystate.css

emptystate.css

137 ms

source.min.js

source.min.js

1470 ms

css

css

68 ms

Accessibility Review

cubic.fm accessibility score

87

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

Heading elements are not in a sequentially-descending order

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

Best Practices

cubic.fm best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cubic.fm SEO score

93

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

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cubic.fm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Cubic.fm 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

cubic.fm

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