5.1 sec in total
350 ms
3.8 sec
909 ms
Click here to check amazing Textkernel content for Germany. Otherwise, check out these important facts you probably never knew about textkernel.de
KI Recruiting-Software von Textkernel bringt seit 20 Jahren Kandidaten und Jobs zusammen - für HR und Personaldienstleistung.
Visit textkernel.deWe analyzed Textkernel.de page load time and found that the first response time was 350 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
textkernel.de performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.7 s
3/100
25%
Value7.5 s
27/100
10%
Value3,900 ms
1/100
30%
Value0.088
92/100
15%
Value14.4 s
9/100
10%
350 ms
1966 ms
125 ms
117 ms
121 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Textkernel.de, 67% (37 requests) were made to D19v1r09zwwgux.cloudfront.net and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Textkernel.com.
Page size can be reduced by 516.2 kB (59%)
877.9 kB
361.8 kB
In fact, the total size of Textkernel.de main page is 877.9 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. Javascripts take 582.9 kB which makes up the majority of the site volume.
Potential reduce by 65.3 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 65.3 kB or 75% of the original size.
Potential reduce by 927 B
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. Textkernel images are well optimized though.
Potential reduce by 366.0 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 366.0 kB or 63% of the original size.
Potential reduce by 83.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. Textkernel.de needs all CSS files to be minified and compressed as it can save up to 83.9 kB or 82% of the original size.
Number of requests can be reduced by 31 (65%)
48
17
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Textkernel. 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 10 to 1 for CSS and as a result speed up the page load time.
textkernel.de
350 ms
1966 ms
language-selector.css.gzip
125 ms
normalize.css.gzip
117 ms
style.css.gzip
121 ms
responsive.css.gzip
135 ms
font-awesome.min.css
207 ms
jquery.min.js
212 ms
humanize.js.gzip
129 ms
css
149 ms
css
212 ms
colorbox-2.css.gzip
71 ms
wp-embed.min.js.gzip
71 ms
custom.js.gzip
70 ms
jquery.colorbox.js.gzip
75 ms
sitepress.js.gzip
63 ms
gfplaceholderaddon.js.gzip
123 ms
slidebars.css.gzip
123 ms
jquery.fancybox.css.gzip
122 ms
slidebars.js.gzip
125 ms
parsley.min.js.gzip
482 ms
custom.js.gzip
123 ms
jquery.fancybox.pack.js.gzip
479 ms
addthis_widget.js
1083 ms
trac.js
471 ms
wp-emoji-release.min.js
290 ms
analytics.js
240 ms
logo@2x.png
193 ms
de.png
199 ms
en.png
191 ms
nl.png
199 ms
fr.png
195 ms
1.jpg
210 ms
bg-pattern.png
202 ms
icon-demo-medium@2x.png
305 ms
product-icon-extract@2x.png
311 ms
product-icon-sourcebox@2x.png
199 ms
product-icon-search@2x.png
288 ms
product-icon-match@2x.png
204 ms
product-icon-jobfeed@2x.png
202 ms
product-icon-harvester@2x.png
278 ms
bertrandt-ag-logo-224x84.gif
655 ms
Haufe-logo-224x84.jpg
653 ms
Baloise_logo1.jpg
659 ms
xing_logo-224x84.png
654 ms
kwp_logo-224x84.png
655 ms
logo_Rabobank-224x84.png
655 ms
azR40LUJrT4HaWK28zHmVA.woff
94 ms
3nZS3BKzlvhkwl4yjCQcjPesZW2xOQ-xsNqO47m55DA.woff
122 ms
fontawesome-webfont.woff
118 ms
anMUvcNT0H1YN4FII8wprx7IBmrqA5IG9z8WNe77b9o.woff
441 ms
anMUvcNT0H1YN4FII8wpr0bathaSTBR2c4i13_wzlb0.woff
440 ms
collect
54 ms
widgets.js
357 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
350 ms
textkernel.de accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
textkernel.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
textkernel.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Textkernel.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 Textkernel.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.
textkernel.de
Open Graph data is detected on the main page of Textkernel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: