9 sec in total
1.8 sec
7 sec
216 ms
Visit ctg.io now to see the best up-to-date Ctg content and also check out these interesting facts you probably never knew about ctg.io
We remove complexity of addressable media production and make your marketing system flow across the customer journey.
Visit ctg.ioWe analyzed Ctg.io page load time and found that the first response time was 1.8 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ctg.io performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value8.8 s
1/100
25%
Value4.5 s
72/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value5.6 s
69/100
10%
1804 ms
218 ms
443 ms
328 ms
222 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 96% of them (53 requests) were addressed to the original Ctg.io, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ctg.io.
Page size can be reduced by 658.1 kB (49%)
1.4 MB
691.9 kB
In fact, the total size of Ctg.io main page is 1.4 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. 25% of websites need less resources to load. Images take 540.9 kB which makes up the majority of the site volume.
Potential reduce by 31.5 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 31.5 kB or 79% of the original size.
Potential reduce by 14.2 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. Ctg images are well optimized though.
Potential reduce by 297.1 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 297.1 kB or 76% of the original size.
Potential reduce by 315.4 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. Ctg.io needs all CSS files to be minified and compressed as it can save up to 315.4 kB or 83% of the original size.
Number of requests can be reduced by 25 (46%)
54
29
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ctg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.ctg.io
1804 ms
framework.css
218 ms
style.css
443 ms
colors.css
328 ms
plugins.css
222 ms
enrichments.css
224 ms
emotion.css
540 ms
emotion_ctg.css
555 ms
paypal.css
437 ms
jquery-1.7.2.min.js
975 ms
jquery.shopware.js
1351 ms
jquery.emotion.js
759 ms
bg_header_shadow.png
108 ms
ga.js
23 ms
bg_searchfield.png
109 ms
bg_arrow_search.gif
213 ms
ico_ajax-loader.gif
218 ms
logo.jpg
219 ms
ico_myaccount.png
220 ms
ico_listing-bottom-active.png
226 ms
ico-flags.png
327 ms
ico_basket.png
437 ms
bg_ajax_basket.png
436 ms
wrapper_sprite.png
434 ms
wrapper_bg.png
437 ms
mainnavigation_bg.png
440 ms
mainnav_shadow.png
542 ms
banner-1-firma.jpg
1184 ms
banner-2-ausweise.jpg
992 ms
banner-3-sa.jpg
1076 ms
banner-4-zub.jpg
973 ms
banner-5-sys.jpg
1003 ms
zu-4001551fb906266932_285x255.jpg
873 ms
zu-4004551fb92db3e4c8_285x255.jpg
1223 ms
__utm.gif
43 ms
Rondo-transparent54c6139a26eff_720x600.jpg
1586 ms
Kombi54c6149c4ae4d_720x600.jpg
1616 ms
ceVo_classic55e7dc542a2a1_720x600.jpg
1541 ms
bg_breadcrumb.png
1245 ms
emotionNewcomer
1768 ms
emotionTopSeller
1823 ms
bg_footer.png
1726 ms
bg_footer_menu.png
1764 ms
bg_newsletter.png
1796 ms
bg_arrow_newsletter.gif
1899 ms
ico_shopware.png
1944 ms
ico_closebutton.png
1987 ms
detailinfo_shadow.png
1981 ms
sprite-banner-slider.png
2015 ms
sprite_slider_arrows.png
2036 ms
ZU-90036-3_285x255.jpg
572 ms
ZU-90033-1_285x255.jpg
528 ms
zu-2000251fb8c79535dc_285x255.jpg
501 ms
zu-40201-2_285x255.jpg
498 ms
print.css
112 ms
ctg.io accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
ctg.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ctg.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ctg.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Ctg.io 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.
ctg.io
Open Graph description is not detected on the main page of Ctg. 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: