xemacs.org Website Information

Daily Unique Visits: 27,699

Daily Page Views: 166,194

Income Per Day: $332

Estimated Value: $239,040

xemacs.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

No name server records were found.

and is probably hosted by Hetzner Online GmbH. See the full list of other websites hosted by Hetzner Online GmbH.

The highest website xemacs.org position in Alexa rank database was 41875 and the lowest rank position was 996190. Current position of xemacs.org in Alexa rank database is 51779.

Desktop speed score of xemacs.org (94/100) is better than the results of 92.73% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of xemacs.org (64/100) is better than the results of 11.2% of other sites and means that the page is not mobile-friendly.

Mobile speed score of xemacs.org (88/100) is better than the results of 91.94% of other sites and shows that the landing page performance on mobile devices is excellent.

xemacs.org 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.

xemacs.org 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: XEMACS.ORG
Registry Domain ID: D3676695-LROR
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://www.networksolutions.com
Updated Date: 2018-01-13T19:39:02Z
Creation Date: 1996-04-28T04:00:00Z
Registry Expiry Date: 2023-04-29T04:00:00Z
Registrar Registration Expiration Date:
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: domain.operations@web.com
Registrar Abuse Contact Phone: +1.8777228662
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization:
Registrant State/Province: FL
Registrant Country: US
Name Server: ROBOTNS2.SECOND-NS.DE
Name Server: ROBOTNS3.SECOND-NS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2022-02-18T11:04:52Z

xemacs.org server information

Servers Location

xemacs.org desktop page speed rank

Last tested: 2019-09-02

Desktop Speed Good

94/100

xemacs.org 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://xemacs.org/Images/cbxSmall.jpg (expiration not specified)
http://xemacs.org/Images/linklint.gif (expiration not specified)
http://xemacs.org/Images/xemacs.gif (expiration not specified)
http://xemacs.org/bitbucket-logo-150x75.png (expiration not specified)
http://xemacs.org/default.css (expiration not specified)

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://xemacs.org/default.css

priority - 0Optimize images

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

Optimize the following images to reduce their size by 1.4KiB (27% reduction).

Compressing http://xemacs.org/Images/linklint.gif could save 771B (63% reduction).
Compressing http://xemacs.org/Images/cbxSmall.jpg could save 449B (18% reduction).
Compressing https://www.w3.org/Icons/valid-xhtml10 could save 259B (14% reduction).

priority - 0Minify 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 836B (14% reduction).

Minifying http://xemacs.org/ could save 836B (14% reduction) after compression.

xemacs.org Desktop Resource Breakdown

Total Resources	8
Number of Hosts	3
Static Resources	6
CSS Resources	1

xemacs.org mobile page speed rank

Last tested: 2019-10-12

Mobile Speed Good

88/100

xemacs.org 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://xemacs.org/default.css

priority - 4Leverage 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 - 0Optimize images

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

Optimize the following images to reduce their size by 1.4KiB (27% reduction).

priority - 0Minify 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 836B (14% reduction).

Minifying http://xemacs.org/ could save 836B (14% reduction) after compression.

xemacs.org Mobile Resource Breakdown

Total Resources	8
Number of Hosts	3
Static Resources	6
CSS Resources	1

xemacs.org mobile page usability

Last tested: 2019-10-12

Mobile Usability Bad

64/100

xemacs.org 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.

English renders only 6 pixels tall (16 CSS pixels).

Australia and 5 others render only 6 pixels tall (16 CSS pixels).

Troubleshooting XEmacs and 19 others render only 6 pixels tall (16 CSS pixels).

http://ftp.uk.…rg/pub/xemacs/ and 80 others render only 6 pixels tall (16 CSS pixels).

Since the late…ail addresses. and 52 others render only 6 pixels tall (16 CSS pixels).

Objects in mir…they appear. and 2 others render only 6 pixels tall (16 CSS pixels).

. and 2 others render only 6 pixels tall (16 CSS pixels).
Official and 2 others render only 6 pixels tall (16 CSS pixels).
Site content repository: and 1 others render only 5 pixels tall (13 CSS pixels).
Discussion of…ion, problems: and 5 others render only 5 pixels tall (13 CSS pixels).
<https://www.xemacs.org> and 3 others render only 5 pixels tall (13 CSS pixels).
Conform with <…sitional.dtd"> and 1 others render only 5 pixels tall (13 CSS pixels).
PSGML renders only 5 pixels tall (13 CSS pixels).

priority - 15Size 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="./Languages/German/index.html">German</a> and 5 others are close to other tap targets.

The tap target <input type="submit" name="submit"> is close to 2 other tap targets.

The tap target <a href="http://www.xem…bin/namazu.cgi">help</a> and 67 others are close to other tap targets.

The tap target <a href="./Releases/index.html#Stable">Stable</a> and 2 others are close to other tap targets.
The tap target <a href="https://www.xemacs.org"><https://www.xemacs.org></a> and 3 others are close to other tap targets.

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.

xemacs.org HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Line: 1 Column: - 2
"...<?xml version="1..."

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 3 Column: 44 - 81
"...-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."