Tools & Wizards About Us
digikey.ee screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

digikey.ee

DigiKey Electronics Estonia - Electronic Components Distributor

Page Load Speed

4.4 sec in total

First Response

228 ms

Resources Loaded

3.3 sec

Page Rendered

886 ms

digikey.ee screenshot

About Website

Click here to check amazing Digi Key content. Otherwise, check out these important facts you probably never knew about digikey.ee

Digi-Key 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.ee

Key Findings

We analyzed Digikey.ee page load time and found that the first response time was 228 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

digikey.ee performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value13,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.172

69/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

www.digikey.ee

228 ms

fonts.css

53 ms

global.css

112 ms

empty.css

94 ms

combined.css

89 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 82% of them (80 requests) were addressed to the original Digikey.ee, 5% (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 (1.7 sec) belongs to the original domain Digikey.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.8 kB (50%)

Content Size

886.0 kB

After Optimization

442.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digikey.ee main page is 886.0 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. 60% of websites need less resources to load. HTML takes 338.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 291.3 kB

  • Original 338.4 kB
  • After minification 264.8 kB
  • After compression 47.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 73.6 kB, which is 22% 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 291.3 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 311 B

  • Original 182.1 kB
  • After minification 181.8 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

-31%

Potential reduce by 80.0 kB

  • Original 260.3 kB
  • After minification 241.8 kB
  • After compression 180.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 80.0 kB or 31% of the original size.

CSS Optimization

-68%

Potential reduce by 72.1 kB

  • Original 105.3 kB
  • After minification 86.2 kB
  • After compression 33.2 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.ee needs all CSS files to be minified and compressed as it can save up to 72.1 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (61%)

Requests Now

89

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 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 23 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.ee

www.digikey.ee

228 ms

fonts.css

fonts.css

53 ms

global.css

global.css

112 ms

empty.css

empty.css

94 ms

combined.css

combined.css

89 ms

banner.css

banner.css

383 ms

cookie-notice.css

cookie-notice.css

290 ms

modal.css

modal.css

109 ms

carousel.css

carousel.css

130 ms

homepage.css

homepage.css

391 ms

cobrowse.css

cobrowse.css

137 ms

footer.css

footer.css

143 ms

intl-country-select-popup.css

intl-country-select-popup.css

163 ms

needHelp.css

needHelp.css

173 ms

evergage.min.js

evergage.min.js

47 ms

dk-web-components.esm.js

dk-web-components.esm.js

165 ms

optimize.js

optimize.js

56 ms

74107c42

74107c42

194 ms

seal.js

seal.js

206 ms

global.js

global.js

195 ms

header.js

header.js

213 ms

flymenu-initialized.js

flymenu-initialized.js

210 ms

enavsearchbar.js

enavsearchbar.js

225 ms

carousel.js

carousel.js

752 ms

homepage.js

homepage.js

241 ms

lazysizes.min.js

lazysizes.min.js

250 ms

multitrack.js

multitrack.js

450 ms

forms2.min.js

forms2.min.js

132 ms

mktoemail.js

mktoemail.js

273 ms

egain.js

egain.js

534 ms

oneTag.js

oneTag.js

299 ms

cobrowse.js

cobrowse.js

338 ms

footer.js

footer.js

426 ms

z0RJGAB

z0RJGAB

428 ms

InvalidRequest.aspx

InvalidRequest.aspx

360 ms

A6K2D-JZV2Q-KQATA-ZDLX9-S2NGL

A6K2D-JZV2Q-KQATA-ZDLX9-S2NGL

173 ms

setpflangcookie

setpflangcookie

670 ms

logo_dk.png

logo_dk.png

657 ms

EE.png

EE.png

181 ms

logo-sm.png

logo-sm.png

654 ms

Bulb.png

Bulb.png

655 ms

CartMonitor.png

CartMonitor.png

656 ms

parttracing-tab.jpg

parttracing-tab.jpg

656 ms

techforum-tab.jpg

techforum-tab.jpg

656 ms

webinars-tab.jpg

webinars-tab.jpg

1081 ms

schemeit-tab.jpg

schemeit-tab.jpg

1017 ms

Settings.png

Settings.png

952 ms

FastShipping.png

FastShipping.png

1042 ms

FreeShip.png

FreeShip.png

904 ms

Incoterms.png

Incoterms.png

688 ms

Payment.png

Payment.png

747 ms

Visa.png

Visa.png

1014 ms

MasterCard.png

MasterCard.png

1060 ms

American%20Express.png

American%20Express.png

1166 ms

PayPal.png

PayPal.png

1116 ms

Apple%20Pay.png

Apple%20Pay.png

1124 ms

Google%20Pay.png

Google%20Pay.png

1275 ms

Marketplace.png

Marketplace.png

1159 ms

icon-Parts.png

icon-Parts.png

1192 ms

icon-Distributor.png

icon-Distributor.png

1167 ms

TechForum2.png

TechForum2.png

1184 ms

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

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

1201 ms

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

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

1354 ms

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

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

1252 ms

homepage-associations.png

homepage-associations.png

1368 ms

facebook_white_icon.png

facebook_white_icon.png

1566 ms

twitter_white_logo.png

twitter_white_logo.png

1461 ms

youtube_white_icon.png

youtube_white_icon.png

1477 ms

instagram_white_icon.png

instagram_white_icon.png

1442 ms

linkedin_white_icon.png

linkedin_white_icon.png

1658 ms

appstore-button.png

appstore-button.png

1659 ms

google-play-button.png

google-play-button.png

1488 ms

Worlds-Largest.jpg

Worlds-Largest.jpg

495 ms

seal_image.php

seal_image.php

21 ms

dk_woff.woff

dk_woff.woff

1333 ms

New%20Products.jpg

New%20Products.jpg

1487 ms

utag.js

utag.js

552 ms

EG86992109

EG86992109

428 ms

getForm

getForm

95 ms

config.json

config.json

105 ms

z0RJGAB

z0RJGAB

1261 ms

headerinfo.ashx

headerinfo.ashx

1007 ms

GetCurrentUser

GetCurrentUser

1024 ms

Product%20Services.jpg

Product%20Services.jpg

1075 ms

Help%20Support.jpg

Help%20Support.jpg

1053 ms

Conversion%20Calculators.jpg

Conversion%20Calculators.jpg

1129 ms

forms2.css

forms2.css

51 ms

forms2-theme-simple.css

forms2-theme-simple.css

67 ms

Webinar.jpg

Webinar.jpg

1327 ms

z0RJGAB

z0RJGAB

897 ms

XDFrame

XDFrame

50 ms

Services.png

Services.png

1031 ms

Content.png

Content.png

1137 ms

Tools.png

Tools.png

1099 ms

https:/

https:/

3 ms

z0RJGAB

z0RJGAB

866 ms

z0RJGAB

z0RJGAB

142 ms

Accessibility Review

digikey.ee accessibility score

90

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

digikey.ee best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

digikey.ee SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digikey.ee 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.ee 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.ee

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: