Tools & Wizards About Us
pedrini.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pedrini.com

Utensili per la tavola e per la cucina dal 1942 - Pedrini

Page Load Speed

3.3 sec in total

First Response

632 ms

Resources Loaded

2.6 sec

Page Rendered

164 ms

pedrini.com screenshot

About Website

Click here to check amazing Pedrini content for Italy. Otherwise, check out these important facts you probably never knew about pedrini.com

Pedrini vanta un'ampia gamma di utensili da cucina e per la tavola, scopri tutti i nostri prodotti. Cuciniamo insieme a te, dal 1942.

Visit pedrini.com

Key Findings

We analyzed Pedrini.com page load time and found that the first response time was 632 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pedrini.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value34.5 s

0/100

25%

SI (Speed Index)

Value25.7 s

0/100

10%

TBT (Total Blocking Time)

Value920 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.37

29/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

pedrini.com

632 ms

menu.css

310 ms

generale.css

207 ms

boxricerca.css

207 ms

menutendina.css

229 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 32% of them (22 requests) were addressed to the original Pedrini.com, 12% (8 requests) were made to Apis.google.com and 7% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (734 ms) belongs to the original domain Pedrini.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 699.3 kB (63%)

Content Size

1.1 MB

After Optimization

406.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pedrini.com main page is 1.1 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. CSS take 529.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 57.0 kB

  • Original 72.2 kB
  • After minification 69.5 kB
  • After compression 15.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.0 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 9.2 kB

  • Original 128.8 kB
  • After minification 119.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. Pedrini images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 226.5 kB

  • Original 375.6 kB
  • After minification 374.2 kB
  • After compression 149.2 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 226.5 kB or 60% of the original size.

CSS Optimization

-77%

Potential reduce by 406.6 kB

  • Original 529.2 kB
  • After minification 526.8 kB
  • After compression 122.6 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. Pedrini.com needs all CSS files to be minified and compressed as it can save up to 406.6 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (69%)

Requests Now

62

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pedrini. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pedrini.com

pedrini.com

632 ms

menu.css

menu.css

310 ms

generale.css

generale.css

207 ms

boxricerca.css

boxricerca.css

207 ms

menutendina.css

menutendina.css

229 ms

pagineinterne.css

pagineinterne.css

354 ms

stile-lista.css

stile-lista.css

304 ms

stile-lista-prodotti.css

stile-lista-prodotti.css

307 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

317 ms

menu_laterale.js

menu_laterale.js

344 ms

Loader_1020302.js

Loader_1020302.js

139 ms

getcod.cgi

getcod.cgi

319 ms

urchin.js

urchin.js

5 ms

v1.js

v1.js

30 ms

f1a.jpg

f1a.jpg

557 ms

home_new2012.jpg

home_new2012.jpg

397 ms

slogan_pedrini.gif

slogan_pedrini.gif

189 ms

pedrinistore.gif

pedrinistore.gif

163 ms

titolo_cerca_prodotto.gif

titolo_cerca_prodotto.gif

126 ms

avviaricerca.gif

avviaricerca.gif

117 ms

home-land3.jpg

home-land3.jpg

527 ms

logo_pedrini.gif

logo_pedrini.gif

394 ms

numeroverde.gif

numeroverde.gif

396 ms

planetservice.gif

planetservice.gif

396 ms

f2store.jpg

f2store.jpg

734 ms

f3a.jpg

f3a.jpg

566 ms

analytics.js

analytics.js

5 ms

collect

collect

28 ms

jquery.min.js

jquery.min.js

26 ms

zBfOJNZK5lQ

zBfOJNZK5lQ

87 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

40 ms

www-embed-player.js

www-embed-player.js

66 ms

base.js

base.js

104 ms

font-awesome.min.css

font-awesome.min.css

81 ms

shinystat.cgi

shinystat.cgi

341 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

93 ms

ad_status.js

ad_status.js

91 ms

__utm.gif

__utm.gif

31 ms

sdk.js

sdk.js

335 ms

widgets.js

widgets.js

50 ms

platform.js

platform.js

157 ms

page.js

page.js

78 ms

1TF2XTZ

1TF2XTZ

71 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

119 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

145 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

113 ms

1px.png

1px.png

45 ms

sm13.html

sm13.html

128 ms

icons.15.svg.css

icons.15.svg.css

192 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

25 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

57 ms

fastbutton

fastbutton

143 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

22 ms

ga.js

ga.js

53 ms

postmessageRelay

postmessageRelay

101 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

39 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

39 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

29 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

24 ms

rpc:shindig_random.js

rpc:shindig_random.js

54 ms

184 ms

xd_arbiter.php

xd_arbiter.php

213 ms

xd_arbiter.php

xd_arbiter.php

434 ms

jot

jot

108 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

like.php

like.php

122 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

480 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

543 ms

Accessibility Review

pedrini.com accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

pedrini.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pedrini.com SEO score

91

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pedrini.com can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pedrini.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pedrini.com

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