Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

funkwhale.audio

Funkwhale

Page Load Speed

5.7 sec in total

First Response

410 ms

Resources Loaded

4.8 sec

Page Rendered

399 ms

funkwhale.audio screenshot

About Website

Welcome to funkwhale.audio homepage info - get ready to check Funkwhale best content for India right away, or after learning these important things about funkwhale.audio

Funkwhale - A platform for all your audio

Visit funkwhale.audio

Key Findings

We analyzed Funkwhale.audio page load time and found that the first response time was 410 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

funkwhale.audio performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

funkwhale.audio

410 ms

www.funkwhale.audio

221 ms

www.funkwhale.audio

438 ms

style.css

1439 ms

fork-awesome.min.css

211 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 74% of them (17 requests) were addressed to the original Funkwhale.audio, 22% (5 requests) were made to and 4% (1 request) were made to Ui.funkwhale.audio. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Funkwhale.audio.

Page Optimization Overview & Recommendations

Page size can be reduced by 889.8 kB (33%)

Content Size

2.7 MB

After Optimization

1.8 MB

In fact, the total size of Funkwhale.audio main page is 2.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. 35% of websites need less resources to load. CSS take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 14.2 kB

  • Original 18.7 kB
  • After minification 17.0 kB
  • After compression 4.5 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 14.2 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 186.5 kB

  • Original 1.2 MB
  • After minification 979.6 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, Funkwhale needs image optimization as it can save up to 186.5 kB 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

-54%

Potential reduce by 515 B

  • Original 951 B
  • After minification 951 B
  • After compression 436 B

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 515 B or 54% of the original size.

CSS Optimization

-46%

Potential reduce by 688.7 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 793.5 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. Funkwhale.audio needs all CSS files to be minified and compressed as it can save up to 688.7 kB or 46% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funkwhale. According to our analytics all requests are already optimized.

Accessibility Review

funkwhale.audio accessibility score

100

Accessibility Issues

Best Practices

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

SEO Factors

funkwhale.audio SEO score

99

Search Engine Optimization Advices

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 Funkwhale.audio 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 Funkwhale.audio 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 description is not detected on the main page of Funkwhale. 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: