Tools & Wizards About Us
idalab.de screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

idalab.de

idalab | Artificial Intelligence for Biotech, Pharma and Medtech

Page Load Speed

1.3 sec in total

First Response

111 ms

Resources Loaded

953 ms

Page Rendered

209 ms

idalab.de screenshot

About Website

Welcome to idalab.de homepage info - get ready to check Idalab best content right away, or after learning these important things about idalab.de

We support biotech, pharma and medtech companies moving forward with artificial intelligence technology.

Visit idalab.de

Key Findings

We analyzed Idalab.de page load time and found that the first response time was 111 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

idalab.de performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

idalab.de

111 ms

gSUMtNGHfef0jAii_NqHNiRNLdhKnaCyNFfv06QuBttfeG3IfFHN4UJLFRbh52jhWDjDjDiK5Q6uZAsRZ2ZRwQFywQqtjhIhwg74MkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFG-Au8SkuliWFXjW4qOAIhdYw0SaBujW48Sagyjh90jhNlOe8qjAUyjKoqZPUCdhFydeyzSabCSaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCiaiaOc8qjAUyjKoqZPUaiaS0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPJHjAFudA80OWgkdkGHfFYOMsMMeMI6MKGHfwnOMsMMeMw6MKGHfwDOMsMMeM96MKGHfwWOMsMMeMS6MKGHfwaOMsMMeMv6MKGHfwdOMsMMegI6MTMgv0Ka73j.js

62 ms

css2

77 ms

legacy.js

54 ms

modern.js

78 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Idalab.de, 26% (9 requests) were made to Assets.squarespace.com and 21% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (646 ms) relates to the external source Sc.lfeeder.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (31%)

Content Size

4.3 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idalab.de main page is 4.3 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. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 255.7 kB

  • Original 287.4 kB
  • After minification 228.2 kB
  • After compression 31.7 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 59.3 kB, which is 21% 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 255.7 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

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

JavaScript Optimization

-51%

Potential reduce by 1.1 MB

  • Original 2.1 MB
  • After minification 2.1 MB
  • After compression 1.0 MB

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 1.1 MB or 51% of the original size.

CSS Optimization

-16%

Potential reduce by 3.1 kB

  • Original 19.2 kB
  • After minification 19.2 kB
  • After compression 16.1 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. Idalab.de needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (60%)

Requests Now

25

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

idalab.de

idalab.de

111 ms

gSUMtNGHfef0jAii_NqHNiRNLdhKnaCyNFfv06QuBttfeG3IfFHN4UJLFRbh52jhWDjDjDiK5Q6uZAsRZ2ZRwQFywQqtjhIhwg74MkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFG-Au8SkuliWFXjW4qOAIhdYw0SaBujW48Sagyjh90jhNlOe8qjAUyjKoqZPUCdhFydeyzSabCSaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCiaiaOc8qjAUyjKoqZPUaiaS0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPJHjAFudA80OWgkdkGHfFYOMsMMeMI6MKGHfwnOMsMMeMw6MKGHfwDOMsMMeM96MKGHfwWOMsMMeMS6MKGHfwaOMsMMeMv6MKGHfwdOMsMMegI6MTMgv0Ka73j.js

gSUMtNGHfef0jAii_NqHNiRNLdhKnaCyNFfv06QuBttfeG3IfFHN4UJLFRbh52jhWDjDjDiK5Q6uZAsRZ2ZRwQFywQqtjhIhwg74MkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeFG-Au8SkuliWFXjW4qOAIhdYw0SaBujW48Sagyjh90jhNlOe8qjAUyjKoqZPUCdhFydeyzSabCSaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0jhyTdAmDOAuuSasyScbljQZCSkoDSWmyScmDSeBRZPoRdhXCiaiaOc8qjAUyjKoqZPUaiaS0SaBujW48SagyjhmDjhy8ZYmC-Ao1OcFzdPJHjAFudA80OWgkdkGHfFYOMsMMeMI6MKGHfwnOMsMMeMw6MKGHfwDOMsMMeM96MKGHfwWOMsMMeMS6MKGHfwaOMsMMeMv6MKGHfwdOMsMMegI6MTMgv0Ka73j.js

62 ms

css2

css2

77 ms

legacy.js

legacy.js

54 ms

modern.js

modern.js

78 ms

extract-css-runtime-ee07f4404f3b07ef81a8-min.en-US.js

extract-css-runtime-ee07f4404f3b07ef81a8-min.en-US.js

71 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

210 ms

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

77 ms

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

209 ms

common-vendors-8db852056516153189c0-min.en-US.js

common-vendors-8db852056516153189c0-min.en-US.js

214 ms

common-11e18ea65739225beb15-min.en-US.js

common-11e18ea65739225beb15-min.en-US.js

215 ms

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

performance-74d24f5c2adcf3b8ee8a-min.en-US.js

213 ms

site.css

site.css

81 ms

jquery.min.js

jquery.min.js

78 ms

js

js

381 ms

static.css

static.css

59 ms

site-bundle.11fff701a22dbd232e9127391845b3e2.js

site-bundle.11fff701a22dbd232e9127391845b3e2.js

41 ms

lftracker_v1_DzLR5a53wDA7BoQ2.js

lftracker_v1_DzLR5a53wDA7BoQ2.js

646 ms

insight.min.js

insight.min.js

291 ms

gtm.js

gtm.js

272 ms

idalab_white_RGB.png

idalab_white_RGB.png

316 ms

idalab_header_bg.png

idalab_header_bg.png

340 ms

Berge+Drive+Photo+copy+2.jpeg

Berge+Drive+Photo+copy+2.jpeg

330 ms

Cloud+data+pipeline+hero+image.jpg

Cloud+data+pipeline+hero+image.jpg

484 ms

AtlasGrotesk-Regular-Web.woff

AtlasGrotesk-Regular-Web.woff

211 ms

AtlasGrotesk-Bold-Web.woff

AtlasGrotesk-Bold-Web.woff

210 ms

d

d

76 ms

d

d

100 ms

d

d

100 ms

d

d

107 ms

d

d

107 ms

d

d

108 ms

insight_tag_errors.gif

insight_tag_errors.gif

116 ms

p.gif

p.gif

22 ms

Accessibility Review

idalab.de accessibility score

97

Accessibility Issues

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

idalab.de best practices score

83

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

idalab.de SEO score

91

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

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 Idalab.de 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 Idalab.de 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

idalab.de

Open Graph data is detected on the main page of Idalab. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: