LongTermSoftware.com Live Audit Report

Full report

On this page

Generated UTC: 2026-06-17T00:37:56Z Audited site: https://longtermsoftware.com/ Audit source specification: uploaded prompt treated as controlling requirements.

Evidence limits for this pass

This report is a live-site audit based on the available web renderer and direct parsed route evidence. The renderer confirmed multiple HTML, JSON, and text routes, but the execution environment could not run a full desktop browser session because container DNS resolution for longtermsoftware.com failed. As a result:

• Confirmed: parsed live page content from the web renderer, route redirects exposed by that renderer, visible text, visible links, and several JSON/text assets.
• Not confirmed: screenshots, Lighthouse scores, Core Web Vitals lab metrics, DevTools Network behavior, exact DOM selectors, color contrast, keyboard behavior, mobile reflow, real curl status codes, and form submission/error behavior.
• Do not treat unknowns as passes. Add the tests listed in section 24 before packaging the next theme ZIP.

---

1. Executive Summary

The current production site has moved in the right strategic direction on the homepage: the primary nav is conventional, the hero communicates .NET/SQL modernization without behavioral drift, and the homepage now includes the approved hourly/retainer/C2C pricing ladder language. However, the site is not internally consistent enough for the next WordPress theme package.

The largest risks are:

1. Pricing truth is split. The homepage shows the new ladder, but /services/ and multiple service detail routes still use old fixed-scope pricing. /pricing/ could not be confirmed in this audit renderer.
2. Contact truth is wrong or incomplete. The contact page shows consulting@longtermsoftware.com as fallback and does not expose the expected direct contact profile.
3. Several service-detail pages use stale templates. Four service pages still show old navigation: AI Systems, Downloads, and Assessment.
4. Machine-readable assets are not synchronized. The manifest uses stale contact information and omits pricing routes/assets. Proof exports show older versions than the manifest.
5. Evidence-route reliability is incomplete. proof-ledger.csv, /machine-readable-evidence/, and /route-qa-contract.json could not be confirmed in this pass.

Overall scorecard

---

2. Current Live State vs Expected Site Truth

---

3. Screenshot Catalog

No screenshots were captured in this pass. See screenshots/SCREENSHOTS-NOT-CAPTURED.md.

Required screenshot set for the next pass:

---

4. Route and Link QA

See route-audit.csv and broken-links.csv.

Route audit table

---

5. Homepage and First Impression Review

Confirmed strengths

• The hero clearly says the company modernizes fragile .NET and SQL systems without behavioral drift.
• Above-the-fold trust signals include hourly entry pricing, monthly advisory retainer pricing, .NET/SQL focus, principal-led architecture, review-first AI, and public proof routes.
• Unsupported AI claims are explicitly denied later on the page.

Issues

Proposed rewritten hero copy

Eyebrow: .NET / SQL modernization · reviewed AI workflows · governed knowledge Headline: Modernize legacy .NET and SQL systems without changing business behavior by accident. Subhead: Map hidden rules, preserve production behavior, and introduce AI only behind source-bound evidence, human review, and clear release gates. Primary CTA: Book a 20-minute fit call Secondary CTA: Compare pricing options Trust strip: $150/hour ad-hoc · $2,000/month advisory · SQL/Web Forms/Classic ASP/VB.NET · no autonomous production authority

Proposed homepage section order

1. Hero with primary CTA and compact trust strip.
2. Problem: hidden rules, AI output risk, proof pressure.
3. Pricing path: four options and non-accumulative retainer note.
4. “Choose your starting point” service cards.
5. Fit-call / diagnostic bridge.
6. Proof status key.
7. Three buyer-readable case templates.
8. Process summary.
9. Resource links.
10. Trust boundaries and footer.

---

6. Header, Navigation, and Search Review

Pass/fail matrix by observed route group

Recommended CSS/header fixes

• Use a single header.php source for every virtual/service page; remove old nav arrays from service-detail renderers.
• Add route QA assertion: exact header link text sequence equals Services | Proof | Industries | Resources | About | Contact on every public HTML route.
• Add Playwright viewport checks at 1366x768, 1280x800, 1024x768, 768x1024, 390x844, 375x667, 320x568.
• Search input should have exactly one accessible name. Current parsed output suggests label duplication: Search LongTermSoftware.com Search.

---

7. Pricing Page Review

Pricing consistency table

Specific pricing recommendations

• Rebuild /pricing/ with four cards:

1. Ad-hoc architecture help: $150/hour, no minimum.
2. Monthly advisory retainer: $100/hour, 20-hour monthly minimum, $2,000/month.
3. Annual modernization retainer: $80/hour, 40-hour monthly minimum, $3,200/month, annual contract.
4. Embedded architect C2C: $75/hour, 40 hours/week, six-month minimum, limited availability.

• Put Monthly Advisory or Annual Modernization in the “recommended/practical default” visual frame. Do not overpromote C2C.
• Add exact note: Retainer hours are reserved monthly capacity. Unused hours do not roll over, accrue, bank, or carry forward unless a signed order form says otherwise.
• Add route QA parity tests comparing /pricing/, /downloads/pricing-ladder.json, /wp-json/lts/v1/pricing, /wp-json/lts/v1/pricing-consistency, llms.txt, manifest, and FAQ.

---

8. Contact and Fit-Call Review

Contact consistency table

Form UX issues

---

9. Services UX Review

Recommended service-card structure

1. Buyer problem — one sentence.
2. Best fit — role/team/system profile.
3. Typical timeline — range or monthly capacity.
4. Pricing path — ad-hoc/retainer/fixed-scope/C2C applicability.
5. Deliverables — 3–5 concrete outputs.
6. Proof route — specific link label.
7. Next step — primary fit-call CTA; secondary resource/proof link.

---

10. Proof, Case Studies, and Sample Artifacts Review

Proof maturity assessment

The proof system is a relative strength. /proof/ acts like a claim-to-evidence ledger, /case-studies/ clearly states narratives are public-safe templates until approved outcomes exist, and /sample-artifacts/ explicitly says templates contain no client data and do not imply production outcomes.

Template-vs-outcome boundary assessment

Top 5 proof improvements

1. Replace repeated Open route link labels with descriptive proof link text.
2. Add a one-line “why this matters to CTO/CIO/procurement” summary to each proof card.
3. Add approval-state badges with definitions linked to the proof status key.
4. Add “what this does not prove” boundary per claim.
5. Keep machine-readable proof but make it clearly secondary for humans.

Recommended proof-card format

Claim: Preserve business behavior during .NET / SQL modernization
Evidence route: Legacy modernization parity proof route
Status: Public-ready template
Controls: comparison screens, parity tests, SQL rule inventory, rollback note
What this proves: method and artifact shape
What this does not prove: client-specific metric or approved outcome
CTA: Open legacy-modernization proof route

---

11. Resources and Downloads Review

Resource inventory table

Recommended resource taxonomy

• Decide fit: Fit call, diagnostic, pricing, FAQ.
• Understand risk: AI readiness checklist, modernization risk review, human-reviewed AI checklist.
• Evaluate proof: proof ledger, case templates, sample artifacts.
• Share internally: proposal packet, proof packet, service one-pagers.
• Machine-readable: llms, manifest, route QA, pricing/service/proof JSON.

---

12. Browser-Local Diagnostic Review

Confirmed text-level findings

• The diagnostic page explicitly says pasted text is not submitted to the server.
• It says no model call is made from the page.
• It warns against secrets, credentials, PHI, source code, and confidential production data.
• It frames output as triage, not final architecture advice.

Not verified

• Network tab behavior after sample input.
• Whether only static assets load.
• Whether result is copyable/exportable.
• Whether CTA appears after result.
• Whether mobile input is usable.

Recommendations

• Add a Use sample input button that inserts the safe sample text from the audit prompt.
• Add local result sections: Likely service path, Risk signals, What not to paste, Recommended next step.
• Add Copy result and Download sanitized summary buttons.
• Track only metadata: diagnostic_start, diagnostic_complete_local, diagnostic_result_cta_click. Never send pasted text.

---

13. Machine-Readable UX and AI-Agent Readiness

Machine-readable consistency table

Recommended JSON/schema fixes

• Generate all files from a single site_truth object.
• Include generated_utc, version, status, contact, pricing, proof_status_key, unsupported_claims, and public_routes in every relevant file.
• Add machine-readable pricing_non_accumulative_note.
• Make manifest include /pricing/, /downloads/pricing-ladder.json, /downloads/service-packages.json, and the pricing REST endpoints.
• Add route QA checks that compare text markers across HTML, JSON, REST, and AI-reader files.

---

14. Accessibility Review

Accessibility table

---

15. Mobile and Responsive UX Review

Viewport table

Because browser rendering was unavailable, this is a test plan/status table, not a visual pass/fail table.

---

16. SEO and Index Hygiene

Search observations

The required site: searches returned no visible results in the available web search for:

• site:longtermsoftware.com hello world
• site:longtermsoftware.com pricing
• site:longtermsoftware.com contact
• site:longtermsoftware.com downloads
• site:longtermsoftware.com "consulting@longtermsoftware.com"
• site:longtermsoftware.com "AI for systems that cannot break"
• site:longtermsoftware.com "LongTermSoftware.com"

This does not prove the site is unindexed, but it is enough to require Search Console verification.

SEO defect table

Recommended title/meta rewrites

---

17. Performance and Technical UX

Lighthouse/performance status

Lighthouse was not run. See lighthouse/LIGHTHOUSE-NOT-RUN.md.

Manual/text-level performance risks

• Multiple pages include large raster image assets according to manifest paths; verify responsive srcset, dimensions, lazy loading, and WebP/AVIF variants.
• Docs page states constraints: no external font files, no jQuery/Bootstrap/Tailwind/Popper/Angular Material frontend payload. These must be validated with network/resource scans.
• Diagnostic must work without remote calls after initial static asset load.

Headers/caching recommendations

• Add cache-busting/versioning for theme CSS/JS/assets.
• Add route QA stale-content assertions after redirects.
• Verify CDN/server cache purges on aliases such as /hello-world/.
• Use immutable caching for versioned static assets; no-cache or short cache for machine-readable truth files during launch.

---

18. Security and Privacy

---

19. Content and Messaging

Strong copy examples

Weak copy examples and rewrites

---

20. Severity-Ranked Findings

---

21. Implementation Backlog

---

22. Exact Copy Recommendations

Pricing non-accumulation note

Retainer hours reserve monthly senior architecture capacity. Unused hours do not roll over, accrue, bank, or carry forward unless a signed order form says otherwise.

Contact card

Principal contact
Mike Kappel
mike@ns12.com
(708) 230-2304
Cicero, IL

Pricing card copy

Ad-hoc architecture help
$150/hour · no minimum
Best for targeted legacy-system, SQL, architecture, or AI workflow questions before a larger engagement.
CTA: Book a fit call

Monthly advisory retainer
$100/hour · 20-hour monthly minimum · $2,000/month
Best for teams that need recurring senior review, backlog shaping, and modernization/AI governance support.
CTA: Discuss monthly advisory

Annual modernization retainer
$80/hour · 40-hour monthly minimum · $3,200/month · annual contract
Best for sustained modernization, parity mapping, release planning, and reviewed AI workflow delivery.
CTA: Discuss annual capacity

Embedded architect C2C
$75/hour · 40 hours/week · six-month minimum · limited availability
Best only when LongTermSoftware is a strong mutual fit for embedded architecture capacity.
CTA: Check availability

Diagnostic result CTA

This local triage suggests the best first step is a .NET / SQL Modernization Blueprint discussion. Copy this sanitized summary and book a 20-minute fit call. Do not include secrets, credentials, PHI, source code, or confidential production data.

---

23. Theme/File Change Recommendations

---

24. Tests to Add to Route QA

1. GET /pricing/ returns 200, canonical /pricing/, H1 contains pricing, and four card labels/rates match expected.
2. GET /contact/, /fit-call/, footer, manifest, llms, schema, and REST contact-profile contain Mike Kappel, mike@ns12.com, (708) 230-2304, Cicero, IL.
3. All public HTML routes have header nav sequence Services, Proof, Industries, Resources, About, Contact.
4. No public route contains stale nav labels AI Systems or Assessment in primary nav.
5. No public service page contains stale fixed-scope-only markers unless explicitly labeled as fixed-scope example.
6. Retainer pages include non-accumulative language.
7. /downloads/pricing-ladder.json, /downloads/service-packages.json, REST pricing, llms, manifest, and pricing HTML match exact values.
8. /downloads/proof-ledger.csv returns 200 and parses with same row count as JSON.
9. /route-qa-contract.json returns 200 application/json and validates schema.
10. /machine-readable-evidence/ returns 200, links AI-reader files, and is human-readable.
11. Old aliases redirect to current routes and response bodies contain current markers.
12. site_truth_snapshot.version equals manifest/llms/proof exports unless intentionally versioned with compatibility notes.
13. Forbidden claims test: no AGI/consciousness/certification/formal partnership/guaranteed compliance/autonomous production authority claims.
14. Playwright viewport test asserts no horizontal scroll at 320px and header does not wrap incorrectly.
15. Keyboard test tabs through skip link, logo, nav, search, CTA, form fields, diagnostic controls.
16. Diagnostic network test asserts pasted input is not sent in request payload/query/body/beacon.
17. Lighthouse CI budgets for homepage/pricing/contact/diagnostic mobile.
18. Link-purpose test flags repeated generic labels: Open route, Read more, Click here, Open resource.
19. PDF landing-page test confirms every PDF has an HTML equivalent.
20. Security smoke test checks HTTPS, HSTS, content-type options, referrer policy, and security.txt.

---

25. Final Recommendation

Do not package the next WordPress theme ZIP until the pricing, contact, stale service templates, and machine-readable synchronization defects are fixed. The homepage direction is strong enough to preserve, but the site currently sends conflicting signals to buyers and AI evaluators.

Minimum release gate:

• /pricing/ confirmed and synchronized.
• Direct contact truth visible and machine-readable.
• All service detail pages use current header/nav/CTA and pricing posture.
• Machine-readable files regenerated from one truth source.
• Route QA covers pricing/contact/proof/diagnostic/viewport/stale redirects.
• Screenshots and Lighthouse artifacts captured from a browser-capable environment.

---

26. Prompt for the next AI theme-build pass

You are building the next LongTermSoftware.com WordPress theme ZIP. Use the live audit findings below as implementation requirements.

Current live findings:
- Homepage direction is good: conventional nav, behavior-preserving .NET/SQL modernization hero, fit-call CTA, proof boundaries, and updated pricing ladder language.
- /pricing/ was not confirmed in audit tooling and must be treated as a critical route to implement/test.
- /contact/ shows consulting@longtermsoftware.com and omits the approved direct contact profile.
- /services/ and service detail pages still show old fixed-scope pricing such as $15k, $30k, $55k, $75k, $95k, $60k, and $45k/quarter.
- Four service detail pages use stale nav: Services, AI Systems, Case Studies, Proof, Downloads, Assessment, Contact.
- llms.txt and ai-agent-manifest.json exist, but manifest contact is stale and pricing routes/assets are missing.
- proof-ledger.json exists but version is behind manifest; proof-ledger.csv and route-qa-contract.json must be verified/fixed.
- /diagnose-system/ has good local-only privacy text, but local network behavior, copy/export result, and post-result CTA must be implemented/tested.
- Search/SEO, screenshots, Lighthouse, accessibility, and security headers need browser/CI verification.

Top 10 implementation priorities:
1. Implement /pricing/ with the exact four-tier pricing ladder.
2. Add non-accumulative retainer hours language anywhere retainers appear.
3. Replace all stale fixed-scope-only service pricing with the approved pricing path.
4. Normalize header/nav/search/fit-call CTA across every public route.
5. Update contact truth everywhere: Mike Kappel, mike@ns12.com, (708) 230-2304, Cicero, IL.
6. Regenerate llms.txt, llms-full.txt, ai-agent-manifest.json, .well-known/ai-plugin.json, pricing-ladder.json, service-packages.json, proof-ledger exports, and REST endpoints from one site_truth object.
7. Fix /machine-readable-evidence/, /route-qa-contract.json, /downloads/proof-ledger.csv, and all REST endpoints.
8. Improve proof/accessibility link labels and card heading hierarchy.
9. Improve diagnostic with sample input, local result, copy/export, and post-result fit-call CTA without sending pasted text.
10. Add Playwright/Lighthouse/route QA tests for routes, redirects, pricing/contact parity, viewports, accessibility, and forbidden claims.

Exact routes/files to change:
- header.php, footer.php, front-page.php, templates/virtual-page.php
- inc/content.php, inc/forms.php, inc/schema.php, inc/rest.php, inc/enhancements-v*.php
- assets/css/app.css, assets/js/app.js
- route-qa-contract.json, tools/route-qa.py
- llms.txt, llms-full.txt, ai-agent-manifest.json, .well-known/ai-plugin.json
- downloads/pricing-ladder.json, downloads/service-packages.json, downloads/proof-ledger.json, downloads/proof-ledger.csv, downloads/conversion-event-taxonomy.json
- docs/*, .uai/*

Pricing acceptance criteria:
- Ad-hoc: $150/hour, no minimum.
- Monthly advisory: $100/hour, 20-hour monthly minimum, $2,000/month.
- Annual modernization: $80/hour, 40-hour monthly minimum, $3,200/month, annual contract.
- Embedded architect C2C: $75/hour, 40 hours/week, six-month minimum, limited availability.
- Retainer hours do not roll over, accrue, bank, or carry forward unless a signed order form says otherwise.
- Monthly Advisory or Annual Modernization is visually framed as the practical/default path. C2C is limited availability, not default.

Contact acceptance criteria:
- HTML, footer, fit-call, schema, llms, manifest, REST contact-profile all show Mike Kappel, mike@ns12.com, tel link for (708) 230-2304, Cicero, IL.
- consulting@longtermsoftware.com is not the primary public contact unless explicitly retained as secondary.

Claims not to make:
- No AGI, consciousness, safety certification, formal vendor partnership, guaranteed compliance, autonomous production authority, unreviewed production outcomes, unsupported client metrics, or private-network probing authority.

Automated tests to run:
- route QA for all listed routes and old aliases.
- pricing/contact HTML vs JSON vs REST vs AI-reader parity.
- Playwright screenshots at 1440x900, 1366x768, 1280x800, 1024x768, 768x1024, 390x844, 375x667, 320x568.
- Lighthouse mobile/desktop for home, pricing, contact, diagnostic.
- axe accessibility checks plus keyboard-only header/menu/search/forms/diagnostic.
- diagnostic network test proving pasted input is never transmitted.
- broken internal link scan and content-type checks.
- sitemap/robots/security.txt checks.

Final response requirements:
- Provide a WordPress theme ZIP.
- Provide updated route-audit results, screenshots, Lighthouse outputs, and changed-file summary.
- Clearly separate confirmed fixes from items needing WordPress admin, analytics/Search Console, server/CDN access, or human approval.