1 sec in total
82 ms
858 ms
84 ms
Welcome to amii.us homepage info - get ready to check Amii best content right away, or after learning these important things about amii.us
Home
Visit amii.usWe analyzed Amii.us page load time and found that the first response time was 82 ms and then it took 942 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
amii.us performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value16.2 s
0/100
25%
Value12.2 s
3/100
10%
Value730 ms
41/100
30%
Value0
100/100
15%
Value15.4 s
7/100
10%
82 ms
94 ms
40 ms
88 ms
87 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Amii.us, 43% (19 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (371 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 669.5 kB (48%)
1.4 MB
739.3 kB
In fact, the total size of Amii.us main page is 1.4 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. 55% of websites need less resources to load. HTML takes 626.0 kB which makes up the majority of the site volume.
Potential reduce by 496.5 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 496.5 kB or 79% of the original size.
Potential reduce by 0 B
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. Amii images are well optimized though.
Potential reduce by 173.0 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 173.0 kB or 43% of the original size.
Number of requests can be reduced by 10 (43%)
23
13
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amii. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
amii.us
82 ms
www.amiius.org
94 ms
minified.js
40 ms
focus-within-polyfill.js
88 ms
polyfill.min.js
87 ms
thunderbolt-commons.354484c3.bundle.min.js
196 ms
main.72e1f7cd.bundle.min.js
202 ms
lodash.min.js
202 ms
react.production.min.js
199 ms
react-dom.production.min.js
231 ms
siteTags.bundle.min.js
247 ms
wix-perf-measure.umd.min.js
229 ms
amii_edited.png
371 ms
bundle.min.js
155 ms
1e3643_f1fadcd033fd4146bf3064e9c4e9e074~mv2_d_5184_3456_s_4_2.jpg
300 ms
1e3643_0643d259faaa4532a6868cae979ac775~mv2_d_5184_3456_s_4_2.jpg
301 ms
9a5f52_45840a30bc234fc2a0f5a8a8c8728c3c~mv2.jpg
306 ms
9a5f52_a72139362ae44f5db52c89526f562db4~mv2.jpg
304 ms
9a5f52_e3677d238e7a47659f35dd0781b7f175~mv2.jpeg
306 ms
84770f_83b527cc664b480a842106670a5fe074~mv2.jpg
305 ms
1e3643_6b202171835a44438a999f773fe0e77f~mv2_d_7360_5068_s_4_2.jpg
300 ms
5a32e87e-0f32-4971-a43f-4ec453bc74ca.woff
56 ms
51v0xj5VPw1cLYHNhfd8ND8E0i7KZn-EPnyo3HZu7kw.woff
53 ms
-HJgNsTwx9qXGSxqew62RQ.woff
54 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
54 ms
137 ms
135 ms
127 ms
133 ms
131 ms
128 ms
173 ms
172 ms
171 ms
197 ms
197 ms
161 ms
deprecation-en.v5.html
9 ms
bolt-performance
49 ms
deprecation-style.v5.css
11 ms
right-arrow.svg
30 ms
WixMadeforDisplay_W_Bd.woff
16 ms
WixMadeforText_W_Bd.woff
16 ms
WixMadeforText_W_Rg.woff
16 ms
amii.us accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
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
amii.us 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
Page has valid source maps
amii.us 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amii.us 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 Amii.us 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.
amii.us
Open Graph data is detected on the main page of Amii. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: