1.1 sec in total
122 ms
772 ms
248 ms
Click here to check amazing Digi Key content for Japan. Otherwise, check out these important facts you probably never knew about digikey.jp
DigiKeyは数千メーカーの数百万点におよぶ製品を取り扱っており、豊富な在庫部品で即日出荷も可能です!Apple Pay、Google Pay™、PayPalでもお支払い可能。オンラインでのご注文をお待ちしています!
Visit digikey.jpWe analyzed Digikey.jp page load time and found that the first response time was 122 ms and then it took 1 sec 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.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.7 s
1/100
25%
Value6.4 s
40/100
10%
Value500 ms
58/100
30%
Value0.177
68/100
15%
Value10.6 s
23/100
10%
122 ms
408 ms
28 ms
25 ms
28 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 8% of them (9 requests) were addressed to the original Digikey.jp, 82% (90 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 (408 ms) relates to the external source Cdn.optimizely.com.
Page size can be reduced by 734.5 kB (57%)
1.3 MB
547.7 kB
In fact, the total size of Digikey.jp main page is 1.3 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 678.4 kB which makes up the majority of the site volume.
Potential reduce by 123.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. This page needs HTML code to be minified as it can gain 17.9 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 123.5 kB or 84% of the original size.
Potential reduce by 56.6 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 56.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 489.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 489.4 kB or 72% 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.jp 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 (24%)
109
83
The browser has sent 109 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.jp
122 ms
3579530909.js
408 ms
header.css
28 ms
footer.css
25 ms
homepage.css
28 ms
reset.css
26 ms
digikey.css
29 ms
fullsite.css
32 ms
responsive.css
37 ms
WebResource.axd
17 ms
ScriptResource.axd
17 ms
ScriptResource.axd
18 ms
WebResource.axd
17 ms
seal_js.php
114 ms
multitrack.js
24 ms
jquery1101min.js
100 ms
header.js
98 ms
afil-fix.js
95 ms
main.js
95 ms
footer.js
100 ms
carouFredSel.js
97 ms
digikey-webtrends.js
97 ms
hamburger.png
54 ms
gray-cart.png
36 ms
gray-profile.png
31 ms
logo_dk.png
33 ms
JP_Flag.png
33 ms
cart-white.png
30 ms
triangle-white.png
29 ms
section-background.jpg
36 ms
subscribe.png
32 ms
search-button.jpg
35 ms
search-button.jpg
36 ms
search-features.jpg
305 ms
shipping-banner.jpg
309 ms
icon-cart.png
308 ms
icon-status.png
296 ms
icon-catalog.png
296 ms
icon-bom.png
296 ms
icon-new.png
296 ms
icon-articles.png
297 ms
icon-videos.png
298 ms
icon-ptm.png
299 ms
icon-rdl.png
297 ms
icon-designtools.png
298 ms
icon-calculators.png
300 ms
icon-select.png
302 ms
lineartech_LT6375_image.jpg
305 ms
red-button-background.jpg
300 ms
TE_usb-type-c_image.jpg
303 ms
nxp_KL81-82_image.jpg
306 ms
amphenolrf_board-to-board_image.jpg
305 ms
honeywell_ABPseries_image.jpg
309 ms
texasinstruments_LMK61xx_image.jpg
297 ms
xp_external-power-supplies_image.jpg
298 ms
alphawire_custom-wires_image.jpg
298 ms
adi_icoupler_image.jpg
297 ms
vicor_PFM-isolated-AC-DC_image.jpg
290 ms
wurth_WE-MAPI_image.jpg
297 ms
linear_tech_white.jpg
292 ms
linear_tech_color.jpg
291 ms
te_connectivity_white.jpg
296 ms
te_connectivity_color.jpg
295 ms
freescale_white.jpg
294 ms
freescale_color.jpg
294 ms
amphenol_rf_white.jpg
295 ms
amphenol_rf_color.jpg
291 ms
honeywell_white.jpg
293 ms
headerinfo.ashx
197 ms
utag.js
186 ms
seal_image.php
39 ms
honeywell_color.jpg
95 ms
texas_instruments_white.jpg
87 ms
texas_instruments_color.jpg
86 ms
XP_white.jpg
88 ms
XP_color.jpg
88 ms
alphawire_white.jpg
92 ms
alphawire_color.jpg
86 ms
analog_devices_white.jpg
90 ms
analog_devices_color.jpg
88 ms
vicor_white.jpg
82 ms
vicor_color.jpg
82 ms
wurth_white.jpg
94 ms
wurth_color.jpg
90 ms
promo-carousel-prev.png
80 ms
promo-carousel-next.png
79 ms
footer-background-notop.jpg
77 ms
jp.png
78 ms
worldwide.png
77 ms
mobileapp_32.png
77 ms
techxchange_32.png
75 ms
youtube_32.png
75 ms
facebook_32.png
73 ms
twitter_32.png
73 ms
linkedin_32.png
72 ms
googleplus_32.png
75 ms
App_Store_Btn.png
77 ms
Google_Store_Btn.png
74 ms
homepage-associations.png
76 ms
white-phone.png
73 ms
white-mail.png
72 ms
app_store_btn_lrg.png
73 ms
google_store_btn_lrg.png
73 ms
event
28 ms
utag.107.js
9 ms
utag.151.js
4 ms
utag.158.js
5 ms
utag.164.js
4 ms
utag.171.js
6 ms
utag.185.js
5 ms
digikey.jp 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.jp 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.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digikey.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Digikey.jp 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.jp
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: