Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

wemap.fr

Félicitations ! Votre domaine a bien été créé chez OVHcloud !

Page Load Speed

2.7 sec in total

First Response

465 ms

Resources Loaded

1.5 sec

Page Rendered

692 ms

About Website

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

OVHcloud accompagne votre évolution grâce au meilleur des infrastructures web : hébergement, nom de domaine, serveur dédié, CDN, Cloud, Big Data, ...

Visit wemap.fr

Key Findings

We analyzed Wemap.fr page load time and found that the first response time was 465 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wemap.fr performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

wemap.fr

465 ms

www.wemap.fr

338 ms

punycode.min.js

157 ms

jquery-1.11.3.min.js

315 ms

transparentTriangle.svg

111 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Wemap.fr and no external sources were called. The less responsive or slowest element that took the longest time to load (465 ms) belongs to the original domain Wemap.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.0 kB (19%)

Content Size

448.1 kB

After Optimization

361.1 kB

In fact, the total size of Wemap.fr main page is 448.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 331.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 13.4 kB

  • Original 17.6 kB
  • After minification 17.4 kB
  • After compression 4.3 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 13.4 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 9.9 kB

  • Original 331.7 kB
  • After minification 321.8 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. Wemap images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 63.7 kB

  • Original 98.8 kB
  • After minification 98.8 kB
  • After compression 35.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 63.7 kB or 65% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wemap. According to our analytics all requests are already optimized.

Accessibility Review

wemap.fr accessibility score

75

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

Image elements do not have [alt] attributes

Best Practices

wemap.fr best practices score

67

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

SEO Factors

wemap.fr SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

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 Wemap.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 Wemap.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 Wemap. 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: