rotterdam.nl website information.
rotterdam.nl domain name is registered by .NL top-level domain registry. See the other sites registred in .NL domain zone.
Following name servers are specified for rotterdam.nl domain:
- ns2.rotterdam.nl
- ns1.rotterdam.nl
and probably website rotterdam.nl is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.
According to Alexa traffic rank the highest website rotterdam.nl position was 14605 (in the world). The lowest Alexa rank position was 853711. Now website rotterdam.nl ranked in Alexa database as number 14915 (in the world).
Website rotterdam.nl Desktop speed measurement score (35/100) is better than the results of 11.34% of other sites shows that the page desktop performance can be improved.
rotterdam.nl Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of rotterdam.nl (31/100) is better than the results of 10.59% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
Date | Rank | Change |
---|---|---|
Nov-18-2024 | 14,915 | -147 |
Nov-17-2024 | 14,768 | -11 |
Nov-16-2024 | 14,757 | -22 |
Nov-15-2024 | 14,735 | 134 |
Nov-14-2024 | 14,869 | 50 |
Nov-13-2024 | 14,919 | 0 |
Nov-12-2024 | 14,919 | 0 |
Advertisement
rotterdam.nl Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
rotterdam.nl whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
Domain name: rotterdam.nl
Status: active
Registrar:
Gemeente Rotterdam
Zuiderparkweg 300
3085BW Rotterdam
Netherlands
Abuse Contact:
DNSSEC: yes
Domain nameservers:
ns1.rotterdam.nl 193.176.221.253
ns2.rotterdam.nl 193.176.221.254
Creation Date: 1995-03-08
Updated Date: 2024-06-20
Record maintained by: SIDN BV
rotterdam.nl server information
rotterdam.nl desktop page speed rank
Last tested: 2016-10-11
rotterdam.nl Desktop Speed Test Quick Summary
priority - 155 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.5MiB (78% reduction).
Compressing http://www.rotterdam.nl/twittercontrol/json.ashx?q…194659&_=1476153194667 could save 244.9KiB (92% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/3/096.js could save 45.5KiB (75% reduction).
Compressing http://www.rotterdam.nl/cpr-cdd5d86a6f6f46f283af850f5b4d4f25 could save 31KiB (80% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/scripts/knockout-2.3.0.js could save 26.5KiB (63% reduction).
Compressing http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 could save 14.8KiB (74% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/2/695.js could save 14.5KiB (69% reduction).
Compressing http://www.rotterdam.nl/ could save 12.5KiB (70% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/json.ashx…194660&_=1476153195589 could save 11KiB (78% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/23/468.js could save 10.4KiB (67% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/22/39/524.js could save 9.7KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/119.css could save 9KiB (80% reduction).
Compressing http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css could save 7.8KiB (83% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/1/497.js could save 7.5KiB (70% reduction).
Compressing http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c could save 7.2KiB (74% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/scripts/knockout.mapping-latest.js could save 6KiB (64% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/1/237.js could save 5.7KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/14/91/759.js could save 5KiB (71% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/17/95/578.js could save 4.6KiB (69% reduction).
Compressing http://www.rotterdam.nl/twittercontrol/communitedtwitter.js could save 4KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/49/172.js could save 3.4KiB (74% reduction).
Compressing http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d could save 2.9KiB (73% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/communited_instagram.js could save 2.7KiB (71% reduction).
Compressing http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83 could save 2.2KiB (76% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/120.css could save 2.1KiB (69% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/22/39/523.js could save 2KiB (56% reduction).
Compressing http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c could save 1.8KiB (69% reduction).
Compressing http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7 could save 1.2KiB (63% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js could save 970B (61% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/24/950.js could save 673B (62% reduction).
Compressing http://www.gis.rotterdam.nl/rik/config.js could save 531B (61% reduction).
priority - 20 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://invitation.opinionbar.com/popups/p20673/overlay.js (expiration not specified)
http://www.gis.rotterdam.nl/rik/config.js (expiration not specified)
http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css (expiration not specified)
http://www.gis.rotterdam.nl/rik/v2.3/rik.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/communited_instagram.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/scripts/knockout-2.3.0.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/scripts/knockout.mapping-latest.js (expiration not specified)
http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c (expiration not specified)
http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c (expiration not specified)
http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 (expiration not specified)
http://www.rotterdam.nl/cpr-b96a4f33a0004450a8284f205b5669fe (expiration not specified)
http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83 (expiration not specified)
http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d (expiration not specified)
http://www.rotterdam.nl/cpr-cdd5d86a6f6f46f283af850f5b4d4f25 (expiration not specified)
http://www.rotterdam.nl/cpr-ceb376847a504898ba6d8ce5b633af73 (expiration not specified)
http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7 (expiration not specified)
http://www.rotterdam.nl/cpr-f3c93f5aa3d75859e040090a6c033f56 (expiration not specified)
http://www.rotterdam.nl/cpr/contentimages/banner_map.gif (expiration not specified)
http://www.rotterdam.nl/cpr/images/btn_rss.gif (expiration not specified)
http://www.rotterdam.nl/cpr/images/default_list_style.gif (expiration not specified)
http://www.rotterdam.nl/eCache/TER/1/237.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/1/497.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/119.css (expiration not specified)
http://www.rotterdam.nl/eCache/TER/120.css (expiration not specified)
http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/14/91/759.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/17/95/578.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/19/98/218.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/2/695.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/521.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/523.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/524.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/23/468.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/24/950.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/3/096.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/49/172.js (expiration not specified)
http://www.rotterdam.nl/twittercontrol/communitedtwitter.js (expiration not specified)
http://ssl.siteimprove.com/js/siteanalyze_6006165.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
priority - 18 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 22 blocking script resources and 11 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://code.jquery.com/ui/1.10.0/jquery-ui.min.js
http://www.rotterdam.nl/eCache/TER/2/695.js
http://www.rotterdam.nl/eCache/TER/23/468.js
http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js
http://www.rotterdam.nl/eCache/TER/14/91/759.js
http://www.rotterdam.nl/eCache/TER/1/497.js
http://www.rotterdam.nl/eCache/TER/3/096.js
http://www.rotterdam.nl/eCache/TER/22/39/521.js
http://www.rotterdam.nl/eCache/TER/17/95/578.js
http://www.rotterdam.nl/eCache/TER/19/98/218.js
http://www.rotterdam.nl/eCache/TER/22/39/524.js
http://www.rotterdam.nl/eCache/TER/22/39/523.js
http://www.rotterdam.nl/eCache/TER/1/237.js
http://www.rotterdam.nl/InstagramControl/communited_instagram.js
http://www.rotterdam.nl/InstagramControl/scripts/knockout-2.3.0.js
http://www.rotterdam.nl/InstagramControl/scripts/knockout.mapping-latest.js
http://www.gis.rotterdam.nl/rik/v2.3/rik.js
http://www.gis.rotterdam.nl/rik/config.js
http://www.rotterdam.nl/eCache/TER/24/950.js
http://www.rotterdam.nl/eCache/TER/49/172.js
http://www.rotterdam.nl/twittercontrol/communitedtwitter.js
Optimize CSS Delivery of the following:
http://www.rotterdam.nl/eCache/TER/120.css
http://www.rotterdam.nl/eCache/TER/119.css
http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d
http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2
http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83
http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7
http://www.rotterdam.nl/cpr-f3c93f5aa3d75859e040090a6c033f56
http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c
http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c
http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css
priority - 6 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 59.4KiB (40% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/2/695.js could save 12.1KiB (58% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/23/468.js could save 7.1KiB (47% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/1/237.js could save 3.1KiB (38% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/1/497.js could save 2.7KiB (26% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/22/39/524.js could save 2.5KiB (19% reduction).
Minifying http://www.rotterdam.nl/twittercontrol/communitedtwitter.js could save 2.4KiB (43% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/49/172.js could save 2.2KiB (50% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/14/91/759.js could save 2.1KiB (30% reduction).
Minifying http://www.rotterdam.nl/InstagramControl/communited_instagram.js could save 1.9KiB (50% reduction).
priority - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 2 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 17.6KiB (19% reduction).
Minifying http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 could save 4.7KiB (24% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/119.css could save 2KiB (18% reduction).
Minifying http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c could save 1.6KiB (17% reduction).
Minifying http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css could save 1.5KiB (17% reduction).
Minifying http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d could save 981B (24% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/120.css could save 605B (20% reduction).
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 5.9KiB (16% reduction).
Compressing http://pbs.twimg.com/profile_images/720191801336799232/Lsp7iFg4_normal.jpg could save 962B (55% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…k5MzYyNTQ0Mw%3D%3D.2.c could save 899B (18% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…MjUwNjk1MzU4Mw%3D%3D.2 could save 849B (12% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…M1MTA1ODM2OA%3D%3D.2.c could save 828B (12% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…Q1OTY0MzYxNA%3D%3D.2.c could save 812B (15% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 3.8KiB (22% reduction).
rotterdam.nl Desktop Resources
Total Resources | 70 |
Number of Hosts | 11 |
Static Resources | 52 |
JavaScript Resources | 27 |
CSS Resources | 13 |
rotterdam.nl Desktop Resource Breakdown
rotterdam.nl mobile page speed rank
Last tested: 2016-10-11
rotterdam.nl Mobile Speed Test Quick Summary
priority - 154 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.5MiB (78% reduction).
Compressing http://www.rotterdam.nl/twittercontrol/json.ashx?q…192376&_=1476153192382 could save 244.9KiB (92% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/3/096.js could save 45.5KiB (75% reduction).
Compressing http://www.rotterdam.nl/cpr-cdd5d86a6f6f46f283af850f5b4d4f25 could save 31KiB (80% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/scripts/knockout-2.3.0.js could save 26.5KiB (63% reduction).
Compressing http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 could save 14.8KiB (74% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/2/695.js could save 14.5KiB (69% reduction).
Compressing http://www.rotterdam.nl/ could save 12.5KiB (70% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/json.ashx…192377&_=1476153193278 could save 11KiB (78% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/23/468.js could save 10.4KiB (67% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/22/39/524.js could save 9.7KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/119.css could save 9KiB (80% reduction).
Compressing http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css could save 7.8KiB (83% reduction).
Compressing http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c could save 7.2KiB (74% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/scripts/knockout.mapping-latest.js could save 6KiB (64% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/1/237.js could save 5.7KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/14/91/759.js could save 5KiB (71% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/17/95/578.js could save 4.6KiB (69% reduction).
Compressing http://www.rotterdam.nl/twittercontrol/communitedtwitter.js could save 4KiB (70% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/49/172.js could save 3.4KiB (74% reduction).
Compressing http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d could save 2.9KiB (73% reduction).
Compressing http://www.rotterdam.nl/InstagramControl/communited_instagram.js could save 2.7KiB (71% reduction).
Compressing http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83 could save 2.2KiB (76% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/120.css could save 2.1KiB (69% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/22/39/523.js could save 2KiB (56% reduction).
Compressing http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c could save 1.8KiB (69% reduction).
Compressing http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7 could save 1.2KiB (63% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js could save 970B (61% reduction).
Compressing http://www.rotterdam.nl/eCache/TER/24/950.js could save 673B (62% reduction).
Compressing http://www.gis.rotterdam.nl/rik/config.js could save 531B (61% reduction).
priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 10 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://code.jquery.com/ui/1.10.0/jquery-ui.min.js
http://www.rotterdam.nl/eCache/TER/2/695.js
http://www.rotterdam.nl/eCache/TER/23/468.js
http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js
http://www.rotterdam.nl/eCache/TER/14/91/759.js
http://www.rotterdam.nl/eCache/TER/1/497.js
http://www.rotterdam.nl/eCache/TER/3/096.js
http://www.rotterdam.nl/eCache/TER/22/39/521.js
http://www.rotterdam.nl/eCache/TER/17/95/578.js
http://www.rotterdam.nl/eCache/TER/19/98/218.js
http://www.rotterdam.nl/eCache/TER/22/39/524.js
http://www.rotterdam.nl/eCache/TER/22/39/523.js
http://www.rotterdam.nl/eCache/TER/1/237.js
Optimize CSS Delivery of the following:
http://www.rotterdam.nl/eCache/TER/120.css
http://www.rotterdam.nl/eCache/TER/119.css
http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d
http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2
http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83
http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7
http://www.rotterdam.nl/cpr-f3c93f5aa3d75859e040090a6c033f56
http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c
http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c
priority - 30 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://invitation.opinionbar.com/popups/p20673/overlay.js (expiration not specified)
http://www.gis.rotterdam.nl/rik/config.js (expiration not specified)
http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css (expiration not specified)
http://www.gis.rotterdam.nl/rik/v2.3/rik.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/communited_instagram.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/scripts/knockout-2.3.0.js (expiration not specified)
http://www.rotterdam.nl/InstagramControl/scripts/knockout.mapping-latest.js (expiration not specified)
http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c (expiration not specified)
http://www.rotterdam.nl/cpr-16ad1a58c3062818e050090a8203680c (expiration not specified)
http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 (expiration not specified)
http://www.rotterdam.nl/cpr-b96a4f33a0004450a8284f205b5669fe (expiration not specified)
http://www.rotterdam.nl/cpr-bfaf311d5a0f2d1de040090a66034a83 (expiration not specified)
http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d (expiration not specified)
http://www.rotterdam.nl/cpr-cdd5d86a6f6f46f283af850f5b4d4f25 (expiration not specified)
http://www.rotterdam.nl/cpr-ceb376847a504898ba6d8ce5b633af73 (expiration not specified)
http://www.rotterdam.nl/cpr-e2ceb306f86c7538e040090a6c0350a7 (expiration not specified)
http://www.rotterdam.nl/cpr-f3c93f5aa3d75859e040090a6c033f56 (expiration not specified)
http://www.rotterdam.nl/cpr/contentimages/banner_map.gif (expiration not specified)
http://www.rotterdam.nl/cpr/images/btn_rss.gif (expiration not specified)
http://www.rotterdam.nl/cpr/images/default_list_style.gif (expiration not specified)
http://www.rotterdam.nl/cpr/images/logo-gemeente-rotterdam-2.png (expiration not specified)
http://www.rotterdam.nl/eCache/TER/1/237.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/119.css (expiration not specified)
http://www.rotterdam.nl/eCache/TER/120.css (expiration not specified)
http://www.rotterdam.nl/eCache/TER/138.dGFhbD17cGFnZTp0YWFsfQ.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/14/91/759.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/17/95/578.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/19/98/218.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/2/695.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/521.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/523.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/22/39/524.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/23/468.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/24/950.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/3/096.js (expiration not specified)
http://www.rotterdam.nl/eCache/TER/49/172.js (expiration not specified)
http://www.rotterdam.nl/twittercontrol/communitedtwitter.js (expiration not specified)
http://ssl.siteimprove.com/js/siteanalyze_6006165.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
priority - 6 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 56.8KiB (41% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/2/695.js could save 12.1KiB (58% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/23/468.js could save 7.1KiB (47% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/1/237.js could save 3.1KiB (38% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/22/39/524.js could save 2.5KiB (19% reduction).
Minifying http://www.rotterdam.nl/twittercontrol/communitedtwitter.js could save 2.4KiB (43% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/49/172.js could save 2.2KiB (50% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/14/91/759.js could save 2.1KiB (30% reduction).
Minifying http://www.rotterdam.nl/InstagramControl/communited_instagram.js could save 1.9KiB (50% reduction).
priority - 2 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 17.6KiB (19% reduction).
Minifying http://www.rotterdam.nl/cpr-783f05c2e0d91efce040090a660343e2 could save 4.7KiB (24% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/119.css could save 2KiB (18% reduction).
Minifying http://www.rotterdam.nl/cpr-16ad1a58c3042818e050090a8203680c could save 1.6KiB (17% reduction).
Minifying http://www.gis.rotterdam.nl/rik/v2.3/Style/openlayers.css could save 1.5KiB (17% reduction).
Minifying http://www.rotterdam.nl/cpr-cc74b6eda91a45beb9007844f2f1d98d could save 981B (24% reduction).
Minifying http://www.rotterdam.nl/eCache/TER/120.css could save 605B (20% reduction).
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 5.9KiB (16% reduction).
Compressing http://pbs.twimg.com/profile_images/720191801336799232/Lsp7iFg4_normal.jpg could save 962B (55% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…k5MzYyNTQ0Mw%3D%3D.2.c could save 899B (18% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…MjUwNjk1MzU4Mw%3D%3D.2 could save 849B (12% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…M1MTA1ODM2OA%3D%3D.2.c could save 828B (12% reduction).
Compressing https://scontent.cdninstagram.com/t51.2885-15/s150…Q1OTY0MzYxNA%3D%3D.2.c could save 812B (15% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 3.8KiB (22% reduction).
rotterdam.nl Mobile Resources
Total Resources | 65 |
Number of Hosts | 11 |
Static Resources | 52 |
JavaScript Resources | 26 |
CSS Resources | 13 |
rotterdam.nl Mobile Resource Breakdown
rotterdam.nl mobile page usability
Last tested: 2016-10-11
rotterdam.nl Mobile Usability Test Quick Summary
priority - 0 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="/plattegrond">Bezoek Rotterd…actieve kaart.</a>
is close to 1 other tap targets.The tap target
<a href="/rss_feed_20100429133214">RSS</a>
and 2 others are close to other tap targets.rotterdam.nl similar domains
www.rotterdam.net
www.rotterdam.org
www.rotterdam.info
www.rotterdam.biz
www.rotterdam.us
www.rotterdam.mobi
www.otterdam.nl
www.rotterdam.nl
www.eotterdam.nl
www.reotterdam.nl
www.erotterdam.nl
www.dotterdam.nl
www.rdotterdam.nl
www.drotterdam.nl
www.fotterdam.nl
www.rfotterdam.nl
www.frotterdam.nl
www.totterdam.nl
www.rtotterdam.nl
www.trotterdam.nl
www.rtterdam.nl
www.ritterdam.nl
www.roitterdam.nl
www.riotterdam.nl
www.rktterdam.nl
www.roktterdam.nl
www.rkotterdam.nl
www.rltterdam.nl
www.roltterdam.nl
www.rlotterdam.nl
www.rptterdam.nl
www.roptterdam.nl
www.rpotterdam.nl
www.roterdam.nl
www.rorterdam.nl
www.rotrterdam.nl
www.rortterdam.nl
www.rofterdam.nl
www.rotfterdam.nl
www.roftterdam.nl
www.rogterdam.nl
www.rotgterdam.nl
www.rogtterdam.nl
www.royterdam.nl
www.rotyterdam.nl
www.roytterdam.nl
www.rotrerdam.nl
www.rottrerdam.nl
www.rotferdam.nl
www.rottferdam.nl
www.rotgerdam.nl
www.rottgerdam.nl
www.rotyerdam.nl
www.rottyerdam.nl
www.rottrdam.nl
www.rottwrdam.nl
www.rottewrdam.nl
www.rottwerdam.nl
www.rottsrdam.nl
www.rottesrdam.nl
www.rottserdam.nl
www.rottdrdam.nl
www.rottedrdam.nl
www.rottderdam.nl
www.rottrrdam.nl
www.rotterrdam.nl
www.rottedam.nl
www.rotteedam.nl
www.rotteredam.nl
www.rotteerdam.nl
www.rotteddam.nl
www.rotterddam.nl
www.rottefdam.nl
www.rotterfdam.nl
www.rottefrdam.nl
www.rottetdam.nl
www.rottertdam.nl
www.rottetrdam.nl
www.rotteram.nl
www.rotterxam.nl
www.rotterdxam.nl
www.rotterxdam.nl
www.rottersam.nl
www.rotterdsam.nl
www.rottersdam.nl
www.rotteream.nl
www.rotterdeam.nl
www.rotterram.nl
www.rotterdram.nl
www.rotterfam.nl
www.rotterdfam.nl
www.rottercam.nl
www.rotterdcam.nl
www.rottercdam.nl
www.rotterdm.nl
www.rotterdqm.nl
www.rotterdaqm.nl
www.rotterdqam.nl
www.rotterdwm.nl
www.rotterdawm.nl
www.rotterdwam.nl
www.rotterdsm.nl
www.rotterdasm.nl
www.rotterdzm.nl
www.rotterdazm.nl
www.rotterdzam.nl
www.rotterda.nl
www.rotterdan.nl
www.rotterdamn.nl
www.rotterdanm.nl
www.rotterdaj.nl
www.rotterdamj.nl
www.rotterdajm.nl
www.rotterdak.nl
www.rotterdamk.nl
www.rotterdakm.nl
rotterdam.nl Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
rotterdam.nl TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.