Tools & Wizards About Us
parts.digikey.it screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% 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

parts.digikey.it

DigiKey Electronics Italia - Distributore di componenti elettronici

Page Load Speed

7.3 sec in total

First Response

2.2 sec

Resources Loaded

2.9 sec

Page Rendered

2.1 sec

parts.digikey.it screenshot

About Website

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

Digi-Key offre milioni di prodotti di migliaia di produttori, molti dei quali in magazzino e disponibili per la spedizione in giornata. Si accettano Apple Pay, Google Pay™ e Paypal. Ordina subito onli...

Visit parts.digikey.it

Key Findings

We analyzed Parts.digikey.it page load time and found that the first response time was 2.2 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

parts.digikey.it performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,070 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

it

2225 ms

dksusCSS

7 ms

jquery.chosen.css

9 ms

print.css

16 ms

logo_dk.png

18 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Parts.digikey.it, 10% (6 requests) were made to Digikey.it and 8% (5 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Digikey.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 869.8 kB (73%)

Content Size

1.2 MB

After Optimization

321.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Parts.digikey.it main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 583.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 409.4 kB

  • Original 468.2 kB
  • After minification 321.0 kB
  • After compression 58.8 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 147.2 kB, which is 31% 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 409.4 kB or 87% of the original size.

Image Optimization

-23%

Potential reduce by 21.0 kB

  • Original 90.6 kB
  • After minification 69.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, Parts Digi Key needs image optimization as it can save up to 21.0 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 399.8 kB

  • Original 583.3 kB
  • After minification 555.6 kB
  • After compression 183.5 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 399.8 kB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 39.6 kB

  • Original 49.5 kB
  • After minification 39.6 kB
  • After compression 9.9 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. Parts.digikey.it needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Parts 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 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

it

it

2225 ms

dksusCSS

dksusCSS

7 ms

jquery.chosen.css

jquery.chosen.css

9 ms

print.css

print.css

16 ms

logo_dk.png

logo_dk.png

18 ms

IT_Flag.png

IT_Flag.png

15 ms

cart-white.png

cart-white.png

16 ms

triangle-white.png

triangle-white.png

15 ms

chat-white.png

chat-white.png

27 ms

header.css

header.css

10 ms

footer.css

footer.css

7 ms

jquery-ui.css

jquery-ui.css

7 ms

global.css

global.css

48 ms

gray-button-background.jpg

gray-button-background.jpg

15 ms

share.png

share.png

16 ms

link-icon.png

link-icon.png

15 ms

toggleJS

toggleJS

28 ms

seal_js.php

seal_js.php

59 ms

mobileapp_32.png

mobileapp_32.png

29 ms

digikey_wtvars.js

digikey_wtvars.js

40 ms

digikey_wtbaseV2.js

digikey_wtbaseV2.js

40 ms

digikey-webtrends.js

digikey-webtrends.js

38 ms

header.js

header.js

77 ms

jquery141min.js

jquery141min.js

35 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

37 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

39 ms

jquery.ui.position.min.js

jquery.ui.position.min.js

32 ms

jquery.ui.dialog.min.js

jquery.ui.dialog.min.js

37 ms

jquery.mb.menu.js

jquery.mb.menu.js

30 ms

dkdialogs.js

dkdialogs.js

34 ms

currencySetter.js

currencySetter.js

35 ms

indexPageScript

indexPageScript

23 ms

jumpToJS

jumpToJS

23 ms

addthis_widget.js

addthis_widget.js

65 ms

techxchange_32.png

techxchange_32.png

32 ms

youtube_32.png

youtube_32.png

34 ms

facebook_32.png

facebook_32.png

37 ms

twitter_32.png

twitter_32.png

31 ms

linkedin_32.png

linkedin_32.png

32 ms

googleplus_32.png

googleplus_32.png

31 ms

homepage-associations.png

homepage-associations.png

32 ms

footer-background.jpg

footer-background.jpg

44 ms

it.png

it.png

45 ms

wtid.js

wtid.js

97 ms

seal_image.php

seal_image.php

5 ms

worldwide.png

worldwide.png

5 ms

headerinfo.ashx

headerinfo.ashx

246 ms

utag.js

utag.js

237 ms

chosen-sprite.png

chosen-sprite.png

32 ms

300lo.json

300lo.json

43 ms

dcs.gif

dcs.gif

48 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

26 ms

datapair

datapair

32 ms

datapair

datapair

46 ms

datapair

datapair

46 ms

datapair

datapair

45 ms

utag.145.js

utag.145.js

77 ms

utag.151.js

utag.151.js

9 ms

utag.158.js

utag.158.js

9 ms

utag.164.js

utag.164.js

7 ms

Accessibility Review

parts.digikey.it 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

parts.digikey.it 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

parts.digikey.it 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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

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

parts.digikey.it

Open Graph description is not detected on the main page of Parts 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: