1 sec in total
194 ms
688 ms
164 ms
Visit digikey.com now to see the best up-to-date Digi Key content for United States and also check out these interesting facts you probably never knew about digikey.com
DigiKey offers millions of products from thousands of manufacturers, many in-stock quantities available to ship same day. Apple Pay, Google Pay™ & Paypal accepted, order online today!
Visit digikey.comWe analyzed Digikey.com page load time and found that the first response time was 194 ms and then it took 852 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
digikey.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.0 s
6/100
25%
Value8.1 s
21/100
10%
Value3,450 ms
2/100
30%
Value0.177
68/100
15%
Value12.2 s
15/100
10%
194 ms
261 ms
9 ms
8 ms
13 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 96% of them (131 requests) were addressed to the original Digikey.com, 1% (2 requests) were made to Sealserver.trustkeeper.net and 1% (1 request) were made to Cdn.optimizely.com. The less responsive or slowest element that took the longest time to load (261 ms) relates to the external source Cdn.optimizely.com.
Page size can be reduced by 1.8 MB (51%)
3.6 MB
1.7 MB
In fact, the total size of Digikey.com main page is 3.6 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. 55% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 166.0 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 22.8 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 166.0 kB or 86% of the original size.
Potential reduce by 283.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, Digi Key needs image optimization as it can save up to 283.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 75% of the original size.
Potential reduce by 259.5 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.com needs all CSS files to be minified and compressed as it can save up to 259.5 kB or 80% of the original size.
Number of requests can be reduced by 18 (13%)
136
118
The browser has sent 136 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 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.digikey.com
194 ms
346228540.js
261 ms
header.css
9 ms
footer.css
8 ms
homepage.css
13 ms
reset.css
9 ms
digikey.css
10 ms
fullsite.css
9 ms
responsive.css
10 ms
ScriptResource.axd
20 ms
seal_js.php
100 ms
multitrack.js
14 ms
jquery1101min.js
40 ms
afil-fix.js
40 ms
header.js
38 ms
digikey-webtrends.js
39 ms
main.js
38 ms
footer.js
40 ms
carouFredSel.js
41 ms
hamburger.png
37 ms
logo_dk.png
33 ms
US_Flag.png
32 ms
cart-white.png
35 ms
triangle-white.png
38 ms
gray-cart.png
35 ms
gray-profile.png
35 ms
chat-white.png
36 ms
subscribe.png
38 ms
search-button.jpg
39 ms
engineers-week_banner.jpg
42 ms
shipping-banner.jpg
38 ms
icon-cart.png
39 ms
icon-status.png
40 ms
icon-catalog.png
40 ms
icon-bom.png
42 ms
icon-new.png
43 ms
icon-articles.png
41 ms
icon-videos.png
44 ms
icon-ptm.png
44 ms
icon-rdl.png
43 ms
icon-designtools.png
45 ms
icon-calculators.png
45 ms
icon-select.png
45 ms
lineartech_LT3042_image.jpg
46 ms
bourns_inductors_image.jpg
47 ms
nxp_mini-logic_image.jpg
47 ms
amphenol_micro-mini_series_image.jpg
47 ms
texasinstruments_DP83867IR_image.jpg
24 ms
te_sensor-solutions_image.jpg
29 ms
freescale_iMX-6ultralite_image.jpg
33 ms
molex_RFtechnology_image.jpg
32 ms
atmel_SAML22_image.jpg
34 ms
honeywell_digital-compassing-solutions_image.jpg
32 ms
rohm_BD7682_image.jpg
32 ms
wurth_USB_3-1_TypeC_image.jpg
33 ms
microchip_MCP9600_image.jpg
42 ms
bel_powerprotectconnect_image.jpg
40 ms
infineon_CoolMOS_P6_image.jpg
40 ms
keystone_RJ45-jacks_image.jpg
44 ms
fairchild_MEMS-motion-tracking-image.jpg
40 ms
panasonic_PAN9310-9320_image.jpg
41 ms
onsemi_sub-1_GHz_image.jpg
46 ms
cree_mh-family_image.jpg
48 ms
vicor_PFM-isolated-AC-DC_image.jpg
45 ms
toshiba_UMOS_IX-H_image.jpg
46 ms
epson_RX8900_image.jpg
43 ms
linear_tech_white.jpg
45 ms
linear_tech_color.jpg
181 ms
bourns_white.jpg
180 ms
bourns_color.jpg
180 ms
nxp_white.jpg
178 ms
nxp_color.jpg
180 ms
amphenol_commercial_white.jpg
175 ms
amphenol_commercial_color.jpg
178 ms
texas_instruments_white.jpg
180 ms
texas_instruments_color.jpg
179 ms
te_sensor_solutions_white.jpg
178 ms
te_sensor_solutions_color.jpg
177 ms
molex_white.jpg
180 ms
molex_color.jpg
177 ms
atmel_white.jpg
177 ms
atmel_color.jpg
179 ms
honeywell_white.jpg
178 ms
honeywell_color.jpg
175 ms
rohm_white.jpg
179 ms
rohm_color.jpg
169 ms
wurth_white.jpg
169 ms
wurth_color.jpg
168 ms
microchip_white.jpg
169 ms
microchip_color.jpg
168 ms
bel_white.jpg
169 ms
bel_color.jpg
161 ms
infineon_white.jpg
159 ms
infineon_color.jpg
157 ms
keystone_white.jpg
159 ms
keystone_color.jpg
159 ms
fairchild_white.jpg
159 ms
fairchild_color.jpg
155 ms
panasonic_white.jpg
155 ms
panasonic_color.jpg
155 ms
onsemi_white.jpg
154 ms
onsemi_color.jpg
152 ms
cree_white.jpg
153 ms
utag.js
127 ms
seal_image.php
76 ms
headerinfo.ashx
84 ms
cree_color.jpg
75 ms
vicor_white.jpg
75 ms
vicor_color.jpg
75 ms
toshiba_white.jpg
75 ms
toshiba_color.jpg
73 ms
epson_white.jpg
73 ms
epson_color.jpg
73 ms
mobileapp_32.png
80 ms
techxchange_32.png
73 ms
facebook_32.png
73 ms
googleplus_32.png
72 ms
linkedin_32.png
71 ms
twitter_32.png
72 ms
youtube_32.png
71 ms
App_Store_Btn.png
72 ms
Google_Store_Btn.png
71 ms
homepage-associations.png
71 ms
white-phone.png
71 ms
white-mail.png
69 ms
app_store_btn_lrg.png
70 ms
google_store_btn_lrg.png
69 ms
section-background.jpg
69 ms
search-button.jpg
69 ms
red-button-background.jpg
68 ms
promo-carousel-prev.png
69 ms
promo-carousel-next.png
68 ms
footer-background-notop.jpg
67 ms
us.png
67 ms
worldwide.png
68 ms
geo2.js
66 ms
event
32 ms
digikey.com 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
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.com 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.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digikey.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Digikey.com 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.com
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: