moolenaar.net Website Information

Daily Unique Visits: 3,866

Daily Page Views: 15,464

Income Per Day: $43

Estimated Value: $23,220

moolenaar.net is registered under .NET top-level domain. Please check other sites in .NET zone.

No name server records were found.

and is probably hosted by PAIR-NETWORKS - pair Networks, US. See the full list of other websites hosted by PAIR-NETWORKS - pair Networks, US.

The highest website moolenaar.net position in Alexa rank database was 40472 and the lowest rank position was 994043. Current position of moolenaar.net in Alexa rank database is 324640.

Desktop speed score of moolenaar.net (92/100) is better than the results of 90.97% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of moolenaar.net (66/100) is better than the results of 14.96% of other sites and means that the page is not mobile-friendly.

Mobile speed score of moolenaar.net (85/100) is better than the results of 90.58% of other sites and shows that the landing page performance on mobile devices is excellent.

moolenaar.net Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

moolenaar.net whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain Name: MOOLENAAR.NET
Registry Domain ID: 4853409_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.pairdomains.com
Registrar URL: http://www.pairdomains.com
Updated Date: 2022-10-31T18:12:46Z
Creation Date: 1999-03-31T05:00:00Z
Registry Expiry Date: 2028-03-31T04:00:00Z
Registrar: pair Networks, Inc. d/b/a pair Domains
Registrar IANA ID: 99
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: ok https://icann.org/epp#ok
Name Server: DNS.PAIR.COM
Name Server: NS7.NS0.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2023-11-24T15:17:22Z

moolenaar.net server information

Servers Location

moolenaar.net desktop page speed rank

Last tested: 2018-07-27

Desktop Speed Good

92/100

moolenaar.net Desktop Speed Test Quick Summary

priority - 3Leverage 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://moolenaar.net/2018_small.png (expiration not specified)
http://moolenaar.net/freebsd.gif (expiration not specified)
http://moolenaar.net/images/NLUUG-award.jpg (expiration not specified)
http://moolenaar.net/kopk.jpg (expiration not specified)
http://moolenaar.net/style.css (expiration not specified)
http://moolenaar.net/vim_anim.gif (expiration not specified)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)

priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://moolenaar.net/style.css

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 11KiB (16% reduction).

Compressing http://moolenaar.net/2018_small.png could save 7KiB (16% reduction).
Compressing http://moolenaar.net/images/NLUUG-award.jpg could save 2.9KiB (18% reduction).
Compressing http://moolenaar.net/kopk.jpg could save 1.2KiB (16% reduction).

priority - 1Enable 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 8.7KiB (67% reduction).

Compressing http://moolenaar.net/ could save 8.6KiB (68% reduction).
Compressing http://moolenaar.net/style.css could save 135B (39% reduction).

moolenaar.net Desktop Resource Breakdown

Total Resources	10
Number of Hosts	3
Static Resources	8
JavaScript Resources	3
CSS Resources	1

moolenaar.net mobile page speed rank

Last tested: 2018-05-07

Mobile Speed Good

85/100

moolenaar.net Mobile Speed Test Quick Summary

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://moolenaar.net/style.css

priority - 5Leverage 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:

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 11KiB (16% reduction).

priority - 1Enable 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 8.7KiB (67% reduction).

Compressing http://moolenaar.net/ could save 8.6KiB (68% reduction).
Compressing http://moolenaar.net/style.css could save 135B (39% reduction).

moolenaar.net Mobile Resource Breakdown

Total Resources	10
Number of Hosts	3
Static Resources	8
JavaScript Resources	3
CSS Resources	1

moolenaar.net mobile page usability

Last tested: 2018-05-07

Mobile Usability Medium

66/100

moolenaar.net Mobile Usability Test Quick Summary

priority - 34Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Malējs, Dzirnavnieks and 38 others render only 6 pixels tall (16 CSS pixels).

In Holland the…und the world. and 24 others render only 6 pixels tall (16 CSS pixels).

I am very prou…d company :-). and 56 others render only 6 pixels tall (16 CSS pixels).

alphabetical and 1 others render only 6 pixels tall (16 CSS pixels).

'Weinig aandac…in Nederland` and 18 others render only 6 pixels tall (16 CSS pixels).

Vim - Vi IMproved and 9 others render only 6 pixels tall (16 CSS pixels).

language - paper size renders only 6 pixels tall (16 CSS pixels).

English - Letter and 2 others render only 6 pixels tall (16 CSS pixels).

It took more t…e heavy stuff. and 4 others render only 6 pixels tall (16 CSS pixels).

Send comments…moolenaar.net. renders only 5 pixels tall (13 CSS pixels).

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 7Size 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.

The tap target <a href="genealogy.html">here</a> and 4 others are close to other tap targets.

The tap target <a href="vim.html">Vim - Vi IMproved</a> and 11 others are close to other tap targets.

The tap target <a href="2018_en_a4.pdf">English - A4</a> and 2 others are close to other tap targets.

moolenaar.net HTML validation