Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

garnier.pt

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

Page Load Speed

16.2 sec in total

First Response

232 ms

Resources Loaded

14.9 sec

Page Rendered

1 sec

garnier.pt screenshot

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.

Visit garnier.pt

Key Findings

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

Performance Metrics

garnier.pt performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

www.garnier.pt

232 ms

otSDKStub.js

151 ms

bundle.css

109 ms

gothamfonts.css

132 ms

api.js

134 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 38% of them (21 requests) were addressed to the original Garnier.pt, 13% (7 requests) were made to Cdn.cookielaw.org and 11% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Garnier.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.4 kB (31%)

Content Size

899.9 kB

After Optimization

624.5 kB

In fact, the total size of Garnier.pt main page is 899.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 421.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 274.2 kB

  • Original 330.8 kB
  • After minification 330.3 kB
  • After compression 56.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 274.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 21 B

  • Original 421.3 kB
  • After minification 421.3 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. Garnier images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 1.1 kB

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 36.7 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

-0%

Potential reduce by 64 B

  • Original 109.9 kB
  • After minification 109.9 kB
  • After compression 109.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (55%)

Requests Now

51

After Optimization

23

The browser has sent 51 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 19 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

garnier.pt accessibility score

81

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

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

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

garnier.pt SEO score

82

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

    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: