3.9 sec in total
365 ms
3.4 sec
138 ms
Visit ecosign.net now to see the best up-to-date Ecosign content for Germany and also check out these interesting facts you probably never knew about ecosign.net
Studieren Sie Nachhaltiges Design an der ecosign / Akademie für Gestaltung in Köln! ➜ Informieren Sie sich jetzt! ❤ Wir freuen uns auf Sie.
Visit ecosign.netWe analyzed Ecosign.net page load time and found that the first response time was 365 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ecosign.net performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value17.5 s
0/100
25%
Value6.1 s
44/100
10%
Value1,590 ms
12/100
30%
Value0
100/100
15%
Value9.7 s
29/100
10%
365 ms
1316 ms
216 ms
213 ms
400 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 78% of them (70 requests) were addressed to the original Ecosign.net, 7% (6 requests) were made to D3vbj265bmdenw.cloudfront.net and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ecosign.net.
Page size can be reduced by 630.0 kB (32%)
2.0 MB
1.4 MB
In fact, the total size of Ecosign.net main page is 2.0 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 34.8 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 34.8 kB or 75% of the original size.
Potential reduce by 389.3 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. Obviously, Ecosign needs image optimization as it can save up to 389.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.4 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 157.4 kB or 58% of the original size.
Potential reduce by 48.6 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. Ecosign.net needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 83% of the original size.
Number of requests can be reduced by 29 (37%)
78
49
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecosign. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ecosign.net
365 ms
www.ecosign.net
1316 ms
content.css
216 ms
stylesheet_fab097ae4c.css
213 ms
ee3680.js
400 ms
jquery.min.js
34 ms
css_browser_selector.js
216 ms
jquery.yasp.js
220 ms
gen_validatorv31.js
350 ms
cursordivscroll.js
253 ms
jquery.jplayer.min.js
429 ms
javascript_757c080409.js
314 ms
css
44 ms
jquery.uniform.min.js
314 ms
uniform.default.css
325 ms
cursordivscroll.js
368 ms
jquery.jplayer.min.js
523 ms
iscroll.js
523 ms
mobile.js
433 ms
jquery.fancybox-1.3.4.pack.js
454 ms
jquery.fancybox-1.3.4.css
481 ms
jquery.amx_slider.js
519 ms
styles_amx.css
540 ms
js_jquery.js
563 ms
conversion.js
27 ms
visitor.js
168 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
5 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
7 ms
ga.js
15 ms
02.jpg
213 ms
03.jpg
108 ms
04.jpg
211 ms
05_02.jpg
232 ms
06.jpg
229 ms
07.jpg
250 ms
08.jpg
212 ms
09.jpg
315 ms
10.jpg
317 ms
11.jpg
320 ms
12.jpg
446 ms
13.jpg
461 ms
14.jpg
359 ms
15.jpg
420 ms
16.jpg
422 ms
17.jpg
424 ms
18.jpg
468 ms
19_02.jpg
525 ms
21.jpg
529 ms
22.jpg
529 ms
24.jpg
721 ms
25.jpg
722 ms
26.jpg
579 ms
27.jpg
721 ms
28.jpg
720 ms
29.jpg
720 ms
30.jpg
720 ms
31.jpg
822 ms
32.jpg
820 ms
33.jpg
823 ms
34.jpg
819 ms
35.jpg
823 ms
36.jpg
828 ms
37.jpg
924 ms
__utm.gif
15 ms
38.jpg
898 ms
39.jpg
898 ms
collect
53 ms
t.js
493 ms
40.jpg
835 ms
41.jpg
734 ms
42.jpg
744 ms
43.jpg
826 ms
44.jpg
812 ms
45_02.jpg
810 ms
logo-ecosign-koeln.png
800 ms
bookmarks-facebook.png
736 ms
bookmarks-twitter.png
753 ms
bookmarks-google.png
827 ms
nav-linie.png
818 ms
icon-link-pfeil.png
727 ms
spr_social.png
753 ms
cnt.php
240 ms
144 ms
3f20c57ef2eefabcc034da6fc5ac9184.png
151 ms
b545561a3d269ae9786546ec34101e6e.png
49 ms
d7c1f10123ef94bb5df4270c8db630ff.png
53 ms
9ca9f6048b33cfdeaf06a0630fc5db91.png
43 ms
feed989c32c41810796d45b4252091f9.png
46 ms
621f2124492891be6bb28e6ebd1fdb66.png
43 ms
28 ms
ecosign.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ecosign.net 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
ecosign.net SEO score
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 Ecosign.net 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 Ecosign.net 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.
ecosign.net
Open Graph description is not detected on the main page of Ecosign. 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: