bitcoin.org

bitcoin.org is SSL secured

Free website and domain report on bitcoin.org

Last Updated: 15th February, 2023 Update Now
Overview

Snoop Summary for bitcoin.org

This is a free and comprehensive report about bitcoin.org. The domain bitcoin.org is currently hosted on a server located in United States with the IP address 104.22.69.176, where the local currency is USD and English is the local language. Our records indicate that bitcoin.org is privately registered by Privacy service provided by Withheld for Privacy ehf. Bitcoin.org is expected to earn an estimated $2,103 USD per day from advertising revenue. The sale of bitcoin.org would possibly be worth $1,534,895 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Bitcoin.org receives an estimated 335,077 unique visitors every day - an insane amount of traffic! This report was last updated 15th February, 2023.

About bitcoin.org

Site Preview: bitcoin.org bitcoin.org
Title: Bitcoin - Open source P2P money
Description: 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.
Keywords and Tags: hardware, popular, software
Related Terms: bitcoin btc, bitcoin difficulty, bitcoin transaction accelerator, bitcoin wallet login, buy bitcoin by bank wire, buy bitcoin by credit card, buy bitcoin by paypal, sell bitcoin by bank wire, sell bitcoin by credit card, sell bitcoin by paypal
Fav Icon:
Age: Over 16 years old
Domain Created: 18th August, 2008
Domain Updated: 23rd September, 2021
Domain Expires: 18th August, 2029
Review

Snoop Score

4/5 (Excellent!)

Valuation

$1,534,895 USD
Note: All valuation figures are estimates.

Popularity

Very High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 5,468
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 83
Moz Page Authority: 71

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 335,077
Monthly Visitors: 10,198,688
Yearly Visitors: 122,303,105
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $2,103 USD
Monthly Revenue: $63,996 USD
Yearly Revenue: $767,443 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: bitcoin.org 11
Domain Name: bitcoin 7
Extension (TLD): org 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.07 seconds
Load Time Comparison: Faster than 73% of sites

PageSpeed Insights

Avg. (All Categories) 78
Performance 90
Accessibility 82
Best Practices 80
SEO 91
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://bitcoin.org/en/
Updated: 24th October, 2021

1.32 seconds
First Contentful Paint (FCP)
85%
9%
6%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
90

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for bitcoin.org. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.021
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://bitcoin.org/
http/1.1
0
124.48800000129
337
0
301
text/html
https://bitcoin.org/
http/1.1
125.03799999831
263.61099997303
569
0
302
text/html
https://bitcoin.org/en/
h2
264.23500000965
410.8239999623
5846
24061
200
text/html
Document
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
h2
423.21599996649
460.03399998881
6664
26711
200
text/css
Stylesheet
https://bitcoin.org/css/main.css?1630339663
h2
423.33600000711
485.57700001402
22610
122693
200
text/css
Stylesheet
https://bitcoin.org/js/base.js?1630339663
h2
423.49399998784
458.33399996627
4621
12070
200
application/javascript
Script
https://bitcoin.org/js/main.js?1630339663
h2
423.75299998093
493.12100000679
8385
28438
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
h2
424.09400001634
492.63100000098
33777
95931
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery-ui.min.js
h2
424.31400000351
495.52399996901
64738
240022
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
h2
424.60099997697
479.64199999114
5406
13995
200
application/javascript
Script
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
h2
424.85199996736
448.48399999319
3805
9687
200
application/javascript
Script
https://bitcoin.org/img/icons/ico_close.svg?1630339663
h2
499.45999996271
521.52899996145
1191
939
200
image/svg+xml
Image
https://bitcoin.org/img/icons/logotop.svg?1630339663
h2
515.76899999054
567.55099998554
3519
6259
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
h2
542.22699999809
575.76599996537
1771
2824
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_business.svg?1630339663
h2
542.38699999405
569.22399997711
1740
3189
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
h2
542.5089999917
602.13899996597
2217
4090
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663
h2
542.6279999665
606.18900001282
1405
1591
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_instant.svg?1630339663
h2
542.74299996905
565.7019999926
1360
1780
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_worldwide.svg?1630339663
h2
543.05199999362
567.11299996823
3817
6893
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_lowfee.svg?1630339663
h2
543.21299999719
565.33399998443
2643
4691
200
image/svg+xml
Image
https://bitcoin.org/img/home/bitcoin-img.svg?1630339663
h2
543.35599998012
566.30800000858
4106
11659
200
image/svg+xml
Image
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
h2
543.46600000281
566.63499999559
6427
12401
200
image/svg+xml
Image
https://bitcoin.org/js/analytics.js
h2
543.67499996442
568.06399999186
968
436
200
application/javascript
Script
https://bitcoin.org/img/icons/ico_angle.svg?1528322191
h2
546.37399996864
566.00200000685
1164
953
200
image/svg+xml
Image
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
h2
547.20199998701
672.24699998042
22820
22216
200
application/octet-stream
Font
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
h2
547.43599996436
650.93800000614
22632
22028
200
application/octet-stream
Font
https://bitcoin.org/getip.txt
h2
558.84899996454
663.58300001593
312
0
200
text/plain
XHR
https://bitcoin.org/img/icons/play-btn.svg?1528322191
h2
567.86299997475
596.93299996434
1083
752
200
image/svg+xml
Image
https://bitcoin.org/img/hero/overview-tablet.svg?1528322191
h2
568.00999998813
590.64499998931
2339
8580
200
image/svg+xml
Image
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
h2
569.0969999996
593.58300000895
21435
20820
200
application/octet-stream
Font
https://bitcoin.org/img/hero/footer-bg.svg?1528322191
h2
578.54999997653
601.29999998026
1521
4903
200
image/svg+xml
Image
https://bitcoin.org/img/icons/netstatus_normal.svg?1528322191
h2
579.76599998074
603.03299996303
903
256
200
image/svg+xml
Image
https://www.google-analytics.com/analytics.js
h2
656.7170000053
662.31799998786
20477
49932
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j94&a=215895913&t=pageview&_s=1&dl=https%3A%2F%2Fbitcoin.org%2Fen%2F&ul=en-us&de=UTF-8&dt=Bitcoin%20-%20Open%20source%20P2P%20money&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=9220212&gjid=1317044357&cid=50881024.1635041475&tid=UA-170755108-1&_gid=994240636.1635041475&_r=1&_slc=1&z=1341236035
h2
710.23699996294
713.77299999585
575
2
200
text/plain
XHR
https://bitcoin.org/js/cookieconsent/light-floating.css
h2
713.17100001033
742.06099996809
1567
3246
200
text/css
Stylesheet
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
442.549
7.031
528.361
15.928
544.575
29.259
573.846
8.838
586.482
19.747
606.562
5.984
621.851
5.489
647.062
5.001
676.021
8.286
691.713
8.99
705.361
9.443
716.075
23.598
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images
Images can slow down the page's load time. Bitcoin.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Bitcoin.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Bitcoin.org should consider minifying CSS files.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Bitcoin.org should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/js/main.js?1630339663
8385
2381
https://bitcoin.org/js/base.js?1630339663
4621
2232
Reduce unused CSS — Potential savings of 20 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Bitcoin.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/css/main.css?1630339663
22610
20649
Reduce unused JavaScript — Potential savings of 77 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
58495
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
20654
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 150 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://bitcoin.org/en/
147.577
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Bitcoin.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 278 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
22820
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
22632
https://bitcoin.org/css/main.css?1630339663
22610
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
21435
https://www.google-analytics.com/analytics.js
20477
https://bitcoin.org/js/main.js?1630339663
8385
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
6664
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
6427
Avoids an excessive DOM size — 420 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
420
Maximum DOM Depth
14
Maximum Child Elements
28
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Bitcoin.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://bitcoin.org/en/
91.16
5.983
2.411
Unattributable
82.125
3.292
0.195
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
83.178
Script Evaluation
66.476
Style & Layout
50.325
Parse HTML & CSS
23.373
Rendering
21.627
Script Parsing & Compilation
10.55
Keep request counts low and transfer sizes small — 35 requests • 278 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
35
284750
Script
8
142177
Font
3
66887
Image
16
37206
Stylesheet
3
30841
Document
1
5846
Other
4
1793
Media
0
0
Third-party
2
21052
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21052
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0098244383558832
0.0057179270854347
0.0051981155322133
0.0001106520593292
9.8718994107426E-5
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 1.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 690 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Bitcoin.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
6664
70
https://bitcoin.org/css/main.css?1630339663
22610
230
https://bitcoin.org/js/base.js?1630339663
4621
150
https://bitcoin.org/js/main.js?1630339663
8385
190
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
270
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
310
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
5406
70
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
3805
70
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Bitcoin.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://bitcoin.org/
190
https://bitcoin.org/
150
https://bitcoin.org/en/
0

Diagnostics

Serve static assets with an efficient cache policy — 30 resources found
Bitcoin.org can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20477
https://bitcoin.org/js/jquery/jquery-ui.min.js
14400000
64738
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
14400000
33777
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
14400000
22820
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
14400000
22632
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
14400000
21435
https://bitcoin.org/js/main.js?1630339663
14400000
8385
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
14400000
5406
https://bitcoin.org/js/base.js?1630339663
14400000
4621
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
14400000
3805
https://bitcoin.org/js/analytics.js
14400000
968
https://bitcoin.org/css/main.css?1630339663
2592000000
22610
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
2592000000
6664
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
2592000000
6427
https://bitcoin.org/img/home/bitcoin-img.svg?1630339663
2592000000
4106
https://bitcoin.org/img/icons/main_ico_worldwide.svg?1630339663
2592000000
3817
https://bitcoin.org/img/icons/logotop.svg?1630339663
2592000000
3519
https://bitcoin.org/img/icons/main_ico_lowfee.svg?1630339663
2592000000
2643
https://bitcoin.org/img/hero/overview-tablet.svg?1528322191
2592000000
2339
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
2592000000
2217
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
2592000000
1771
https://bitcoin.org/img/icons/ico_business.svg?1630339663
2592000000
1740
https://bitcoin.org/js/cookieconsent/light-floating.css
2592000000
1567
https://bitcoin.org/img/hero/footer-bg.svg?1528322191
2592000000
1521
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663
2592000000
1405
https://bitcoin.org/img/icons/main_ico_instant.svg?1630339663
2592000000
1360
https://bitcoin.org/img/icons/ico_close.svg?1630339663
2592000000
1191
https://bitcoin.org/img/icons/ico_angle.svg?1528322191
2592000000
1164
https://bitcoin.org/img/icons/play-btn.svg?1528322191
2592000000
1083
https://bitcoin.org/img/icons/netstatus_normal.svg?1528322191
2592000000
903
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
125.04499999341
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
103.50200004177
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
24.486000009347
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
https://bitcoin.org/img/icons/ico_business.svg?1630339663
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663
https://bitcoin.org/img/icons/ico_close.svg?1630339663
82

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of bitcoin.org. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Bitcoin.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
OK

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that bitcoin.org should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
jQuery UI
1.11.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://bitcoin.org/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
High
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for bitcoin.org. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
45

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of bitcoin.org. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 74
Performance 70
Accessibility 80
Best Practices 80
SEO 92
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://bitcoin.org/en/
Updated: 24th October, 2021

2.12 seconds
First Contentful Paint (FCP)
67%
21%
12%

0.02 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on mobile
70

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for bitcoin.org. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.006
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://bitcoin.org/
http/1.1
0
116.47199979052
338
0
301
text/html
https://bitcoin.org/
http/1.1
117.05800006166
217.69300010055
541
0
302
text/html
https://bitcoin.org/en/
h2
218.29799981788
323.67900013924
5846
24061
200
text/html
Document
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
h2
337.71000010893
370.99900003523
6664
26711
200
text/css
Stylesheet
https://bitcoin.org/css/main.css?1630339663
h2
337.83000009134
370.26100000367
22610
122693
200
text/css
Stylesheet
https://bitcoin.org/js/base.js?1630339663
h2
338.05399993435
430.84800010547
4623
12070
200
application/javascript
Script
https://bitcoin.org/js/main.js?1630339663
h2
338.31099979579
372.55699979141
8386
28438
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
h2
338.48599996418
431.31100013852
33777
95931
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery-ui.min.js
h2
338.69699994102
375.46199979261
64738
240022
200
application/javascript
Script
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
h2
339.01300001889
364.70500007272
5406
13995
200
application/javascript
Script
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
h2
339.20900011435
430.48200011253
3805
9687
200
application/javascript
Script
https://bitcoin.org/img/icons/ico_close.svg?1630339663
h2
433.33700019866
455.48699982464
1191
939
200
image/svg+xml
Image
https://bitcoin.org/img/icons/logotop.svg?1630339663
h2
438.97099979222
460.53900010884
3520
6259
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
h2
483.10500010848
508.42199986801
1771
2824
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_business.svg?1630339663
h2
483.23100013658
506.71999994665
1739
3189
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
h2
483.37299982086
507.16699985787
2217
4090
200
image/svg+xml
Image
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663
h2
483.50499989465
505.31500019133
1405
1591
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_instant.svg?1630339663
h2
483.68299985304
506.44400017336
1360
1780
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_worldwide.svg?1630339663
h2
483.76799980178
505.72199979797
3817
6893
200
image/svg+xml
Image
https://bitcoin.org/img/icons/main_ico_lowfee.svg?1630339663
h2
483.8470001705
507.61500000954
2643
4691
200
image/svg+xml
Image
https://bitcoin.org/img/home/bitcoin-img.svg?1630339663
h2
483.94700000063
506.01200014353
4106
11659
200
image/svg+xml
Image
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
h2
484.06800022349
510.54200017825
6427
12401
200
image/svg+xml
Image
https://bitcoin.org/js/analytics.js
h2
484.25900004804
506.2339999713
968
436
200
application/javascript
Script
https://bitcoin.org/img/icons/menumobile.svg?1528322191
h2
486.30100023001
524.03699979186
1145
859
200
image/svg+xml
Image
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
h2
488.79799991846
523.67600006983
22829
22216
200
application/octet-stream
Font
https://bitcoin.org/getip.txt
h2
499.13900019601
602.25600004196
312
0
200
text/plain
XHR
https://bitcoin.org/img/hero/overview-mob.svg?1528322191
h2
508.26899986714
548.14000008628
2210
8045
200
image/svg+xml
Image
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
h2
508.83200019598
534.86600005999
21435
20820
200
application/octet-stream
Font
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
h2
509.06200008467
537.88900002837
22641
22028
200
application/octet-stream
Font
https://bitcoin.org/img/hero/footer-bg.svg?1528322191
h2
522.90399977937
561.4049998112
1522
4903
200
image/svg+xml
Image
https://bitcoin.org/img/icons/netstatus_normal.svg?1528322191
h2
524.61700001732
547.5949998945
903
256
200
image/svg+xml
Image
https://www.google-analytics.com/analytics.js
h2
628.65999992937
670.6220000051
20476
49932
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j94&a=1550827176&t=pageview&_s=1&dl=https%3A%2F%2Fbitcoin.org%2Fen%2F&ul=en-us&de=UTF-8&dt=Bitcoin%20-%20Open%20source%20P2P%20money&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=2016769516&gjid=990027838&cid=1390092384.1635041489&tid=UA-170755108-1&_gid=1522552760.1635041489&_r=1&_slc=1&z=1712173468
h2
698.35700001568
702.28100009263
575
2
200
text/plain
XHR
https://bitcoin.org/js/cookieconsent/light-floating.css
h2
700.47899987549
725.0069999136
1567
3246
200
text/css
Stylesheet
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
356.594
6.903
467.941
46.283
514.236
5.473
527.276
22.988
551.23
29.93
588.612
5.473
610.771
5.216
640.137
13.084
705.152
22.724
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Properly size images
Images can slow down the page's load time. Bitcoin.org should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Bitcoin.org should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Bitcoin.org should consider minifying CSS files.
Minify JavaScript — Potential savings of 5 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Bitcoin.org should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/js/main.js?1630339663
8386
2381
https://bitcoin.org/js/base.js?1630339663
4623
2233
Reduce unused CSS — Potential savings of 20 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Bitcoin.org should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/css/main.css?1630339663
22610
20618
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://bitcoin.org/en/
106.377
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Bitcoin.org should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 277 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
22829
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
22641
https://bitcoin.org/css/main.css?1630339663
22610
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
21435
https://www.google-analytics.com/analytics.js
20476
https://bitcoin.org/js/main.js?1630339663
8386
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
6664
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
6427
Avoids an excessive DOM size — 420 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
420
Maximum DOM Depth
14
Maximum Child Elements
28
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Bitcoin.org should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://bitcoin.org/en/
448.656
26.488
10.072
Unattributable
289.124
14.008
0.644
https://bitcoin.org/js/jquery/jquery-ui.min.js
98.236
67.804
14.724
https://www.google-analytics.com/analytics.js
96.44
86.968
3.852
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
70.38
54.632
6.428
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
337.08
Style & Layout
269.484
Script Evaluation
268.528
Parse HTML & CSS
94.332
Rendering
51.832
Script Parsing & Compilation
42.156
Keep request counts low and transfer sizes small — 34 requests • 277 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
34
283513
Script
8
142179
Font
3
66905
Image
15
35976
Stylesheet
3
30841
Document
1
5846
Other
4
1766
Media
0
0
Third-party
2
21051
Minimize third-party usage — Third-party code blocked the main thread for 30 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21051
33.48
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00576171875
5.9895833333333E-5
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
3870
93
https://www.google-analytics.com/analytics.js
7680
91
https://bitcoin.org/en/
1362
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 3.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 6.2 s
The time taken for the page to become fully interactive.

Other

First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.

Opportunities

Reduce unused JavaScript — Potential savings of 77 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
58495
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
20654

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 5.1 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,650 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Bitcoin.org should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
6664
180
https://bitcoin.org/css/main.css?1630339663
22610
930
https://bitcoin.org/js/base.js?1630339663
4623
630
https://bitcoin.org/js/main.js?1630339663
8386
630
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
33777
1380
https://bitcoin.org/js/jquery/jquery-ui.min.js
64738
1830
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
5406
330
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
3805
180
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Bitcoin.org should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://bitcoin.org/
630
https://bitcoin.org/
480
https://bitcoin.org/en/
0

Diagnostics

Serve static assets with an efficient cache policy — 29 resources found
Bitcoin.org can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20476
https://bitcoin.org/js/jquery/jquery-ui.min.js
14400000
64738
https://bitcoin.org/js/jquery/jquery-1.11.2.min.js
14400000
33777
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
14400000
22829
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
14400000
22641
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
14400000
21435
https://bitcoin.org/js/main.js?1630339663
14400000
8386
https://bitcoin.org/js/jquery/jquery.qrcode.min.js
14400000
5406
https://bitcoin.org/js/base.js?1630339663
14400000
4623
https://bitcoin.org/js/cookieconsent/cookieconsent.js?1630339663
14400000
3805
https://bitcoin.org/js/analytics.js
14400000
968
https://bitcoin.org/css/main.css?1630339663
2592000000
22610
https://bitcoin.org/css/font-awesome-4.4.0/css/font-awesome.min.css
2592000000
6664
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
2592000000
6427
https://bitcoin.org/img/home/bitcoin-img.svg?1630339663
2592000000
4106
https://bitcoin.org/img/icons/main_ico_worldwide.svg?1630339663
2592000000
3817
https://bitcoin.org/img/icons/logotop.svg?1630339663
2592000000
3520
https://bitcoin.org/img/icons/main_ico_lowfee.svg?1630339663
2592000000
2643
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
2592000000
2217
https://bitcoin.org/img/hero/overview-mob.svg?1528322191
2592000000
2210
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
2592000000
1771
https://bitcoin.org/img/icons/ico_business.svg?1630339663
2592000000
1739
https://bitcoin.org/js/cookieconsent/light-floating.css
2592000000
1567
https://bitcoin.org/img/hero/footer-bg.svg?1528322191
2592000000
1522
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663
2592000000
1405
https://bitcoin.org/img/icons/main_ico_instant.svg?1630339663
2592000000
1360
https://bitcoin.org/img/icons/ico_close.svg?1630339663
2592000000
1191
https://bitcoin.org/img/icons/menumobile.svg?1528322191
2592000000
1145
https://bitcoin.org/img/icons/netstatus_normal.svg?1528322191
2592000000
903
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://bitcoin.org/font/titillium/TitilliumWeb-Regular.woff2
34.878000151366
https://bitcoin.org/font/titillium/TitilliumWeb-Bold.woff2
26.033999864012
https://bitcoin.org/font/titillium/TitilliumWeb-SemiBold.woff2
28.826999943703
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://bitcoin.org/img/icons/logo-footer.svg?1630339663
https://bitcoin.org/img/icons/ico_individuals.svg?1630339663
https://bitcoin.org/img/icons/ico_business.svg?1630339663
https://bitcoin.org/img/icons/ico_developers.svg?1630339663
https://bitcoin.org/img/icons/ico_arrow_down.svg?1630339663

Other

First Contentful Paint (3G) — 7120.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
80

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of bitcoin.org. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Bitcoin.org may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
OK

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that bitcoin.org should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.11.2
jQuery UI
1.11.3
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://bitcoin.org/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 5 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
Medium
1
High
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for bitcoin.org. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.
Document uses legible font sizes — 95.88% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.cc_container .cc_message
4.05%
10.2px
.cc_container .cc_btn
0.07%
10.2px
95.88%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of bitcoin.org. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of bitcoin.org on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.22.69.176
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Redacted for Privacy
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: Reykjavik
State: Capital Region
Post Code: 101
Email: b2ca2017df2e442ca3fe6a83500ce004.protect@withheldforprivacy.com
Phone: +354.4212434
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.100.56
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 94/100
WOT Child Safety: 93/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.bitcoin.org
Issued By: E1
Valid From: 30th December, 2022
Valid To: 30th March, 2023
Subject: CN = *.bitcoin.org
Hash: 6acbac77
Issuer: CN = E1
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x049A1668AA02E8BA9FB6B736DBC8EB4BE224
Serial Number (Hex): 049A1668AA02E8BA9FB6B736DBC8EB4BE224
Valid From: 30th December, 2024
Valid To: 30th March, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:5A:F3:ED:2B:FC:36:C2:37:79:B9:52:30:EA:54:6F:CF:55:CB:2E:AC
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://e1.o.lencr.org
CA Issuers - URI:http://e1.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Dec 30 17:39:20.072 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:75:A9:2C:A3:F3:50:07:D1:BD:9D:F4:CE:
94:D9:4B:7B:81:01:ED:7B:30:C1:8B:6C:E0:1A:8C:BB:
59:C6:7E:46:02:20:22:51:22:47:FF:F9:72:46:F7:0E:
99:5B:EE:81:53:42:A0:1C:C2:ED:08:9C:9C:C9:14:11:
2B:73:93:C3:D9:7F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Dec 30 17:39:20.525 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AD:34:79:0A:44:EE:C7:AC:23:BF:DA:
DA:3C:E6:F6:A8:EF:49:CF:CF:26:FB:19:82:A9:2B:89:
98:4E:C0:DE:54:02:21:00:90:51:10:23:FB:A6:2D:CD:
2D:A5:C4:D1:AF:9D:60:B2:B8:8A:3F:06:9C:82:2E:33:
5C:3C:94:C1:01:2B:74:23
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:bitcoin.org
DNS:*.bitcoin.org
Technical

DNS Lookup

A Records

Host IP Address Class TTL
bitcoin.org. 138.68.248.245 IN 299

NS Records

Host Nameserver Class TTL
bitcoin.org. dns1.registrar-servers.com. IN 1799
bitcoin.org. dns2.registrar-servers.com. IN 1799

MX Records

Priority Host Server Class TTL
10 bitcoin.org. mx.zoho.com. IN 1799
20 bitcoin.org. mx2.zoho.com. IN 1799

SOA Records

Domain Name Primary NS Responsible Email TTL
bitcoin.org. dns1.registrar-servers.com. hostmaster.registrar-servers.com. 3600

TXT Records

Host Value Class TTL
bitcoin.org. google-site-verification=HQ6n1bD-lkg0C8_rr6GYh1LXqaY4wspMvxv4fYVW4N4 IN 1798
bitcoin.org. v=spf1 IN 1799

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 15th February, 2023
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
Last-Modified: 19th January, 2023
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Security-Policy: script-src 'self' www.google-analytics.com blockchain.info 'unsafe-inline'
CF-Cache-Status: DYNAMIC
CF-RAY: 799ba9ac5d3ce6c8-EWR

Whois Lookup

Created: 18th August, 2008
Changed: 23rd September, 2021
Expires: 18th August, 2029
Registrar: NameCheap, Inc.
Status: clientTransferProhibited
Nameservers: keanu.ns.cloudflare.com
meera.ns.cloudflare.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: Capital Region
Owner Country: IS
Owner Phone: REDACTED FOR PRIVACY
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: bitcoin.org
Registry Domain ID: 95f8bd6f31564abd9c35804710ed58fe-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2021-09-23T09:18:07Z
Creation Date: 2008-08-18T13:19:55Z
Registry Expiry Date: 2029-08-18T13:19:55Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Capital Region
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: IS
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: keanu.ns.cloudflare.com
Name Server: meera.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-02-15T05:32:26Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
keanu.ns.cloudflare.com 172.64.35.167
meera.ns.cloudflare.com 173.245.58.195
Related

Subdomains

Domain Subdomain
online

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$1,087,110 USD 4/5
$76,045 USD 3/5
$1,004 USD
0/5

Sites hosted on the same IP address