Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

bellame.com

Inspired by Luxury, Powered by Science | Bellame Beauty

Page Load Speed

716 ms in total

First Response

41 ms

Resources Loaded

517 ms

Page Rendered

158 ms

bellame.com screenshot

About Website

Click here to check amazing Bellame content for United States. Otherwise, check out these important facts you probably never knew about bellame.com

An ultra-luxurious line packed with a powerhouse, clinical grade ingredients—minus harsh chemicals like parabens and phthalates — Acqua Lumiere’s patented technology delivers exactly what your skin ne...

Visit bellame.com

Key Findings

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

Performance Metrics

bellame.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value37.1 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.761

5/100

15%

TTI (Time to Interactive)

Value32.3 s

0/100

10%

Network Requests Diagram

bellame.com

41 ms

bellame.com

45 ms

js

139 ms

fbevents.js

52 ms

google_tag.script.js

30 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 69% of them (34 requests) were addressed to the original Bellame.com, 8% (4 requests) were made to Fonts.googleapis.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (144 ms) relates to the external source Tag.rmp.rakuten.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (27%)

Content Size

6.7 MB

After Optimization

4.9 MB

In fact, the total size of Bellame.com main page is 6.7 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. Only a small number of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 88.1 kB

  • Original 105.9 kB
  • After minification 99.2 kB
  • After compression 17.8 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 88.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.4 MB
  • After minification 4.4 MB

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. Bellame images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 671.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 344.2 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 671.3 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 158.0 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. Bellame.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 21 (46%)

Requests Now

46

After Optimization

25

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

Accessibility Review

bellame.com accessibility score

80

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

<frame> or <iframe> elements do not have a title

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bellame.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bellame.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Bellame.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 Bellame.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 Bellame. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: