Tools & Wizards About Us
we.fr screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

we.fr

Page Load Speed

3.4 sec in total

First Response

512 ms

Resources Loaded

2.4 sec

Page Rendered

434 ms

we.fr screenshot

About Website

Welcome to we.fr homepage info - get ready to check We best content right away, or after learning these important things about we.fr

Ce nom de domaine a été réservé par Force Business

Visit we.fr

Key Findings

We analyzed We.fr page load time and found that the first response time was 512 ms and then it took 2.9 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

we.fr performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

D3dXZlEqBTEBJw==

512 ms

preload.css

160 ms

bootstrap.css

652 ms

font-awesome.min.css

5 ms

animate.min.css

497 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original We.fr, 9% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (811 ms) relates to the external source Force-business.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 650.8 kB (54%)

Content Size

1.2 MB

After Optimization

550.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of We.fr main page is 1.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. 45% of websites need less resources to load. CSS take 465.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 10.9 kB

  • Original 14.6 kB
  • After minification 11.7 kB
  • After compression 3.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 3.0 kB, which is 20% 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 10.9 kB or 74% of the original size.

Image Optimization

-7%

Potential reduce by 28.2 kB

  • Original 420.2 kB
  • After minification 392.0 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. We images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 203.8 kB

  • Original 301.8 kB
  • After minification 283.8 kB
  • After compression 98.0 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 203.8 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 407.9 kB

  • Original 465.0 kB
  • After minification 387.1 kB
  • After compression 57.1 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. We.fr needs all CSS files to be minified and compressed as it can save up to 407.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (70%)

Requests Now

46

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

D3dXZlEqBTEBJw==

D3dXZlEqBTEBJw==

512 ms

preload.css

preload.css

160 ms

bootstrap.css

bootstrap.css

652 ms

font-awesome.min.css

font-awesome.min.css

5 ms

animate.min.css

animate.min.css

497 ms

slidebars.css

slidebars.css

172 ms

lightbox.css

lightbox.css

183 ms

jquery.bxslider.css

jquery.bxslider.css

236 ms

shCore.css

shCore.css

240 ms

style-blue.css

style-blue.css

768 ms

width-full.css

width-full.css

272 ms

buttons.css

buttons.css

628 ms

fb_styles.css

fb_styles.css

339 ms

jquery.min.js

jquery.min.js

811 ms

home_full.js

home_full.js

345 ms

jquery.cookie.js

jquery.cookie.js

427 ms

bootstrap.min.js

bootstrap.min.js

585 ms

wow.min.js

wow.min.js

508 ms

slidebars.js

slidebars.js

678 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

630 ms

holder.js

holder.js

662 ms

buttons.js

buttons.js

675 ms

styleswitcher.js

styleswitcher.js

631 ms

jquery.mixitup.min.js

jquery.mixitup.min.js

708 ms

circles.min.js

circles.min.js

709 ms

shCore.js

shCore.js

795 ms

shBrushXml.js

shBrushXml.js

709 ms

shBrushJScript.js

shBrushJScript.js

724 ms

app.js

app.js

757 ms

index.js

index.js

756 ms

css

css

26 ms

close.png

close.png

120 ms

loading.gif

loading.gif

121 ms

prev.png

prev.png

122 ms

next.png

next.png

181 ms

bx_loader.gif

bx_loader.gif

202 ms

logo.png

logo.png

201 ms

flag_swiss.png

flag_swiss.png

201 ms

flag_france.png

flag_france.png

208 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

47 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

44 ms

_fUwxgthNvUM9WCtMyMvbA.woff

_fUwxgthNvUM9WCtMyMvbA.woff

44 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

11 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

41 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

41 ms

widgets.js

widgets.js

39 ms

bg-parking2.jpg

bg-parking2.jpg

717 ms

analytics.js

analytics.js

21 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

43 ms

collect

collect

28 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html

26 ms

info.json

info.json

94 ms

jot

jot

95 ms

Accessibility Review

we.fr accessibility score

86

Accessibility Issues

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.

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

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

Best Practices

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

SEO Factors

we.fr SEO score

100

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 uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise We.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that We.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

we.fr

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