3.2 sec in total
267 ms
2.6 sec
324 ms
Click here to check amazing Amsterdamopendata content. Otherwise, check out these important facts you probably never knew about amsterdamopendata.nl
Visit amsterdamopendata.nlWe analyzed Amsterdamopendata.nl page load time and found that the first response time was 267 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
amsterdamopendata.nl performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value8.6 s
1/100
25%
Value9.4 s
12/100
10%
Value710 ms
42/100
30%
Value0.453
20/100
15%
Value7.6 s
46/100
10%
267 ms
955 ms
83 ms
159 ms
256 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Amsterdamopendata.nl, 67% (22 requests) were made to Data.amsterdam.nl and 18% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Files.datapress.com.
Page size can be reduced by 568.6 kB (54%)
1.1 MB
491.0 kB
In fact, the total size of Amsterdamopendata.nl main page is 1.1 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. Javascripts take 480.4 kB which makes up the majority of the site volume.
Potential reduce by 13.9 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 13.9 kB or 73% of the original size.
Potential reduce by 23.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. Amsterdamopendata images are well optimized though.
Potential reduce by 342.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 342.2 kB or 71% of the original size.
Potential reduce by 188.5 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. Amsterdamopendata.nl needs all CSS files to be minified and compressed as it can save up to 188.5 kB or 75% of the original size.
Number of requests can be reduced by 18 (62%)
29
11
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amsterdamopendata. 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 6 to 1 for CSS and as a result speed up the page load time.
amsterdamopendata.nl
267 ms
data.amsterdam.nl
955 ms
theme-my-login.css
83 ms
debug_avenir.css
159 ms
main.css
256 ms
font-awesome.min.css
180 ms
select2.min.css
35 ms
dashicons.min.css
278 ms
jquery.min.js
29 ms
themed-profiles.js
174 ms
ssba.min.js
162 ms
modernizr.min.js
40 ms
jquery.cookie.min.js
62 ms
typeahead.jquery.js
466 ms
select2.min.js
43 ms
moment.min.js
47 ms
bootstrap.min.js
238 ms
datapress.js
467 ms
wp-embed.min.js
342 ms
prum.min.js
156 ms
amsterdam-front-1024.jpg
1038 ms
andreas.svg
145 ms
bullet3.png
144 ms
bullet2.png
144 ms
html.png
143 ms
api.png
143 ms
bullet1.png
142 ms
datapress-promo.png
299 ms
analytics.js
100 ms
AvenirLTStd-Heavy.woff
89 ms
fontawesome-webfont.woff
246 ms
jquery.cookie.js
84 ms
collect
12 ms
amsterdamopendata.nl accessibility score
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
amsterdamopendata.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
amsterdamopendata.nl SEO score
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
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amsterdamopendata.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Amsterdamopendata.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.
amsterdamopendata.nl
Open Graph description is not detected on the main page of Amsterdamopendata. 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: