Website audit

Send four visitors through your website. See what they think.

Three real buyer types and one AI agent walk your site, page by page, and narrate the friction as they hit it — then score it and tell you what to fix first.

  • Takes about two minutes
  • No signup to see your score
  • Tests AI-agent readability
0.0/10

Report findings

Website audit

dataweavers.com

A credible, well-built enterprise site that converts ready buyers smoothly but makes first-time visitors and price-checkers work harder than they should.

September 2, 2026
Lead generation
Full
Visit the site
7.2
/ 10
Solid with gaps
8.9
AI readability

Dataweavers presents a polished, credible enterprise platform-operations site that converts confident, in-category buyers well but asks first-time visitors and budget-screening evaluators to do more work than they should. The path from the hero to an enquiry is short and clean, proof is specific and backed by recognisable enterprise logos, and the site is highly readable to both people and machines. The main gaps are a metaphor-first hero that delays saying what the company actually does, and pricing that is fully gated behind a sales conversation.

What this site is

What they do
Azure-native enterprise platform-operations company selling Arc, Fusion and Spark for DXP/CMS environments (Sitecore, Optimizely, Contentstack).
Who it is for
Enterprise digital, IT and platform-engineering leaders running Sitecore, Optimizely or Contentstack DXP/CMS on Azure.
Sectors
Government, healthcare, automotive, financial services, enterprise digital.
What they sell
Azure-native platform-operations products: Arc (headless platform operations), Fusion (DXP management automation) and Spark (instant content publishing) for enterprise DXP/CMS environments.
Conversion event
Submit the contact form or book a demo (sales enquiry)
Proof on hand
Enterprise customer logos (Toyota, Isuzu Ute, Beckman Coulter, UnitingCare, Stamford Health, Heritage Bank, Global Payments); ISO27001 certification; a metrics-led State Transport Department case study; product stats such as 2.5 billion annual page views and a 50% reduction in content-editor change time.
Buyer facts found
What each product does; supported platforms (Sitecore, Optimizely, Contentstack); contact email and three regional phone numbers; plan tier names; onboarding timeframe of 10 to 15 days; an Azure Marketplace purchase path for Spark.
Buyer facts missing
Any indicative pricing or price range; a named (non-anonymised) reference customer for the flagship case study.
Machine readability
Server-rendered HTML with schema.org Organization JSON-LD and a clean title, meta description and single H1; robots.txt permits AI crawlers; no llms.txt file (returns 404).

For a visitor who already understands DXP and platform operations and is ready to talk, Dataweavers is easy to buy from: one click from the hero reaches a short contact form, with email and regional phone numbers as alternatives. The biggest opportunity sits at the top of the funnel — helping category-unaware visitors grasp the offer within the first screen, and giving comparison shoppers at least an indicative price so they can self-qualify before committing to a sales conversation.

The four visitors

Cold visitor

Priya

Digital marketing lead at a large enterprise, new to the platform-operations category

Awareness

Mixed

Arrived

Followed a link after hearing Dataweavers mentioned alongside Sitecore, with no prior idea of what they do.

Wants

To work out, quickly, what Dataweavers actually offers and whether it is relevant to her organisation.

Judges on

Whether the first screen tells her what the company does and who it is for.

  • Lands on the homepage and reads a headline built on metaphor rather than a plain description of the offer.
  • Reads the supporting line about “friction in enterprise infrastructure and operations” and starts to form a picture.
  • Scrolls to a row of recognisable enterprise logos, which reassures her the company is credible.
  • Sees the FAST / RESILIENT / SECURE value pillars and gets the gist of the promise.
  • Opens the Products menu and finds Arc, Fusion and Spark.
  • Skims the Arc page (“Unlock Headless without the Headaches”) but the language is pitched at technical buyers.
  • Leaves still a little unsure whether it fits her role, planning to research the category first.

Ready to act

Marcus

Platform engineering manager at a Sitecore shop, ready to start a conversation

Task execution

Good

Arrived

Came in on a colleague's recommendation already knowing he wants to talk to Dataweavers.

Wants

To make contact with as little friction as possible.

Judges on

How fast and painless it is to reach a human.

  • Arrives on the homepage and immediately spots the primary call to action.
  • Clicks “Get in touch” in the hero — a single click.
  • Lands on the contact page headed “Need a hand? Let us know how we can help.”
  • Sees a short form: first name, last name, email, phone, company and message.
  • Notes the email address and three regional phone numbers as alternatives.
  • Fills in the form (we stop before submitting on the client's behalf).
  • Comes away confident: reaching out took one click and under a minute.

Comparison shopper

Elena

IT procurement lead evaluating Dataweavers against alternatives and in-house options

Evaluation

Mixed

Arrived

Shortlisting vendors and wants to compare capability, proof and cost before booking any calls.

Wants

Enough substance — especially a price signal — to decide whether Dataweavers makes the shortlist.

Judges on

Whether she can self-qualify on capability, proof and budget without talking to sales.

  • Scans the homepage for substance rather than slogans.
  • Goes to the Plans page (“Build your Plan”) to gauge cost.
  • Finds Bronze / Silver / Gold tiers laid out but no prices anywhere.
  • Is frustrated: she cannot judge budget fit without contacting sales.
  • Moves to the Arc product page to compare capabilities.
  • Finds strong, specific proof (2.5 billion annual page views; 50% faster content edits).
  • Reads the State Transport Department case study — impressive numbers, but the client is anonymised.
  • Notes the ISO27001 credential, but still has to make contact just to get a price.

AI agent

Answer-engine crawler

Automated agent extracting facts about Dataweavers for an AI answer engine

Task execution

Good

Arrived

Dispatched to summarise what Dataweavers does, who it serves and how to contact it.

Wants

Clean, structured, JavaScript-free facts it can extract and cite.

Judges on

Server-rendered content, structured data, extractable buyer facts and crawl policy.

  • Fetches the homepage HTML and finds full content server-rendered, no JavaScript required.
  • Parses a schema.org Organization block embedded as JSON-LD.
  • Extracts a clean title, meta description and a single H1.
  • Looks for an llms.txt guide and receives a 404.
  • Reads robots.txt: only preview paths are disallowed; answer engines are not blocked.
  • Extracts contact email, phone numbers and product facts, but finds no pricing to report.

Journey feed

Cold visitor

Priya

Homepage

Lands on the homepage and reads the hero headline.

“It’s what’s behind the scenes that keeps you ahead” — nice line, but what do they actually do?

Ready to act

Marcus

Homepage

Scans the header and hero for the way to make contact.

I already know I want to talk to them — where do I click?

AI agent

Answer-engine crawler

Homepage (HTML)

Fetches the homepage HTML.

Full content is present without running JavaScript — easy to read.

Comparison shopper

Elena

Homepage

Scans the homepage for substance over slogans.

Looks polished. Now, can I compare capability and cost without a sales call?

Cold visitor

Priya

Homepage

Reads the supporting line under the headline.

“Friction in enterprise infrastructure and operations” — okay, this is about keeping big platforms running.

AI agent

Answer-engine crawler

Homepage (HTML)

Parses the embedded schema.org JSON-LD.

An Organization block with name, URL and logo — clean structured data to cite.

Ready to act

Marcus

Homepage

Clicks “Get in touch” in the hero.

There it is, right in the hero. One click.

Comparison shopper

Elena

Plans

Opens the Plans page to gauge cost.

“Build your Plan” — good, let’s see the tiers and what they cost.

Cold visitor

Priya

Homepage

Scrolls to the customer logo row.

Toyota, Isuzu, Beckman Coulter — serious companies use this. That helps.

AI agent

Answer-engine crawler

Homepage (HTML)

Extracts title, meta description and H1.

Title spells out ‘DXP & CMS Platform Operations for Enterprises’ — clearer than the visible headline.

Ready to act

Marcus

Contact

Lands on the contact page.

“Need a hand? Let us know how we can help.” — and there’s a form right here.

Comparison shopper

Elena

Plans

Reviews the tier structure.

Bronze, Silver, Gold are here — but I don’t see a single price.

Cold visitor

Priya

Homepage

Reads the FAST / RESILIENT / SECURE value pillars.

Launch faster, stay live, stay secure — I get the promise now.

Ready to act

Marcus

Contact

Reads the form fields.

First name, last name, email, phone, company, message — short and reasonable.

Comparison shopper

Elena

Plans

Looks for any indicative pricing.

Nothing. I can’t tell if this is in budget without booking a call.

AI agent

Answer-engine crawler

llms.txt

Requests /llms.txt.

404 — no machine-guidance file to tell me what to prioritise.

Cold visitor

Priya

Products menu

Opens the Products dropdown.

Arc, Fusion, Spark — three products. Which one is for someone like me?

Ready to act

Marcus

Contact

Notes the alternative contact channels.

There’s hello@dataweavers.com and phone numbers for AU, UK and US if I’d rather call.

Comparison shopper

Elena

Arc for Sitecore

Opens the Arc product page to compare capability.

“Unlock Headless without the Headaches” — let’s see what it actually does.

AI agent

Answer-engine crawler

robots.txt

Reads robots.txt.

Only preview paths disallowed; no block on answer engines. Good to crawl.

Cold visitor

Priya

Arc for Sitecore

Skims the Arc page copy.

This is written for engineers. I follow the gist but it’s not aimed at me.

Ready to act

Marcus

Contact

Fills in the form (we stop before submitting).

Quick to complete. That was painless.

Comparison shopper

Elena

Arc for Sitecore

Reads the proof points on the Arc page.

“Over 2.5 billion page views annually” and “50%” faster edits — that’s concrete.

Cold visitor

Priya

Homepage

Leaves to research the category before deciding.

Credible company, but I need to understand headless platform ops first.

Comparison shopper

Elena

State Transport Department case study

Reads the flagship case study.

25% more releases, zero downtime — strong. Shame the client is unnamed, though.

AI agent

Answer-engine crawler

Site-wide

Compiles extractable buyer facts.

Products, platforms and contact details are all clear; pricing is simply absent.

Ready to act

Marcus

Contact

Finishes the enquiry flow.

One click from the hero to a ready-to-send form. Exactly what I wanted.

Comparison shopper

Elena

Plans / Contact

Decides she must contact sales to get a price.

Capability and proof are strong, but I’m forced into a call just to learn the cost.

How each score was reached

Nav Detail binds here.

Navigation & findability — 7.5

Primary navigation is clean, conventional and stays out of the way, with the enquiry action always within reach. Products and Platforms use dropdowns, and the header carries a persistent contact button at both desktop and mobile widths. The one gap is that the lower-commitment “Book a demo” page is not surfaced in the main navigation or hero, so every visitor is funnelled to the open-ended contact route.

  • Header links resolve cleanly, e.g. “CONTACT US” and hero “Get in touch” both point to /contact.
  • On mobile (375×812) the nav collapses to a hamburger while a “Get in touch” link stays visible in the header, so the primary action never requires opening the menu.

Message clarity (ICP fit) — 6.5

Once a visitor is inside the platform-operations category the messaging is sharp, but the hero leads with metaphor rather than plain description, so a first-time or non-technical visitor has to read on before they know what is being sold. The meta title is clearer about the offer than the headline the visitor actually sees first.

  • The hero headline is “It’s what’s behind the scenes that keeps you ahead.” — evocative, but it does not name the product category.
  • The supporting line, “Friction in enterprise infrastructure and operations grinds even the most sophisticated companies to a crawl…”, begins to clarify the offer but only after the metaphor.
  • By contrast the page title, “DXP & CMS Platform Operations for Enterprises | Dataweavers”, states the offer plainly.

Trust & credibility — 8.0

Trust is a clear strength. The site pairs recognisable enterprise logos with a formal security credential and a results-led case study, which is exactly what a risk-averse enterprise buyer looks for.

  • Named customer logos include Toyota, Isuzu Ute, Beckman Coulter, UnitingCare, Stamford Health and Heritage Bank.
  • The case study states hard outcomes such as “Release velocity increased 25% in 6 months” and zero-downtime deployments, and the company advertises ISO27001 certification.

Proof depth — 7.5

Proof is specific and quantified rather than generic, which lends real credibility. The one thing that softens it is that the flagship case study anonymises the client and the quoted person, which makes the strongest evidence harder to verify.

  • Product proof is concrete, e.g. “over 2.5 billion page views annually” and “Content Editors reduced time to make changes by 50%”.
  • The case-study customer is unnamed (“State Transport Department”) and the testimonial is attributed only to a “Development Manager, Enterprise Applications”.

Conversion path — 7.0

The core enquiry path is genuinely low-friction: one click from the hero reaches a short form, with email and phone as alternatives for buyers who prefer them. Two things hold the score back — pricing is fully gated, so budget-screening visitors cannot self-qualify, and only the high-commitment “get in touch” option is offered up front.

  • The contact form asks for just six fields under the heading “Need a hand? Let us know how we can help.”, plus hello@dataweavers.com and three regional phone numbers.
  • The Plans page (“Build your Plan”) lists Bronze/Silver/Gold tiers but shows no prices at all, so cost is only discoverable by contacting sales.

AI readability — 8.9

The site is highly legible to AI answer engines: it renders its content server-side, ships structured data, and exposes real contact channels, with no crawl restrictions on answer engines. The only material gap is the absence of an llms.txt guide.

  • Readable without JavaScript: 3/3 — full page content is present in server-rendered HTML.
  • Buyer facts extractable: 2/3 — products, platforms and contact details extract cleanly, but pricing is absent.
  • Structured data present: 2/2 — a schema.org Organization block is embedded as JSON-LD.
  • Non-form contact channel: 1/1 — a public email address and phone numbers are published.
  • Raw subtotal 8/9, scaled to 8.9/10; crawl-policy deduction 0 (robots.txt does not block answer engines).

Report findings

Ranked by likely impact. Each finding quotes the page it came from.

Worth fixing

Message clarity

Lead the hero with what Dataweavers does, not a metaphor

The first screen is where a category-unaware or non-technical visitor decides whether the site is relevant to them. Leading with metaphor makes them work to place the offer, and some will leave before the supporting copy resolves it. The page title already states the offer plainly — the visible headline should do the same.

It’s what’s behind the scenes that keeps you ahead.

View the page

What to do

  • Add a plain-language descriptor near the hero (e.g. ‘Azure-native platform operations for enterprise DXP and CMS’) so the offer is clear within one screen.
  • Keep the current headline as an emotional hook but pair it with a concrete sub-line naming the product category and who it is for.
  • Name the supported platforms (Sitecore, Optimizely, Contentstack) above the fold so buyers self-identify immediately.
  • Test the revised hero with someone unfamiliar with the category to confirm they can say what you do in 5 seconds.

Worth fixing

Conversion path

Give comparison shoppers an indicative price so they can self-qualify

The Plans page sets up tiers but shows no cost, so an evaluator screening on budget cannot tell whether Dataweavers is even in range without booking a sales call. Buyers who prefer to self-qualify may drop out rather than commit to a conversation, and the ones who do enquire arrive with no price expectation set.

Build your Plan

View the page

What to do

  • Publish an indicative starting price or a price range for each product, even if final pricing is bespoke.
  • If exact figures cannot be shown, add a ‘starting from’ signal or a typical-engagement band so evaluators can gauge fit.
  • Explain what drives price (environments, scale, support tier) so buyers understand the model before contacting sales.
  • Add a lightweight ‘get a quote’ path distinct from the general contact form.

Worth checking

Conversion path

Surface ‘Book a demo’ as a lower-commitment CTA on the homepage

A dedicated Book a Demo page exists but is not linked from the homepage header or hero, so every visitor is funnelled to the open-ended ‘Get in touch’ route. Offering a demo alongside contact gives warmer-but-not-ready buyers a clearer, lower-commitment next step.

Book a 1:1 demo with a Dataweavers expert.

View the page

What to do

  • Add a secondary ‘Book a demo’ CTA in the header and hero alongside ‘Get in touch’.
  • Make clear what a demo covers so buyers know what they are signing up for.
  • Confirm the demo page carries a working scheduler or form rather than only descriptive copy.

Worth checking

Proof depth

Name the case-study client, or add a named reference, to harden your best proof

The flagship case study carries strong, specific numbers but anonymises both the client and the person quoted, which weakens the most persuasive evidence on the site. Enterprise buyers weight named references heavily; an unnamed one invites doubt about whether it is real or repeatable.

We used to be overwhelmed just keeping the platform running. Now we’re delivering so fast the business can’t keep up.

View the page

What to do

  • Where the client permits, name the organisation and the person quoted to maximise credibility.
  • If anonymity is contractually required, add a short note explaining why, and include at least one fully named reference elsewhere on the site.
  • Add a logo or sector detail that lets buyers place the customer without breaching confidentiality.

Worth checking

Machine readability

Add an llms.txt to guide AI answer engines

The site is already highly readable to machines, but there is no llms.txt file, so answer engines get no steer on which pages best summarise the offer. As buyers increasingly ask AI assistants to shortlist vendors, a small guidance file helps ensure Dataweavers is represented accurately.

User-agent: *

View the page

What to do

  • Publish an llms.txt pointing to the pages that best describe the products, platforms and contact routes.
  • Keep it short and current so it reflects the live offer.
  • Ensure key buyer facts (what you do, who you serve, how to contact) are stated plainly on those linked pages.

Keep doing

Proof depth

Keep leading with specific, quantified proof

The site backs its claims with concrete numbers rather than vague superlatives, which is exactly what technical and procurement buyers respond to. This specificity is a real differentiator and should be extended across more products and case studies.

Content Editors reduced time to make changes by 50%

View the page

What to do

  • Keep pairing every capability claim with a measurable outcome.
  • Roll the same quantified style out to the Fusion and Spark product pages.
  • Refresh the figures periodically so they stay current and defensible.

Keep doing

Conversion path

Keep the enquiry path short, with email and phone alternatives

For a ready buyer the path to contact is genuinely low-friction: one click from the hero to a short form, with email and regional phone numbers offered as alternatives. This respects different buyer preferences and is a strength worth protecting as the site evolves.

Need a hand? Let us know how we can help.

View the page

What to do

  • Keep the contact form short — resist adding fields that raise friction.
  • Keep the email address and regional phone numbers visible for buyers who prefer them.
  • Confirm submissions are acknowledged on-screen so visitors know it worked.

Send me a copy of this report

All findings with their tasks, the four visitor journeys and the methodology. We will email it within one business day.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Methodology and limitations

How this review was run

We assessed dataweavers.com the way four different visitors would experience it: a first-time visitor still placing what you do, a buyer ready to make contact, a comparison shopper weighing you against the alternatives, and an automated AI agent reading the site for facts. We reviewed the content and structure of the key pages on the path to an enquiry, and walked that path live in a browser at both desktop (1440×900) and mobile (375×812) widths, scoring it against established Nielsen Norman usability heuristics alongside friction measures such as clicks to goal, scroll depth and form length. We also scored how readable the site is to AI answer engines.

Pages reviewed included the homepage, Plans, Products (Arc for Sitecore), the Products overview, the State Transport Department case study, Book a Demo, Contact, and the site’s robots.txt and sitemap.

This is a UX and content review, not a page-speed or accessibility audit; for performance timings we recommend Google PageSpeed Insights.

  • Homepage (/)
  • Plans (/plans)
  • Products overview (/products)
  • Arc for Sitecore (/products/arc-for-sitecore)
  • State Transport Department case study (/case-studies/dataweavers-state-transport-department)
  • Book a Demo (/book-a-demo)
  • Contact (/contact)
  • robots.txt and sitemap.xml