Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ifj.ch

With the IFJ from business plan to self-employment

Page Load Speed

5.5 sec in total

First Response

1.1 sec

Resources Loaded

2.8 sec

Page Rendered

1.6 sec

ifj.ch screenshot

About Website

Visit ifj.ch now to see the best up-to-date IFJ content for Switzerland and also check out these interesting facts you probably never knew about ifj.ch

Das Institut für Jungunternehmen begleitet dich während deiner Firmengründung. Mit dem IFJ gründest du dein Startup gratis und einfach.

Visit ifj.ch

Key Findings

We analyzed Ifj.ch page load time and found that the first response time was 1.1 sec and then it took 4.4 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

ifj.ch performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.402

25/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

www.ifj.ch

1116 ms

all.css

112 ms

css

35 ms

ifj_redesign_2018.css

509 ms

script-v2.js

408 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 74% of them (49 requests) were addressed to the original Ifj.ch, 6% (4 requests) were made to Pro.fontawesome.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ifj.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 420.8 kB (28%)

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Ifj.ch main page is 1.5 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. 55% of websites need less resources to load. Images take 911.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 64.6 kB

  • Original 76.7 kB
  • After minification 56.3 kB
  • After compression 12.1 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 20.4 kB, which is 27% 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 64.6 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 22.7 kB

  • Original 911.2 kB
  • After minification 888.4 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. IFJ images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 152.6 kB

  • Original 254.3 kB
  • After minification 251.8 kB
  • After compression 101.7 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 152.6 kB or 60% of the original size.

CSS Optimization

-74%

Potential reduce by 180.8 kB

  • Original 243.3 kB
  • After minification 241.6 kB
  • After compression 62.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. Ifj.ch needs all CSS files to be minified and compressed as it can save up to 180.8 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (50%)

Requests Now

62

After Optimization

31

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFJ. 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

ifj.ch accessibility score

55

Accessibility Issues

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-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

ifj.ch best practices score

83

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

ifj.ch SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifj.ch 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 Ifj.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 IFJ. 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: