Tools & Wizards About Us
loreal.fi screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

loreal.fi

L’Oréal, world leader in beauty : makeup, cosmetics, haircare, perfume

Page Load Speed

4 sec in total

First Response

481 ms

Resources Loaded

2.1 sec

Page Rendered

1.4 sec

loreal.fi screenshot

About Website

Welcome to loreal.fi homepage info - get ready to check Loreal best content for Spain right away, or after learning these important things about loreal.fi

Offering all women and men worldwide the best of cosmetics, haircare and perfume in terms of quality, efficacy and safety. Discover our brands and values.

Visit loreal.fi

Key Findings

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

Performance Metrics

loreal.fi performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value4,050 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

481 ms

otSDKStub.js

65 ms

bundle.css

20 ms

ecb_intercept.js

879 ms

vendors.bundle.js

39 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Loreal.fi, 5% (3 requests) were made to Cdn.cookielaw.org and 3% (2 requests) were made to Ecb.qualquantsignals.com. The less responsive or slowest element that took the longest time to load (932 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 231.1 kB (76%)

Content Size

304.0 kB

After Optimization

72.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Loreal.fi main page is 304.0 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. 70% of websites need less resources to load. HTML takes 247.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 217.1 kB

  • Original 247.4 kB
  • After minification 191.2 kB
  • After compression 30.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. This page needs HTML code to be minified as it can gain 56.2 kB, which is 23% 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 217.1 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-3%

Potential reduce by 237 B

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 7.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

-31%

Potential reduce by 13.7 kB

  • Original 44.1 kB
  • After minification 44.1 kB
  • After compression 30.4 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.fi needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (14%)

Requests Now

51

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

481 ms

otSDKStub.js

otSDKStub.js

65 ms

bundle.css

bundle.css

20 ms

ecb_intercept.js

ecb_intercept.js

879 ms

vendors.bundle.js

vendors.bundle.js

39 ms

bundle.js

bundle.js

45 ms

keyboard.min.js

keyboard.min.js

630 ms

66976695-4e60-4bfb-a909-c0449b1bd801.json

66976695-4e60-4bfb-a909-c0449b1bd801.json

514 ms

gtm.js

gtm.js

932 ms

loreal-paris-logo.svg

loreal-paris-logo.svg

575 ms

garnier-logo.svg

garnier-logo.svg

575 ms

maybelline-logo.svg

maybelline-logo.svg

504 ms

nyx-logo.svg

nyx-logo.svg

587 ms

stylenanda-logo.svg

stylenanda-logo.svg

586 ms

essie-logo.svg

essie-logo.svg

594 ms

darklovely-logo.svg

darklovely-logo.svg

595 ms

mixa-logo-100x100.png

mixa-logo-100x100.png

582 ms

mg-logo.svg

mg-logo.svg

588 ms

miely-logo.svg

miely-logo.svg

641 ms

margiela.svg

margiela.svg

607 ms

lancome.svg

lancome.svg

594 ms

kiehls.svg

kiehls.svg

644 ms

armani.svg

armani.svg

602 ms

ysl.svg

ysl.svg

597 ms

biotherm.svg

biotherm.svg

644 ms

hr.svg

hr.svg

671 ms

it.svg

it.svg

670 ms

ud.svg

ud.svg

668 ms

rl.svg

rl.svg

672 ms

mugler.svg

mugler.svg

706 ms

viktor.svg

viktor.svg

709 ms

valentino.svg

valentino.svg

712 ms

azzaro-logo.png

azzaro-logo.png

708 ms

diesel.svg

diesel.svg

713 ms

atelier.svg

atelier.svg

705 ms

prada.svg

prada.svg

707 ms

cacharel.svg

cacharel.svg

860 ms

yuesai.svg

yuesai.svg

875 ms

loreal-pro-logo.svg

loreal-pro-logo.svg

891 ms

kerastase-logo.svg

kerastase-logo.svg

895 ms

logo.png

logo.png

891 ms

redken-logo.svg

redken-logo.svg

876 ms

matrix-logo.svg

matrix-logo.svg

892 ms

pureology-logo.svg

pureology-logo.svg

892 ms

lrp.svg

lrp.svg

899 ms

location

location

387 ms

79AWorBl4EBACisA0gAAAA=

79AWorBl4EBACisA0gAAAA=

17 ms

HelveticaNowDisplayW05-Lt.woff

HelveticaNowDisplayW05-Lt.woff

355 ms

HelveticaNowDisplayW05-Rg.woff

HelveticaNowDisplayW05-Rg.woff

341 ms

HelveticaNowDisplayW05-Bold.woff

HelveticaNowDisplayW05-Bold.woff

337 ms

Halesworth-Medium.woff

Halesworth-Medium.woff

336 ms

Halesworth-Bold.woff

Halesworth-Bold.woff

348 ms

vichy.svg

vichy.svg

346 ms

cerave.svg

cerave.svg

336 ms

skinceuticals.svg

skinceuticals.svg

335 ms

decleor.svg

decleor.svg

338 ms

ServerOnline.gif

ServerOnline.gif

117 ms

otBannerSdk.js

otBannerSdk.js

251 ms

Accessibility Review

loreal.fi accessibility score

69

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

High

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

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

loreal.fi 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.fi SEO score

85

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

loreal.fi

Open Graph data is detected on the main page of Loreal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: