Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

pampers.it

Pannolini, salviettine, teli e prodotti per bambini - Pampers.it

Page Load Speed

5.9 sec in total

First Response

423 ms

Resources Loaded

5.2 sec

Page Rendered

283 ms

pampers.it screenshot

About Website

Click here to check amazing Pampers content for Italy. Otherwise, check out these important facts you probably never knew about pampers.it

Il portale di mamme e bimbi per conoscere i nostri i pannolini, teli e salviette, partecipare ai concorsi e leggere gli articoli dei nostri esperti.

Visit pampers.it

Key Findings

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

Performance Metrics

pampers.it performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value35.2 s

0/100

25%

SI (Speed Index)

Value25.4 s

0/100

10%

TBT (Total Blocking Time)

Value12,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.564

12/100

15%

TTI (Time to Interactive)

Value32.7 s

0/100

10%

Network Requests Diagram

pampers.it

423 ms

www.pampers.it

1401 ms

bootstrap.css

320 ms

main1.css

1369 ms

main2.css

1162 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 78% of them (76 requests) were addressed to the original Pampers.it, 7% (7 requests) were made to Privacyportal.fatergroup.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Pampers.it.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.8 MB (44%)

Content Size

6.4 MB

After Optimization

3.5 MB

In fact, the total size of Pampers.it main page is 6.4 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. 70% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 88.2 kB

  • Original 96.3 kB
  • After minification 49.2 kB
  • After compression 8.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 47.1 kB, which is 49% 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 88.2 kB or 92% of the original size.

Image Optimization

-5%

Potential reduce by 173.7 kB

  • Original 3.2 MB
  • After minification 3.1 MB

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. Pampers images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.1 MB
  • After compression 334.1 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 1.1 MB or 77% of the original size.

CSS Optimization

-91%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.4 MB
  • After compression 134.0 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. Pampers.it needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (18%)

Requests Now

82

After Optimization

67

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

Accessibility Review

pampers.it accessibility score

76

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

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

pampers.it best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

pampers.it SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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