Tools & Wizards About Us
urbandive.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% 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

urbandive.com

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

Page Load Speed

2.2 sec in total

First Response

396 ms

Resources Loaded

1.7 sec

Page Rendered

72 ms

urbandive.com screenshot

About Website

Visit urbandive.com now to see the best up-to-date Urbandive content and also check out these interesting facts you probably never knew about urbandive.com

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

Visit urbandive.com

Key Findings

We analyzed Urbandive.com page load time and found that the first response time was 396 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

urbandive.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

fr.mappy.com

396 ms

app.dabc5016aceb1f6cac8d.css

154 ms

address-route.dcd5112783d686d8be9f.css

230 ms

1667.b330a38382b33f90f3ad.css

233 ms

5530.db4f634db3160fa3ed19.css

237 ms

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

Page Optimization Overview & Recommendations

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

Content Size

235.4 kB

After Optimization

176.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Urbandive.com main page is 235.4 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. 30% of websites need less resources to load. CSS take 102.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 48.5 kB

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

Image Optimization

-12%

Potential reduce by 8.4 kB

  • Original 68.5 kB
  • After minification 60.1 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, Urbandive needs image optimization as it can save up to 8.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-2%

Potential reduce by 2.5 kB

  • Original 102.6 kB
  • After minification 102.6 kB
  • After compression 100.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. Urbandive.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (71%)

Requests Now

73

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Urbandive. 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

396 ms

app.dabc5016aceb1f6cac8d.css

app.dabc5016aceb1f6cac8d.css

154 ms

address-route.dcd5112783d686d8be9f.css

address-route.dcd5112783d686d8be9f.css

230 ms

1667.b330a38382b33f90f3ad.css

1667.b330a38382b33f90f3ad.css

233 ms

5530.db4f634db3160fa3ed19.css

5530.db4f634db3160fa3ed19.css

237 ms

config-web.json

config-web.json

495 ms

9051.f46fdb9e8fcdd6e59436.css

9051.f46fdb9e8fcdd6e59436.css

238 ms

bicycle-city-route.ac8e6ed38a5ec063b79f.css

bicycle-city-route.ac8e6ed38a5ec063b79f.css

240 ms

bicycle-department-route.80b0ca919af8ad0490fd.css

bicycle-department-route.80b0ca919af8ad0490fd.css

239 ms

bicycle-region-route.80b0ca919af8ad0490fd.css

bicycle-region-route.80b0ca919af8ad0490fd.css

308 ms

bicycle-route.01cd0f60b9d3a50e627d.css

bicycle-route.01cd0f60b9d3a50e627d.css

311 ms

common-route.17151dbe4fc680472a11.css

common-route.17151dbe4fc680472a11.css

310 ms

department-route.14500536105e311d502e.css

department-route.14500536105e311d502e.css

311 ms

geoentity-at-address.5cb068072540fe6f4d5c.css

geoentity-at-address.5cb068072540fe6f4d5c.css

312 ms

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

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

314 ms

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

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

385 ms

itinerary-results-route.234cd733ad016355dc33.css

itinerary-results-route.234cd733ad016355dc33.css

387 ms

itinerary-search-pois-route.c2547dd322ebcc05c346.css

itinerary-search-pois-route.c2547dd322ebcc05c346.css

388 ms

itineraryHP-route.689f5909b083aab60dde.css

itineraryHP-route.689f5909b083aab60dde.css

390 ms

poi-on-search.7f58a03a5dfe4d57d050.css

poi-on-search.7f58a03a5dfe4d57d050.css

391 ms

poi.7743d87b866d26569255.css

poi.7743d87b866d26569255.css

392 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

463 ms

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

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

464 ms

quiz-route.9f308d49ac91768eaf23.css

quiz-route.9f308d49ac91768eaf23.css

466 ms

region-route.14500536105e311d502e.css

region-route.14500536105e311d502e.css

467 ms

roadbook-route.16154d3124c8e155fb14.css

roadbook-route.16154d3124c8e155fb14.css

468 ms

search.b1bd8575352367fcb048.css

search.b1bd8575352367fcb048.css

539 ms

seoCountryPage-route.d2f90fe410115109db67.css

seoCountryPage-route.d2f90fe410115109db67.css

540 ms

seoDepartmentPage-route.8618365b57c4d2c30929.css

seoDepartmentPage-route.8618365b57c4d2c30929.css

541 ms

seoRegionPage-route.8618365b57c4d2c30929.css

seoRegionPage-route.8618365b57c4d2c30929.css

543 ms

tools-route.962bee1f833fe46dbec8.css

tools-route.962bee1f833fe46dbec8.css

544 ms

traffic-city-route.b499122cb5094a06902b.css

traffic-city-route.b499122cb5094a06902b.css

545 ms

traffic-department-route.80b0ca919af8ad0490fd.css

traffic-department-route.80b0ca919af8ad0490fd.css

615 ms

traffic-region-route.80b0ca919af8ad0490fd.css

traffic-region-route.80b0ca919af8ad0490fd.css

618 ms

traffic-route.a8ce451b39ac456f0faa.css

traffic-route.a8ce451b39ac456f0faa.css

617 ms

zfe-city-route.b499122cb5094a06902b.css

zfe-city-route.b499122cb5094a06902b.css

619 ms

smarttag.js

smarttag.js

334 ms

zfe-department-route.80b0ca919af8ad0490fd.css

zfe-department-route.80b0ca919af8ad0490fd.css

562 ms

zfe-region-route.80b0ca919af8ad0490fd.css

zfe-region-route.80b0ca919af8ad0490fd.css

482 ms

zfe-route.493543f32f21784228a7.css

zfe-route.493543f32f21784228a7.css

467 ms

fr-FR.js

fr-FR.js

467 ms

ua-parser.min.js

ua-parser.min.js

480 ms

app.204f8d02cb149ef22b9b.js

app.204f8d02cb149ef22b9b.js

845 ms

round_icon-4.png

round_icon-4.png

342 ms

arrow-left.cbcec1cd8c4c5e6c0e5a.svg

arrow-left.cbcec1cd8c4c5e6c0e5a.svg

78 ms

itinerary.576c35e3e85f9ea5cf9e.svg

itinerary.576c35e3e85f9ea5cf9e.svg

79 ms

logo-mappy.240ee493d753b97b2d11.svg

logo-mappy.240ee493d753b97b2d11.svg

80 ms

prefooter_image.04b0a0cd7e28982f6ea1.png

prefooter_image.04b0a0cd7e28982f6ea1.png

156 ms

magnifying-glass.ad2adc7326ded8c5a74a.svg

magnifying-glass.ad2adc7326ded8c5a74a.svg

82 ms

down.dff89806fc18e7ee9d08.svg

down.dff89806fc18e7ee9d08.svg

156 ms

tooltip-right.cf1015630e68ac99783a.svg

tooltip-right.cf1015630e68ac99783a.svg

155 ms

lock.4d8b4a563af9e8549719.svg

lock.4d8b4a563af9e8549719.svg

157 ms

question.e331c0d06a989e074726.svg

question.e331c0d06a989e074726.svg

158 ms

facebook.594de5e8accf8b407217.svg

facebook.594de5e8accf8b407217.svg

232 ms

twitter.ac1d4bb78da2ca5fe5dc.svg

twitter.ac1d4bb78da2ca5fe5dc.svg

249 ms

rss.b81b9a520cca657aa773.svg

rss.b81b9a520cca657aa773.svg

233 ms

logo_bonjour.f6816c68196b517c2be7.svg

logo_bonjour.f6816c68196b517c2be7.svg

234 ms

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

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

235 ms

logo-ratp-ss.1ee525deab80401a2ab9.png

logo-ratp-ss.1ee525deab80401a2ab9.png

309 ms

french-flag.7854a0340b65fd410696.svg

french-flag.7854a0340b65fd410696.svg

311 ms

round_icon-4.png

round_icon-4.png

342 ms

hotel.svg

hotel.svg

346 ms

parking.svg

parking.svg

347 ms

supermarches-hypermarches.svg

supermarches-hypermarches.svg

348 ms

station-service.svg

station-service.svg

346 ms

bar-club.svg

bar-club.svg

411 ms

banque.svg

banque.svg

418 ms

hopital.svg

hopital.svg

421 ms

poste.svg

poste.svg

423 ms

fontaines-a-eau.svg

fontaines-a-eau.svg

422 ms

France.85e2587ba72c56b6552f.png

France.85e2587ba72c56b6552f.png

275 ms

Belgium.8c5c6477d3c9cff1e636.png

Belgium.8c5c6477d3c9cff1e636.png

275 ms

UnitedKingdom.36ab1200179cb739a923.png

UnitedKingdom.36ab1200179cb739a923.png

288 ms

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

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

427 ms

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

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

440 ms

Accessibility Review

urbandive.com 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

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

SEO Factors

urbandive.com 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 Urbandive.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 Urbandive.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

urbandive.com

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