Access mauboussin.us. Mauboussin Joaillier

3

Performance

Renders faster than
20% of other websites
88

Accessibility

Visual factors better than
that of 68% of websites
67

Best Practices

More advanced features
available than in
24% of websites
88

SEO

Google-friendlier than
65% of websites

First Response

599 ms

Resources Loaded

5.8 sec

Page Rendered

1.3 sec

About Website

Click here to check amazing Mauboussin content. Otherwise, check out these important facts you probably never knew about mauboussin.us

Mauboussin est un joaillier français créé en 1827 à Paris. L'ensemble du catalogue Mauboussin est disponible sur notre boutique e-commerce.

Visit mauboussin.us

Key Findings

We analyzed Mauboussin.us page load time and found that the first response time was 599 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.1 s

0/100

25%

SI (Speed Index)

Value36.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value1.002

2/100

15%

TTI (Time to Interactive)

Value49.1 s

0/100

10%

599 ms

88f1b0e3f97c3e22254a54dff57805fb.css

975 ms

b46b4d5507cd9218a6e845b5c3f2d35d.min.js

1047 ms

font-awesome.min.css

38 ms

ld.js

29 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mauboussin.us, 1% (1 request) were made to Mauboussin.fr and 1% (1 request) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Static.mauboussin.fr.

Content Size

14.0 MB

After Optimization

13.7 MB

In fact, the total size of Mauboussin.us main page is 14.0 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 13.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 255.9 kB

Original 290.7 kB
After minification 247.1 kB
After compression 34.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. This page needs HTML code to be minified as it can gain 43.5 kB, which is 15% 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 255.9 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 66.9 kB

Original 13.2 MB
After minification 13.1 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. Mauboussin images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.0 kB

Original 345.8 kB
After minification 345.8 kB
After compression 343.9 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 0 B

Original 230.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.

Requests Now

107

After Optimization

103

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

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

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

FR
Encoding

UTF-8

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

mauboussin.us

Open Graph description is not detected on the main page of Mauboussin. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Mauboussin Joaillier - Depuis 1827

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)