Consensys.Github.Io - Info consensys.github.io

consensys.github.io receives about 1,633 unique visitors and 1,633 (1.00 per visitor) page views per day which should earn about $6.66/day from advertising revenue. Estimated site value is $4,863.87. According to Alexa Traffic Rank consensys.github.io is ranked number 1,333,673 in the world and 3.6E-5% of global Internet users visit it. Site is hosted in Netherlands and links to network IP address 185.199.108.153. This server supports HTTPS and HTTP/2.

About - consensys.github.io


Technologies used on Website

CDN
Fastly
PaaS
GitHub Pages
Caching
Varnish
Web Frameworks
Ruby on Rails

consensys.github.io Profile

Title: ConsenSys
Last update was 129 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with consensys.github.io in any way. Only publicly available statistics data are displayed.

How popular is consensys.github.io?

1.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,633
Monthly Unique Visitors:
39,192
Pages per Visit:
1.00
Daily Pageviews:
1,633
Alexa Rank:
1,333,673 visit alexa
Alexa Reach:
3.6E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  consensys.github.io
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is consensys.github.io?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
consensys.github.io
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
consensys.github.io
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much consensys.github.io can earn?

Daily Revenue:
$6.66
Monthly Revenue:
$199.80
Yearly Revenue:
$2,430.90
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do consensys.github.io lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is consensys.github.io worth?

Website Value:
$4,863.87

+ Where is consensys.github.io hosted?

+ How fast does consensys.github.io load?

Average Load Time:
(248 ms) 99 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

97
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 260 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 659 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
659
Maximum DOM Depth
21
Maximum Child Elements
116
Keep request counts low and transfer sizes small - 15 requests • 767 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
15767 KB
Script
2407 KB
Image
7166 KB
Font
4144 KB
Document
251 KB
Stylesheet
00 KB
Media
00 KB
Other
00 KB
Third-party
14767 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://consensys.github.io/
0 ms17 ms1 KB0 KB200text/htmlDocument
https://consensys.net/
29 ms462 ms50 KB283 KB200text/htmlDocument
https://consensys.net/static/js/common.bbbf91a5.chunk.js
483 ms594 ms342 KB1300 KB200application/javascriptScript
https://consensys.net/static/js/main.5ee7448a.chunk.js
483 ms524 ms65 KB392 KB200application/javascriptScript
https://i1.wp.com/content.consensys.net/wp-content/uploads/feature-case-study-project-komgo-ConsenSys.jpg?quality=60&resize=60,40
498 ms516 ms1 KB1 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/webinars-featured-enterprise-ethereum.jpg?quality=60&resize=60,40
498 ms515 ms1 KB0 KB200image/webpImage
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
513 ms570 ms34 KB34 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
514 ms541 ms37 KB36 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
514 ms578 ms37 KB36 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Light.bd47bdea.woff2
514 ms539 ms36 KB35 KB200font/woff2Font
https://i0.wp.com/content.consensys.net/wp-content/uploads/consensys-2.0-abstract-hero.jpg?w=1440&quality=100
1187 ms1269 ms161 KB160 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-solutions.png?quality=100&fit=250,250
1187 ms1205 ms1 KB1 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-startups.png?quality=100&fit=250,250
1188 ms1206 ms1 KB0 KB200image/webpImage
https://i2.wp.com/content.consensys.net/wp-content/uploads/icon-dev.png?quality=100&fit=250,250
1188 ms1205 ms1 KB1 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-education.png?quality=100&fit=250,250
1188 ms1206 ms1 KB1 KB200image/webpImage
Serve static assets with an efficient cache policy - 6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://consensys.net/static/js/common.bbbf91a5.chunk.js
86400000 ms342 KB
https://consensys.net/static/js/main.5ee7448a.chunk.js
86400000 ms65 KB
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
86400000 ms37 KB
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
86400000 ms37 KB
https://consensys.net/static/media/Graphik-Light.bd47bdea.woff2
86400000 ms36 KB
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
86400000 ms34 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
44 ms
7 ms
489 ms
8 ms
512 ms
16 ms
530 ms
55 ms
589 ms
5 ms
600 ms
31 ms
643 ms
24 ms
688 ms
527 ms
1215 ms
10 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
57 ms
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
27 ms
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
64 ms
https://consensys.net/static/media/Graphik-Light.bd47bdea.woff2
25 ms
JavaScript execution time - 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://consensys.net/static/js/main.5ee7448a.chunk.js
497 ms479 ms6 ms
Other
212 ms4 ms2 ms
Avoids enormous network payloads - Total size was 767 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://consensys.net/static/js/common.bbbf91a5.chunk.js
342 KB
https://i0.wp.com/content.consensys.net/wp-content/uploads/consensys-2.0-abstract-hero.jpg?w=1440&quality=100
161 KB
https://consensys.net/static/js/main.5ee7448a.chunk.js
65 KB
https://consensys.net/
50 KB
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
37 KB
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
37 KB
https://consensys.net/static/media/Graphik-Light.bd47bdea.woff2
36 KB
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
34 KB
https://i1.wp.com/content.consensys.net/wp-content/uploads/feature-case-study-project-komgo-ConsenSys.jpg?quality=60&resize=60,40
1 KB
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-solutions.png?quality=100&fit=250,250
1 KB
Minimizes main-thread work - 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
491 ms
Style & Layout
107 ms
Other
73 ms
Script Parsing & Compilation
35 ms
Rendering
20 ms
Parse HTML & CSS
13 ms
Garbage Collection
5 ms
Avoid chaining critical requests - 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 20 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

76
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 4.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 1,140 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 5.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 270 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 3990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 790 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 5.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 13 requests • 1,394 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
131394 KB
Image
5792 KB
Script
2407 KB
Font
4144 KB
Document
251 KB
Stylesheet
00 KB
Media
00 KB
Other
00 KB
Third-party
121393 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://consensys.github.io/
0 ms48 ms1 KB0 KB200text/htmlDocument
https://consensys.net/
63 ms498 ms50 KB283 KB200text/htmlDocument
https://consensys.net/static/js/common.bbbf91a5.chunk.js
519 ms623 ms342 KB1300 KB200application/javascriptScript
https://consensys.net/static/js/main.5ee7448a.chunk.js
519 ms559 ms65 KB392 KB200application/javascriptScript
https://i1.wp.com/content.consensys.net/wp-content/uploads/feature-case-study-project-komgo-ConsenSys.jpg?quality=60&resize=60,40
533 ms550 ms1 KB1 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/webinars-featured-enterprise-ethereum.jpg?quality=60&resize=60,40
533 ms551 ms1 KB0 KB200image/webpImage
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
546 ms646 ms34 KB34 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
547 ms575 ms37 KB36 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
547 ms613 ms37 KB36 KB200font/woff2Font
https://consensys.net/static/media/Graphik-Extralight.49743ded.woff2
547 ms617 ms36 KB36 KB200font/woff2Font
https://i0.wp.com/content.consensys.net/wp-content/uploads/consensys-2.0-abstract-hero.jpg?w=3840&quality=100
1256 ms1422 ms788 KB788 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-solutions.png?quality=100&fit=500,500
1256 ms1273 ms1 KB1 KB200image/webpImage
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-startups.png?quality=100&fit=500,500
1256 ms1272 ms1 KB0 KB200image/webpImage
Serve static assets with an efficient cache policy - 6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://consensys.net/static/js/common.bbbf91a5.chunk.js
86400000 ms342 KB
https://consensys.net/static/js/main.5ee7448a.chunk.js
86400000 ms65 KB
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
86400000 ms37 KB
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
86400000 ms37 KB
https://consensys.net/static/media/Graphik-Extralight.49743ded.woff2
86400000 ms36 KB
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
86400000 ms34 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
1 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
79 ms
8 ms
528 ms
8 ms
551 ms
14 ms
566 ms
45 ms
622 ms
34 ms
657 ms
6 ms
663 ms
5 ms
672 ms
28 ms
714 ms
572 ms
1286 ms
13 ms
1303 ms
9 ms
1466 ms
24 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
99 ms
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
29 ms
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
66 ms
https://consensys.net/static/media/Graphik-Extralight.49743ded.woff2
70 ms
Reduce JavaScript execution time - 2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
https://consensys.net/static/js/main.5ee7448a.chunk.js
2158 ms1972 ms26 ms
Other
1014 ms19 ms8 ms
https://consensys.net/static/js/common.bbbf91a5.chunk.js
104 ms20 ms83 ms
Avoids enormous network payloads - Total size was 1,394 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://i0.wp.com/content.consensys.net/wp-content/uploads/consensys-2.0-abstract-hero.jpg?w=3840&quality=100
788 KB
https://consensys.net/static/js/common.bbbf91a5.chunk.js
342 KB
https://consensys.net/static/js/main.5ee7448a.chunk.js
65 KB
https://consensys.net/
50 KB
https://consensys.net/static/media/Graphik-Medium.81459c89.woff2
37 KB
https://consensys.net/static/media/Graphik-Semibold.e55e3d50.woff2
37 KB
https://consensys.net/static/media/Graphik-Extralight.49743ded.woff2
36 KB
https://consensys.net/static/media/Graphik-Regular.5da74ad6.woff2
34 KB
https://i1.wp.com/content.consensys.net/wp-content/uploads/feature-case-study-project-komgo-ConsenSys.jpg?quality=60&resize=60,40
1 KB
https://i0.wp.com/content.consensys.net/wp-content/uploads/icon-solutions.png?quality=100&fit=500,500
1 KB
Minimize main-thread work - 3.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
2020 ms
Style & Layout
516 ms
Other
338 ms
Rendering
199 ms
Script Parsing & Compilation
145 ms
Parse HTML & CSS
48 ms
Garbage Collection
45 ms
Avoids an excessive DOM size - 659 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
659
Maximum DOM Depth
21
Maximum Child Elements
116
Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 50 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

49.8KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.

None of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

Reduce server response time

In our test, your server responded in 0.48 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://consensys.net/blog/" class="">Blog</a> is close to 1 other tap targets .
The tap target <a href="https://consen…et/developers/" class="">Developer Portal</a> and 3 others are close to other tap targets .
The tap target <a href="https://consen…eum/use-cases/">Explore blockchain use cases →</a> is close to 1 other tap targets .
The tap target <a href="https://labs.consensys.net/" class="hero-nav-item__link--25Px6"></a> and 2 others are close to other tap targets .
The tap target <a href="https://consensys.net/about/" class="">About</a> and 28 others are close to other tap targets.
The tap target <a href="https://media.consensys.net/">Follow ConsenSys on Medium</a> is close to 1 other tap targets.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://consensys.net/static/js/common.bbbf91a5.chunk.js (24 hours)
https://consensys.net/static/js/main.5ee7448a.chunk.js (24 hours)
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
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
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
You have compression enabled. Learn more about enabling compression.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does consensys.github.io use compression?

consensys.github.io does not use compression.
Original size: 167 B
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

consensys.github.io supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: www.github.com
Organization: GitHub, Inc.
Location: San Francisco, California, US
Issuer: DigiCert SHA2 High Assurance Server CA
Valid from: Jun 27 00:00:00 2018 GMT
Valid until: Jun 20 12:00:00 2020 GMT
Authority: Is not a CA
Keysize:
Common Name: DigiCert SHA2 High Assurance Server CA
Organization: DigiCert Inc, OU=www.digicert.com
Location: US
Issuer: DigiCert High Assurance EV Root CA
Valid from: Oct 22 12:00:00 2013 GMT
Valid until: Oct 22 12:00:00 2028 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

consensys.github.io supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: GitHub.com
Content-Type: text/html; charset=utf-8
Last-Modified: Mon, 26 Oct 2015 04:37:37 GMT
ETag: "562dae11-a7"
Access-Control-Allow-Origin: *
Expires: Sun, 24 Nov 2019 04:38:02 GMT
Cache-Control: max-age=600
X-Proxy-Cache: MISS
X-GitHub-Request-Id: 49E4:6309:3D66B8:4EB4C7:5DDA06CC
Content-Length: 167
Accept-Ranges: bytes
Date: Sun, 24 Nov 2019 04:28:02 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-chi21153-CHI
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1574569683.964533,VS0,VE22
Vary: Accept-Encoding
X-Fastly-Request-ID: 492e825015f0d2637cc3cad1f8d4cf7b35086ee8

+ DNS Lookup

Type Ip Target TTL
A 185.199.108.153 3576
A 185.199.109.153 3576
A 185.199.110.153 3576
A 185.199.111.153 3576

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 129 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with consensys.github.io in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

guernseystamps.com
18 secs
finam.aero
1 min
rainerland.net
1 min
cheshirskykot-effect.ru
2 mins
radiowidhwidh.com
2 mins
from2usa.com
3 mins
radiosovet.ru
3 mins
chamber.gorenton.com
4 mins
radiosahan.com
4 mins
raarbg.com
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
consensys.github.io widget