4.9 sec in total
196 ms
4.1 sec
632 ms
Welcome to nanolive.com homepage info - get ready to check Nano Live best content right away, or after learning these important things about nanolive.com
Nanolive’s - automated label-free live cell imaging and analysis solutions. Our AI-powered digital assays enable analysis of label-free image data.
Visit nanolive.comWe analyzed Nanolive.com page load time and found that the first response time was 196 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nanolive.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value16.2 s
0/100
25%
Value15.8 s
0/100
10%
Value1,490 ms
14/100
30%
Value1.145
1/100
15%
Value18.0 s
3/100
10%
196 ms
1669 ms
23 ms
31 ms
184 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nanolive.com, 64% (75 requests) were made to Nanolive.ch and 6% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Nanolive.ch.
Page size can be reduced by 269.7 kB (11%)
2.4 MB
2.1 MB
In fact, the total size of Nanolive.com main page is 2.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. 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 196.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 196.5 kB or 83% of the original size.
Potential reduce by 34 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. Nano Live images are well optimized though.
Potential reduce by 61.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.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. Nanolive.com has all CSS files already compressed.
Number of requests can be reduced by 69 (70%)
98
29
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nano Live. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
nanolive.com
196 ms
www.nanolive.ch
1669 ms
loader.js
23 ms
uc-block.bundle.js
31 ms
supsystic-for-all-admin.css
184 ms
leaflet.css
279 ms
mappress.css
283 ms
sfsi-style.css
380 ms
style.css
281 ms
bundle.js
15 ms
gtm.js
93 ms
css
31 ms
formreset.min.css
194 ms
formsmain.min.css
197 ms
readyclass.min.css
281 ms
browsers.min.css
284 ms
materialize-getaquote.css
386 ms
style.css
294 ms
jquery.min.js
397 ms
jquery-migrate.min.js
376 ms
shine.min.js
377 ms
jquery.json.min.js
380 ms
gravityforms.min.js
396 ms
utils.min.js
472 ms
zem7vkk.css
87 ms
mediaelementplayer-legacy.min.css
469 ms
wp-mediaelement.min.css
472 ms
core.min.js
476 ms
modernizr.custom.min.js
477 ms
jquery.shuffle.min.js
482 ms
random-shuffle-min.js
562 ms
custom.js
569 ms
ol.js
773 ms
scripts.js
569 ms
materialize.js
682 ms
scripts.js
575 ms
jquery.noty.packaged.min.js
656 ms
enquire.min.js
662 ms
scripts.min.js
775 ms
smoothscroll.js
670 ms
jquery.fitvids.js
750 ms
jquery.mobile.js
756 ms
magnific-popup.js
765 ms
api.js
55 ms
salvattore.js
774 ms
wp-polyfill-inert.min.js
764 ms
regenerator-runtime.min.js
674 ms
wp-polyfill.min.js
694 ms
dom-ready.min.js
681 ms
hooks.min.js
686 ms
i18n.min.js
681 ms
a11y.min.js
666 ms
placeholders.jquery.min.js
671 ms
vendor-theme.min.js
677 ms
p.css
36 ms
style.css
676 ms
gravityforms.css
599 ms
gf-image-voting.css
599 ms
table.css
662 ms
scripts-theme.min.js
687 ms
common.js
687 ms
mediaelement-and-player.min.js
766 ms
mediaelement-migrate.min.js
611 ms
wp-mediaelement.min.js
642 ms
p.css
18 ms
837973697
281 ms
604699368
280 ms
715117141
415 ms
nanolive_home_page_logo.png
267 ms
nano-icon_automated-workflow_600px_rgb.jpg
472 ms
nano-icon_Long-term-monitoring_600px_rgb.jpg
267 ms
nano-icon_reliable-live-cell-data_600px_rgb.jpg
266 ms
nano-icon_digital-analytical-solutions_600px_rgb.jpg
274 ms
CX-96focus_web_350px.jpg
275 ms
nanolive-cx-fluo-product-shot.png
470 ms
nanolive-cx-product-shot.png
470 ms
Testimonials-Amgen-1.png
471 ms
Testimonials-Idorsia-1.png
682 ms
Testimonials-ULL-1.png
682 ms
Testimonials-LUCA-1.png
586 ms
ImageGeneration_WorkflowSLDA_rescaled_web.png
836 ms
TiO2-nanoparticle-effects-on-cellular-morphology_thumb.jpg
584 ms
Word-cloud_thumb.png
585 ms
nanolive-badge-swiss-high-precision-250x250.png
683 ms
preloader.gif
651 ms
d
191 ms
d
425 ms
d
417 ms
4iCv6KVjbNBYlgoCjC3Ttw.ttf
399 ms
d
425 ms
4iCs6KVjbNBYlgo6eA.ttf
425 ms
d
415 ms
4iCv6KVjbNBYlgoC1CzTtw.ttf
425 ms
d
497 ms
4iCv6KVjbNBYlgoCxCvTtw.ttf
496 ms
modules.woff
603 ms
1686706452-cb4f6284b65f5cdcb85a034a7bb18fc75a9d98f4d41aa627ba6ffd9f45b5a297-d
138 ms
1247997810-798d0303215e82a74f4848a5654b218f1c73e46170ee79e71b6138f6f990e922-d
135 ms
recaptcha__en.js
215 ms
837973697
184 ms
604699368
175 ms
715117141
198 ms
anchor
44 ms
1247997810-798d0303215e82a74f4848a5654b218f1c73e46170ee79e71b6138f6f990e922-d
101 ms
1686706452-cb4f6284b65f5cdcb85a034a7bb18fc75a9d98f4d41aa627ba6ffd9f45b5a297-d
96 ms
1441384613-b1b73c02eabaddb015512d2b17825a53ee7c8416bed410731eb8bff9495ae1da-d
319 ms
styles__ltr.css
4 ms
recaptcha__en.js
13 ms
sLPIoIr_9R2H1vFE63bCW9_RmUPMbLk-XyKwDAco0G4.js
36 ms
webworker.js
54 ms
logo_48.png
25 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
22 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
21 ms
recaptcha__en.js
24 ms
print.css
96 ms
style.min.css
102 ms
nanolive.com 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
nanolive.com 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
Missing source maps for large first-party JavaScript
nanolive.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanolive.com 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 Nanolive.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.
nanolive.com
Open Graph data is detected on the main page of Nano Live. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: