2 sec in total
117 ms
1.8 sec
132 ms
Visit nanocages.com now to see the best up-to-date Nanocages content for China and also check out these interesting facts you probably never knew about nanocages.com
Younan Xia (Chinese: 夏幼南) is the Brock Family Chair and Georgia Research Alliance (GRA) Eminent Scholar in Nanomedicine at Georgia Tech.
Visit nanocages.comWe analyzed Nanocages.com page load time and found that the first response time was 117 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
nanocages.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value9.8 s
0/100
25%
Value3.1 s
93/100
10%
Value610 ms
49/100
30%
Value0.001
100/100
15%
Value9.5 s
30/100
10%
117 ms
91 ms
88 ms
42 ms
49 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Nanocages.com, 46% (36 requests) were made to Static.parastorage.com and 30% (24 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.3 MB (74%)
3.1 MB
815.6 kB
In fact, the total size of Nanocages.com main page is 3.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 112.7 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 112.7 kB or 84% of the original size.
Potential reduce by 17.6 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. Obviously, Nanocages needs image optimization as it can save up to 17.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.1 MB
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 2.1 MB or 76% of the original size.
Potential reduce by 44.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. Nanocages.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 52 (72%)
72
20
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nanocages. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nanocages.com
117 ms
www.nanocages.com
91 ms
bt
88 ms
require.min.js
42 ms
main-r.min.js
49 ms
viewer.css
59 ms
UpgradeBrowser.js
47 ms
dynamicmodel
29 ms
98c30e_c7da372ceb7b8eb22a21c3176e8c1ffc_1190.json.z
291 ms
98c30e_0d38e1a495ffa8441a216e5fa7d546fc_1160.json.z
295 ms
ugc-viewer
101 ms
bt
104 ms
skins.min.js
96 ms
components.min.js
47 ms
utils.min.js
90 ms
core.min.js
89 ms
react-with-addons.min.js
43 ms
lodash.min.js
24 ms
TweenMax.min.js
86 ms
layout.min.js
89 ms
tpa.min.js
88 ms
fonts.min.js
84 ms
animations.min.js
83 ms
swfobject.min.js
91 ms
mousetrap.min.js
86 ms
tweenEngine.min.js
86 ms
DrawSVGPlugin.min.js
85 ms
react-dom.min.js
82 ms
ScrollToPlugin.min.js
83 ms
widgets.min.js
84 ms
experiment.js
84 ms
render.min.js
85 ms
wixappsCore.min.js
87 ms
wixappsClassics.min.js
88 ms
wixappsBuilder.min.js
85 ms
zepto.min.js
85 ms
color.min.js
84 ms
react-dom-server.min.js
191 ms
bt
61 ms
latin.css
18 ms
dc.js
188 ms
bt
185 ms
98c30e_08f5a8a03390415bae552141289f2129.jpg
242 ms
mobileIEFix.css
45 ms
css
43 ms
98c30e_ab3695baafe692f3c5427c7762132c6d.html
175 ms
98c30e_a037af08e920486bb81483fbf496477d.jpg
327 ms
98c30e_586bee93a6c145afb9af05003ffa455b.png
350 ms
98c30e_4f93a99186454cebba808a5f75094ff6.jpg
347 ms
98c30e_e84a56c539b44f509bb9039cf76c9736.jpg
340 ms
98c30e_a472d12e646f41a685759eb00e8b6a68.jpg
395 ms
98c30e_11d457302393474fb301fd65bb42b355.jpg
373 ms
98c30e_c4759cfa7b054fdf9331f0ede3b97b08.jpg
533 ms
98c30e_bb5ab9c4168443b78ccc4560e21b7045.jpg
678 ms
98c30e_ff03c38631644e76a03357d37afd7719.png
513 ms
98c30e_f936791e077a4654b5f43afeca569c60.png
537 ms
98c30e_1facaed740a0450991bc916f56df3eab.png
526 ms
98c30e_67931ec1add84958a4d65d5095d01cca.png
626 ms
98c30e_4023dca198864ffc933231729a4991e7.png
708 ms
98c30e_a3e1c2b014544572964ad5a5a91d5032.png
822 ms
98c30e_ee2fe292d1c84c0cbfbe8c89a1102192.png
681 ms
98c30e_ee17d7bca20b4a35b5977fd4d04a0e1a.png
750 ms
98c30e_559151b8c6c54501b2d2af7e39a86554.png
853 ms
98c30e_d4dd75670dca442e9a80711f6760f191.png
867 ms
4f857b2e8a316c4e1ed16717a3d4ec8c.png
688 ms
b4412694dfff1fde0e7bc219a1008f4d.png
690 ms
98c30e_c2786bc1fbee4995ba0736c81e1d0c09.png
915 ms
bt
94 ms
bt
94 ms
arrows_white_new3.png
91 ms
ironpatern.png
92 ms
indented_bg.png
89 ms
indented_bg_inverted.png
90 ms
__utm.gif
63 ms
bt
45 ms
analytics.js
11 ms
collect
19 ms
collect
53 ms
ugc-viewer
40 ms
nanocages.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
nanocages.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
nanocages.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanocages.com 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 Nanocages.com 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.
nanocages.com
Open Graph data is detected on the main page of Nanocages. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: