Tools & Wizards About Us
toobrain.com screenshot

Report Summary

  • 0

    Performance

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

toobrain.com

Startseite - toobrain.com

Page Load Speed

41 sec in total

First Response

348 ms

Resources Loaded

40.4 sec

Page Rendered

170 ms

toobrain.com screenshot

About Website

Visit toobrain.com now to see the best up-to-date Toobrain content and also check out these interesting facts you probably never knew about toobrain.com

toobrain - die innovative Lernplattform erklärt für euch schwerige Dinge einfach. User haben auch die Möglichkeit selbst Lernvideos hochzuladen.

Visit toobrain.com

Key Findings

We analyzed Toobrain.com page load time and found that the first response time was 348 ms and then it took 40.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

toobrain.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

toobrain.com

348 ms

www.toobrain.com

318 ms

index.htm

114 ms

temp.css

97 ms

loadscript.php

626 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 79% of them (55 requests) were addressed to the original Toobrain.com, 6% (4 requests) were made to Pagead2.googlesyndication.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Sedotracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.8 kB (48%)

Content Size

596.4 kB

After Optimization

311.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Toobrain.com main page is 596.4 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. 30% of websites need less resources to load. Images take 234.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 18.5 kB

  • Original 25.7 kB
  • After minification 22.7 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 12% 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 18.5 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 11.5 kB

  • Original 234.1 kB
  • After minification 222.6 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. Toobrain images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 150.1 kB

  • Original 214.3 kB
  • After minification 149.1 kB
  • After compression 64.2 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 150.1 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 104.6 kB

  • Original 122.2 kB
  • After minification 81.7 kB
  • After compression 17.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. Toobrain.com needs all CSS files to be minified and compressed as it can save up to 104.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (51%)

Requests Now

65

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toobrain.com

toobrain.com

348 ms

www.toobrain.com

www.toobrain.com

318 ms

index.htm

index.htm

114 ms

temp.css

temp.css

97 ms

loadscript.php

loadscript.php

626 ms

show_ads.js

show_ads.js

11 ms

et_mmedetect.js

et_mmedetect.js

19665 ms

layout.css

layout.css

113 ms

base.css

base.css

96 ms

iehacks.css

iehacks.css

187 ms

basemod.css

basemod.css

192 ms

content.css

content.css

191 ms

print_020_draft.css

print_020_draft.css

193 ms

print_base.css

print_base.css

97 ms

topnav_m.png

topnav_m.png

99 ms

topnav_l.png

topnav_l.png

175 ms

topnav_r.png

topnav_r.png

96 ms

submit_small.png

submit_small.png

98 ms

t27.png

t27.png

98 ms

t27_m.png

t27_m.png

93 ms

header_l.png

header_l.png

193 ms

header_m.png

header_m.png

195 ms

header_r.png

header_r.png

199 ms

arrow.png

arrow.png

196 ms

button_login.png

button_login.png

195 ms

bg.png

bg.png

197 ms

nav_1.png

nav_1.png

277 ms

nav_arrow.png

nav_arrow.png

289 ms

nav_2.png

nav_2.png

290 ms

nav_3.png

nav_3.png

290 ms

eufnds.jpg

eufnds.jpg

292 ms

icons_small.png

icons_small.png

292 ms

video_teaser.png

video_teaser.png

374 ms

video_teaser_h1.png

video_teaser_h1.png

377 ms

video_teaser_m.png

video_teaser_m.png

379 ms

video_teaser_b.png

video_teaser_b.png

381 ms

vorteile.png

vorteile.png

381 ms

usp_1.png

usp_1.png

381 ms

usp_2.png

usp_2.png

486 ms

requests.png

requests.png

488 ms

groups.png

groups.png

489 ms

usp_6.png

usp_6.png

490 ms

start_requests_t.png

start_requests_t.png

490 ms

arrow_green.png

arrow_green.png

489 ms

start_requests_b.png

start_requests_b.png

590 ms

teaser_register.png

teaser_register.png

589 ms

blue25.png

blue25.png

587 ms

blue25_m.png

blue25_m.png

585 ms

blue25_cam.png

blue25_cam.png

588 ms

ca-pub-2083006405626117.js

ca-pub-2083006405626117.js

148 ms

zrt_lookup.html

zrt_lookup.html

43 ms

show_ads_impl.js

show_ads_impl.js

60 ms

cm

cm

225 ms

blue25_butt.png

blue25_butt.png

558 ms

20100202104147000161_13_t.png

20100202104147000161_13_t.png

878 ms

vita_henkhansen_t.png

vita_henkhansen_t.png

705 ms

right_bottom.png

right_bottom.png

603 ms

feedback.png

feedback.png

606 ms

ads

ads

128 ms

osd.js

osd.js

7 ms

right_h1.png

right_h1.png

529 ms

skyscraper_bg.png

skyscraper_bg.png

599 ms

DE_Asso_18-7-14_banners_SSD_changes_120x600.gif

DE_Asso_18-7-14_banners_SSD_changes_120x600.gif

12 ms

178 ms

abg.js

abg.js

35 ms

cnt.php

cnt.php

19997 ms

footer.png

footer.png

95 ms

ga.js

ga.js

22 ms

__utm.gif

__utm.gif

14 ms

__utm.gif

__utm.gif

9 ms

Accessibility Review

toobrain.com accessibility score

34

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

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

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

toobrain.com 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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

toobrain.com SEO score

82

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

Document doesn't have a <title> element

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toobrain.com 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 Toobrain.com main page’s claimed encoding is iso-8859-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

toobrain.com

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