Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

digikey.be

DigiKey België - Verdeler van elektronische onderdelen

Page Load Speed

967 ms in total

First Response

100 ms

Resources Loaded

682 ms

Page Rendered

185 ms

digikey.be screenshot

About Website

Welcome to digikey.be homepage info - get ready to check Digi Key best content for Belgium right away, or after learning these important things about digikey.be

DigiKey biedt miljoenen producten van duizenden fabrikanten, waarvan vele in voorraad en nog dezelfde dag te verzenden zijn. Apple Pay, Google Pay™ en Paypal worden aanvaard, bestel vandaag nog online...

Visit digikey.be

Key Findings

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

Performance Metrics

digikey.be performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

www.digikey.be

100 ms

346228540.js

216 ms

header.css

38 ms

footer.css

43 ms

homepage.css

36 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 7% of them (9 requests) were addressed to the original Digikey.be, 84% (107 requests) were made to Digikey.com and 5% (6 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (216 ms) relates to the external source Cdn.optimizely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 752.3 kB (56%)

Content Size

1.3 MB

After Optimization

593.5 kB

In fact, the total size of Digikey.be 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. 55% of websites need less resources to load. Javascripts take 644.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 141.4 kB

  • Original 164.6 kB
  • After minification 144.5 kB
  • After compression 23.1 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.1 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 141.4 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 75.9 kB

  • Original 453.4 kB
  • After minification 377.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 75.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 469.9 kB

  • Original 644.9 kB
  • After minification 616.1 kB
  • After compression 175.0 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 469.9 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 65.1 kB

  • Original 82.9 kB
  • After minification 61.9 kB
  • After compression 17.8 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.be needs all CSS files to be minified and compressed as it can save up to 65.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (20%)

Requests Now

127

After Optimization

101

The browser has sent 127 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.

Accessibility Review

digikey.be 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.be 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.be SEO score

80

Search Engine Optimization Advices

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

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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: