Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

agnesb.fr

agnès b. Boutique en ligne

Page Load Speed

4.4 sec in total

First Response

248 ms

Resources Loaded

3 sec

Page Rendered

1.1 sec

agnesb.fr screenshot

About Website

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

Découvrez la boutique en ligne agnès b. et commandez les collections femme, homme et enfants. E-Réservation et retrait gratuit en magasin.

Visit agnesb.fr

Key Findings

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

Performance Metrics

agnesb.fr performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.513

15/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

agnesb.fr

248 ms

www.agnesb.fr

324 ms

www.agnesb.eu

530 ms

bootstrap.min.css

22 ms

nouislider.min.css

41 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Agnesb.fr, 63% (61 requests) were made to Agnesb-agnesb-com-storage.omn.proximis.com and 35% (34 requests) were made to Agnesb.eu. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Agnesb-agnesb-com-storage.omn.proximis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 736.8 kB (27%)

Content Size

2.7 MB

After Optimization

2.0 MB

In fact, the total size of Agnesb.fr main page is 2.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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 709.5 kB

  • Original 766.8 kB
  • After minification 726.4 kB
  • After compression 57.2 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 709.5 kB or 93% of the original size.

Image Optimization

-0%

Potential reduce by 8.5 kB

  • Original 1.9 MB
  • After minification 1.9 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. Agnesb images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 18.8 kB

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 58.4 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 18.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (38%)

Requests Now

93

After Optimization

58

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

Accessibility Review

agnesb.fr accessibility score

58

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

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

Image elements do not have [alt] attributes

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

High

Heading elements are not in a sequentially-descending order

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

agnesb.fr 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

agnesb.fr SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    FR

  • Encoding

    UTF-8

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