2.6 sec in total
359 ms
1.9 sec
388 ms
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.nlWe 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.
amsterdam.nl performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value6.9 s
6/100
25%
Value4.8 s
66/100
10%
Value2,310 ms
5/100
30%
Value0.004
100/100
15%
Value8.4 s
39/100
10%
359 ms
170 ms
25 ms
57 ms
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 size can be reduced by 1.0 MB (66%)
1.5 MB
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.
Potential reduce by 35.5 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.
Potential reduce by 13.7 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.
Potential reduce by 307.7 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.
Potential reduce by 650.0 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.
Number of requests can be reduced by 31 (57%)
54
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.
amsterdam.nl
359 ms
www.amsterdam.nl
170 ms
c3b0086ea7a236a93fc4382be9dbe8ec.css
25 ms
706334aef8e877e6811f32e658794755.css
57 ms
6884d5b69df317bab3c957eb1fd33274.css
86 ms
GSA-Zoekbox.css
58 ms
6e5f95fc56ef3b7289e80bbf6f4f2af5.css
51 ms
b6eb28460a14f8f736b466504fe7d053.css
60 ms
ed947734120074e6eaac3d6442783bf9.css
55 ms
21555c7adcfc14eddf98b71bd67dbf73.css
82 ms
a100f7520815208695c3961de9d7c0cb.css
80 ms
44376a21782438c44ef6d9c1c6caa2fa.css
80 ms
read.aspx
556 ms
c0a9e94f19d6ddc57009a525750042a7.js
109 ms
3680cf49-2b05-4b8a-af28-fa9e27d2bed0.js
140 ms
jquery.min.js
111 ms
jquery-migrate-1.2.1.min.js
86 ms
read.aspx
460 ms
16df300190002cd57d2b46d2781e7eab.js
88 ms
jquery.history.js
87 ms
jquery.jBreadCrumb.1.1.js
85 ms
imagesloaded.pkgd.min.js
87 ms
33b5efab805af3f6f1a16a77f110d8a8.js
98 ms
a556579d04f40a6c8f21e8db3777355d.js
106 ms
b5675c324999e0d5f706c1d15bda117d.js
638 ms
6b7d8e2aa5cce756a51ad3597834a0ea.js
103 ms
141f6b67e09da9ea09b28443c3ab933a.js
125 ms
gsa_functions_clean.js
108 ms
2df52e66951edf22475b0ec866dc16a2.js
111 ms
analytics.js
86 ms
andreas.svg
19 ms
andreas.png
66 ms
andreas-print.png
67 ms
17099-039_obs_de_achthoek_groep8b_22jan2015_e_v_eis-1.jpg
65 ms
koningsdag.jpg
65 ms
17544-132_sportenfuntour_20okt2015_e_v_eis.jpg
69 ms
beer.png
69 ms
ipod.png
68 ms
kaart.jpg
69 ms
img.gif
52 ms
sprite_bullets_big.png
61 ms
sprite_bullets_small.png
67 ms
sprite_backgrounds.png
69 ms
sprite_buttons.png
70 ms
crease_background_normal.png
68 ms
aeh_____-webfont.woff
16 ms
typeahead_bundle.js
553 ms
siteanalyze_6004851.js
621 ms
www.amsterdam.nl
482 ms
collect
21 ms
collect
15 ms
17099-039_obs_de_achthoek_groep8b_22jan2015_e_v_eis-1.jpg
22 ms
linkpointer.png
5 ms
collect
55 ms
e338bf9caa35f1ef45436af570533344.css
17 ms
049a4e3f86373cbb5a5ccbca972e5177.css
9 ms
2f3ad209ccb3916087ff3654f77a4417.css
9 ms
66778473d0c30c967f70101f80652785.css
9 ms
amsterdam.nl accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
amsterdam.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
amsterdam.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
NL
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.
amsterdam.nl
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: