5.8 sec in total
288 ms
5.3 sec
191 ms
Welcome to codetwo.de homepage info - get ready to check Codetwo best content for Germany right away, or after learning these important things about codetwo.de
Lösungen für Microsoft 365 und Exchange. Über 100.000 Unternehmen in 150 Ländern benutzen täglich unsere Software. 24-Stunden-Kundenservice. Microsoft Gold Partner.
Visit codetwo.deWe analyzed Codetwo.de page load time and found that the first response time was 288 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
codetwo.de performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value4.4 s
38/100
25%
Value3.2 s
91/100
10%
Value900 ms
31/100
30%
Value0
100/100
15%
Value7.8 s
44/100
10%
288 ms
673 ms
195 ms
197 ms
207 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 85% of them (125 requests) were addressed to the original Codetwo.de, 3% (4 requests) were made to Google-analytics.com and 2% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Codetwo.de.
Page size can be reduced by 529.0 kB (49%)
1.1 MB
550.1 kB
In fact, the total size of Codetwo.de main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 577.3 kB which makes up the majority of the site volume.
Potential reduce by 43.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 43.2 kB or 80% of the original size.
Potential reduce by 34.0 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. Codetwo images are well optimized though.
Potential reduce by 382.8 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 382.8 kB or 66% of the original size.
Potential reduce by 68.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. Codetwo.de needs all CSS files to be minified and compressed as it can save up to 68.9 kB or 78% of the original size.
Number of requests can be reduced by 80 (56%)
142
62
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Codetwo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
codetwo.de
288 ms
www.codetwo.de
673 ms
reset.css
195 ms
text.css
197 ms
grid.css
207 ms
jquery-ui-1.10.0.min.css
213 ms
jquery.fancybox.css
211 ms
image.css
208 ms
base.css
388 ms
navigation.css
393 ms
jquery-ui.css
402 ms
typo.css
401 ms
button.css
404 ms
icon.css
403 ms
content.css
601 ms
header.css
596 ms
menu.css
599 ms
feature-list.css
597 ms
screenshot-list.css
601 ms
faq.css
603 ms
video-list.css
808 ms
text.css
803 ms
pricing.css
804 ms
screencast-list.css
801 ms
page-product.css
805 ms
main-page.css
807 ms
counter.css
1004 ms
clientlogo.css
1008 ms
jquery-1.9.0.min.js
1159 ms
jquery-ui-1.10.0.min.js
1213 ms
jquery.droppy.js
1003 ms
jquery.bxslider.min.js
1037 ms
jquery.fancybox.pack.js
1210 ms
jquery.scrollUp.min.js
1205 ms
jquery.fancybox-media.js
1201 ms
main.js
1210 ms
lib.js
1350 ms
in.js
36 ms
ga-events.js
1409 ms
sliding.js
1228 ms
cookielaw.js
1218 ms
collapse.js
1213 ms
script.js
1217 ms
script-custom.js
1341 ms
faq.js
1389 ms
pricing.js
1237 ms
download.js
1236 ms
screencast-list.js
1229 ms
menu-accordion.js
1228 ms
tabs.js
1356 ms
testimonial-list.js
1390 ms
clientlogo.js
1226 ms
gtm.js
64 ms
bg-logo.png
799 ms
lang-options.gif
799 ms
bg-hoffman.jpg
1225 ms
hfm-box-bg.gif
931 ms
joc-social-de-bg.gif
978 ms
gplus-35x35.gif
991 ms
facebook-35x35.gif
992 ms
linkedin-35x35.gif
997 ms
twitter-35x35.gif
1123 ms
makieta-01-01.png
1153 ms
makieta-01-02.png
1183 ms
makieta-01-03.png
1188 ms
makieta-01-04.png
1198 ms
buttontype.cgi
117 ms
tracking.js
97 ms
makieta-01-05.png
1309 ms
makieta-02-01.png
1326 ms
dc.js
38 ms
analytics.js
22 ms
conversion_async.js
22 ms
48 ms
linkid.js
25 ms
script_data.js
122 ms
__utm.gif
18 ms
collect
14 ms
collect
19 ms
makieta-02-02.png
1229 ms
39 ms
collect
83 ms
makieta-02-03.png
1199 ms
makieta-02-04.png
1200 ms
makieta-02-05.png
1229 ms
makieta-03-01.png
1329 ms
makieta-03-02.png
1321 ms
ga-audiences
18 ms
localization.de.1.2169ce9f7efb40e17b2d66a3ceb7be22_b358330da399a61e2d070cd1b17b1ba9.js
63 ms
ping
96 ms
makieta-03-03.png
1236 ms
makieta-03-04.png
1186 ms
makieta-03-05.png
1189 ms
makieta-04-01.png
1216 ms
makieta-04-02.png
1315 ms
makieta-04-03.png
1336 ms
makieta-04-04.png
1232 ms
makieta-04-05.png
1179 ms
makieta-05-01.png
1180 ms
makieta-05-02.png
1207 ms
makieta-05-03.png
1309 ms
makieta-05-04.png
1329 ms
makieta-05-05.png
1216 ms
makieta-06-01.png
1199 ms
makieta-06-02.png
1181 ms
makieta-06-03.png
1212 ms
widgets.js
136 ms
secureAnonymousFramework
219 ms
plusone.js
105 ms
sliding.tollfree.css
1285 ms
cb=gapi.loaded_0
28 ms
sliding.mailus.css
1205 ms
sliding.opinion.css
1176 ms
cookielaw.css
1177 ms
makieta-06-04.png
1190 ms
makieta-06-05.png
1206 ms
makieta-07-01.png
1183 ms
makieta-07-02.png
1172 ms
makieta-07-03.png
1170 ms
makieta-07-04.png
1175 ms
makieta-07-05.png
1174 ms
makieta-08-01.png
1182 ms
makieta-08-02.png
1184 ms
makieta-08-03.png
1175 ms
rss-20x20.png
1175 ms
wp-ex2013-migration-guide-hp-banner-de.png
1183 ms
ms-partner.gif
1187 ms
windows-7.gif
1187 ms
windows-8.gif
1181 ms
windows-server-2012.gif
1174 ms
windows-server-2008-r2.gif
1179 ms
msexchange-gold-award.gif
1190 ms
msexchange-readers-choice-winner.gif
1189 ms
msexchange-readers-choice-runnerup.gif
1197 ms
tucows.gif
1185 ms
cnet.gif
1169 ms
gplus-32x32.png
1183 ms
twitter-32x32.png
1197 ms
ytube-32x32.png
1184 ms
linkedin-32x32.png
1196 ms
facebook-32x32.png
1176 ms
btn-your-opinion-de.gif
1169 ms
bg-logo-grey.gif
1191 ms
btn-clients-prev.gif
1185 ms
btn-clients-next.gif
1185 ms
top.png
1194 ms
bg.gif
1122 ms
codetwo.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
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
Buttons do not have an accessible name
Links do not have a discernible name
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
codetwo.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
codetwo.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codetwo.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Codetwo.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.
codetwo.de
Open Graph data is detected on the main page of Codetwo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: