Report Summary

  • 50

    Performance

    Renders faster than
    70% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 73% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

joomfish.net

JoomFish multilingual content manager - Think Network GmbH

Page Load Speed

25.9 sec in total

First Response

409 ms

Resources Loaded

15.6 sec

Page Rendered

9.9 sec

joomfish.net screenshot

About Website

Visit joomfish.net now to see the best up-to-date Joom Fish content for Germany and also check out these interesting facts you probably never knew about joomfish.net

The initial idea of the extension relates back to year 2003 when Mambo didn’t know anything about multilingual websites. The first initial version was called MambelFish as an analogy to the f…

Visit joomfish.net

Key Findings

We analyzed Joomfish.net page load time and found that the first response time was 409 ms and then it took 25.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

joomfish.net performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

joomfish.net

409 ms

305 ms

3240 ms

wp-emoji-release.min.js

822 ms

simple-payments.css

772 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Joomfish.net, 67% (39 requests) were made to Thinknetwork.com and 5% (3 requests) were made to Secure.gravatar.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Thinknetwork.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 923.8 kB (23%)

Content Size

4.1 MB

After Optimization

3.1 MB

In fact, the total size of Joomfish.net main page is 4.1 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. 50% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 20.0 kB

  • Original 27.5 kB
  • After minification 26.6 kB
  • After compression 7.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. 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 20.0 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 73.7 kB

  • Original 2.8 MB
  • After minification 2.8 MB

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. Joom Fish images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 510.4 kB

  • Original 757.4 kB
  • After minification 711.5 kB
  • After compression 246.9 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 510.4 kB or 67% of the original size.

CSS Optimization

-73%

Potential reduce by 319.7 kB

  • Original 439.5 kB
  • After minification 416.6 kB
  • After compression 119.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. Joomfish.net needs all CSS files to be minified and compressed as it can save up to 319.7 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (86%)

Requests Now

50

After Optimization

7

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

Accessibility Review

joomfish.net accessibility score

89

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

Buttons do not have an accessible name

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

Best Practices

joomfish.net 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

SEO Factors

joomfish.net SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Joomfish.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Joomfish.net 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 Joom Fish. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: