Tools & Wizards About Us
mappy.fr screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

mappy.fr

Mappy - Plans, comparateur d'itinéraires et cartes de France

Page Load Speed

2.2 sec in total

First Response

439 ms

Resources Loaded

1.7 sec

Page Rendered

70 ms

mappy.fr screenshot

About Website

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

Recherche d'adresses, de lieux, comparateur d'itinéraires pour préparer vos déplacements partout en France

Visit mappy.fr

Key Findings

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

Performance Metrics

mappy.fr performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

fr.mappy.com

439 ms

app.f7c714f08481d4b419b8.css

151 ms

address-route.20b62867aae6ed409d05.css

228 ms

1393.dcd49b5802f344f00253.css

240 ms

283.f0ad1cf0ab1dc167a78f.css

237 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mappy.fr, 12% (8 requests) were made to Poiassets.mappy.net and 2% (1 request) were made to Ab.mappy.net. The less responsive or slowest element that took the longest time to load (692 ms) relates to the external source Fr.mappy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.1 kB (25%)

Content Size

217.1 kB

After Optimization

163.1 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-75%

Potential reduce by 46.7 kB

  • Original 62.4 kB
  • After minification 62.4 kB
  • After compression 15.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 46.7 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 4.9 kB

  • Original 52.5 kB
  • After minification 47.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. Mappy images are well optimized though.

CSS Optimization

-2%

Potential reduce by 2.5 kB

  • Original 102.3 kB
  • After minification 102.3 kB
  • After compression 99.8 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. Mappy.fr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (76%)

Requests Now

62

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fr.mappy.com

fr.mappy.com

439 ms

app.f7c714f08481d4b419b8.css

app.f7c714f08481d4b419b8.css

151 ms

address-route.20b62867aae6ed409d05.css

address-route.20b62867aae6ed409d05.css

228 ms

1393.dcd49b5802f344f00253.css

1393.dcd49b5802f344f00253.css

240 ms

283.f0ad1cf0ab1dc167a78f.css

283.f0ad1cf0ab1dc167a78f.css

237 ms

9051.de445368fb2c3f89d21f.css

9051.de445368fb2c3f89d21f.css

243 ms

bicycle-city-route.ac8e6ed38a5ec063b79f.css

bicycle-city-route.ac8e6ed38a5ec063b79f.css

242 ms

bicycle-department-route.80b0ca919af8ad0490fd.css

bicycle-department-route.80b0ca919af8ad0490fd.css

242 ms

bicycle-region-route.80b0ca919af8ad0490fd.css

bicycle-region-route.80b0ca919af8ad0490fd.css

304 ms

bicycle-route.01cd0f60b9d3a50e627d.css

bicycle-route.01cd0f60b9d3a50e627d.css

313 ms

common-route.93fc7a55272537d9076a.css

common-route.93fc7a55272537d9076a.css

314 ms

department-route.30cd909988f121275124.css

department-route.30cd909988f121275124.css

317 ms

geoentity-at-address.5cb068072540fe6f4d5c.css

geoentity-at-address.5cb068072540fe6f4d5c.css

315 ms

itinerary-expense-report-route.0eb904b779998e5f22c9.css

itinerary-expense-report-route.0eb904b779998e5f22c9.css

318 ms

itinerary-geoentity-on-search-pois-route.88281517e87d07e80a3b.css

itinerary-geoentity-on-search-pois-route.88281517e87d07e80a3b.css

381 ms

itinerary-results-route.7c83755fa465e1f5a80c.css

itinerary-results-route.7c83755fa465e1f5a80c.css

388 ms

itinerary-search-pois-route.22f942b39c23911df09f.css

itinerary-search-pois-route.22f942b39c23911df09f.css

393 ms

itineraryHP-route.1022d8c56cf50b278677.css

itineraryHP-route.1022d8c56cf50b278677.css

395 ms

poi-on-search.7f58a03a5dfe4d57d050.css

poi-on-search.7f58a03a5dfe4d57d050.css

390 ms

poi.7743d87b866d26569255.css

poi.7743d87b866d26569255.css

396 ms

quiz-cities-route.38f266b6c9d4b4c1813a.css

quiz-cities-route.38f266b6c9d4b4c1813a.css

462 ms

quiz-department-cities-route.38f266b6c9d4b4c1813a.css

quiz-department-cities-route.38f266b6c9d4b4c1813a.css

464 ms

quiz-region-cities-route.38f266b6c9d4b4c1813a.css

quiz-region-cities-route.38f266b6c9d4b4c1813a.css

465 ms

quiz-route.9f308d49ac91768eaf23.css

quiz-route.9f308d49ac91768eaf23.css

467 ms

region-route.30cd909988f121275124.css

region-route.30cd909988f121275124.css

467 ms

roadbook-route.bc38425bbeb541f06805.css

roadbook-route.bc38425bbeb541f06805.css

468 ms

search.ee3bceeec05a7b4bfa4d.css

search.ee3bceeec05a7b4bfa4d.css

538 ms

seoCountryPage-route.b9df7d454525e1ea8b62.css

seoCountryPage-route.b9df7d454525e1ea8b62.css

541 ms

seoDepartmentPage-route.408f736a269821b29cda.css

seoDepartmentPage-route.408f736a269821b29cda.css

541 ms

seoRegionPage-route.408f736a269821b29cda.css

seoRegionPage-route.408f736a269821b29cda.css

542 ms

tools-route.962bee1f833fe46dbec8.css

tools-route.962bee1f833fe46dbec8.css

544 ms

traffic-city-route.b499122cb5094a06902b.css

traffic-city-route.b499122cb5094a06902b.css

544 ms

traffic-department-route.80b0ca919af8ad0490fd.css

traffic-department-route.80b0ca919af8ad0490fd.css

613 ms

traffic-region-route.80b0ca919af8ad0490fd.css

traffic-region-route.80b0ca919af8ad0490fd.css

616 ms

traffic-route.a8ce451b39ac456f0faa.css

traffic-route.a8ce451b39ac456f0faa.css

617 ms

zfe-city-route.b499122cb5094a06902b.css

zfe-city-route.b499122cb5094a06902b.css

618 ms

config-web.json

config-web.json

337 ms

smarttag.js

smarttag.js

18 ms

zfe-department-route.80b0ca919af8ad0490fd.css

zfe-department-route.80b0ca919af8ad0490fd.css

556 ms

zfe-region-route.80b0ca919af8ad0490fd.css

zfe-region-route.80b0ca919af8ad0490fd.css

480 ms

zfe-route.493543f32f21784228a7.css

zfe-route.493543f32f21784228a7.css

471 ms

fr-FR.js

fr-FR.js

464 ms

ua-parser.min.js

ua-parser.min.js

479 ms

app.1e31d3c3abda433a6206.js

app.1e31d3c3abda433a6206.js

692 ms

suggestion.svg

suggestion.svg

340 ms

chevron.4e873f4cc41ef70399ab.svg

chevron.4e873f4cc41ef70399ab.svg

80 ms

itinerary.576c35e3e85f9ea5cf9e.svg

itinerary.576c35e3e85f9ea5cf9e.svg

78 ms

prefooter_image.04b0a0cd7e28982f6ea1.png

prefooter_image.04b0a0cd7e28982f6ea1.png

156 ms

logo_bonjour.f6816c68196b517c2be7.svg

logo_bonjour.f6816c68196b517c2be7.svg

81 ms

logo-mappy.240ee493d753b97b2d11.svg

logo-mappy.240ee493d753b97b2d11.svg

83 ms

logo-ratp-group-fr.2d84a7237bf849a57b79.png

logo-ratp-group-fr.2d84a7237bf849a57b79.png

156 ms

logo-ratp-ss.1ee525deab80401a2ab9.png

logo-ratp-ss.1ee525deab80401a2ab9.png

156 ms

french-flag.7854a0340b65fd410696.svg

french-flag.7854a0340b65fd410696.svg

156 ms

down.svg

down.svg

353 ms

bulle-i.svg

bulle-i.svg

359 ms

cadenas.svg

cadenas.svg

357 ms

bulle-interrogation.svg

bulle-interrogation.svg

360 ms

facebook.svg

facebook.svg

359 ms

twitter.svg

twitter.svg

413 ms

rss.svg

rss.svg

429 ms

France.85e2587ba72c56b6552f.png

France.85e2587ba72c56b6552f.png

115 ms

Belgium.8c5c6477d3c9cff1e636.png

Belgium.8c5c6477d3c9cff1e636.png

189 ms

UnitedKingdom.36ab1200179cb739a923.png

UnitedKingdom.36ab1200179cb739a923.png

191 ms

fira-sans-v16-latin-regular.638c6c27dba69db97f1d.woff

fira-sans-v16-latin-regular.638c6c27dba69db97f1d.woff

189 ms

fira-sans-v16-latin-500.5b6fa2d4698b328de283.woff

fira-sans-v16-latin-500.5b6fa2d4698b328de283.woff

266 ms

Accessibility Review

mappy.fr accessibility score

54

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

Image elements do not have [alt] attributes

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mappy.fr SEO score

85

Search Engine Optimization Advices

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

mappy.fr

Open Graph data is detected on the main page of Mappy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: