5.7 sec in total
12 ms
941 ms
4.8 sec
Visit aeternity.github.io now to see the best up-to-date Aeternity Github content for China and also check out these interesting facts you probably never knew about aeternity.github.io
æternity blockchain is an Erlang-based scalable smart contract platform engineered by programming pioneers to address some of the most fundamental challenges native to earlier blockchains. It is desig...
Visit aeternity.github.ioWe analyzed Aeternity.github.io page load time and found that the first response time was 12 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
aeternity.github.io performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.7 s
59/100
25%
Value7.6 s
26/100
10%
Value1,600 ms
12/100
30%
Value0
100/100
15%
Value16.9 s
5/100
10%
12 ms
40 ms
55 ms
34 ms
53 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aeternity.github.io, 80% (37 requests) were made to Docs.aeternity.com and 11% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (656 ms) relates to the external source Youtube-nocookie.com.
Page size can be reduced by 234.5 kB (9%)
2.8 MB
2.5 MB
In fact, the total size of Aeternity.github.io main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 78.6 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. This page needs HTML code to be minified as it can gain 23.4 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 78.6 kB or 88% of the original size.
Potential reduce by 95.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Aeternity Github images are well optimized though.
Potential reduce by 60.4 kB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 60.4 kB or 29% of the original size.
Potential reduce by 0 B
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. Aeternity.github.io has all CSS files already compressed.
Number of requests can be reduced by 7 (18%)
40
33
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aeternity Github. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
aeternity.github.io
12 ms
docs.aeternity.com
40 ms
docs.aeternity.com
55 ms
normalize.css
34 ms
webflow.css
53 ms
aeternity-2-5-1.webflow.css
50 ms
script.js
263 ms
jquery-3.5.1.min.dc5e7f18c8.js
14 ms
webflow.js
88 ms
youtube-placeholder.2b05e7d68d.svg
195 ms
F9cqkdx1Llo
311 ms
YbpLVo7R1gs
656 ms
aeternity-logo.svg
204 ms
noise.png
206 ms
photo-1620207418302-439b387441b0.jpeg
208 ms
aeternitycommunity.png
235 ms
State-Channels.png
261 ms
FATE-VM.png
237 ms
Sophia-Smart-Contracts.png
251 ms
AENS-Naming-System.png
243 ms
interoperable.png
257 ms
Universal.svg
266 ms
Secure.svg
268 ms
Scalable.svg
281 ms
Open-Source.svg
278 ms
Sustainable.svg
290 ms
Decentralized.svg
288 ms
Public-Private.svg
293 ms
User-Friendly.svg
343 ms
Governance.svg
341 ms
6214ab195029bc25dc69ab66_ae-darker.jpeg
484 ms
6207c6b1b9f6d95383955ebf_Build-on-Aeternity.jpeg
483 ms
Twitter_1Twitter.png
343 ms
Instagram_1Instagram.png
482 ms
Telegram_1Telegram.png
484 ms
Discord_1Discord.png
485 ms
Youtube_1Youtube.png
582 ms
Reddit_1Reddit.png
580 ms
LinkedIn_1LinkedIn.png
582 ms
Medium_1Medium.png
582 ms
ClashDisplay-Variable.ttf
420 ms
RobotoMono-VariableFont_wght.ttf
420 ms
ClashGrotesk-Variable.ttf
421 ms
www-player.css
17 ms
www-embed-player.js
34 ms
base.js
61 ms
aeternity.github.io 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
aeternity.github.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
aeternity.github.io 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeternity.github.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Aeternity.github.io 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.
aeternity.github.io
Open Graph data is detected on the main page of Aeternity Github. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: