Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

avent.com

Baby Care Products, Accessories & Baby Essentials | Share the Care

Page Load Speed

1.8 sec in total

First Response

205 ms

Resources Loaded

1.3 sec

Page Rendered

246 ms

avent.com screenshot

About Website

Click here to check amazing Avent content. Otherwise, check out these important facts you probably never knew about avent.com

#ShareTheCare with Philips Avent baby products. Find the baby accessories and newborn essentials new parents need like bottles, pacifiers, nipples and more.

Visit avent.com

Key Findings

We analyzed Avent.com page load time and found that the first response time was 205 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

avent.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value3,990 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

avent.com

205 ms

philips-avent.html

216 ms

satellitelib.js

60 ms

clientlibs.min.160308.css

40 ms

_page.webfont.all.js

26 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Avent.com, 37% (10 requests) were made to Philips.com and 30% (8 requests) were made to Crsc.philips.com. The less responsive or slowest element that took the longest time to load (310 ms) relates to the external source Philips.com.

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

996.4 kB

In fact, the total size of Avent.com main page is 3.8 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. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 197.5 kB

  • Original 215.7 kB
  • After minification 81.0 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 134.6 kB, which is 62% 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 197.5 kB or 92% of the original size.

Image Optimization

-9%

Potential reduce by 26.3 kB

  • Original 297.4 kB
  • After minification 271.1 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. Avent images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 1.4 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 543.9 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.4 MB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 163.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. Avent.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (56%)

Requests Now

18

After Optimization

8

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

Accessibility Review

avent.com accessibility score

89

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-*] attributes do not match their roles

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

Some elements have a [tabindex] value greater than 0

Best Practices

avent.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

avent.com SEO score

92

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Avent.com 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 Avent.com 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 data is detected on the main page of Avent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: