Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

loreal-paris.be

Maquillage, soin, coloration & Soin Homme | L'Oréal Paris

Page Load Speed

429 ms in total

First Response

149 ms

Resources Loaded

221 ms

Page Rendered

59 ms

loreal-paris.be screenshot

About Website

Visit loreal-paris.be now to see the best up-to-date Loreal Paris content for Belgium and also check out these interesting facts you probably never knew about loreal-paris.be

Découvrez tous les produits beauté de L’Oréal Paris et faites-vous inspirer par les dernières tendances maquillage, soin de cheveux, coloration cheveux, soin visage et styling !

Visit loreal-paris.be

Key Findings

We analyzed Loreal-paris.be page load time and found that the first response time was 149 ms and then it took 280 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster. This domain responded with an error, which can significantly jeopardize Loreal-paris.be rating and web reputation

Performance Metrics

loreal-paris.be performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value2,950 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

loreal-paris.be

149 ms

main.css

4 ms

beacon.js

48 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 67% of them (2 requests) were addressed to the original Loreal-paris.be, 33% (1 request) were made to Performance.radar.cloudflare.com. The less responsive or slowest element that took the longest time to load (149 ms) belongs to the original domain Loreal-paris.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.1 kB (48%)

Content Size

8.6 kB

After Optimization

4.5 kB

In fact, the total size of Loreal-paris.be main page is 8.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 6.4 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 4.1 kB

  • Original 6.4 kB
  • After minification 6.0 kB
  • After compression 2.3 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 4.1 kB or 64% of the original size.

CSS Optimization

-1%

Potential reduce by 13 B

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 2.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. Loreal-paris.be has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Loreal Paris. According to our analytics all requests are already optimized.

Accessibility Review

loreal-paris.be accessibility score

89

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

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.

Best Practices

loreal-paris.be 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

Page has valid source maps

SEO Factors

loreal-paris.be SEO score

93

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loreal-paris.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Loreal-paris.be 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 Loreal Paris. 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: