Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

fmi.ch

FMI - Friedrich Miescher Institute for Biomedical Research

Page Load Speed

7.9 sec in total

First Response

478 ms

Resources Loaded

3.8 sec

Page Rendered

3.7 sec

fmi.ch screenshot

About Website

Welcome to fmi.ch homepage info - get ready to check FMI best content for Switzerland right away, or after learning these important things about fmi.ch

The Friedrich Miescher Institute (FMI) in Basel carries out biomedical research in the areas of epigenetics, quantitative biology, and neurobiology.

Visit fmi.ch

Key Findings

We analyzed Fmi.ch page load time and found that the first response time was 478 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fmi.ch performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

fmi.ch

478 ms

www.fmi.ch

577 ms

style.min.css

311 ms

widgets.js

104 ms

all.css

78 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 44% of them (23 requests) were addressed to the original Fmi.ch, 21% (11 requests) were made to Platform.twitter.com and 12% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Fmi.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.6 kB (4%)

Content Size

4.9 MB

After Optimization

4.7 MB

In fact, the total size of Fmi.ch main page is 4.9 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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.7 kB

  • Original 37.6 kB
  • After minification 28.0 kB
  • After compression 6.9 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 9.6 kB, which is 26% 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 30.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 39.0 kB

  • Original 4.6 MB
  • After minification 4.6 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. FMI images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 6.1 kB

  • Original 25.9 kB
  • After minification 24.9 kB
  • After compression 19.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 6.1 kB or 23% of the original size.

CSS Optimization

-82%

Potential reduce by 112.8 kB

  • Original 137.9 kB
  • After minification 135.9 kB
  • After compression 25.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. Fmi.ch needs all CSS files to be minified and compressed as it can save up to 112.8 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

21

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

Accessibility Review

fmi.ch accessibility score

68

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fmi.ch best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fmi.ch SEO score

80

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

High

Tap targets are not sized appropriately

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 Fmi.ch 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 Fmi.ch 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 FMI. 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: