Improving Engineering Strength

Is the digital platform technically strong, performant, accessible and resilient?

What this dimension measures

Engineering Strength evaluates performance, crawlability, indexation control, rendering, stability and security — the delivery layer everything else depends on.

Why it matters

Technical faults cap the ceiling of every other dimension: uncrawled content cannot rank, and unrendered content cannot be read by anything.
Performance is a direct conversion variable, most sharply on mobile networks.
Rendering strategy determines whether AI crawlers, many of which execute little or no JavaScript, see the content at all.

What strong looks like

Core Web Vitals passing at the 75th percentile on real-user data.
Primary content present in the server-rendered HTML.
Clean crawl: correct status codes, canonicals, sitemaps and robots directives.
Valid certificates, secure headers, and no mixed content.

Common failures

Client-only rendering that hides substantive content from crawlers and AI retrieval.
Uncontrolled parameter and faceted URLs generating crawl waste.
Large unoptimised media dominating load.
Broken canonicals, redirect chains and stale sitemaps.

Relevant professional practices

Front-end engineering and accessibility. These are reference disciplines and evidence inputs — they are not separate scores.

Practice lens: Engineering & Accessibility

Who typically owns it

How Brand & Signal evaluates it

Field and lab performance measurement across templates.
Crawlability, indexation and status-code health.
Server-rendered versus client-rendered content parity.
Sitemap, robots and canonical correctness.
Transport security and header configuration.

Score 3: Substantive content depends on client-side rendering; obvious accessibility failures on primary templates.
Score 5: Pages render, but Core Web Vitals fail on mobile and keyboard paths break in places.
Score 7: Vitals pass on most templates; accessibility issues are isolated rather than structural.
Score 9: Server-rendered content, vitals passing across templates, and no blocking accessibility failures on any primary path.

How to improve it

Server-render or pre-render substantive content; treat JavaScript as enhancement.
Fix the largest contentful element first — usually an image or a font.
Resolve crawl waste before adding new content.
Automate a crawl and vitals check on every release.

Test it yourself

Disable JavaScript and reload your three most important pages — is the content still there?
Run a mobile Lighthouse pass and record LCP, INP and CLS.
Tab through a form end to end without touching the mouse.
Check colour contrast on body text and buttons against WCAG 2.2 AA.

Evidence and sources

Field performance data and lab audits
Full-site crawl and log-level status analysis
Rendered versus raw HTML comparison
Robots, sitemap and header inspection

Related dimensions

Read the dimension in full Score your site