1.6 sec in total
410 ms
1.1 sec
68 ms
Visit gov.kyber.org now to see the best up-to-date Gov Kyber content for United States and also check out these interesting facts you probably never knew about gov.kyber.org
A place dedicated to the Kyber community and focused on discussions about important KyberDAO governance topics.
Visit gov.kyber.orgWe analyzed Gov.kyber.org page load time and found that the first response time was 410 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
gov.kyber.org performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value3.6 s
60/100
25%
Value3.6 s
86/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.6 s
91/100
10%
410 ms
152 ms
203 ms
284 ms
157 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Gov.kyber.org, 54% (26 requests) were made to Global.discourse-cdn.com and 42% (20 requests) were made to Sjc6.discourse-cdn.com. The less responsive or slowest element that took the longest time to load (681 ms) relates to the external source Global.discourse-cdn.com.
Page size can be reduced by 136.5 kB (48%)
283.8 kB
147.4 kB
In fact, the total size of Gov.kyber.org main page is 283.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 155.5 kB which makes up the majority of the site volume.
Potential reduce by 130.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 130.4 kB or 84% of the original size.
Potential reduce by 15 B
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 6.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Gov.kyber.org has all CSS files already compressed.
Number of requests can be reduced by 45 (96%)
47
2
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gov Kyber. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
gov.kyber.org
410 ms
browser-detect-99f42f91bffa8ca1606d62b70bb92f981d83921e78ccdbd3d9538f07007f27ac.br.js
152 ms
vendor.7b22befba122f915b0551569ab805acd-aac41b730fbea71ac3b69bd32fb1dfe329cf44c55dd752c4970e3720e905d5dd.br.js
203 ms
chunk.ee92f1d1e17b8598eb54.d41d8cd9.br.js
284 ms
chunk.9de0d5a88a01de8d7f73.d41d8cd9.br.js
157 ms
checklist-273fb3ab5f7d346fa16c1482aedbd81035c5f677a83d7940da78abf7c1e16744.br.js
145 ms
discourse-adplugin-b2f0b2c25942f571bd80e9b35458cc8f66cfb317b0f97dc7948474445cbb8a14.br.js
132 ms
discourse-adplugin_admin-42777d881f7108a2c5f33ba5ca3e5ca7a44bad97a47ed36c747ae2b2cd52f339.br.js
247 ms
discourse-ai-6a636f2a6d0ca62d5ae0a5f28e36eec52f0286ea020dcef012f0cd2959b2a8a6.br.js
266 ms
discourse-akismet-7a9c3c786f220e0b2a361580075231abe2282ef59c27d650b40ec7b7d88f8222.br.js
284 ms
discourse-cakeday-0f8efec788b95db09845daf3ca3137368e3767d2f2a2699b4c4d349a82e4f53e.br.js
262 ms
discourse-deprecation-collector-afb8e3a917714f2895b0d5d78db1b52d80b511ccf9a9417f0c80e0cec5da77dd.br.js
319 ms
discourse-details-48148ec534a4c5e9614302186b345123ba1358787c41bc31cbd17231f794fe42.br.js
368 ms
discourse-lazy-videos-93eefdae5b7d15a7cb3301aeba28935598be3f8484243b33146694690e2dd474.br.js
381 ms
discourse-local-dates-a1b9590bc8f26e3bcd3d4cf00594250816149a8c4f00c75ffed0bfcf3e409d74.br.js
388 ms
discourse-narrative-bot-643f10339e287d380f81413fde738a8ad3a6e2a5ee4d7e30f2e841f92c78e5eb.br.js
396 ms
discourse-presence-fc08c21eda4e026fe0e91d04f30a77cd839e6e0c9e443bc9bd9817cb6eddf0d4.br.js
397 ms
discourse-solved-fa653576c58ecea2c612917c93d5f739606d3fe1db28ae7db6f84120cdf2433f.br.js
463 ms
footnote-9e6a21e04868e13dc75adf73cfaab1be722d32b46af9a8b1894712c647ab6499.br.js
502 ms
footnote_extra-295b457b90cb18fedfdb544868c494c71842a27c0781d3042fa4fd26589204fa.br.js
504 ms
hosted-site-633043af2d58d76ecf8070d1a5c822d51901b13ee9f0d23c014e6f7bd7ee43e0.br.js
517 ms
hosted-site_admin-3e38d4fc1a066ce90a180effe2b3d6c2b4c1f56e969fd64ecc02b3b78065edf9.br.js
516 ms
poll-c514fbef324ad213e9825daf68ecdfebd34a708e617429299d36fa1dd3fd6c6f.br.js
531 ms
spoiler-alert-77512c36f465902e7dbf3b8252c7cd6387edc9bf4ca804b79466212c1d1c843d.br.js
618 ms
en-80a97fb6cffc6739c90b61cd0263aa655aa02a6a06669704f1cac49213461a15.br.js
681 ms
discourse-client-performance.js
229 ms
color_definitions_light_5_1_65acc1d23f034a1a4e50e3885ec912605573aa62.css
19 ms
desktop_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
30 ms
checklist_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
27 ms
discourse-adplugin_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
23 ms
discourse-ai_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
27 ms
discourse-akismet_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
28 ms
discourse-cakeday_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
54 ms
discourse-details_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
53 ms
discourse-lazy-videos_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
56 ms
discourse-local-dates_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
55 ms
discourse-narrative-bot_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
54 ms
discourse-presence_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
54 ms
discourse-solved_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
55 ms
footnote_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
56 ms
hosted-site_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
56 ms
poll_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
57 ms
spoiler-alert_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
57 ms
discourse-ai_desktop_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
58 ms
poll_desktop_a57f990dba9551f54a0f1ece56e60c7b5198d1bf.css
62 ms
desktop_theme_1_b7f08b0ac1353fe77d351e2bbd4db1e3c23fc524.css
58 ms
start-discourse-7c0f5f4daf3c942b7b6ecfe8e62e2e5a0f6555924859cf055314c0df3d617353.br.js
601 ms
browser-update-9070f07226d022f68c06506e046ae33f8fe725302ff53955cd3d483f2fc47ff6.br.js
580 ms
gov.kyber.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
gov.kyber.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
gov.kyber.org SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gov.kyber.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gov.kyber.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
gov.kyber.org
Open Graph data is detected on the main page of Gov Kyber. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: