1.5 sec in total
133 ms
1.2 sec
207 ms
Welcome to digikey.de homepage info - get ready to check Digi Key best content for Germany right away, or after learning these important things about digikey.de
DigiKey bietet Millionen Produkte von Tausenden von Herstellern, viele davon auf Lager und am selben Tag versandbereit. Wir akzeptieren Apple Pay, Google Pay™ und Paypal, bestellen Sie jetzt online.
Visit digikey.deWe analyzed Digikey.de page load time and found that the first response time was 133 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
digikey.de performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value12.1 s
0/100
25%
Value10.2 s
8/100
10%
Value3,910 ms
1/100
30%
Value0.177
68/100
15%
Value16.5 s
5/100
10%
133 ms
335 ms
115 ms
95 ms
94 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 7% of them (9 requests) were addressed to the original Digikey.de, 85% (108 requests) were made to Digikey.com and 6% (7 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (388 ms) relates to the external source Digikey.com.
Page size can be reduced by 746.6 kB (55%)
1.4 MB
623.1 kB
In fact, the total size of Digikey.de 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. 60% of websites need less resources to load. Javascripts take 640.1 kB which makes up the majority of the site volume.
Potential reduce by 143.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. This page needs HTML code to be minified as it can gain 20.4 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 143.8 kB or 85% of the original size.
Potential reduce by 82.5 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, Digi Key needs image optimization as it can save up to 82.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 455.3 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 455.3 kB or 71% of the original size.
Potential reduce by 65.1 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. Digikey.de needs all CSS files to be minified and compressed as it can save up to 65.1 kB or 79% of the original size.
Number of requests can be reduced by 26 (21%)
126
100
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digi Key. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.digikey.de
133 ms
2342910375.js
335 ms
header.css
115 ms
footer.css
95 ms
homepage.css
94 ms
reset.css
105 ms
digikey.css
120 ms
fullsite.css
97 ms
responsive.css
113 ms
WebResource.axd
13 ms
ScriptResource.axd
13 ms
ScriptResource.axd
10 ms
WebResource.axd
13 ms
seal_js.php
76 ms
multitrack.js
104 ms
jquery1101min.js
98 ms
header.js
100 ms
afil-fix.js
224 ms
main.js
222 ms
footer.js
226 ms
carouFredSel.js
230 ms
digikey-webtrends.js
107 ms
hamburger.png
107 ms
seal_image.php
166 ms
headerinfo.ashx
148 ms
gray-cart.png
108 ms
gray-profile.png
108 ms
logo_dk.png
109 ms
DE_Flag.png
110 ms
cart-white.png
110 ms
triangle-white.png
107 ms
section-background.jpg
108 ms
subscribe.png
109 ms
search-button.jpg
135 ms
search-button.jpg
144 ms
net-30.jpg
188 ms
shipping-banner.jpg
135 ms
icon-cart.png
133 ms
icon-status.png
136 ms
icon-catalog.png
134 ms
icon-bom.png
135 ms
icon-new.png
136 ms
icon-articles.png
137 ms
icon-videos.png
144 ms
icon-ptm.png
136 ms
icon-rdl.png
137 ms
icon-designtools.png
136 ms
icon-calculators.png
137 ms
icon-select.png
138 ms
lineartech_LT3042_image.jpg
143 ms
red-button-background.jpg
138 ms
amphenolrf_board-to-board_image.jpg
139 ms
texasinstruments_DP83867IR_image.jpg
143 ms
te_sensor-solutions_image.jpg
143 ms
infineon_CoolMOS_P6_image.jpg
145 ms
3m_EMR-RFI_image.jpg
144 ms
onsemi_sub-1_GHz_image.jpg
145 ms
xp_ECP130_image.jpg
145 ms
cree_xlamp-XQ-E_image.jpg
146 ms
vicor_PFM-isolated-AC-DC_image.jpg
146 ms
fairchild_MEMS-motion-tracking-image.jpg
140 ms
recom_REC20-30_image.jpg
141 ms
utag.js
124 ms
idt_versaclock-6_image.jpg
64 ms
epcos_filmcapacitors_image.jpg
49 ms
rohm_BD9G341AEFJ_image.jpg
48 ms
yageo_automotive-grade_image.jpg
49 ms
atmel_SAML22_image.jpg
62 ms
linear_tech_white.jpg
60 ms
linear_tech_color.jpg
40 ms
amphenol_rf_white.jpg
35 ms
amphenol_rf_color.jpg
37 ms
texas_instruments_white.jpg
35 ms
texas_instruments_color.jpg
36 ms
te_sensor_solutions_white.jpg
38 ms
te_sensor_solutions_color.jpg
48 ms
infineon_white.jpg
55 ms
infineon_color.jpg
53 ms
3M_white.jpg
48 ms
3M_color.jpg
50 ms
onsemi_white.jpg
59 ms
onsemi_color.jpg
60 ms
XP_white.jpg
61 ms
XP_color.jpg
63 ms
cree_white.jpg
68 ms
cree_color.jpg
69 ms
vicor_white.jpg
88 ms
vicor_color.jpg
67 ms
fairchild_white.jpg
70 ms
fairchild_color.jpg
74 ms
recom_white.jpg
90 ms
recom_color.jpg
125 ms
idt_white.jpg
83 ms
idt_color.jpg
81 ms
epcos_white.jpg
92 ms
tdk_color.jpg
121 ms
rohm_white.jpg
153 ms
rohm_color.jpg
98 ms
yageo_white.jpg
132 ms
yageo_color.jpg
136 ms
atmel_white.jpg
116 ms
atmel_color.jpg
153 ms
promo-carousel-prev.png
110 ms
promo-carousel-next.png
112 ms
footer-background-notop.jpg
112 ms
de.png
114 ms
worldwide.png
114 ms
mobileapp_32.png
145 ms
techxchange_32.png
173 ms
youtube_32.png
134 ms
facebook_32.png
203 ms
twitter_32.png
209 ms
linkedin_32.png
226 ms
googleplus_32.png
157 ms
App_Store_Btn.png
282 ms
Google_Store_Btn.png
304 ms
homepage-associations.png
150 ms
white-phone.png
388 ms
white-mail.png
285 ms
app_store_btn_lrg.png
210 ms
google_store_btn_lrg.png
243 ms
utag.108.js
10 ms
utag.151.js
5 ms
utag.158.js
5 ms
utag.164.js
6 ms
utag.171.js
6 ms
utag.184.js
6 ms
digikey.de accessibility score
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
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.
digikey.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
digikey.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 doesn't use 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 Digikey.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 Digikey.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.
digikey.de
Open Graph description is not detected on the main page of Digi Key. 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: