Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

be-only.com

Botte De Pluie | Be Only

Page Load Speed

2.7 sec in total

First Response

195 ms

Resources Loaded

2.4 sec

Page Rendered

59 ms

About Website

Welcome to be-only.com homepage info - get ready to check Be Only best content right away, or after learning these important things about be-only.com

Bienvenue chez Be Only ! Découvrez notre grande collection de bottes, boots et bottines de pluie pour femmes et enfants. Livraison offerte dès 69€ d'achat !

Visit be-only.com

Key Findings

We analyzed Be-only.com page load time and found that the first response time was 195 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

be-only.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value5,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.8 s

1/100

10%

Network Requests Diagram

www.be-only.com

195 ms

minified.js

44 ms

focus-within-polyfill.js

97 ms

polyfill.min.js

1333 ms

thunderbolt-commons.d9eb8f0e.bundle.min.js

78 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Be-only.com, 38% (18 requests) were made to Static.parastorage.com and 29% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 684.8 kB (47%)

Content Size

1.5 MB

After Optimization

768.4 kB

In fact, the total size of Be-only.com main page is 1.5 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. 30% of websites need less resources to load. HTML takes 778.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 635.4 kB

  • Original 778.1 kB
  • After minification 776.4 kB
  • After compression 142.7 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 635.4 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 45.7 kB

  • Original 423.3 kB
  • After minification 377.6 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. Obviously, Be Only needs image optimization as it can save up to 45.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 251.8 kB
  • After minification 251.8 kB
  • After compression 248.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 11 (37%)

Requests Now

30

After Optimization

19

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

Accessibility Review

be-only.com accessibility score

98

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

Links do not have a discernible name

Best Practices

be-only.com 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

be-only.com SEO score

91

Search Engine Optimization Advices

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 doesn't use 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 Be-only.com 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 Be-only.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 Be Only. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: