Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

infai.org

Home - InfAI

Page Load Speed

6 sec in total

First Response

1.2 sec

Resources Loaded

4.3 sec

Page Rendered

531 ms

infai.org screenshot

About Website

Click here to check amazing InfAI content. Otherwise, check out these important facts you probably never knew about infai.org

Visit infai.org

Key Findings

We analyzed Infai.org page load time and found that the first response time was 1.2 sec and then it took 4.8 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

infai.org performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

Aktuelles

1182 ms

font-awesome.min.css

580 ms

default.css.php

196 ms

infai.css

290 ms

default.js

291 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 76% of them (35 requests) were addressed to the original Infai.org, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Wiki.dbpedia.org. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source 2017.semantics.cc.

Page Optimization Overview & Recommendations

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

Content Size

577.5 kB

After Optimization

445.9 kB

In fact, the total size of Infai.org main page is 577.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 448.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 28.8 kB

  • Original 39.9 kB
  • After minification 37.0 kB
  • After compression 11.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 28.8 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 38.9 kB

  • Original 448.4 kB
  • After minification 409.5 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. InfAI images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 22.8 kB

  • Original 35.1 kB
  • After minification 26.3 kB
  • After compression 12.3 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 22.8 kB or 65% of the original size.

CSS Optimization

-76%

Potential reduce by 41.1 kB

  • Original 54.0 kB
  • After minification 49.9 kB
  • After compression 12.9 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. Infai.org needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (44%)

Requests Now

45

After Optimization

25

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

Accessibility Review

infai.org accessibility score

94

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

Links do not have a discernible name

Best Practices

infai.org 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

infai.org SEO score

93

Search Engine Optimization Advices

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

    DE

  • Language Claimed

    DE

  • Encoding

    ISO8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infai.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Infai.org main page’s claimed encoding is iso8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of InfAI. 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: