Tools & Wizards About Us
a2maastricht.nl screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

a2maastricht.nl

De totstandkoming en resultaten van project A2 Maastricht

Page Load Speed

3.9 sec in total

First Response

1.1 sec

Resources Loaded

2.7 sec

Page Rendered

102 ms

a2maastricht.nl screenshot

About Website

Welcome to a2maastricht.nl homepage info - get ready to check A2 Maastricht best content for Netherlands right away, or after learning these important things about a2maastricht.nl

Van de planprocedures tot de bouwmethode van de Koning Willem-Alexandertunnel en de Groene Loper. Hier vind je alle kennis over dit enorme infraproject.

Visit a2maastricht.nl

Key Findings

We analyzed A2maastricht.nl page load time and found that the first response time was 1.1 sec and then it took 2.8 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

a2maastricht.nl performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value26.2 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value2,400 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value1.729

0/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

a2maastricht.nl

1143 ms

js

46 ms

seBasis.css

440 ms

jquery-1.6.1.min.js

618 ms

jquery.jscrollpane.css

202 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 96% of them (66 requests) were addressed to the original A2maastricht.nl, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain A2maastricht.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.1 kB (27%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A2maastricht.nl main page is 1.5 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. 40% of websites need less resources to load. Images take 991.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.0 kB

  • Original 40.7 kB
  • After minification 39.0 kB
  • After compression 8.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 32.0 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 31.9 kB

  • Original 991.5 kB
  • After minification 959.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. A2 Maastricht images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 316.1 kB

  • Original 445.2 kB
  • After minification 419.7 kB
  • After compression 129.1 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 316.1 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 29.1 kB

  • Original 35.2 kB
  • After minification 22.5 kB
  • After compression 6.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. A2maastricht.nl needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (51%)

Requests Now

67

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

a2maastricht.nl

a2maastricht.nl

1143 ms

js

js

46 ms

seBasis.css

seBasis.css

440 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

618 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

202 ms

jquery.mousewheel.js

jquery.mousewheel.js

203 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

392 ms

colorbox.css

colorbox.css

425 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

499 ms

seBasis.js

seBasis.js

386 ms

superfish.css

superfish.css

477 ms

superfish-navbar.css

superfish-navbar.css

501 ms

hoverIntent.js

hoverIntent.js

547 ms

superfish.js

superfish.js

554 ms

supersubs.js

supersubs.js

602 ms

WebResource.axd

WebResource.axd

603 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

638 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

764 ms

se3_basis_page_js.js

se3_basis_page_js.js

572 ms

lijnblauw.gif

lijnblauw.gif

94 ms

m_bereikbaarlogo_klein.gif

m_bereikbaarlogo_klein.gif

85 ms

degroeneloper.gif

degroeneloper.gif

101 ms

a2actueelheader.png

a2actueelheader.png

330 ms

a2actueelplay.png

a2actueelplay.png

170 ms

x321y0w226h185cw1283ch1051_ft18221.jpg

x321y0w226h185cw1283ch1051_ft18221.jpg

177 ms

w986h240_ft10605.jpg

w986h240_ft10605.jpg

220 ms

w986h240_ft20904.jpg

w986h240_ft20904.jpg

221 ms

w986h240_ft20903.jpg

w986h240_ft20903.jpg

382 ms

w986h240_ft20839.jpg

w986h240_ft20839.jpg

476 ms

w986h240_ft20838.jpg

w986h240_ft20838.jpg

395 ms

w986h240_ft20822.jpg

w986h240_ft20822.jpg

386 ms

w986h240_ft20820.jpg

w986h240_ft20820.jpg

330 ms

w986h240_ft20808.jpg

w986h240_ft20808.jpg

726 ms

w986h240_ft20809.jpg

w986h240_ft20809.jpg

425 ms

w986h240_ft20810.jpg

w986h240_ft20810.jpg

496 ms

w986h240_ft20787.jpg

w986h240_ft20787.jpg

582 ms

w986h240_ft20729.jpg

w986h240_ft20729.jpg

528 ms

w986h240_ft20728.jpg

w986h240_ft20728.jpg

532 ms

w986h240_ft20727.jpg

w986h240_ft20727.jpg

671 ms

w986h240_ft20600.jpg

w986h240_ft20600.jpg

612 ms

w986h240_ft20516.jpg

w986h240_ft20516.jpg

658 ms

w986h240_ft20515.jpg

w986h240_ft20515.jpg

692 ms

logohome.gif

logohome.gif

684 ms

hoekjelinks.png

hoekjelinks.png

706 ms

hoekjerechts.png

hoekjerechts.png

749 ms

googleplay.png

googleplay.png

781 ms

appstore.png

appstore.png

801 ms

eu-logo.gif

eu-logo.gif

788 ms

hpsitemgl.jpg

hpsitemgl.jpg

810 ms

twitter_icoon.jpg

twitter_icoon.jpg

952 ms

twitter_bird.gif

twitter_bird.gif

841 ms

a2maastrichtfilm.jpg

a2maastrichtfilm.jpg

884 ms

hoekjelinksonder.png

hoekjelinksonder.png

852 ms

hoekjerechtsonder.png

hoekjerechtsonder.png

826 ms

zoekback.gif

zoekback.gif

692 ms

tabrood.gif

tabrood.gif

722 ms

tabblauw.gif

tabblauw.gif

746 ms

tabgroen.gif

tabgroen.gif

755 ms

taboranje.gif

taboranje.gif

763 ms

loop-cursor.png

loop-cursor.png

785 ms

homenieuwsback.gif

homenieuwsback.gif

830 ms

ga.js

ga.js

8 ms

snelnaarback.gif

snelnaarback.gif

832 ms

__utm.gif

__utm.gif

72 ms

lte50423_0-webfont.woff

lte50423_0-webfont.woff

732 ms

linkpijl.gif

linkpijl.gif

726 ms

enquete.png

enquete.png

711 ms

overlay.png

overlay.png

717 ms

arrows-ffffff.png

arrows-ffffff.png

764 ms

Accessibility Review

a2maastricht.nl accessibility score

49

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

a2maastricht.nl best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

a2maastricht.nl SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    ISO_8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A2maastricht.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that A2maastricht.nl main page’s claimed encoding is iso_8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

a2maastricht.nl

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