Tools & Wizards About Us
mappy.nl screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

mappy.nl

Mappy - Plattegronden, routevergelijker en kaarten van België

Page Load Speed

2.7 sec in total

First Response

442 ms

Resources Loaded

2.1 sec

Page Rendered

164 ms

mappy.nl screenshot

About Website

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

Opzoeken van adressen, plaatsen, routes vergelijken om uw reisweg overal in België te plannen.

Visit mappy.nl

Key Findings

We analyzed Mappy.nl page load time and found that the first response time was 442 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 40% of websites can load faster.

Performance Metrics

mappy.nl performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

mappy.nl

442 ms

en.mappy.com

497 ms

geoip

163 ms

getoax.php

376 ms

portal.css

453 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Mappy.nl, 54% (7 requests) were made to App.mappy.net and 15% (2 requests) were made to Dlive.pagesjaunes.fr. The less responsive or slowest element that took the longest time to load (820 ms) relates to the external source App.mappy.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.3 kB (75%)

Content Size

73.9 kB

After Optimization

18.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Mappy.nl main page is 73.9 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. 25% of websites need less resources to load. HTML takes 68.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 55.3 kB

  • Original 68.6 kB
  • After minification 67.6 kB
  • After compression 13.4 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 55.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.9 kB
  • After minification 4.9 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.

JavaScript Optimization

-28%

Potential reduce by 88 B

  • Original 319 B
  • After minification 317 B
  • After compression 231 B

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 88 B or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (27%)

Requests Now

11

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 11 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 as a result speed up the page load time.

Network Requests Diagram

mappy.nl

mappy.nl

442 ms

en.mappy.com

en.mappy.com

497 ms

geoip

geoip

163 ms

getoax.php

getoax.php

376 ms

portal.css

portal.css

453 ms

portal.js

portal.js

820 ms

portal.en_GB.js

portal.en_GB.js

343 ms

1521123918@x01

1521123918@x01

202 ms

rta.js

rta.js

99 ms

logo.png

logo.png

85 ms

Dosis-Regular.woff

Dosis-Regular.woff

162 ms

Dosis-Bold.woff

Dosis-Bold.woff

194 ms

MappyIcons-Regular.woff

MappyIcons-Regular.woff

500 ms

Accessibility Review

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

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mappy.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Mappy.nl 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.nl

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: