AI Readiness Assessment
https://www.nutun.com
Assessed2026-07-31
Reference0731/NUT/73
IndustryBusiness services and outsourcing
Scale187 / 82
TrafficNAAwaiting live domain connection, provided as part of service deployment.
Regulated sectorNot established
Listed companyNot established
Manual equivalent11 days · £6,732estimate only
Foundations assessed now · the automated tests
Your Digital Doorway
PeopleAI systems
AI readiness · Pages
18.2%
AI readiness · PDFs
N/A
Misinformation · Pages
Extremely likely
Misinformation · PDFs
N/A
0%25%50%75%100%
Governancestage 2 · not assessed yet...more
64 judgements need a named person in the organisation to confirm, because they turn on what you know to be true rather than anything measurement can settle: whether a claim is supported, whether a page is still current, which of two versions is the one to quote. In order, they cover: who is answerable for this content; is it still true today; can each claim be backed; does our published content agree; will the right meaning come across; can someone reach it and act on it. An answer recorded against each, with a name and a date, is what turns published content into governed content.
Visibilitystage 3 · not assessed yet...more
Once the foundations are sound and the content is governed, the visibility stage measures how AI systems and agents actually find the estate: which pages they reach, how often, and how the organisation is represented when they answer questions about it, tracked over time. Building visibility on unconfirmed foundations only amplifies whatever is wrong, which is why it comes last.
Key findings · AI readiness
How much of your content is reachable and readable, rather than blocked, buried or missing. Higher is better.
AI readiness is very low.the content can be reached, but the way the pages are built keeps much of it from being read cleanly.
What is holding it back
- The page arrives with almost no readable text, so the answer is absent from what is served, not merely hard to find.1 page
- The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong.1 page
- With no real headings the extracted text arrives as one unlabelled block, and each section reads alike.1 page
Key findings · Misinformation
Where your content could lead an AI system to state something incorrect. Only direct routes to a wrong answer count here.
Misinformation risk is high.The pages read as extremely likely and the documents as likely zero to cause it, which is why the risk reads as high.
What could cause it
- The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong.pages
- Google search shows the site's current content while the AI services are turned away and answer from older or outside sources, so the same question brings back different information depending on which door the public uses, and the two answers can conflict.pages
- With no real headings the extracted text arrives as one unlabelled block, and each section reads alike.pages
▸Overall findings what makes up the figures · click to view
The front door5 of 15 AI systems turned away at the door. Content behind the door cannot be read by whoever is refused, and that holds the figures down. The full picture is the Digital doorway below.
The site as a whole · 32.2%the estate's shared machinery measures 87.1% built. The figure shown is lower because the assessment found search and ai answers diverge, which raise the chance of an answer being wrong, and a direct route to a wrong answer caps what can be relied on, however well built. The evidence for each finding is under Site infrastructure below.
Pages · 18.2%the average of 1 pages, each scored on its own build and its own misinformation exposure; today they range 8.8% to 8.8%. Each page's evidence is under Pages considered below.
▸Digital doorway measured at the front door · click to view
Anyone asking for this site, a person on a phone or an AI system building an answer, is either let in or turned away, in milliseconds, by machinery most organisations never see. An AI system refused here gets nothing at all: to that system the organisation simply does not answer.
The door changes without notice: a security setting, a network change or a new crawler policy can close it silently. It is measured live on the day of assessment, and it is worth watching continuously rather than once.
People
4 out of 4 served
AI systems
5 out of 15 turned away
People are served in full; 5 of the 15 AI systems are turned away at the door.
Whether the estate can be reached and read at all: access rules, links, redirects, sitemap, transport.
▸The site as a whole 32.2% Very likely 3 out of 25
| Check | Result | Evidence | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS26 | warning | the sitemap lists the site's addresses but records no date against any of them, so nothing in it says how current they are | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the sitemap carries last-modified dates, and how old the most recent of them is. What good looks like The sitemap carries recent last-modified dates. Why it matters Absent or stale dates leave the age of the content unstated, so fresh pages read as no newer than old ones. What we found on this page the sitemap lists the site's addresses but records no date against any of them, so nothing in it says how current they are The evidence, taken from the page as served The sitemap this site publishes, as read
The sitemap was read for the date each address records for itself.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DS03 | warning | 6 of 15 AI crawlers asking for the site are refused by the security layer in front of it while the other 9 are served, so the content is closed to those AI services and open to the rest. The refused services answer about the site from outside sources. The door decides call by call: this check's own requests saw 6 of 15 refused and the front-door probe 5 of 15, and the verdict stands on the worse of the two. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check The same page loads for a browser but is refused when the request names itself as an AI service. What good looks like The page returns the same response to a named AI service as to a browser, with no edge block. Why it matters The block sits in front of the site and leaves no trace in its own logs, so the estate is closed off unnoticed. What we found on this page 6 of 15 AI crawlers asking for the site are refused by the security layer in front of it while the other 9 are served, so the content is closed to those AI services and open to the rest. The refused services answer about the site from outside sources. The door decides call by call: this check's own requests saw 6 of 15 refused and the front-door probe 5 of 15, and the verdict stands on the worse of the two. The evidence, taken from the page as served Each crawler's own request to the entry page, and the status it received
Hostwww.nutun.com · resolves to 172.67.71.74, 104.26.4.225, 104.26.5.225 · Cloudflare
Address trailwww.nutun.com
Checked2026-07-31 16:39 UTC · request sent from 10.100.100.212 (our checker)
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AR27 | fail | the front door serves the search crawlers while refusing the AI services: 3 search crawler(s) are served the page while 5 of 10 AI answer services' own crawlers are refused. Search results are fed the site's current content; the AI answer services are not, so a person asking a search engine and a person asking an AI assistant receive different information, and the two answers can conflict. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What we check Whether the front door answers Google consistently: the crawling that feeds search results on one side, and the paths that feed AI answers on the other. What good looks like Search crawling and the AI answer services are given the same access, so both speak from the site's current content. Why it matters Google search shows the site's current content while the AI services are turned away and answer from older or outside sources, so the same question brings back different information depending on which door the public uses, and the two answers can conflict. What we found on this page the front door serves the search crawlers while refusing the AI services: 3 search crawler(s) are served the page while 5 of 10 AI answer services' own crawlers are refused. Search results are fed the site's current content; the AI answer services are not, so a person asking a search engine and a person asking an AI assistant receive different information, and the two answers can conflict. The evidence, taken from the page as served The search crawlers and the AI services at the same door, in the same minute
Measured at the same door within the same minute; the full grid is in the view for the front-door check.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: search crawling and the AI answer services are given the same access, so both speak from the site's current content. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Passing checks are omitted here; the full record is in the exports.
Pages considered 1 pages
The highest-priority pages, chosen from the site's own signals of importance.
▸https://www.nutun.com 8.8% Extremely likely 18 out of 57
| Check | Result | Evidence | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MX01 | warning | the site took 658ms to start answering; beyond about 345ms an automated reader is liable to give up first | |||||||||||
What we check How quickly the page starts to reply, measured against a 345 millisecond first-byte threshold. What good looks like The page starts to reply promptly, within the first-byte threshold. Why it matters Past the waiting limit the answer is assembled from stale or third-party material instead of from your page. What we found on this page the site took 658ms to start answering; beyond about 345ms an automated reader is liable to give up first The evidence, taken from the page as served How long this page took to start answering
Timed from the request leaving our checker to the first byte coming back, on the page as served. The 345ms figure is the point beyond which an automated reader is liable to give up.
| |||||||||||||
| CT08 | fail | the page carries no headings at all, so it reads as one undivided block of text with nothing marking out its sections | |||||||||||
What we check The page uses real heading tags rather than text merely styled to look like a heading. What good looks like The page uses real heading tags, not text merely styled to look like a heading. Why it matters With no real headings the extracted text arrives as one unlabelled block, and each section reads alike. What we found on this page the page carries no headings at all, so it reads as one undivided block of text with nothing marking out its sections The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for headings of any level. <noscript> <noscript> <noscript> <div id="app" data-page="{"component":"Welcome","props":{"errors":{},"auth&…Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page uses real heading tags, not text merely styled to look like a heading. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| CT10 | fail | the page carries no main heading, so nothing on it states what the page is about | |||||||||||
What we check The page carries a main heading (the H1), its own statement of what the page is about. What good looks like The page carries a single main heading stating what it is about. Why it matters With no main heading the page never states its own subject, so the sections beneath it hang from nothing. What we found on this page the page carries no main heading, so nothing on it states what the page is about The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for a heading of any level, and carries none. <html lang="en"> <head> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"/> <meta name="google-site-verification" content="h8FhtvYs8K8IniIzpWsLLNzsEBQ2zDw0DxNtfzr5PPY"/> <link rel="preconnect" href="https://fonts.googleapis.com"/> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin=""/> <link href="https://fonts.googleapis.com/css2?family=Anton&family=Sora:wght@100..800&display=swap" rel="stylesheet"/> <title>A Global Leader In Omnichannel BPO Services | Nutun</title> <meta name="description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:title" content="A Global Leader In Omnichannel BPO Services"/> <meta property="og:description" content="Offshore your customer service and debt collection to a … Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page carries a single main heading stating what it is about. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| CT12 | fail | the page does not mark out where its main content or navigation or header or footer begins or ends, so a machine reading it cannot tell the page's own content from the parts repeated across the site | |||||||||||
What we check The page marks its regions with landmark tags such as main, nav, header and footer. What good looks like The page marks its regions with landmark tags such as main, nav, header and footer. Why it matters Without them nothing states where the content starts and the furniture ends, so the two come out mixed together. What we found on this page the page does not mark out where its main content or navigation or header or footer begins or ends, so a machine reading it cannot tell the page's own content from the parts repeated across the site The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the blocks that mark out its main content, its navigation, its header and its footer. <noscript> <noscript> <noscript> <div id="app" data-page="{"component":"Welcome","props":{"errors":{},"auth&…Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page marks its regions with landmark tags such as main, nav, header and footer. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| MS11 | warning | the page does not mark out which part holds its main content | |||||||||||
What we check Whether the page marks which region holds its main content, as against navigation and footer. What good looks like The page marks which region holds its main content. Why it matters Nothing separates the substance from the surrounding furniture, so menus and boilerplate travel with the text. What we found on this page the page does not mark out which part holds its main content The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its main content. <noscript> <noscript> <noscript> <div id="app" data-page="{"component":"Welcome","props":{"errors":{},"auth&… | |||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"/> <meta name="google-site-verification" content="h8FhtvYs8K8IniIzpWsLLNzsEBQ2zDw0DxNtfzr5PPY"/> <link rel="preconnect" href="https://fonts.googleapis.com"/> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin=""/> <link href="https://fonts.googleapis.com/css2?family=Anton&family=Sora:wght@100..800&display=swap" rel="stylesheet"/> <title>A Global Leader In Omnichannel BPO Services | Nutun</title> <meta name="description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:title" content="A Global Leader In Omnichannel BPO Services"/> <meta property="og:description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:type" content="website"/> <meta property="og:url" content="https://www.nutun.com"/> <meta name="twitter:card" content="summary"/> <meta name="twitter:title" content="A Global Leader In Omnichannel BPO Servi… | |||||||||||||
| CT04 | warning | the page shows the year 2024 in its text, but nothing on the page states it as the date of the content | |||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page shows the year 2024 in its text, but nothing on the page states it as the date of the content The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag stating the date of the content. The year shown above was found in the page's own text. <head> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"/> <meta name="google-site-verification" content="h8FhtvYs8K8IniIzpWsLLNzsEBQ2zDw0DxNtfzr5PPY"/> <link rel="preconnect" href="https://fonts.googleapis.com"/> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin=""/> <link href="https://fonts.googleapis.com/css2?family=Anton&family=Sora:wght@100..800&display=swap" rel="stylesheet"/> <title>A Global Leader In Omnichannel BPO Services | Nutun</title> <meta name="description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:title" content="A Global Leader In Omnichannel BPO Services"/> <meta property="og:description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:type" content="website"/> <meta property="og:url" content="https://www.nutun.com"/> <meta name="twitter:card" content="summary"/> <meta name="twitter:title" content="A Global Leader In Omnichannel BPO Servi… | |||||||||||||
| AR01 | fail | only 51 characters of extractable text in the raw HTML response, below the 200-character threshold: the served HTML does not carry the page's main content as text | |||||||||||
What we check The page as first served, and whether its text is there before any JavaScript runs. What good looks like The served HTML already carries the page's text, before any JavaScript runs. Why it matters The page arrives with almost no readable text, so the answer is absent from what is served, not merely hard to find. What we found on this page only 51 characters of extractable text in the raw HTML response, below the 200-character threshold: the served HTML does not carry the page's main content as text The evidence, taken from the page as served All the text extractable from the raw served HTML
A Global Leader In Omnichannel BPO Services | Nutun Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the served HTML already carries the page's text, before any JavaScript runs. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a real and common route to a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| AR13 | warning | only 51 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts repeated across the site | |||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page only 51 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts repeated across the site The evidence, taken from the page as served The main text extracted from the page, as served
A Global Leader In Omnichannel BPO Services | Nutun | |||||||||||||
| CT35 | warning | the page carries no copyright line in the content as served, so there is nothing on it to date it by, and an absent copyright line is one of the marks of a copied template | |||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters A copyright year in the past reads as a page nobody has attended to, and it is the usual sign of a template copied from somewhere else. Either way an AI treats the content as stale and can present old material as current. What we found on this page the page carries no copyright line in the content as served, so there is nothing on it to date it by, and an absent copyright line is one of the marks of a copied template The evidence, taken from the page as served The foot of this page, as served
The foot of the page was read for a copyright line. (this part of the page was empty as served) | |||||||||||||
| CT24 | warning | the page's own content runs to 51 characters | |||||||||||
What we check The page holds enough main text to be substantive, measured against a 400 character floor. What good looks like The page holds enough main text to be substantive. Why it matters A page of a few sentences offers almost nothing to quote, so it adds little beyond its own existence. What we found on this page the page's own content runs to 51 characters The evidence, taken from the page as served How much of this page is its own content
Counted from the page as served, before any script runs. The page's own content is the part it marks out as its main content; where it marks out none, the whole of its text is counted.
| |||||||||||||
| CT14 | fail | the page does not mark out its navigation, so the menu links run into the page's own words when it is read | |||||||||||
What we check Navigation is marked as navigation, so its links separate cleanly from the body text. What good looks like Navigation is marked as navigation, so its links separate cleanly from the body text. Why it matters Unmarked menus read as ordinary sentences once the page is extracted, padding each passage with link text. What we found on this page the page does not mark out its navigation, so the menu links run into the page's own words when it is read The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its navigation. <noscript> <noscript> <noscript> <div id="app" data-page="{"component":"Welcome","props":{"errors":{},"auth&…Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: navigation is marked as navigation, so its links separate cleanly from the body text. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| CT15 | warning | the page does not mark out its footer, so the repeated foot-of-page text runs into the page's own words when it is read | |||||||||||
What we check The footer is marked as a footer, so the small print separates from the body text. What good looks like The footer is marked as a footer, so the small print separates from the body text. Why it matters Unmarked footer text joins the body of each page, so the same boilerplate is quoted back as page content. What we found on this page the page does not mark out its footer, so the repeated foot-of-page text runs into the page's own words when it is read The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its footer. <noscript> <noscript> <noscript> <div id="app" data-page="{"component":"Welcome","props":{"errors":{},"auth&… | |||||||||||||
| AJ05 | warning | no site-search control detected on this page | |||||||||||
What we check Whether a search box for the site is present in the page as it is served. What good looks like A search box is present in the served markup, so the site's own content can be queried directly. Why it matters With no search box on the page, its links are the only route from here into the rest of the site. What we found on this page no site-search control detected on this page The evidence, taken from the page as served The head of this page, as served
The page was read for a search box: a search form, a control named for search, or a box labelled as one. <head> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"/> <meta name="google-site-verification" content="h8FhtvYs8K8IniIzpWsLLNzsEBQ2zDw0DxNtfzr5PPY"/> <link rel="preconnect" href="https://fonts.googleapis.com"/> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin=""/> <link href="https://fonts.googleapis.com/css2?family=Anton&family=Sora:wght@100..800&display=swap" rel="stylesheet"/> <title>A Global Leader In Omnichannel BPO Services | Nutun</title> <meta name="description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:title" content="A Global Leader In Omnichannel BPO Services"/> <meta property="og:description" content="Offshore your customer service and debt collection to a global BPO leader in South Africa. Innovative, outsourced solutions. Chat with us today!"/> <meta property="og:type" content="website"/> <meta property="og:url" content="https://www.nutun.com"/> <meta name="twitter:card" content="summary"/> <meta name="twitter:title" content="A Global Leader In Omnichannel BPO Servi… | |||||||||||||
| MS13 | warning | 2 of 2 iframes untitled | |||||||||||
What we check Each embedded panel on the page carries a title saying what it contains. What good looks like Each embedded panel carries a title saying what it contains. Why it matters The embedded region stays unnamed, so what it holds is left unstated in the page around it. What we found on this page 2 of 2 iframes untitled The evidence, taken from the page as served The iframes with no title attribute, as served
<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-K8RLP9GH" height="0" width="0" style="display:none;visibility:hidden"/> <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-5TWRHND8" height="0" width="0" style="display:none;visibility:hidden"/> | |||||||||||||
| AR03 | fail | 99% of the words a person sees are missing from the page as first delivered (51 characters delivered, 8564 once the page finishes building itself): the page's content exists only after JavaScript runs, so it is absent on the raw-HTML fetch path | |||||||||||
What we check How much of the page's content exists only once JavaScript has run. What good looks like The page's content is present in the served HTML, so it does not depend on JavaScript to appear. Why it matters The page is fetched successfully but the answer is missing from what comes back, so the content is absent rather than wrong. What we found on this page 99% of the words a person sees are missing from the page as first delivered (51 characters delivered, 8564 once the page finishes building itself): the page's content exists only after JavaScript runs, so it is absent on the raw-HTML fetch path The evidence, taken from the page as served Content present only after JavaScript runs (absent from the served HTML)
The served HTML carries 51 characters of text; after JavaScript runs the page carries 8564. 99% of the rendered page's words are absent from the HTML the server sends. What the server sends (raw HTML text) A Global Leader In Omnichannel BPO Services | Nutun
Words present only after JavaScript runs
20212022202320242025abilityaboutabsolutelyaccelerateaccoladesaccreditationsachieveacquiringacquisitionacrossactionadaptaddressadoptadoptionadvantageafricaagainagentsaimsallowsalsoamericaanalyticsandyannuallyapproacharoundarticlearticlesassociationsattractaustraliaaverageawardawardsbasebeenbeforebespokebetterbeyondboldboostingbothbpesabposbrownbuildingbuiltbusinessbusinessescapabilitiescarecareers
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's content is present in the served HTML, so it does not depend on JavaScript to appear. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 5 out of a possible 5, because it is one of the checks that decide whether content can be reached and read at all, so it carries the heaviest weight in the figure for this item. Why it moves the misinformation reading This failure is a frequent and direct cause of a wrong answer for the content it affects, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| AR11 | warning | 99% of the words a person sees are missing from the page as first delivered, which is 0.01 of its finished size | |||||||||||
What we check The measured gap between the page as served and the page after the browser has built it. What good looks like The served page and the fully built page carry the same words, with little gap between them. Why it matters Two versions of the same page exist, and which words come back depends on which version was fetched. What we found on this page 99% of the words a person sees are missing from the page as first delivered, which is 0.01 of its finished size The evidence, taken from the page as served This page as first delivered, against the page once its scripts have run
Both were taken from the same request. The first is what the site sent; the second is what a person ends up looking at.
| |||||||||||||
| MS02 | fail | 26 of 84 buttons, links and controls on the loaded page carry no name in the page's code saying what each is for (kinds affected: link) | |||||||||||
What we check Whether the page's buttons, links and form controls each carry a name once the page has loaded. What good looks like The page's buttons, links and form controls each carry a name once the page has loaded. Why it matters Unnamed controls are identified by their position on the screen alone, so a redesign moves what they refer to. What we found on this page 26 of 84 buttons, links and controls on the loaded page carry no name in the page's code saying what each is for (kinds affected: link) The evidence, taken from the page as served The controls on this page that carry no name
Read on the page once its scripts had run.
Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: the page's buttons, links and form controls each carry a name once the page has loaded. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
PDF documents 0 documents
No PDF documents were part of this assessment.
How the scores work method & bands
This report is Stage 1, Foundations: each automated test the engine can run without human input, so there is a usable result at the first stage. Governance (owner-confirmed truth) and Visibility (how AI agents find the estate) are later stages and are shown greyed above.
What was assessed. 1 pages were assessed, selected from 1 reviewed using the site's own signals of importance (its navigation, homepage links, most-linked pages, sitemap, and any llms.txt file), and the first 0 PDF documents found were assessed separately. The industry in the header is classified from the site's own content. The traffic classification comes from a recognised top-sites list or a connected traffic provider; it reads NA when the domain is not connected to a traffic source.
Header identity signals. The regulated sector and listed company values are inferred from the same crawled content, and shown here so the header can stay to the answer alone. Regulated sector reads “Not established”: none. Listed company reads “Not established”: no clear public-listing indicators in the sampled pages.
AI readiness is the weighted share of checks that passed, reported separately for pages and for PDF documents because each is reached and corrected differently. Grade A checks decide whether content can be reached and read at all; grade B whether it is understood correctly; grade C support reliability. A measured score is scaled into a ceiling when an access gate binds it (for example the site blocking AI crawlers at its edge): content that cannot be reached is not partially ready. Scores never read exactly 25, 50, 75 or 100, because those are buckets, not measurements.
Likelihood of misinformation is a band, given as a worst case (the highest any single item or estate-wide finding reaches) and a typical position across the pages or documents. Only checks whose failure is a direct route to a wrong answer carry a band; the rest affect readiness only.
| Band | Range | Meaning |
|---|---|---|
| Likely zero | 0-5% | No failing misinformation-bearing checks. |
| Very little | 6-25% | Unlikely to cause wrong information. |
| Likely | 26-50% | Could contribute to wrong information in some cases. |
| Very likely | 51-75% | A real and common route to wrong information. |
| Extremely likely | 76-100% | A frequent and direct cause of wrong information. |
Of the register's 187 checks, 82 ran automatically in this Foundations stage. 64 are governance questions for the next stage. The remainder need organisation-supplied data or an external service; each check that did not run is listed in the exports.
About us
Built on evidence, not assumptions.
We have been doing this for 25 years. For the last two years, we have been training AI to understand and map AI Readiness (fundamentals, governance, visibility), against our unique dataset of more than 3.7 trillion data points.
3.7
Trillion
Data points, with each result kept since the beginning: probably the largest experience and compliance dataset of its kind. Our AI is trained on factual, controlled, real-world evidence.
$106
Billion
Estimated manual effort avoided through automation. An estimate, and a conservative one: since ARTY was introduced, we have removed 95% of costs and delivered efficiency gains beyond 70x.
119
Million
Websites analysed and mapped for content fundamentals, from the outside in. AI Readiness begins by removing the human issues that undermine Value and create unnecessary Risk.
25
Years
When we started, we were labelled 'the pioneers' of website automation and checking. In 2023, we launched our first AI analysis tools.
Who’s talking about us
