. * * window.aa needs to exist and be usable by ANY module's script, * however early it runs - main-nav's script, for one, runs near * the top of

91探花

, well before the real search-insights.js * so the download * begins as early as before. Repeat calls share the same downloads, a * failed load is retried on the next call, and the versions / SRI * hashes live only here. * * Algolia Insights is unaffected: window.aa above is still created in * on every page and queues events until search-insights loads. * * window.loadAlgoliaLibs({ priority: 'high' }) (Oct 2026): used by the * /search page, where the first results wait on these libraries. Chrome * gives async scripts low priority, behind images and fonts; this asks * for high instead (fetchpriority). Only the first call for a library * sets its priority - later calls share that download. */ (function (win, doc) { var LIBS = [ { ready: function () { return !!win['algoliasearch/lite']; }, src: 'https://cdn.jsdelivr.net/npm/algoliasearch@5.52.1/dist/lite/builds/browser.umd.js', integrity: 'sha256-I2oYUIvhx1g6l4lTP+yoERbzLIHKzw4AKaBRQPwIeDY=' }, { ready: function () { return !!win.instantsearch; }, src: 'https://cdn.jsdelivr.net/npm/instantsearch.js@4.98.0/dist/instantsearch.production.min.js', integrity: 'sha256-ngmqZk4WBxUw257aMYZayyNBd983INngagv0jI6Ecfs=' } ]; function loadOne(lib, options) { if (lib.ready()) return Promise.resolve(); // One download per library, shared by every caller; reset on // failure so the next call retries just the library that failed. if (lib.pending) return lib.pending; lib.pending = new Promise(function (resolve, reject) { var script = doc.createElement('script'); script.src = lib.src; script.integrity = lib.integrity; script.crossOrigin = 'anonymous'; script.async = true; if (options && options.priority === 'high') script.setAttribute('fetchpriority', 'high'); script.onload = function () { lib.ready() ? resolve() : reject(new Error('Loaded but not available: ' + lib.src)); }; script.onerror = function () { script.remove(); reject(new Error('Could not load ' + lib.src)); }; doc.head.appendChild(script); }); lib.pending.catch(function () { lib.pending = null; }); return lib.pending; } win.loadAlgoliaLibs = function (options) { return Promise.all(LIBS.map(function (lib) { return loadOne(lib, options); })); }; })(window, document); . */ window.hsConversationsSettings = window.hsConversationsSettings || {}; window.hsConversationsSettings.loadImmediately = false; (function (win) { var EVENTS = ['pointerdown', 'keydown', 'touchstart', 'scroll', 'mousemove', 'wheel']; var done = false; /* 19 Oct 2026 - chat widget layout shift (field CLS). Phones fail Core Web Vitals on CLS (p75 ~0.2 site-wide in CrUX for months). Biggest cause found: HubSpot's chat container is fixed to the bottom-right corner and changes size - 100x96 launcher to 282x253 when the welcome message pops up (~5 s after load), and to full screen when a visitor opens the chat. Its top-left corner moves, so Chrome scores it as a layout shift: 0.088 per page view at 360x640 (0.044 at 412x850), on every page. Taps happen inside the chat iframe, so the parent page never sees the input and the open/close shifts count too. Fix: whenever the container's size changes it is made transparent for 400 ms (Chrome doesn't score shifts of invisible elements), then shown again at its new size. Tested on live io1001 at 360x640 in a cookie-less frame: the 0.088 shift no longer appears. The chat itself is unchanged - it just appears 0.4 s later at each resize. Relies on HubSpot's container id; if that changes this does nothing (no error). */ function cloakChatResizes() { var ID = 'hubspot-messages-iframe-container'; function watch(c) { if (c.getAttribute('data-bb-cloak')) return; c.setAttribute('data-bb-cloak', '1'); var last = c.offsetWidth + 'x' + c.offsetHeight, timer = null; new MutationObserver(function () { var size = c.offsetWidth + 'x' + c.offsetHeight; if (size === last) return; last = size; c.style.setProperty('opacity', '0', 'important'); clearTimeout(timer); timer = setTimeout(function () { c.style.removeProperty('opacity'); }, 400); }).observe(c, { attributes: true, attributeFilter: ['style', 'class'], subtree: true, childList: true }); } var found = document.getElementById(ID); if (found) { watch(found); return; } if (!document.body || !('MutationObserver' in win)) return; var mo = new MutationObserver(function () { var c = document.getElementById(ID); if (c) { mo.disconnect(); watch(c); } }); mo.observe(document.body, { childList: true }); setTimeout(function () { mo.disconnect(); }, 30000); } function loadWidget() { var api = win.HubSpotConversations; if (api && api.widget && api.widget.status && api.widget.status().loaded) return; try { cloakChatResizes(); } catch (e) {} if (api && api.widget) api.widget.load(); } function onFirstInteraction() { if (done) return; done = true; EVENTS.forEach(function (type) { win.removeEventListener(type, onFirstInteraction, { passive: true }); }); var start = function () { if (win.HubSpotConversations) loadWidget(); else (win.hsConversationsOnReady = win.hsConversationsOnReady || []).push(loadWidget); }; if ('requestIdleCallback' in win) win.requestIdleCallback(start, { timeout: 1500 }); else setTimeout(start, 200); } EVENTS.forEach(function (type) { win.addEventListener(type, onFirstInteraction, { passive: true }); }); })(window);

91探花

Skip to main content
Home
91探花
ioDisease Model Cells

Discover

ioDisease Model Cells

ioDisease Model Cells

Human iPSC-derived disease models

View all ioDisease Model products

ioDisease Model Cells are a range of deterministically programmed human iPSC-derived cells engineered to contain disease-related mutations. Each ioDisease Model Cell can be paired with a genetically matched ioWild Type Cell, to help scientists confidently link genotype to phenotype and make true comparisons in their data.

ioCells are for research use only.

What Scientists Say About ioDisease Models

An image of Dr Mariangela Iovino

Dr Mariangela Iovino

Senior Group Leader | Biology Discovery | Charles River

"Data from assays routinely used at Charles River show that 91探花 disease models have disease-relevant phenotypes, suggesting that the cells can be easily applied to drug discovery programs鈥�

An image of Emma Jones, PhD

Emma Jones, PhD

Senior Scientist | Neurobiology Medicines Discovery Catapult

"More physiologically relevant disease models will permit better and more predictable drug discovery, and will therefore improve the translation of medicines to the clinic"

Wild type and isogenic disease model cells: A true comparison

Be confident in your data by pairing ioDisease Model Cells with the genetically matched ioWild Type control.

Discover ioWild Type Cells
bitbio-vials-Wild_and_Disease-equal_size

The right human model

Are you seeking to solve the paucity of successful treatments for neurodegenerative disease? Learn how ioDisease Model Cells are being used as a physiologically-relevant CNS model for drug discovery that will reproducibly scale to high-throughput screens.

鈥淯ltimately, we hope our ioDisease Model Cells will help provide more effective therapies for neurodegenerative diseases such as Huntington鈥檚 disease. I believe that it is crucial to use the right human model to successfully translate research into the clinic and help patients鈥�

TonyTony Oosterveen PhD 
91探花

Watch the webinar
custom-cells-developing

A next-generation approach to study Huntington鈥檚 disease

Learn about the benchtop benefits and applications of our latest disease model for Huntington鈥檚 disease, ioGlutamatergic Neurons HTT 50CAG/WT.

Download the brochure
bitbio-ioGlutamatergic-Neurons-HTT50CAGWT

Addressing current challenges of in vitro cell models

Discover how experts from across academia and industry are approaching the challenges of accuracy and reproducibility of in vitro cell models as well as potential solutions.

鈥淔or translational applications, it鈥檚 important to identify a model that is relevant, which is mirroring the human disease鈥�

Bit.bio_circle_headshot_Pic0004-removebg-preview (2)Davide Danovi PhD 
King鈥檚 College London

Read the blog
Hero-PINK1-Q456X-Het_ICC_DAPI_MAP2

Don鈥檛 see what you鈥檙e looking for? 

Partner with us to generate custom ioDisease Model Cells. Access our platform to generate custom disease model cells to answer your drug discovery and disease research questions.

Learn more about our custom disease models
91探花 lab scientist with sample

Related pages

Our platform Discover the cell coding platform behind our cells
Product catalogue See the range of human iPSC-derived cells for research and drug discovery
Resources Explore our latest scientific insights, webinars, blogs and video