Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

garnier.pt

Especialistas em Saúde e Beleza da Pele e Cabelo | Garnier

Page Load Speed

4.8 sec in total

First Response

151 ms

Resources Loaded

4.2 sec

Page Rendered

374 ms

About Website

Click here to check amazing Garnier content for Portugal. Otherwise, check out these important facts you probably never knew about garnier.pt

Conhece os nossos produtos, ingredientes, recomendações e cuidados para a saúde e beleza da pele e cabelo. Entra agora no universo Garnier!

Visit garnier.pt

Key Findings

We analyzed Garnier.pt page load time and found that the first response time was 151 ms and then it took 4.6 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

garnier.pt performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.495

16/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

garnier.pt

151 ms

www.garnier.pt

110 ms

otSDKStub.js

60 ms

bundle.css

98 ms

bundle.js

94 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 44% of them (25 requests) were addressed to the original Garnier.pt, 18% (10 requests) were made to Google-analytics.com and 12% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Garnier.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.2 kB (22%)

Content Size

1.8 MB

After Optimization

1.4 MB

In fact, the total size of Garnier.pt main page is 1.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. 70% of websites need less resources to load. Images take 680.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 214.8 kB

  • Original 255.5 kB
  • After minification 232.5 kB
  • After compression 40.7 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 214.8 kB or 84% of the original size.

Image Optimization

-14%

Potential reduce by 94.4 kB

  • Original 680.5 kB
  • After minification 586.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. Obviously, Garnier needs image optimization as it can save up to 94.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 607.5 kB
  • After minification 607.5 kB
  • After compression 605.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. This website has mostly compressed JavaScripts.

CSS Optimization

-35%

Potential reduce by 74.1 kB

  • Original 214.6 kB
  • After minification 214.6 kB
  • After compression 140.5 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. Garnier.pt needs all CSS files to be minified and compressed as it can save up to 74.1 kB or 35% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

21

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

Accessibility Review

garnier.pt accessibility score

88

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 are not valid or misspelled

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

garnier.pt best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

garnier.pt SEO score

75

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

High

robots.txt is not valid

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

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Garnier.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Garnier.pt 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 Garnier. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: