222 ms in total
49 ms
173 ms
0 ms
Click here to check amazing Aes content for United States. Otherwise, check out these important facts you probably never knew about aes.io
Visit aes.ioWe analyzed Aes.io page load time and found that the first response time was 49 ms and then it took 173 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
aes.io performance score
49 ms
42 ms
21 ms
42 ms
43 ms
Our browser made a total of 6 requests to load all elements on the main page. We found that 17% of them (1 request) were addressed to the original Aes.io, 83% (5 requests) were made to App.aes.io. The less responsive or slowest element that took the longest time to load (55 ms) relates to the external source App.aes.io.
Page size can be reduced by 626.7 kB (70%)
901.1 kB
274.5 kB
In fact, the total size of Aes.io main page is 901.1 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. Only 10% of websites need less resources to load. Javascripts take 850.2 kB which makes up the majority of the site volume.
Potential reduce by 651 B
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 651 B or 52% of the original size.
Potential reduce by 582.5 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 582.5 kB or 69% of the original size.
Potential reduce by 43.5 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. Aes.io needs all CSS files to be minified and compressed as it can save up to 43.5 kB or 88% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aes. According to our analytics all requests are already optimized.
aes.io
49 ms
app.aes.io
42 ms
aesio.nocache.js
21 ms
aesio.css
42 ms
standard.css
43 ms
F02FEBD22B174181F115C7F155F7995D.cache.js
55 ms
aes.io SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aes.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Aes.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.
aes.io
Open Graph description is not detected on the main page of Aes. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: