Tools & Wizards About Us
igel-faktor.de screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

igel-faktor.de

Der Igel-Faktor, Fachbuch von Thomas Kilian – * 2008 bis ✝ 2012

Page Load Speed

2.9 sec in total

First Response

525 ms

Resources Loaded

2.1 sec

Page Rendered

214 ms

igel-faktor.de screenshot

About Website

Visit igel-faktor.de now to see the best up-to-date Igel Faktor content and also check out these interesting facts you probably never knew about igel-faktor.de

Thomas Kilian zeigte in seinem Fachbuch „Der Igel-Faktor“ (2009 erschienen), wie man im „virtuellen Steckrübenfeld“ von Kunden gefunden wird.

Visit igel-faktor.de

Key Findings

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

Performance Metrics

igel-faktor.de performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

525 ms

legacy_affl_style.css

187 ms

learndash_quiz_front.min.css

287 ms

dashicons.min.css

379 ms

styles.css

288 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Igel-faktor.de, 2% (1 request) were made to Wp-ux.de. The less responsive or slowest element that took the longest time to load (677 ms) relates to the external source Thoxan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.9 kB (26%)

Content Size

247.5 kB

After Optimization

183.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Igel-faktor.de main page is 247.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. 45% of websites need less resources to load. Images take 165.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 63.7 kB

  • Original 82.3 kB
  • After minification 81.3 kB
  • After compression 18.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. 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 63.7 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 240 B

  • Original 165.2 kB
  • After minification 164.9 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. Igel Faktor images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 20 B

  • Original 44 B
  • After minification 24 B
  • After compression 24 B

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 20 B or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (69%)

Requests Now

39

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

525 ms

legacy_affl_style.css

legacy_affl_style.css

187 ms

learndash_quiz_front.min.css

learndash_quiz_front.min.css

287 ms

dashicons.min.css

dashicons.min.css

379 ms

styles.css

styles.css

288 ms

jquery.dropdown.min.css

jquery.dropdown.min.css

286 ms

learndash_lesson_video.min.css

learndash_lesson_video.min.css

288 ms

style.css

style.css

382 ms

customcss.css

customcss.css

380 ms

learndash.min.css

learndash.min.css

475 ms

borlabs-cookie-1-de.css

borlabs-cookie-1-de.css

385 ms

jquery.min.js

jquery.min.js

484 ms

frontend.js

frontend.js

470 ms

borlabs-cookie-config-de.json.js

borlabs-cookie-config-de.json.js

472 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

474 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

473 ms

public.js

public.js

565 ms

ust.min.js

ust.min.js

492 ms

getcurrentusers-min.js

getcurrentusers-min.js

503 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

502 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

503 ms

footerstyle.css

footerstyle.css

589 ms

underscore.min.js

underscore.min.js

573 ms

wp-util.min.js

wp-util.min.js

573 ms

scripts-footer-min.js

scripts-footer-min.js

677 ms

legacy-scripts-min.js

legacy-scripts-min.js

575 ms

wi_lightbox-min.js

wi_lightbox-min.js

575 ms

wyldinsights-scripts-min.js

wyldinsights-scripts-min.js

665 ms

learndash.js

learndash.js

668 ms

thoxan-logo-2.png

thoxan-logo-2.png

179 ms

igel-faktor1.jpg

igel-faktor1.jpg

273 ms

buch_igel_faktor.jpg

buch_igel_faktor.jpg

200 ms

igel_website-600x400.jpg

igel_website-600x400.jpg

362 ms

rezensionen-600x400.png

rezensionen-600x400.png

365 ms

autor_thomas_kilian1-600x400.jpg

autor_thomas_kilian1-600x400.jpg

274 ms

x-logo-1.svg

x-logo-1.svg

279 ms

boxicons.woff

boxicons.woff

248 ms

getIP.php

getIP.php

508 ms

bct-mailchimp-vanilla-main.png

bct-mailchimp-vanilla-main.png

96 ms

bct-calendly-main.png

bct-calendly-main.png

97 ms

cb-facebook-main.png

cb-facebook-main.png

95 ms

Accessibility Review

igel-faktor.de accessibility score

90

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

Buttons do not have an accessible name

Best Practices

igel-faktor.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

SEO Factors

igel-faktor.de SEO score

100

Search Engine Optimization Advices

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igel-faktor.de 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 Igel-faktor.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

igel-faktor.de

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