Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

amsterdam.nl

Home - Gemeente Amsterdam

Page Load Speed

2.6 sec in total

First Response

359 ms

Resources Loaded

1.9 sec

Page Rendered

388 ms

amsterdam.nl screenshot

About Website

Visit amsterdam.nl now to see the best up-to-date Amsterdam content for Netherlands and also check out these interesting facts you probably never knew about amsterdam.nl

Officiële site van de gemeente Amsterdam met informatie over onze diensten en het bestuur..

Visit amsterdam.nl

Key Findings

We analyzed Amsterdam.nl page load time and found that the first response time was 359 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

amsterdam.nl performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value2,310 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

amsterdam.nl

359 ms

www.amsterdam.nl

170 ms

c3b0086ea7a236a93fc4382be9dbe8ec.css

25 ms

706334aef8e877e6811f32e658794755.css

57 ms

6884d5b69df317bab3c957eb1fd33274.css

86 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 86% of them (50 requests) were addressed to the original Amsterdam.nl, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (638 ms) belongs to the original domain Amsterdam.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (66%)

Content Size

1.5 MB

After Optimization

508.3 kB

In fact, the total size of Amsterdam.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. 50% of websites need less resources to load. CSS take 715.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 35.5 kB

  • Original 44.6 kB
  • After minification 44.5 kB
  • After compression 9.1 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 35.5 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 13.7 kB

  • Original 270.7 kB
  • After minification 256.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. Amsterdam images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 307.7 kB

  • Original 484.9 kB
  • After minification 483.9 kB
  • After compression 177.2 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 307.7 kB or 63% of the original size.

CSS Optimization

-91%

Potential reduce by 650.0 kB

  • Original 715.2 kB
  • After minification 610.9 kB
  • After compression 65.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. Amsterdam.nl needs all CSS files to be minified and compressed as it can save up to 650.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (57%)

Requests Now

54

After Optimization

23

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

Accessibility Review

amsterdam.nl accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

amsterdam.nl SEO score

92

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amsterdam.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 Amsterdam.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

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