The most comprehensive website checker on the Internet

Website Checker Report

for

bitcoin.org

April 21, 2016

Document Purpose

This report presents findings of a complex set of website and server tests and analyzes. The primary purpose of this document is to inform the responsible staff, including administrators, web developers, and IT managers, about the state of the checked systems, and to provide recommendations on how to improve it. The focus of the executed checks is on the compliance with industry standards and best practices. Each alert in this report should be processed separately and further investigated before any action is taken to fix the reported issues. It should be understood that all the performed checks were done automatically and as such they can cover only parts of the tested areas of the target systems. Passing the checks does not imply the tested systems are secure of faultless.

Report Alert Summary
Blacklist Check
Malware and Reputation Check
SSL/TLS Check
- Target 208.64.123.130:443 (bitcoin.org)
Mail Server Health Check
DNS Zone Health Check
HTML Standards Check
Broken Link Check
Website Speed and Usability Check
Email Privacy Check
SEO Check
SERP Rank Check
Site Popularity Check
Response Time Check
- IP Address 208.64.123.130 (bitcoin.org)
Geo Location Check
- IP Address 208.64.123.130
Technology Stack Check
WHOIS Check
- Domain bitcoin.org
- Address 208.64.123.130

Report Alert Summary

113

Report Section
SSL/TLS Check – Target 208.64.123.130:443 (bitcoin.org)	0	2	0	7
Mail Server Health Check – Mail Servers by IP Address	0	0	4	0
DNS Zone Health Check – DNSSEC Module	0	0	0	2
DNS Zone Health Check – Delegation Module	0	0	0	2
HTML Standards Check	30	0	0	0
Website Speed and Usability Check – Google PageSpeed Insights Analysis for Desktop Devices	0	4	0	6
Website Speed and Usability Check – Google PageSpeed Insights Analysis for Mobile Devices	1	3	0	12
Website Speed and Usability Check – sitespeed.io Analysis for Desktop Devices	36	19	0	0
Website Speed and Usability Check – sitespeed.io Analysis for Mobile Devices	37	18	0	0
Email Privacy Check	9	0	0	0
SEO Check	0	25	15	0
SERP Rank Check – Keyword 'bitcoin' on google.com	0	0	3	10
SERP Rank Check – Keyword 'cryptocurrency' on google.com	0	0	1	10
SERP Rank Check – Keyword 'payment network' on google.com	0	0	1	10
SERP Rank Check – Keyword 'electronic money' on google.com	0	0	1	10
Site Popularity Check – Global Ranks	0	0	0	1
Site Popularity Check – Backlinks Statistics	0	0	0	1
Site Popularity Check – Social Networks Stats	0	0	0	1
Geo Location Check – IP Address 208.64.123.130	0	0	0	2
WHOIS Check – Domain bitcoin.org	0	0	0	6
WHOIS Check – Address 208.64.123.130	0	0	0	4

Severity Icons Legend

	Error	The most critical alerts in the report that point out a serious problem that should be fixed immediately.
	Warning	A non-critical problem that requires serious attention was found. Further investigation and fixing should be considered.
	Notice	Alerts of this severity point out possible improvements in the evaluated system or feature. In some cases, the reported state might be intentional. In other cases, optimization might be considered.
	Info	Points out an interesting fact or value. No problem detected and no action is needed if the reported data match the expectations.
	Trace	Provides further details about the tested system or feature. No problem detected and no action is needed if the reported data match the expectations.

Blacklist Check

Many different methods were developed to fight SPAM and other malicious activity on the Internet. One of the systems that is commonly being used is a system of blacklists. The Blacklist Check tests whether a specific mail server is listed in one or more of the well known and widely used DNS-based blackhole list (DNSBL) and real-time blackhole list (RBL) blacklists.

If a mail server's address is on one or more blacklists, it may cause that messages sent through it will never reach their recipients. When a blacklisted mail server attempts to send an email to a mail server that is protected against spam with a solution that relies on using blacklists, the target mail server refuses to accept the message or even blocks the initial network connection from the blacklisted address. For the blacklisted mail server, it is thus impossible to deliver emails to the target mail server.

A mail server can be blacklisted for various reasons, including a server hack or a malware infection. After the primary cause of the problem is mitigated, the mail server administrator is required to ask for a removal on all blacklists that do not delist the mail server automatically. For this purpose, for each blacklist the target server is listed on, the Blacklist Check provides links to delisting request forms, or web pages that contain more information.

IP Address 208.64.123.130

The IP address was checked against 147 blacklists.

Listings on High Volume Reliable Blacklists

No entries found.

Listings on Reliable Blacklists

No entries found.

Listings on Less Reliable Blacklists

No entries found.

IP Address 165.254.167.50

The IP address was checked against 147 blacklists.

Listings on High Volume Reliable Blacklists

No entries found.

Listings on Reliable Blacklists

No entries found.

Listings on Less Reliable Blacklists

No entries found.

IP Address 74.201.155.220

The IP address was checked against 147 blacklists.

Listings on High Volume Reliable Blacklists

No entries found.

Listings on Reliable Blacklists

No entries found.

Listings on Less Reliable Blacklists

No entries found.

Malware and Reputation Check

Phishing web pages and malware sources are often hosted on hacked or infected web sites of otherwise honest web owners, who rarely know about the problem until it is too late. When a web site is marked as a host of malicious content, the site automatically loses lots of its visitors, simply because search engines and security products will not let their users access it. The root cause of the problem can be a security hole in the code of the infected web site, but not always this is the case. The attackers could also exploited the web page hosting company, or even another client's code, whose code runs on the same server.

Malware and Reputation Check asks third party engines to scan the target web site for malware, and it also obtains trust scores from established web reputation services. Currently, the following third party services are used:

Google SafeBrowsing Status

The web site is safe.

PhishTank Database

No entries found.

VirusTotal Scan

The web site was checked by 67 antivirus engines.

The web site is marked as clean by all engines.

SSL/TLS Check

SSL/TLS Check performs a detailed analysis of TLS/SSL certificate and configuration of the target server. The analysis includes checks for known TLS and SSL vulnerabilities, such as OpenSSL, CRIME, CCS injection, Heartbleed, POODLE, BREACH, etc. Security holes in SSL and TLS protocols and libraries have become very popular on the field of Internet security in last couple of years. They usually affect a large number of online servers and software packages and can lead to thefts of sensitive data, such as databases of users, their credentials, and even their identities.

Target 208.64.123.130:443 (bitcoin.org)

Problems Summary

BEAST vulnerability (CVE-2011-3389) is NOT mitigated on server.

Certificate Chain

Main Server Certificate
Subject Name	www.bitcoin.org
Subject Data	OU=Domain Control Validated - RapidSSL(R)
Alternative Names	www.bitcoin.org, bitcoin.org
Prefix Handling	Yes (with and without www)
Valid From	2014-12-10 01:26:51 UTC
Valid To	2017-01-10 21:18:24 UTC (expires 8 months from now)
Key	RSA 2048 bits (e 65537)
Signature Algorithm	SHA256withRSA
Fingerprint	6fa1ae29e14c75cf2ef73c86ad03fa0bad99f1db
Issuer Name	RapidSSL SHA256 CA - G3
Issuer Data	O=GeoTrust Inc., C=US
Extended Validation	No
Certificate Transparency	No
Revocation Information	OCSP, CRL
Revocation Status	Not revoked
Weak Debian Key	No
Self-signed	No
Trusted	Yes (Apple, Java, Microsoft, Mozilla)

Chain Certificate #2
Subject Name	RapidSSL SHA256 CA - G3
Subject Data	O=GeoTrust Inc., C=US
Valid To	2022-05-20 21:39:32 UTC (expires 6 years from now)
Key	RSA 2048 bits (e 65537)
Signature Algorithm	SHA256withRSA
Fingerprint	0e34141846e7423d37f20dc0ab06c9bbd843dc24
Issuer Name	GeoTrust Global CA
Issuer Data	O=GeoTrust Inc., C=US
Revocation Status	Not revoked
Weak Debian Key	No
Self-signed	No

Certificate Paths

Path #1 (TRUSTED)
1	Sent by server	www.bitcoin.org 6fa1ae29e14c75cf2ef73c86ad03fa0bad99f1db RSA 2048 bits / SHA256withRSA
2	Sent by server	RapidSSL SHA256 CA - G3 0e34141846e7423d37f20dc0ab06c9bbd843dc24 RSA 2048 bits / SHA256withRSA
3	In trust store	GeoTrust Global CA (self-signed) de28f4a4ffe5b92fa3c503d1a349a7f9962a8212 RSA 2048 bits / SHA1withRSA

Protocol Details

Details
Secure Renegotiation	Yes
Secure Client-Initiated Renegotiation	No
Insecure Client-Initiated Renegotiation	No
OCSP Stampling	No
Strict Transport Security (HSTS)	Yes
Session Resumption (Session IDs)	Yes
Session Resumption (Session Tickets)	Yes
Deflate Compression	No
Downgrade Attack Prevention (TLS_FALLBACK_SCSV)	Yes
Supports Insecure Ciphers	No
Supports Weak Ciphers	No
Common DH Prime	No
Forward Secrecy	Yes
BREACH Vulnerability	No
CRIME Vulnerability	No
OpenSSL CCS Injection	No
Heartbleed Vulnerability	No
POODLE Vulnerability	No
BEAST Vulnerability	Yes
FREAK Vulnerability	No
LOGJAM Vulnerability	No

Supported Protocols and Cipher Suites

Protocol Support
TLS 1.2	Yes
TLS 1.1	Yes
TLS 1.0	Yes
SSL 3	No
SSL 2	No

TLS 1.2

Cipher Suite	Grade	Size	FS	Export	Anon	Prefer
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)	Secure	128	Yes	No	No	Yes
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)	Secure	256	Yes	No	No	No
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)	Secure	256	No	No	No	No
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)	Secure	256	No	No	No	No
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)	Secure	256	No	No	No	No
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)	Secure	256	No	No	No	No
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)	Secure	128	Yes	No	No	No
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41)	Secure	128	No	No	No	No
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c)	Secure	128	No	No	No	No
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)	Secure	128	No	No	No	No
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)	Secure	128	No	No	No	No
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x0a)	Secure	112	No	No	No	No

TLS 1.1

Cipher Suite	Grade	Size	FS	Export	Anon	Prefer
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)	Secure	128	Yes	No	No	Yes
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)	Secure	256	Yes	No	No	No
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)	Secure	256	No	No	No	No
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)	Secure	256	No	No	No	No
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)	Secure	128	No	No	No	No
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41)	Secure	128	No	No	No	No
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x0a)	Secure	112	No	No	No	No

TLS 1.0

Cipher Suite	Grade	Size	FS	Export	Anon	Prefer
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)	Secure	128	Yes	No	No	Yes
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 2048 bits	Secure	256	Yes	No	No	No
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)	Secure	256	Yes	No	No	No
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)	Secure	256	No	No	No	No
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)	Secure	256	No	No	No	No
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 2048 bits	Secure	128	Yes	No	No	No
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)	Secure	128	No	No	No	No
TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41)	Secure	128	No	No	No	No
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x0a)	Secure	112	No	No	No	No

Mail Server Health Check

Setting up a mail server so that it can really deliver emails to other systems is somehow a difficult task today. Mail server administrators need to know about different kinds of anti-spam mechanisms that are being used in order to setup their MX servers well. Mail Server Health Check helps with mail server configuration with a focus to achieve high email delivery rates.

The check includes finding mail servers for the target domain, checking their availability, evaluating DNS SPF, MX, and PTR records, and their compliance with RFC standards and high delivery rate best practices. Problems in mail server configuration can lead to a wide range of issues from delays in delivery to complete inability to deliver emails to some systems, or having outgoing messages marked as SPAM.

SPF Record Check

SPF records are important parts of the mail delivery system. Many mail servers are configured to check SPF record of each sender that attempts to deliver email to them. SPF records are TXT DNS resource records with a specific syntax. A well configured SPF record may improve email delivery rates and prevent some problems related to SPAM.

No problems detected.

Mail Servers by Hostname

The list of mail servers was obtained from DNS MX records. Each record and was analyzed and checked if it conforms to relevant RFC standards and industry best practices.

No problems detected.

Mail Server mx.zohomail.com

No problems detected.

Mail Server mx2.zohomail.com

No problems detected.

Mail Servers by IP Address

The list of mail servers IP addresses was obtained by resolving DNS MX records hostnames. Each mail server was checked if it is reachable on the network and its PTR and SPF records were analyzed.

No problems detected.

Mail Server 165.254.167.50 (See this IP's blacklist check)

Reverse record domain does not match the target domain. This may affect delivery rate to some systems because some anti-SPAM solutions favour mail servers which reverse name matches the sender's email address domain. This is relevant only if the server is intended to send emails on behalf of the target domain.
Server's greeting banner does not contain the original domain, nor its IP's reverse record domain.

Mail Server 74.201.155.220 (See this IP's blacklist check)

Reverse record domain does not match the target domain. This may affect delivery rate to some systems because some anti-SPAM solutions favour mail servers which reverse name matches the sender's email address domain. This is relevant only if the server is intended to send emails on behalf of the target domain.
Server's greeting banner does not contain the original domain, nor its IP's reverse record domain.

DNS Zone Health Check

Well configured DNS name servers and records are crucial for every Internet project because DNS is one the first technologies that are being used when a visitor is about to access a website, or other service, well before their browser tries to connect to the target server. If DNS is not configured properly, the visitor will be unable to reach the target server, or it might take the visitor much longer time than needed to get to the target service.

DNS Zone Health Check analyzes the status of the domain's DNS zone including IPv6 and DNSSEC settings. It validates all important features of DNS such as syntax, connectivity, delegation, consistency, name server availability, etc. DNS Zone Health Check is based on Zonemaster project by .SE and AFNIC.

Basic Module

This module performs basic DNS checks, such as protocol support and name server discovery, checking glue records, checking NS records.

No problems detected.

Address Module

This module performs checks on resolved name servers' IP addresses.

No problems detected.

Connectivity Module

This module checks how are the name servers reachable.

No problems detected.

Consistency Module

This module verifies that nameservers provide consistent answers.

No problems detected.

DNSSEC Module

This module extensively tests Domain Name System Security Extensions settings.

199.19.56.1 returned no DS records for bitcoin.org.
Delegation from parent to child is not properly signed no_ds.

Delegation Module

This module checks resolution paths and settings of DNS delegation.

IP 216.87.152.33 refers to multiple nameservers (dns2.registrar-servers.com;dns4.registrar-servers.com).
IP 216.87.155.33 refers to multiple nameservers (dns1.registrar-servers.com;dns3.registrar-servers.com;dns5.registrar-servers.com).

Nameserver Module

This module tests behavior of each name server.

No problems detected.

Syntax Module

This module checks the syntax of DNS records.

No problems detected.

Zone Module

This module checks the configuration of the SOA record.

No problems detected.

HTML Standards Check

HTML standards prescribe how HTML code should be written by developers and how it should be interpreted by web browsers. Violation of the HTML standards in a web page code causes that the page may be displayed differently to users with different browsers, or may worsen the web page performance as well as the user experience for some or all of the visitors. Some specific errors may also lead to security issues. It is thus vital for every web page to follow the standards as much as possible.

HTML Standards Check surfs the target website and validates the code of its web pages. It is based on The Nu Html Checker, a modern HTML5 validation engine.

Page https://bitcoin.org/en/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 210. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1">« <im

Page https://bitcoin.org/id/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=id&cc_lang_pref=id">« <im

Page https://bitcoin.org/da/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=da&cc_lang_pref=da">« <im

Page https://bitcoin.org/de/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=de&cc_lang_pref=de">« <im

Page https://bitcoin.org/es/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=es&cc_lang_pref=es">« <im

Page https://bitcoin.org/fr/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=fr&cc_lang_pref=fr">« <im

Page https://bitcoin.org/it/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=it&cc_lang_pref=it">« <im

Page https://bitcoin.org/hu/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=hu&cc_lang_pref=hu">« <im

Page https://bitcoin.org/nl/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=nl&cc_lang_pref=nl">« <im

Page https://bitcoin.org/pl/

From line 141, column 1, to line 141 column 109. Attribute “ontouchstart” not allowed on element “a” at this point.
- /ul>«« ««<a id="menumobile" class="menumobile" onclick="mobileMenuShow(event);" ontouchstart="mobileMenuShow(event);"></a>««
From line 206, column 1, to line 206 column 121. Attribute “ontouchstart” not allowed on element “ul” at this point.
- div>«« ««<ul id="menusimple" class="menusimple menumain" onclick="mobileMenuHover(event);" ontouchstart="mobileMenuHover(event);">« <li
From line 255, column 24, to line 255 column 261. Attribute “ontouchstart” not allowed on element “div” at this point.
- ainvideo"><div onclick="loadYoutubeVideo(event);" ontouchstart="loadYoutubeVideo(event);" data-youtubeurl="//www.youtube.com/embed/Gc2en3nHxA4?rel=0&showinfo=0&wmode=opaque&autoplay=1&cc_load_policy=1&hl=pl&cc_lang_pref=pl">« <im

Broken Link Check

Having working links on a website is crucial for user experience. Whether it is a typo in the code, or the target web page was removed or renamed, the visitors are annoyed when they click a link that does not work. Same holds for broken links to images and other resources. The Brokenlink Check surfs through the target website and analyzes each page's HTML and CSS codes and identify and verify links in all standard elements, including links to third party resources and web pages.

Checking for broken links started on https://bitcoin.org/. 500 links were checked on that page and other linked pages within the same domain. Pages that contained broken links are listed below. Each page contains one or more broken links, for which we show the status/error code redirection chain, position of the broken link in the source code, and its URL.

No broken links found among 500 links that were checked.

Website Speed and Usability Check

This module evaluates web site speed and usability for both desktop and mobile users. Following the industry best practices and recommendations for optimizing the web site speed and usability can significantly increase user experience across all end-user devices. Today, these characteristics are even considered by search engines, and thus a well performing and mobile-ready web site has a higher chance of getting more visitors from search engines than a poorly designed one.

Website Speed and Usability Check uses two different engines – Google PageSpeed Insights and sitespeed.io – in order to deliver as many useful data as possible about the target web site performance and usability. Both engines use a large set of rules that is being used to evaluate the target web site, so it is possible that some recommendations are doubled in the report.

Google PageSpeed Insights Analysis for Desktop Devices

The following is a result of an analysis of https://bitcoin.org/en/.

Overall Page Speed Score: 84

Page Statistics

Metric	Value
Number of HTTP resources loaded by the page	22
Number of unique hosts referenced by the page	2
Total size of all request bytes sent by the page	1.5 KB
Number of static (that is, cacheable) resources on the page	19
Size of uncompressed response for the main HTML document and all iframes on the page	9.61 KB
Size of uncompressed response for text resources on the page that aren't covered by other statistics; that is, non-HTML, non-script, non-CSS resources	0 B
Size of uncompressed response for CSS resources on the page	79.73 KB
Size of response for image resources on the page	120.79 KB
Size of uncompressed response for JS resources on the page	66.03 KB
Size of response for Flash resources on the page	0 B
Size of response for other resources on the page	474 B
Number of JavaScript resources referenced by the page	5
Number of CSS resources referenced by the page	3

Page Rules Scores and Recommendations

For each rule, the measured result is provided as an Impact value. Zero impact value means the analyzed page passed the rule. Non-zero value means there is a possibility for an improvement. The higher the Impact value is, the greater is the impact of the identified problem to the performance or usability.

Avoid landing page redirects (SPEED)

Rule Impact: 0

Your page has no redirects. Learn more about avoiding landing page redirects.

Enable compression (SPEED)

Rule Impact: 0

You have compression enabled. Learn more about enabling compression.

Leverage browser caching (SPEED)

Rule Impact: 2

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.

Details:

Leverage browser caching for the following cacheable resources:
- https://bitcoin.org/js/analytics.js (expiration not specified)
- https://bitcoin.org/js/base.js (expiration not specified)
- https://bitcoin.org/js/cookieconsent/cookieconsent.js (expiration not specified)
- https://bitcoin.org/js/main.js (expiration not specified)

Reduce server response time (SPEED)

Rule Impact: 0

Your server responded quickly. Learn more about server response time optimization.

Minify CSS (SPEED)

Rule Impact: 0

Your CSS is minified. Learn more about minifying CSS.

Minify HTML (SPEED)

Rule Impact: 0

Your HTML is minified. Learn more about minifying HTML.

Minify JavaScript (SPEED)

Rule Impact: 0.37

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Details:

Minify JavaScript for the following resources to reduce their size by 3.6KiB (33% reduction).
- Minifying https://bitcoin.org/js/main.js could save 1.6KiB (32% reduction) after compression.
- Minifying https://bitcoin.org/js/base.js could save 1.1KiB (40% reduction) after compression.
- Minifying https://bitcoin.org/js/cookieconsent/cookieconsent.js could save 903B (29% reduction) after compression.

Eliminate render-blocking JavaScript and CSS in above-the-fold content (SPEED)

Rule Impact: 6

Your page has 3 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Details:

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:
- https://bitcoin.org/js/base.js
- https://bitcoin.org/js/main.js
- https://bitcoin.org/js/cookieconsent/cookieconsent.js
Optimize CSS Delivery of the following:
- https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
- https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css

Optimize images (SPEED)

Rule Impact: 8.254

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

Details:

Optimize the following images to reduce their size by 80.6KiB (80% reduction).
- Compressing and resizing https://bitcoin.org/img/video/video_wuc.jpg could save 80.6KiB (80% reduction).

Prioritize visible content (SPEED)

Rule Impact: 0

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Google PageSpeed Insights Analysis for Mobile Devices

The following is a result of an analysis of https://bitcoin.org/en/.

Overall Page Speed Score: 78

Overall Page Usability Score: 98

Page Statistics

Metric	Value
Number of HTTP resources loaded by the page	23
Number of unique hosts referenced by the page	2
Total size of all request bytes sent by the page	1.55 KB
Number of static (that is, cacheable) resources on the page	20
Size of uncompressed response for the main HTML document and all iframes on the page	9.61 KB
Size of uncompressed response for text resources on the page that aren't covered by other statistics; that is, non-HTML, non-script, non-CSS resources	0 B
Size of uncompressed response for CSS resources on the page	79.73 KB
Size of response for image resources on the page	121.69 KB
Size of uncompressed response for JS resources on the page	66.03 KB
Size of response for Flash resources on the page	0 B
Size of response for other resources on the page	474 B
Number of JavaScript resources referenced by the page	5
Number of CSS resources referenced by the page	3

Page Rules Scores and Recommendations

Avoid app install interstitials that hide content (USABILITY)

Rule Impact: 0

Your page does not appear to have any app install interstitials that hide a significant amount of content. Learn more about the importance of avoiding the use of app install interstitials.

Avoid landing page redirects (SPEED)

Rule Impact: 0

Your page has no redirects. Learn more about avoiding landing page redirects.

Avoid plugins (USABILITY)

Rule Impact: 0

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Configure the viewport (USABILITY)

Rule Impact: 0

Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.

Enable compression (SPEED)

Rule Impact: 0

You have compression enabled. Learn more about enabling compression.

Leverage browser caching (SPEED)

Rule Impact: 3

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.

Details:

Leverage browser caching for the following cacheable resources:
- https://bitcoin.org/js/analytics.js (expiration not specified)
- https://bitcoin.org/js/base.js (expiration not specified)
- https://bitcoin.org/js/cookieconsent/cookieconsent.js (expiration not specified)
- https://bitcoin.org/js/main.js (expiration not specified)

Reduce server response time (SPEED)

Rule Impact: 0

Your server responded quickly. Learn more about server response time optimization.

Minify CSS (SPEED)

Rule Impact: 0

Your CSS is minified. Learn more about minifying CSS.

Minify HTML (SPEED)

Rule Impact: 0

Your HTML is minified. Learn more about minifying HTML.

Minify JavaScript (SPEED)

Rule Impact: 0.37

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Details:

Minify JavaScript for the following resources to reduce their size by 3.6KiB (33% reduction).
- Minifying https://bitcoin.org/js/main.js could save 1.6KiB (32% reduction) after compression.
- Minifying https://bitcoin.org/js/base.js could save 1.1KiB (40% reduction) after compression.
- Minifying https://bitcoin.org/js/cookieconsent/cookieconsent.js could save 903B (29% reduction) after compression.

Eliminate render-blocking JavaScript and CSS in above-the-fold content (SPEED)

Rule Impact: 24

Your page has 3 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Details:

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:
- https://bitcoin.org/js/base.js
- https://bitcoin.org/js/main.js
- https://bitcoin.org/js/cookieconsent/cookieconsent.js
Optimize CSS Delivery of the following:
- https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
- https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css

Optimize images (SPEED)

Rule Impact: 0

Your images are optimized. Learn more about optimizing images.

Prioritize visible content (SPEED)

Rule Impact: 0

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Size content to viewport (USABILITY)

Rule Impact: 0

The contents of your page fit within the viewport. Learn more about sizing content to the viewport.

Size tap targets appropriately (USABILITY)

Rule Impact: 1.481

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.

Details:

The following tap targets are close to other nearby tap targets and may need additional spacing around them.
- The tap target <a href="/en/legal">Legal</a> and 3 others are close to other tap targets.

Use legible font sizes (USABILITY)

Rule Impact: 0

The text on your page is legible. Learn more about using legible font sizes.

sitespeed.io Analysis for Desktop Devices

The following is a result of an analysis of 5 pages, starting from https://bitcoin.org/. The test was done with Viewport set to 1280x800, and User-Agent header set to Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36.

Aggregate Results

This section presents aggregate results across all tested pages. For individual page recommendations, see sections below.

Title / Description	Median Value	Best Value	Worst Value
Images scaled by the browser Never scale images in the browser, that will slow down the rendering.	1.0	0.0	21.0
Cache Time How long time the assets are cached in the browser. Long time is good.	5 minutes	4 weeks	0 seconds
Critical Rendering Path Score Do as little as possible within the HEAD tag so that the browser can start rendering a page as soon as possible (avoid DNS lookups and load CSS/JS files).	55.0	55.0	55.0
Number of CSS images per page Few larger CSS images are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	3.00	1.00	3.00
Number of CSS files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	3.00	3.00	3.00
Document Weight Keep the document at a reasonable size, it will make it possible for the browser to generate the page faster.	9.13 KB	9.08 KB	39.9 KB
Number of DOM elements Too many DOM elements means that the page is complex and will be slower to render	213.0	209.0	1074.0
Number of font files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	1.00	1.00	1.00
Number of images per page Avoid too many images because it will take time for them all to load.	6.00	2.00	133.00
Number of JS files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	5.00	5.00	5.00
Number of JS synchronously inside head Loading Javascript synchronously inside of the HEAD tag will slow down your page rendering. Just don't do it!	3.00	3.00	3.00
Max requests per domain Using HTTP 1.1 you want to avoid loading too many assets from one domain	19.00	13.00	132.00
Number Of Domains Many domains means many DNS lookups and that means slower pages.	2.00	2.00	3.00
Redirects Per Page Avoid doing redirects, it will slow down the page!	0.00	0.00	1.00
Number of requests per page Fewer requests are always faster than many requests.	20.0	14.0	146.0
Requests Without Expires Requests shall always have expire headers, so that they can be cached by the browser	5.00	5.00	54.00
Rule Score The sitespeed.io total rule score for all the pages	87	87	78
No other problems found.

Page Statistics

Page URL (http(s)://bitcoin.org…)	Overall Score	Load Time	Requests	Req. w/ Cache	Size	Size w/ Cache
/en/about-us	78	3363 ms	146	138	281.92 KB	37.45 KB
/en/alerts	86	1680 ms	14	6	161.19 KB	0 B
/id/	87	1826 ms	20	6	270.17 KB	0 B
/nl/	87	1832 ms	20	6	267.02 KB	0 B
/en/	87	2007 ms	20	6	266.97 KB	0 B

Page Rules Scores and Recommendations

Avoid slowing down the critical rendering path

Every request fetched inside of HEAD, will postpone the rendering of the page! Do not load javascript synchronously inside of head, load files from the same domain as the main document (to avoid DNS lookups) and inline CSS for a really fast rendering path. The scoring system for this rule, will give you minus score for synchronously loaded javascript inside of head, css files requested inside of head and minus score for every DNS lookup inside of head.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/en/alerts	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/id/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/nl/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/en/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
Showing 6 / 6 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css

Minify JavaScript and CSS

Minification removes unnecessary characters from a file to reduce its size, thereby improving load times. When a file is minified, comments and unneeded white space characters (space, newline, and tab) are removed. This improves response time since the size of the download files is reduced.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	70	There are 3 components that can be minified.
/en/alerts	70	There are 3 components that can be minified.
/id/	70	There are 3 components that can be minified.
/nl/	70	There are 3 components that can be minified.
/en/	70	There are 3 components that can be minified.
Showing 3 / 3 relevant components: https://bitcoin.org/js/cookieconsent/cookieconsent.js inline <script> tag #1 inline <script> tag #3

Never scale images in HTML

Images should always be sent with the correct size else the browser will download an image that is larger than necessary. This is more important today with responsive web design, meaning you want to avoid downloading non scaled images to a mobile phone or tablet. Note: This rule doesn check images with size 0 (images in carousels etc), so they will be missed by the rule.The rule also skip images where the difference between the sizes are less than a configurable value (default 100 pixels).

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	You have 21 images that are scaled more than 100 pixels in the HTML.
Showing 10 / 21 relevant components: https://avatars.githubusercontent.com/u/2966862?v=3&size=16 https://avatars.githubusercontent.com/u/3898816?v=3&size=16 https://avatars.githubusercontent.com/u/852547?v=3&size=16 https://avatars.githubusercontent.com/u/665854?v=3&size=16 https://avatars.githubusercontent.com/u/6692088?v=3&size=16 https://avatars.githubusercontent.com/u/1000756?v=3&size=16 https://avatars.githubusercontent.com/u/263299?v=3&size=16 https://avatars.githubusercontent.com/u/14154647?v=3&size=16 https://avatars.githubusercontent.com/u/12200693?v=3&size=16 https://avatars.githubusercontent.com/u/5767891?v=3&size=16

Never load JS synchronously in head

Javascript files should never be loaded synchronously in HEAD, because it will block the rendering of the page.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/en/alerts	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/id/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/nl/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/en/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
Showing 3 / 3 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js

Reduce number of total requests

Avoid to have too many requests on your page. The more requests, the slower the page will be for the end user.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	The page uses 146 requests, that is too many to make the page load fast.
Showing 10 / 146 relevant components: https://bitcoin.org/en/about-us https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/css/font-awesome-4.4.0/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css https://www.google-analytics.com/analytics.js https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js

Have expire headers for static components

By adding HTTP expires headers to your static files, the files will be cached in the end users browser.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	There are 53 static components without a future expiration date.
/en/alerts	56	There are 4 static components without a future expiration date.
/id/	56	There are 4 static components without a future expiration date.
/nl/	56	There are 4 static components without a future expiration date.
/en/	56	There are 4 static components without a future expiration date.
Showing 10 / 53 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js https://avatars.githubusercontent.com/u/3578089?v=3&size=16 https://avatars.githubusercontent.com/u/61096?v=3&size=16 https://avatars.githubusercontent.com/u/1130872?v=3&size=16 https://avatars.githubusercontent.com/u/331997?v=3&size=16 https://avatars.githubusercontent.com/u/12899428?v=3&size=16 https://avatars.githubusercontent.com/u/1095675?v=3&size=16

Have expires headers equals or longer than one year

Having really long cache headers are beneficial for caching.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	There are 144 static components without a expire header equal or longer than one year.
/en/alerts	40	There are 12 static components without a expire header equal or longer than one year.
/id/	10	There are 18 static components without a expire header equal or longer than one year.
/nl/	10	There are 18 static components without a expire header equal or longer than one year.
/en/	10	There are 18 static components without a expire header equal or longer than one year.
Showing 10 / 152 relevant components: https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css https://www.google-analytics.com/analytics.js https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js https://bitcoin.org/img/icons/mini_ico_anchor.svg https://bitcoin.org/img/icons/netstatus_normal.svg

Do not load css files when the page has few request

When a page has few requests (or actually maybe always if you dont have a massive amount of css), it is better to inline the css, to make the page to start render as early as possible.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/alerts	40	The page have 13 requests and uses 3 css files. It is better to keep the css inline, when you have so few requests.
Showing 3 / 3 relevant components: https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css

Have a reasonable percentage of textual content compared to the rest of the page

Make sure the amount of HTML elements are too many compared to text content.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	54	The amount of content percentage: 26.64%.
/id/	78	The amount of content percentage: 39.49%.
/nl/	78	The amount of content percentage: 39.24%.
/en/	78	The amount of content percentage: 38.65%.

Use a Content Delivery Network (CDN)

User proximity to web servers impacts response times. Deploying content across multiple geographically dispersed servers helps users perceive that pages are loading faster.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	There are 142 static components that are not on CDN.
/en/alerts	0	There are 10 static components that are not on CDN.
/id/	0	There are 16 static components that are not on CDN.
/nl/	0	There are 16 static components that are not on CDN.
/en/	0	There are 16 static components that are not on CDN.
Showing 4 / 4 relevant components: bitcoin.org: 10 components, 127.0K (80.0K GZip) avatars.githubusercontent.com: 132 components, 125.8K bitcoin.org: 10 components, 127.2K (80.1K GZip) bitcoin.org: 16 components, 239.0K (89.9K GZip)

No other performance or usability problem detected.

sitespeed.io Analysis for Mobile Devices

The following is a result of an analysis of 5 pages, starting from https://bitcoin.org/. The test was done with Viewport set to 320x444, and User-Agent header set to Mozilla/5.0 (iPad; CPU OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25.

Aggregate Results

This section presents aggregate results across all tested pages. For individual page recommendations, see sections below.

Title / Description	Median Value	Best Value	Worst Value
Images scaled by the browser Never scale images in the browser, that will slow down the rendering.	1.0	0.0	31.0
Cache Time How long time the assets are cached in the browser. Long time is good.	5 minutes	4 weeks	0 seconds
Critical Rendering Path Score Do as little as possible within the HEAD tag so that the browser can start rendering a page as soon as possible (avoid DNS lookups and load CSS/JS files).	55.0	55.0	55.0
Number of CSS images per page Few larger CSS images are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	4.00	2.00	4.00
Number of CSS files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	3.00	3.00	3.00
Document Weight Keep the document at a reasonable size, it will make it possible for the browser to generate the page faster.	9.13 KB	9.08 KB	39.9 KB
Number of DOM elements Too many DOM elements means that the page is complex and will be slower to render	213.0	209.0	1074.0
Number of font files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	1.00	1.00	1.00
Number of images per page Avoid too many images because it will take time for them all to load.	6.00	2.00	133.00
Number of JS files per page Few larger files are better when using HTTP 1.1. For HTTP 2.0 it is better with many small files from few domains.	5.00	5.00	5.00
Number of JS synchronously inside head Loading Javascript synchronously inside of the HEAD tag will slow down your page rendering. Just don't do it!	3.00	3.00	3.00
Max requests per domain Using HTTP 1.1 you want to avoid loading too many assets from one domain	20.00	14.00	132.00
Number Of Domains Many domains means many DNS lookups and that means slower pages.	2.00	2.00	3.00
Redirects Per Page Avoid doing redirects, it will slow down the page!	0.00	0.00	1.00
Number of requests per page Fewer requests are always faster than many requests.	21.0	15.0	147.0
Requests Without Expires Requests shall always have expire headers, so that they can be cached by the browser	5.00	5.00	5.00
Rule Score The sitespeed.io total rule score for all the pages	87	87	79
No other problems found.

Page Statistics

Page URL (http(s)://bitcoin.org…)	Overall Score	Load Time	Requests	Req. w/ Cache	Size
/en/about-us	79	1823 ms	147	138	314.93 KB
/en/alerts	86	1675 ms	15	6	158.53 KB
/id/	87	1820 ms	21	6	270.65 KB
/nl/	87	1844 ms	21	6	270.64 KB
/en/	87	1975 ms	21	6	280.88 KB

Page Rules Scores and Recommendations

Avoid slowing down the critical rendering path

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/en/alerts	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/id/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/nl/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
/en/	55	You have 3 javascripts in the critical path and 3 stylesheets using 0 extra domains.
Showing 6 / 6 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css

Minify JavaScript and CSS

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	70	There are 3 components that can be minified.
/en/alerts	70	There are 3 components that can be minified.
/id/	70	There are 3 components that can be minified.
/nl/	70	There are 3 components that can be minified.
/en/	70	There are 3 components that can be minified.
Showing 3 / 3 relevant components: https://bitcoin.org/js/cookieconsent/cookieconsent.js inline <script> tag #1 inline <script> tag #3

Never scale images in HTML

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	You have 31 images that are scaled more than 100 pixels in the HTML.
Showing 10 / 31 relevant components: https://avatars.githubusercontent.com/u/348922?v=3&size=16 https://avatars.githubusercontent.com/u/6249069?v=3&size=16 https://avatars.githubusercontent.com/u/345092?v=3&size=16 https://avatars.githubusercontent.com/u/649246?v=3&size=16 https://avatars.githubusercontent.com/u/747896?v=3&size=16 https://avatars.githubusercontent.com/u/8403418?v=3&size=16 https://avatars.githubusercontent.com/u/3147216?v=3&size=16 https://avatars.githubusercontent.com/u/2691563?v=3&size=16 https://avatars.githubusercontent.com/u/2559390?v=3&size=16 https://avatars.githubusercontent.com/u/1086125?v=3&size=16

Never load JS synchronously in head

Javascript files should never be loaded synchronously in HEAD, because it will block the rendering of the page.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/en/alerts	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/id/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/nl/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
/en/	70	There are 3 scripts that are not loaded asynchronously in head, that will block the rendering.
Showing 3 / 3 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js

Reduce number of total requests

Avoid to have too many requests on your page. The more requests, the slower the page will be for the end user.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	The page uses 147 requests, that is too many to make the page load fast.
Showing 10 / 147 relevant components: https://bitcoin.org/en/about-us https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/css/font-awesome-4.4.0/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css https://www.google-analytics.com/analytics.js https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js

Have expire headers for static components

By adding HTTP expires headers to your static files, the files will be cached in the end users browser.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	56	There are 4 static components without a future expiration date.
/en/alerts	56	There are 4 static components without a future expiration date.
/id/	56	There are 4 static components without a future expiration date.
/nl/	56	There are 4 static components without a future expiration date.
/en/	56	There are 4 static components without a future expiration date.
Showing 4 / 4 relevant components: https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js

Have expires headers equals or longer than one year

Having really long cache headers are beneficial for caching.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	There are 145 static components without a expire header equal or longer than one year.
/en/alerts	35	There are 13 static components without a expire header equal or longer than one year.
/id/	5	There are 19 static components without a expire header equal or longer than one year.
/nl/	5	There are 19 static components without a expire header equal or longer than one year.
/en/	5	There are 19 static components without a expire header equal or longer than one year.
Showing 10 / 153 relevant components: https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css https://www.google-analytics.com/analytics.js https://bitcoin.org/js/base.js https://bitcoin.org/js/main.js https://bitcoin.org/js/cookieconsent/cookieconsent.js https://bitcoin.org/js/analytics.js https://bitcoin.org/img/icons/menumobile.svg https://bitcoin.org/img/icons/mini_ico_anchor.svg

Do not load css files when the page has few request

When a page has few requests (or actually maybe always if you dont have a massive amount of css), it is better to inline the css, to make the page to start render as early as possible.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/alerts	40	The page have 14 requests and uses 3 css files. It is better to keep the css inline, when you have so few requests.
Showing 3 / 3 relevant components: https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css https://bitcoin.org/bd049070b1552db10cd9ae1a4e14d766.css https://bitcoin.org/js/cookieconsent/light-floating.css

Have a reasonable percentage of textual content compared to the rest of the page

Make sure the amount of HTML elements are too many compared to text content.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	54	The amount of content percentage: 26.64%.
/id/	78	The amount of content percentage: 39.49%.
/nl/	78	The amount of content percentage: 39.24%.
/en/	78	The amount of content percentage: 38.65%.

Use a Content Delivery Network (CDN)

User proximity to web servers impacts response times. Deploying content across multiple geographically dispersed servers helps users perceive that pages are loading faster.

Page URL (http(s)://bitcoin.org…)	Score	Message
/en/about-us	0	There are 143 static components that are not on CDN.
/en/alerts	0	There are 11 static components that are not on CDN.
/id/	0	There are 17 static components that are not on CDN.
/nl/	0	There are 17 static components that are not on CDN.
/en/	0	There are 17 static components that are not on CDN.
Showing 4 / 4 relevant components: bitcoin.org: 11 components, 127.5K (80.5K GZip) avatars.githubusercontent.com: 132 components, 134.5K bitcoin.org: 11 components, 127.7K (80.6K GZip) bitcoin.org: 17 components, 239.5K (90.4K GZip)

No other performance or usability problem detected.

Email Privacy Check

Email harvesting is a technique of building a mailing list by searching for email addresses that are publicly available on the Internet. Email Privacy Check simulates a sophisticated email harvesting software and finds emails written in common formats in the source code of web pages. If this check reports a valid email, it should be removed from (or at least obfuscated in the code of) the target website in order to prevent receiving spam to this address – unless this is an intended behavior, e.g. it is a spam trap.

Below are the results of an email address search on https://bitcoin.org/ and linked pages within the same domain.

Email address admin@foo.com found in the code of following pages:
- https://bitcoin.org/en/full-node

Email address privacy@bitcoin.org found in the code of following pages:
- https://bitcoin.org/en/privacy

Email address laanwj@gmail.com found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address gavinandresen@gmail.com found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address jgarzik@pobox.com found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address greg@xiph.org found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address pieter.wuille@gmail.com found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address dev@jonasschnelli.ch found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

Email address bitcoin-security@lists.sourceforge.net found in the code of following pages:
- https://bitcoin.org/id/pengembangan
- https://bitcoin.org/da/udvikling
- https://bitcoin.org/de/entwicklung
- https://bitcoin.org/es/desarrollo
- https://bitcoin.org/fr/developpement
- https://bitcoin.org/it/sviluppo
- https://bitcoin.org/hu/fejlesztes
- https://bitcoin.org/nl/ontwikkeling
- https://bitcoin.org/pl/rozwoj
- https://bitcoin.org/pt_BR/desenvolvimento
- … 14 more pages …

SEO Check

Search Engine Optimization (SEO) techniques cover all kinds of techniques that were developed to help web sites to get better rankings in search engines. The techniques are commonly divided to two major categories – on-page and off-page. SEO Check focuses on an analysis of the code of the web pages, i.e. it is focused on some of the on-page factors, in order to reveal problems that might affect the page's search engine ranking performance and user experience. A large set of rules respecting the industry best practices is used to suggest possible improvements. SEO Check covers only some of the on-page factors, many other factors are untested.

Page https://bitcoin.org/en/

Page Content Analysis

The title length is 31 characters, which is outside the optimal range of 40 to 60 characters.
- Bitcoin - Open source P2P money
The page contains 25 links without the title attribute. Consider adding it, as it improves both SEO and the site's accessibility
- Anchor: Bahasa Indonesia
- >Href: /id/
- Anchor: Dansk
- >Href: /da/
- Anchor: Deutsch
- >Href: /de/
- Anchor: English
- >Href: /en/
- Anchor: Español
- >Href: /es/
- … 40 more lines …
The page contains 2 links with underscores, which are not recognized as word separators by some search engines. Consider replacing underscores with dashes, for example change 'foo_bar' to 'foo-bar'.
- /pt_BR/
- /zh_CN/

Metadata Analysis

The page does not contain a favicon. Consider adding one.
The page does not contain a Google Publisher (Authorship) link. Consider adding one, as this can improve search engine rankings, and also increases the site's overall authority.
The page does not contain a meta charset settings. This can cause some characters to display incorrectly to some visitors.
The page does not contain any meta keywords. It is recommended to have between 5 and 20 meta keywords defined.

Analysis of JavaScript Usage

3 of 3 linked scripts on the page are misplaced and are not loaded asynchronously. Synchronously loaded scripts should be placed just before the closing body tag.
- /js/base.js
- /js/main.js
- /js/cookieconsent/cookieconsent.js

Analysis of Cascading Style Sheets Usage

No problems found.

Page https://bitcoin.org/id/

Page Content Analysis

The title length is 33 characters, which is outside the optimal range of 40 to 60 characters.
- Bitcoin - Uang P2P sumber terbuka
The page contains 25 links without the title attribute. Consider adding it, as it improves both SEO and the site's accessibility
- Anchor: Bahasa Indonesia
- >Href: /id/
- Anchor: Dansk
- >Href: /da/
- Anchor: Deutsch
- >Href: /de/
- Anchor: English
- >Href: /en/
- Anchor: Español
- >Href: /es/
- … 40 more lines …
The page contains 2 links with underscores, which are not recognized as word separators by some search engines. Consider replacing underscores with dashes, for example change 'foo_bar' to 'foo-bar'.
- /pt_BR/
- /zh_CN/

Metadata Analysis

The page does not contain a favicon. Consider adding one.
The page does not contain a Google Publisher (Authorship) link. Consider adding one, as this can improve search engine rankings, and also increases the site's overall authority.
The page does not contain a meta charset settings. This can cause some characters to display incorrectly to some visitors.
The page does not contain any meta keywords. It is recommended to have between 5 and 20 meta keywords defined.

Analysis of JavaScript Usage

3 of 3 linked scripts on the page are misplaced and are not loaded asynchronously. Synchronously loaded scripts should be placed just before the closing body tag.
- /js/base.js
- /js/main.js
- /js/cookieconsent/cookieconsent.js

Analysis of Cascading Style Sheets Usage

No problems found.

Page https://bitcoin.org/da/

Page Content Analysis

The title length is 38 characters, which is outside the optimal range of 40 to 60 characters.
- Bitcoin – P2P-penge med åben kildekode
The page contains 25 links without the title attribute. Consider adding it, as it improves both SEO and the site's accessibility
- Anchor: Bahasa Indonesia
- >Href: /id/
- Anchor: Dansk
- >Href: /da/
- Anchor: Deutsch
- >Href: /de/
- Anchor: English
- >Href: /en/
- Anchor: Español
- >Href: /es/
- … 40 more lines …
The page contains 2 links with underscores, which are not recognized as word separators by some search engines. Consider replacing underscores with dashes, for example change 'foo_bar' to 'foo-bar'.
- /pt_BR/
- /zh_CN/

Metadata Analysis

The page does not contain a favicon. Consider adding one.
The page does not contain a Google Publisher (Authorship) link. Consider adding one, as this can improve search engine rankings, and also increases the site's overall authority.
The page does not contain a meta charset settings. This can cause some characters to display incorrectly to some visitors.
The page does not contain any meta keywords. It is recommended to have between 5 and 20 meta keywords defined.

Analysis of JavaScript Usage

3 of 3 linked scripts on the page are misplaced and are not loaded asynchronously. Synchronously loaded scripts should be placed just before the closing body tag.
- /js/base.js
- /js/main.js
- /js/cookieconsent/cookieconsent.js

Analysis of Cascading Style Sheets Usage

No problems found.

Page https://bitcoin.org/de/

Page Content Analysis

The title length is 30 characters, which is outside the optimal range of 40 to 60 characters.
- Bitcoin - Open Source P2P Geld
The page contains 25 links without the title attribute. Consider adding it, as it improves both SEO and the site's accessibility
- Anchor: Bahasa Indonesia
- >Href: /id/
- Anchor: Dansk
- >Href: /da/
- Anchor: Deutsch
- >Href: /de/
- Anchor: English
- >Href: /en/
- Anchor: Español
- >Href: /es/
- … 40 more lines …
The page contains 2 links with underscores, which are not recognized as word separators by some search engines. Consider replacing underscores with dashes, for example change 'foo_bar' to 'foo-bar'.
- /pt_BR/
- /zh_CN/

Metadata Analysis

The page does not contain a favicon. Consider adding one.
The page does not contain a Google Publisher (Authorship) link. Consider adding one, as this can improve search engine rankings, and also increases the site's overall authority.
The page does not contain a meta charset settings. This can cause some characters to display incorrectly to some visitors.
The page does not contain any meta keywords. It is recommended to have between 5 and 20 meta keywords defined.

Analysis of JavaScript Usage

3 of 3 linked scripts on the page are misplaced and are not loaded asynchronously. Synchronously loaded scripts should be placed just before the closing body tag.
- /js/base.js
- /js/main.js
- /js/cookieconsent/cookieconsent.js

Analysis of Cascading Style Sheets Usage

No problems found.

Page https://bitcoin.org/es/

Page Content Analysis

The title length is 38 characters, which is outside the optimal range of 40 to 60 characters.
- Bitcoin - Dinero P2P de código abierto
The page contains 25 links without the title attribute. Consider adding it, as it improves both SEO and the site's accessibility
- Anchor: Bahasa Indonesia
- >Href: /id/
- Anchor: Dansk
- >Href: /da/
- Anchor: Deutsch
- >Href: /de/
- Anchor: English
- >Href: /en/
- Anchor: Español
- >Href: /es/
- … 40 more lines …
The page contains 2 links with underscores, which are not recognized as word separators by some search engines. Consider replacing underscores with dashes, for example change 'foo_bar' to 'foo-bar'.
- /pt_BR/
- /zh_CN/

Metadata Analysis

The page does not contain a favicon. Consider adding one.
The page does not contain a Google Publisher (Authorship) link. Consider adding one, as this can improve search engine rankings, and also increases the site's overall authority.
The page does not contain a meta charset settings. This can cause some characters to display incorrectly to some visitors.
The page does not contain any meta keywords. It is recommended to have between 5 and 20 meta keywords defined.

Analysis of JavaScript Usage

3 of 3 linked scripts on the page are misplaced and are not loaded asynchronously. Synchronously loaded scripts should be placed just before the closing body tag.
- /js/base.js
- /js/main.js
- /js/cookieconsent/cookieconsent.js

Analysis of Cascading Style Sheets Usage

No problems found.

SERP Rank Check

Search Engine Results Page (SERP) rank is an absolute position of a web site that is returned by a specific search engine for a given keyword. Having the best possible rank of 1 means that the web site appears at the top of the first result page for the given keyword and that it receives the most visitors from searches for that keyword. For each keyword, SERP Check obtains the SERP rank of the target web site and other given domains.

Keyword 'bitcoin' on google.com

Primary Domain: bitcoin.org

Competitor Domains: localbitcoins.com, bitcoinclassic.com

Ranks of Selected Domains Records

1	Bitcoin - Open source P2P money https://bitcoin.org/ Bitcoin is an innovative payment network and a new kind of money. Find all you need to know and get started with Bitcoin on bitcoin.org.

20	LocalBitcoins.com: Fastest and easiest way to buy and sell ... https://localbitcoins.com/ A directory of local buyers and sellers of Bitcoins. Lists the traders closest to your current location.

61	Bitcoin Classic https://bitcoinclassic.com/ We are hard forking bitcoin to a 2 MB blocksize limit. Please join us. The data shows consensus amongst miners for an immediate 2 MB increase, and demand ...

Top 10 Records

Rank	Target URL	Keyword found in
Rank	Target URL	Title	Desc	Url
1	https://bitcoin.org/	YES	YES	YES
2	https://www.bitcoin.com/	YES	YES	YES
3	https://en.wikipedia.org/wiki/Bitcoin	YES	YES	YES
4	https://www.weusecoins.com/	YES	YES	NO
5	http://www.coindesk.com/price/	YES	YES	NO
6	http://www.coindesk.com/information/what-is-bitcoin/	YES	YES	YES
7	http://www.forbes.com/sites/kashmirhill/2013/05/09/25-things-i-learned-about-bitcoin-from-living-on-it-for-a-week/	YES	YES	YES
8	http://www.wired.com/2011/11/mf_bitcoin/	YES	YES	YES
9	http://www.newyorker.com/tech/elements/the-bitcoin-boom	YES	YES	YES
10	http://money.cnn.com/infographic/technology/what-is-bitcoin/	YES	YES	YES

Keyword 'cryptocurrency' on google.com

Primary Domain: bitcoin.org

Competitor Domains: localbitcoins.com, bitcoinclassic.com

Ranks of Selected Domains Records

None of the given domains found within top 100 results for the specified keyword.

Top 10 Records

Rank	Target URL	Keyword found in
Rank	Target URL	Title	Desc	Url
1	https://en.wikipedia.org/wiki/Cryptocurrency	YES	YES	YES
2	https://coinmarketcap.com/	NO	YES	NO
3	http://www.investopedia.com/terms/c/cryptocurrency.asp	YES	YES	YES
4	http://www.bankrate.com/finance/investing/cryptocurrency-alternatives-to-bitcoin-1.aspx	YES	NO	YES
5	https://www.cryptocoinsnews.com/cryptocurrency/	YES	YES	YES
6	https://www.reddit.com/r/CryptoCurrency/	NO	YES	YES
7	http://www.engadget.com/2015/01/21/cryptocurrency-explainer/	YES	YES	YES
8	http://www.newyorker.com/magazine/2011/10/10/the-crypto-currency	NO	NO	NO
9	https://www.technologyreview.com/s/425142/cryptocurrency/	YES	YES	YES
10	http://www.nature.com/news/the-future-of-cryptocurrencies-bitcoin-and-beyond-1.18447	NO	YES	NO

Keyword 'payment network' on google.com

Primary Domain: bitcoin.org

Competitor Domains: localbitcoins.com, bitcoinclassic.com

Ranks of Selected Domains Records

52	Bitcoin - Open source P2P money https://bitcoin.org/ Bitcoin is an innovative payment network and a new kind of money. Find all you need to know and get started with Bitcoin on bitcoin.org.

Top 10 Records

Rank	Target URL	Keyword found in
Rank	Target URL	Title	Desc	Url
1	https://ipn.intuit.com/	YES	YES	NO
2	https://www.paymentservicenetwork.com/	NO	NO	NO
3	https://www.paymentservicenetwork.com/Login.aspx	NO	NO	NO
4	https://en.wikipedia.org/wiki/Payment_system	NO	NO	NO
5	https://www.simple.com/blog/payment-networks-and-methods	YES	YES	YES
6	https://www.auctionpaymentnetwork.com/	YES	NO	YES
7	http://alliedpayment.com/	YES	NO	NO
8	http://paymentsandcardsnetwork.com/	NO	NO	NO
9	https://www.dwolla.com/	NO	YES	NO
10	https://www.cardpaymentoptions.com/alternatives/intuit-payment-network/	YES	YES	YES

Keyword 'electronic money' on google.com

Primary Domain: bitcoin.org

Competitor Domains: localbitcoins.com, bitcoinclassic.com

Ranks of Selected Domains Records

None of the given domains found within top 100 results for the specified keyword.

Top 10 Records

Rank	Target URL	Keyword found in
Rank	Target URL	Title	Desc	Url
1	https://en.wikipedia.org/wiki/Electronic_money	YES	YES	YES
2	http://www.investopedia.com/terms/e/electronic-money.asp	YES	YES	YES
3	http://www.cgap.org/news/bitcoin-vs-electronic-money-digital-different	YES	YES	YES
4	http://www.cgap.org/publications/bitcoin-vs-electronic-money	YES	YES	YES
5	http://ec.europa.eu/finance/payments/emoney/index_en.htm	NO	YES	NO
6	https://www.ecb.europa.eu/stats/money/aggregates/emon/html/index.en.html	YES	YES	NO
7	http://www.exeter.ac.uk/~RDavies/arian/emoney	YES	YES	NO
8	http://www.e-ma.org/	YES	YES	NO
9	http://blogs.worldbank.org/psd/e-money-mobile-money-mobile-banking-what-s-the-difference	NO	YES	NO
10	http://www.businessdictionary.com/definition/electronic-money.html	YES	YES	YES

Site Popularity Check

There are many different metrics that can be used to evaluate a power, or a popularity, of a web site. Site Popularity Check collects values from several reputable sources of these metrics in order to provide a complex picture of the target web site's popularity. Some of the metrics reflect a number of visitors of a web site, which is something that does not change very quickly for most webs. Other metrics reflect a current level of interest in the web site on social networks. Some more complex systems that consider many different factors and combine them into a simplified rank value are also included.

The following values were obtained for domain bitcoin.org.

Global Ranks

Alexa Global Rank	12,159
Compete Rank	8,351
Google PageRank	7
Moz Domain Authority	81.17
Moz Rank	6.91
WebsiteOutlook Value	$202,950.00

Backlinks Statistics

Alexa Backlinks	5,088
Bing Backlinks	233,000
Google Backlinks	648
Moz Backlinks	169,542

Social Networks Stats

Buffer Shares	57
Delicious Shares	1,366
Facebook Likes	3,498
Facebook Shares	3,961
LinkedIn Shares	295
StumbleUpon Shares	1
Pintereset Shares	4
Reddit Score	17

Response Time Check

Response Time Check simply evaluates access times to the target machine from different world-wide locations. It performs two types of checks – ICMP ECHO request and HTTP HEAD request on port 80/TCP. Each check is performed 3 times from each location. The results can be interpreted as a minimal service access times that are to be expected for its users from different locations.

IP Address 208.64.123.130 (bitcoin.org)

ICMP Echo Requests

Client Location	Req. #1	Req. #2	Req. #3	Avg. Time
Prague, Czech Republic, Europe	162 ms	162 ms	162 ms	162 ms
Beauharnois, Canada, North America	72 ms	72 ms	72 ms	72 ms
Amsterdam #1, Netherlands, Europe	149 ms	149 ms	145 ms	148 ms
Amsterdam #2, Netherlands, Europe	145 ms	145 ms	146 ms	145 ms
Roubaix, France, Europe	144 ms	143 ms	145 ms	144 ms
Texas, USA, North America	71 ms	68 ms	68 ms	69 ms
Strasbourg, France, Europe	150 ms	151 ms	150 ms	150 ms
Gravelines, France, Europe	148 ms	149 ms	149 ms	149 ms

HTTP HEAD Requests

Client Location	Req. #1	Req. #2	Req. #3	Avg. Time
Prague, Czech Republic, Europe	323 ms	323 ms	323 ms	323 ms
Beauharnois, Canada, North America	143 ms	143 ms	143 ms	143 ms
Amsterdam #1, Netherlands, Europe	286 ms	289 ms	289 ms	288 ms
Amsterdam #2, Netherlands, Europe	289 ms	283 ms	288 ms	287 ms
Roubaix, France, Europe	286 ms	286 ms	286 ms	286 ms
Texas, USA, North America	135 ms	135 ms	135 ms	135 ms
Strasbourg, France, Europe	299 ms	299 ms	299 ms	299 ms
Gravelines, France, Europe	296 ms	296 ms	296 ms	296 ms

Geo Location Check

Geo Location check tries to obtain location information from an IP address. The quality of the IP address to location mapping data differs for different IP networks. For some IP addresses, the provided latitude and longitude is good enough to identify a part of the city the target server runs in. For other addresses, however, it might only be possibly to identify the country where the server is placed.

Besides the geographic location, this check provides an autonomous system number (ASN) and border gateway protocol (BGP) information, which are directly related with routing and connections of networks in the Internet. This information might help with finding an Internet Service Provider (ISP) of the given IP address. In many cases, however, smaller ISPs do not own their own autonomous system and belong under an autonomous system of a bigger provider.

IP Address 208.64.123.130

Location on Map

Basic Location
Latitude, Longitude:	39.746, -75.5466
City:	Wilmington
Country:	United States
Continent:	North America
Timezone:	UTC-04:00

BGP and ASN Information
BGP Origin ASN:	32421
BGP Prefix:	208.64.123.0/24
ASN Name / ISP:	BLCC - Black Lotus Communications,US
ASN Country Code:	US
ASN Registry:	arin
ASN Allocation Date:	2004-04-30

Technology Stack Check

Technology Stack Check is based on WhatWeb scanner, a tool that utilizes over 1500 plugins to recognize various web technologies such as content management systems, web server software, JavaScript libraries, blogging platforms, web framework modules, etc. The result of the check provides a list of web site related information and detected technologies.

Target URL https://bitcoin.org/

HTTP Status: 302 (Redirect)

Plugin Name and Description	Certainty	Value Type	Value
Country Shows the country the IPv4 address belongs to. This uses the GeoIP IP2Country database from http://software77.net/geo-ip/.	100 %	Module	US
	100 %	String	UNITED STATES
HTTPServer HTTP server header string. This plugin also attempts to identify the operating system from the server header.	100 %	OS	Ubuntu Linux
	100 %	String	nginx/1.4.6 (Ubuntu)
IP IP address of the target, if available.	100 %	String	208.64.123.130
nginx Nginx (Engine-X) is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server. - Homepage: http://nginx.net/	100 %	Version	1.4.6
RedirectLocation HTTP Server string location. used with http-status 301 and 302	100 %	String	https://bitcoin.org/en/
Title The HTML page title	100 %	String	302 Found
UncommonHeaders Uncommon HTTP server headers. The blacklist includes all the standard headers and many non standard but common ones. Interesting but fairly common headers should have their own plugins, eg. x-powered-by, server and x-aspnet-version. Info about headers can be found at www.http-stats.com	100 %	String	strict-transport-security,content-security-policy

Target URL https://bitcoin.org/en/

HTTP Status: 200 (OK)

Plugin Name and Description	Certainty	Value Type	Value
Country Shows the country the IPv4 address belongs to. This uses the GeoIP IP2Country database from http://software77.net/geo-ip/.	100 %	Module	US
	100 %	String	UNITED STATES
HTML5 HTML version 5, detected by the doctype declaration	100 %	No values detected.
HTTPServer HTTP server header string. This plugin also attempts to identify the operating system from the server header.	100 %	OS	Ubuntu Linux
	100 %	String	nginx/1.4.6 (Ubuntu)
IP IP address of the target, if available.	100 %	String	208.64.123.130
nginx Nginx (Engine-X) is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server. - Homepage: http://nginx.net/	100 %	Version	1.4.6
Script This plugin detects instances of script HTML elements and returns the script language/type.	100 %	String	text/javascript
Title The HTML page title	100 %	String	Bitcoin - Open source P2P money
UncommonHeaders Uncommon HTTP server headers. The blacklist includes all the standard headers and many non standard but common ones. Interesting but fairly common headers should have their own plugins, eg. x-powered-by, server and x-aspnet-version. Info about headers can be found at www.http-stats.com	100 %	String	strict-transport-security,content-security-policy

WHOIS Check

WHOIS is an old Internet protocol that is used to provide information about Internet resources, such as domains and IP address blocks.

The most common use of WHOIS tools is to find information about domain names. The WHOIS database domain record usually contains a full name of the owner, a person or a company, their physical address, telephone contact, and administrative and technical email contact. The record also contains information about the domain status, its date of registration, the date of last record change and the date of the domain expiration. Although the WHOIS protocol is widely used, there is no standard for the format of its records and hence every WHOIS server can give you information in different format. The quality and the accuracy of the information provided thus depends on each WHOIS server provider.

The original purpose of WHOIS was to provide an open directory of domain owners but this have changed since the spam and other forms of abuse started to be unbearable. Today, subjects that own Internet resources commonly use various proxy services in order to protect their personal information from being publicly available. A domain proxy registration service company registers domains for its clients under its own name, giving only its own information to the public and protecting its clients' identities and personal information.

Domain bitcoin.org

Domain
Domain:	bitcoin.org
Status:	clientTransferProhibited
Created:	2008-08-18 13:19:55 UTC (7 years ago)
Changed:	2016-03-07 06:37:09 UTC (one month ago)
Expires:	2021-08-18 13:19:55 UTC (5 years from now)

Registrar
Name:	eNom, Inc.

Registrant Contact
Organization:	WhoisGuard, Inc.
Name:	WhoisGuard Protected
Email:	e0a93ccd1b824a6c8fcc025e8e9d2dfa.protect@whoisguard.com
Phone:	+507.8365503
Fax:	+51.17057182
City:	Panama
ZIP Code:	00000
Address:	P.O. Box 0823-03411
State:	Panama
Country Code:	PA
ID:	1218c483a90fa491

Admin Contact
Organization:	WhoisGuard, Inc.
Name:	WhoisGuard Protected
Email:	e0a93ccd1b824a6c8fcc025e8e9d2dfa.protect@whoisguard.com
Phone:	+507.8365503
Fax:	+51.17057182
City:	Panama
ZIP Code:	00000
Address:	P.O. Box 0823-03411
State:	Panama
Country Code:	PA
ID:	1218c483a90fa491

Technical Contact
Organization:	WhoisGuard, Inc.
Name:	WhoisGuard Protected
Email:	e0a93ccd1b824a6c8fcc025e8e9d2dfa.protect@whoisguard.com
Phone:	+507.8365503
Fax:	+51.17057182
City:	Panama
ZIP Code:	00000
Address:	P.O. Box 0823-03411
State:	Panama
Country Code:	PA
ID:	1218c483a90fa491

Nameservers

Name:

dns1.registrar-servers.com

Name:

dns2.registrar-servers.com

Name:

dns3.registrar-servers.com

Name:

dns4.registrar-servers.com

Name:

dns5.registrar-servers.com

Address 208.64.123.130

Domain
Domain:	208.64.120.0 - 208.64.127.255
Status:	registered
Created:	2005-12-22 00:00:00 UTC (10 years ago)
Changed:	2012-03-02 00:00:00 UTC (4 years ago)

Registrant Contact
Organization:	Black Lotus Communications
City:	Wilmington
ZIP Code:	19801
Address:	1000 N. West St., Suite 1200
Country:	US
Country Code:	US
Created:	2004-04-22 00:00:00 UTC (12 years ago)
Changed:	2014-12-30 00:00:00 UTC (one year ago)

Admin Contact
Name:	Network Operations Center
Email:	noc@blacklotus.net
Phone:	+1-757-304-0668

Technical Contact
Name:	Network Operations Center
Email:	noc@blacklotus.net
Phone:	+1-757-304-0668

Document Purpose

Table of Contents

Report Alert Summary

Blacklist Check

IP Address 208.64.123.130

Listings on High Volume Reliable Blacklists

Listings on Reliable Blacklists

Listings on Less Reliable Blacklists

IP Address 165.254.167.50

Listings on High Volume Reliable Blacklists

Listings on Reliable Blacklists

Listings on Less Reliable Blacklists

IP Address 74.201.155.220

Listings on High Volume Reliable Blacklists

Listings on Reliable Blacklists

Listings on Less Reliable Blacklists

Malware and Reputation Check

Google SafeBrowsing Status

PhishTank Database

VirusTotal Scan

SSL/TLS Check

Target 208.64.123.130:443 (bitcoin.org)

Problems Summary

Certificate Chain

Certificate Paths

Protocol Details

Supported Protocols and Cipher Suites

TLS 1.2

TLS 1.1

TLS 1.0

Mail Server Health Check

SPF Record Check

Mail Servers by Hostname

Mail Server mx.zohomail.com

Mail Server mx2.zohomail.com

Mail Servers by IP Address

Mail Server 165.254.167.50 (See this IP's blacklist check)

Mail Server 74.201.155.220 (See this IP's blacklist check)

DNS Zone Health Check

Basic Module

Address Module

Connectivity Module

Consistency Module

DNSSEC Module

Delegation Module

Nameserver Module

Syntax Module

Zone Module

HTML Standards Check

Broken Link Check

Website Speed and Usability Check

Google PageSpeed Insights Analysis for Desktop Devices

Page Statistics

Page Rules Scores and Recommendations

Avoid landing page redirects (SPEED)

Enable compression (SPEED)

Leverage browser caching (SPEED)

Reduce server response time (SPEED)

Minify CSS (SPEED)

Minify HTML (SPEED)

Minify JavaScript (SPEED)

Eliminate render-blocking JavaScript and CSS in above-the-fold content (SPEED)

Optimize images (SPEED)

Prioritize visible content (SPEED)

Google PageSpeed Insights Analysis for Mobile Devices

Page Statistics

Page Rules Scores and Recommendations

Avoid app install interstitials that hide content (USABILITY)

Avoid landing page redirects (SPEED)

Avoid plugins (USABILITY)

Configure the viewport (USABILITY)

Enable compression (SPEED)

Leverage browser caching (SPEED)

Reduce server response time (SPEED)

Minify CSS (SPEED)

Minify HTML (SPEED)

Minify JavaScript (SPEED)

Eliminate render-blocking JavaScript and CSS in above-the-fold content (SPEED)

Optimize images (SPEED)

Prioritize visible content (SPEED)