Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

lepage.fr

Montres & Bijoux, de marque et de luxe | Lepage Joaillier

Page Load Speed

8.7 sec in total

First Response

2.1 sec

Resources Loaded

6.1 sec

Page Rendered

536 ms

lepage.fr screenshot

About Website

Visit lepage.fr now to see the best up-to-date Lepage content for France and also check out these interesting facts you probably never knew about lepage.fr

Vente en ligne de bijoux et de montres de grandes marques. Le meilleur du luxe depuis 1922 avec lepage.

Visit lepage.fr

Key Findings

We analyzed Lepage.fr page load time and found that the first response time was 2.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lepage.fr performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value7,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.465

19/100

15%

TTI (Time to Interactive)

Value34.7 s

0/100

10%

Network Requests Diagram

lepage.fr

2087 ms

css

64 ms

4b9900785ab40005532d6dec5921225d.js

267 ms

styles.css

583 ms

styles-responsive.css

412 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 85% of them (133 requests) were addressed to the original Lepage.fr, 2% (3 requests) were made to V2.zopim.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Lepage.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (44%)

Content Size

3.2 MB

After Optimization

1.8 MB

In fact, the total size of Lepage.fr main page is 3.2 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. 75% 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 121.7 kB

  • Original 142.7 kB
  • After minification 127.3 kB
  • After compression 20.9 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 15.3 kB, which is 11% 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 121.7 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 149.7 kB

  • Original 1.6 MB
  • After minification 1.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. Lepage images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 785.2 kB

  • Original 1.1 MB
  • After minification 825.9 kB
  • After compression 278.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 785.2 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 370.4 kB

  • Original 428.8 kB
  • After minification 344.3 kB
  • After compression 58.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. Lepage.fr needs all CSS files to be minified and compressed as it can save up to 370.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (40%)

Requests Now

146

After Optimization

88

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

Accessibility Review

lepage.fr accessibility score

86

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-hidden="true"] elements contain focusable descendents

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

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

Links do not have a discernible name

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

High

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

Best Practices

lepage.fr best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

lepage.fr SEO score

91

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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