5.2 sec in total
285 ms
4.5 sec
376 ms
Click here to check amazing Eidex content. Otherwise, check out these important facts you probably never knew about eidex.de
EIDEX Werbemittel Fullservice ► Versand von Werbeartikeln und Give Aways ✓ Größte Auswahl an Werbemitteln in München ➜ hier mehr erfahren
Visit eidex.deWe analyzed Eidex.de page load time and found that the first response time was 285 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eidex.de performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.3 s
10/100
25%
Value8.0 s
22/100
10%
Value20 ms
100/100
30%
Value0.007
100/100
15%
Value5.7 s
68/100
10%
285 ms
367 ms
100 ms
198 ms
196 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 65% of them (91 requests) were addressed to the original Eidex.de, 20% (28 requests) were made to Static.xx.fbcdn.net and 8% (11 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Eidex.de.
Page size can be reduced by 620.3 kB (18%)
3.4 MB
2.8 MB
In fact, the total size of Eidex.de main page is 3.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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 50.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 50.8 kB or 79% of the original size.
Potential reduce by 336.1 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, Eidex needs image optimization as it can save up to 336.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 197.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 197.1 kB or 71% of the original size.
Potential reduce by 36.3 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. Eidex.de needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 83% of the original size.
Number of requests can be reduced by 48 (35%)
137
89
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eidex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
eidex.de
285 ms
www.eidex.de
367 ms
styles.css
100 ms
anythingslider.css
198 ms
news.css
196 ms
fader.css
199 ms
jquery.fullbg.js
201 ms
jquery.dropshadow.js
200 ms
jquery.anythingslider.js
298 ms
jquery.easing.1.3.js
293 ms
swfobject.js
293 ms
jquery.anythingslider.fx.js
290 ms
slides.min.jquery.js
292 ms
tooltip.js
294 ms
highslide.js
679 ms
general.js
387 ms
highslide.css
484 ms
all.js
159 ms
jquery.min.js
489 ms
spacer.gif
113 ms
display_thumb.php
192 ms
display_thumb.php
512 ms
display_thumb.php
265 ms
display_thumb.php
238 ms
display_thumb.php
275 ms
display_thumb.php
496 ms
xing.png
230 ms
news_screen.png
325 ms
display_thumb.php
534 ms
display_thumb.php
481 ms
display_thumb.php
486 ms
display_thumb.php
528 ms
display_thumb.php
696 ms
display_thumb.php
699 ms
display_thumb.php
735 ms
display_thumb.php
717 ms
ga.js
25 ms
logo.png
637 ms
bg_sticker.png
636 ms
bg_mainnav.png
732 ms
mainnav_arrows.png
734 ms
transp_black.png
792 ms
button_right.png
793 ms
button1.png
811 ms
bg_eidex_film.png
1002 ms
bg_pageup.png
808 ms
promo_bg_e24.png
810 ms
promo_bg_about.png
969 ms
fb_head.png
877 ms
display_thumb.php
1016 ms
display_thumb.php
1009 ms
display_thumb.php
1030 ms
display_thumb.php
1082 ms
display_thumb.php
1179 ms
display_thumb.php
1113 ms
display_thumb.php
1121 ms
__utm.gif
32 ms
161 ms
display_thumb.php
967 ms
xd_arbiter.php
153 ms
xd_arbiter.php
287 ms
display_thumb.php
1037 ms
display_thumb.php
1274 ms
display_thumb.php
1016 ms
display_thumb.php
1241 ms
display_thumb.php
998 ms
fan.php
541 ms
display_thumb.php
1179 ms
display_thumb.php
1035 ms
display_thumb.php
1018 ms
display_thumb.php
1011 ms
display_thumb.php
1021 ms
display_thumb.php
984 ms
display_thumb.php
982 ms
display_thumb.php
927 ms
display_thumb.php
875 ms
display_thumb.php
846 ms
display_thumb.php
867 ms
display_thumb.php
850 ms
display_thumb.php
862 ms
display_thumb.php
899 ms
display_thumb.php
908 ms
ebiMDO3r-8l.css
172 ms
jGc-59L_9lo.css
217 ms
6qHpHChjY_J.css
259 ms
k5BhlqovqZn.css
292 ms
ztINr5qMqM_.css
331 ms
uVjHKJ0glvg.css
339 ms
q68gy-v_YMF.js
372 ms
FJmpeSpHpjS.js
397 ms
0wM5s1Khldu.js
299 ms
1bNoFZUdlYZ.js
337 ms
njO1TPvGzoR.js
350 ms
OloiM1PZafe.js
394 ms
LTv6ZK-5zxz.js
495 ms
1FCa-btixu2.js
419 ms
Oagsvfb4VWi.js
422 ms
pObvZSrFc_4.js
416 ms
Kt4tkgSRvHH.js
417 ms
H3EKDTObx05.js
419 ms
eR-qA8bp1RM.js
454 ms
1QuX41zDRrx.js
455 ms
display_thumb.php
878 ms
display_thumb.php
884 ms
display_thumb.php
868 ms
display_thumb.php
869 ms
display_thumb.php
906 ms
prev.png
843 ms
next.png
775 ms
slider_ctrl_default.png
753 ms
bg_body.jpg
840 ms
display_thumb.php
774 ms
progress.gif
783 ms
528482_10150929442969488_1334224245_n.jpg
311 ms
safe_image.php
695 ms
safe_image.php
868 ms
575058_10150929506349488_1746094655_n.jpg
345 ms
10628430_827729790620963_4921722445944387189_n.jpg
445 ms
12805734_1333774363314927_9014870906858986346_n.jpg
424 ms
12241632_130395453990802_4053736156150547219_n.jpg
465 ms
426202_286652694730544_1421431938_n.jpg
473 ms
11951840_153003275037169_5083768745644305874_n.jpg
461 ms
10616346_749470281778991_5131815032800419565_n.jpg
492 ms
934113_10154447610994488_2373331280858855140_n.jpg
535 ms
3855_10154447590029488_7547646552502000824_n.jpg
532 ms
12118696_10154290837104488_9123302807033542991_n.png
695 ms
wL6VQj7Ab77.png
147 ms
s7jcwEQH7Sx.png
149 ms
QDwYpIaRyfG.png
148 ms
pimRBh7B6ER.png
149 ms
K00K-UgnsKu.png
148 ms
gxbPuQdXIZP.png
75 ms
zoomin.cur
99 ms
I6-MnjEovm5.js
44 ms
pQrUxxo5oQp.js
81 ms
transp_white.png
102 ms
zoomout.cur
101 ms
loader.white.gif
101 ms
display_thumb.php
823 ms
eidex.de 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
eidex.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
eidex.de 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eidex.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 Eidex.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.
eidex.de
Open Graph description is not detected on the main page of Eidex. 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: