Tools & Wizards About Us
digikey.mx screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

digikey.mx

DigiKey México - Distribuidor de componentes electrónicos

Page Load Speed

2.6 sec in total

First Response

463 ms

Resources Loaded

1.6 sec

Page Rendered

485 ms

digikey.mx screenshot

About Website

Visit digikey.mx now to see the best up-to-date Digi Key content and also check out these interesting facts you probably never knew about digikey.mx

DigiKey ofrece millones de productos de miles de fabricantes, mucha cantidades en stock disponibles para envío en el mismo día. Se acepta Apple Pay, Google Pay™ y Paypal. ¡Haga su pedio hoy por intern...

Visit digikey.mx

Key Findings

We analyzed Digikey.mx page load time and found that the first response time was 463 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

digikey.mx performance score

0

Network Requests Diagram

www.digikey.com.mx

463 ms

fonts.css

13 ms

global.min.css

22 ms

empty.css

20 ms

combined.css

46 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Digikey.mx, 6% (5 requests) were made to Info.digikey.com and 2% (2 requests) were made to Sealserver.trustwave.com. The less responsive or slowest element that took the longest time to load (618 ms) relates to the external source Digikey.com.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.7 kB (43%)

Content Size

991.5 kB

After Optimization

565.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digikey.mx main page is 991.5 kB. 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. HTML takes 359.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 308.5 kB

  • Original 359.8 kB
  • After minification 284.7 kB
  • After compression 51.3 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 75.0 kB, which is 21% 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 308.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 338.9 kB
  • After minification 337.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. Digi Key images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 25.9 kB

  • Original 200.5 kB
  • After minification 200.5 kB
  • After compression 174.7 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 25.9 kB or 13% of the original size.

CSS Optimization

-97%

Potential reduce by 90.1 kB

  • Original 92.4 kB
  • After minification 2.9 kB
  • After compression 2.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. Digikey.mx needs all CSS files to be minified and compressed as it can save up to 90.1 kB or 97% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (66%)

Requests Now

79

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 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 22 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.digikey.com.mx

www.digikey.com.mx

463 ms

fonts.css

fonts.css

13 ms

global.min.css

global.min.css

22 ms

empty.css

empty.css

20 ms

combined.css

combined.css

46 ms

banner.css

banner.css

41 ms

cookie-notice.css

cookie-notice.css

41 ms

modal.css

modal.css

42 ms

carousel.css

carousel.css

50 ms

homepage.css

homepage.css

55 ms

cobrowse.css

cobrowse.css

48 ms

footer.css

footer.css

47 ms

intl-country-select-popup.css

intl-country-select-popup.css

44 ms

needHelp.css

needHelp.css

80 ms

evergage.min.js

evergage.min.js

52 ms

dk-web-components.esm.js

dk-web-components.esm.js

69 ms

dk-web-components.js

dk-web-components.js

319 ms

init.js

init.js

55 ms

seal.js

seal.js

128 ms

global.min.js

global.min.js

52 ms

header.js

header.js

115 ms

analytics.js

analytics.js

112 ms

enavsearchbar.js

enavsearchbar.js

68 ms

carousel.js

carousel.js

118 ms

homepage.js

homepage.js

115 ms

lazysizes.min.js

lazysizes.min.js

115 ms

multitrack.js

multitrack.js

114 ms

forms2.min.js

forms2.min.js

144 ms

mktoemail.js

mktoemail.js

126 ms

egain.js

egain.js

130 ms

oneTag.js

oneTag.js

126 ms

cobrowse.js

cobrowse.js

126 ms

footer.js

footer.js

137 ms

datadog-rum.js

datadog-rum.js

282 ms

collector

collector

315 ms

gtm.js

gtm.js

305 ms

setpflangcookie

setpflangcookie

532 ms

MX.png

MX.png

436 ms

Bulb.png

Bulb.png

451 ms

CartMonitor.png

CartMonitor.png

451 ms

parttracing-tab.jpg

parttracing-tab.jpg

438 ms

techforum-tab.jpg

techforum-tab.jpg

452 ms

webinars-tab.jpg

webinars-tab.jpg

437 ms

schemeit-tab.jpg

schemeit-tab.jpg

456 ms

Settings.png

Settings.png

459 ms

FastShipping.png

FastShipping.png

463 ms

FreeShip.png

FreeShip.png

488 ms

Incoterms.png

Incoterms.png

488 ms

Payment.png

Payment.png

472 ms

Visa.png

Visa.png

469 ms

MasterCard.png

MasterCard.png

478 ms

American%20Express.png

American%20Express.png

528 ms

Discover.png

Discover.png

492 ms

PayPal.png

PayPal.png

491 ms

Apple%20Pay.png

Apple%20Pay.png

496 ms

Google%20Pay.png

Google%20Pay.png

530 ms

Marketplace.png

Marketplace.png

531 ms

TechForum2.png

TechForum2.png

503 ms

icon-messaging-we-chat-120x120.png.PNG

icon-messaging-we-chat-120x120.png.PNG

506 ms

icon-delivery-truck5-120x120.png.png

icon-delivery-truck5-120x120.png.png

519 ms

icon-warehouse-cart-packages3-120x120.png.png

icon-warehouse-cart-packages3-120x120.png.png

543 ms

homepage-associations.png

homepage-associations.png

534 ms

facebook_white_icon.png

facebook_white_icon.png

536 ms

twitter_white_logo.png

twitter_white_logo.png

571 ms

youtube_white_icon.png

youtube_white_icon.png

618 ms

instagram_white_icon.png

instagram_white_icon.png

590 ms

linkedin_white_icon.png

linkedin_white_icon.png

567 ms

appstore-button.png

appstore-button.png

572 ms

google-play-button.png

google-play-button.png

575 ms

utag.js

utag.js

278 ms

logo_dk.png

logo_dk.png

574 ms

icon-angle-down.png

icon-angle-down.png

597 ms

04-shipping-boxes.jpg

04-shipping-boxes.jpg

561 ms

DevelopmentBoards.Jpg

DevelopmentBoards.Jpg

549 ms

seal_image.php

seal_image.php

186 ms

EG86992109

EG86992109

350 ms

getForm

getForm

88 ms

forms2.css

forms2.css

31 ms

forms2-theme-simple.css

forms2-theme-simple.css

53 ms

XDFrame

XDFrame

32 ms

dk_woff.woff

dk_woff.woff

175 ms

Robotics.jpg

Robotics.jpg

195 ms

Wi-Fi.jpg

Wi-Fi.jpg

188 ms

SEO Factors

digikey.mx SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digikey.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Digikey.mx 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.

Social Sharing Optimization

digikey.mx

Open Graph data is detected on the main page of Digi Key. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: