Prototype Only For prototype purposes only. All content and images are not final and are only here to show what is possible.
SEO / AEO Compare
Performance Analysis

Site Speed Report

Prototype vs. Projected React Build

This Page Loaded In
—
seconds (HTML prototype)
Projected React Load
—
seconds (estimated)
Estimated Improvement
Calculating...
faster load with React + code splitting + image optimization
JSON-LD Schema

Checking for schema blocks on this page...

What improves in the React build (all else equal):
  • Code splitting — only the current page's JS is loaded
  • Image optimization — WebP conversion + lazy loading via React Image
  • CDN caching of static assets via Vercel/Netlify edge network
  • Tree-shaking removes unused CSS and JS from the bundle
  • Prefetching — next pages load before the user clicks

Developer note: Remove this banner and modal entirely from the React production build.

SEO / AEO / Local SEO

Live site vs prototype

How the live www.ncutility.com compares with the redesign prototype on SEO, answer-engine (AEO), and local SEO readiness. Every live finding is sourced; anything we could not check is marked Not verified.

North Central Utility · www.ncutility.com vs the redesign prototype · Audit date 2026-09-27

SEO readiness

58/100
79/100

14 checks. Not verified and excluded: live 1, prototype 0.

AEO readiness

60/100
60/100

5 checks. Not verified and excluded: live 0, prototype 0.

Local SEO readiness

67/100
79/100

10 checks. Not verified and excluded: live 4, prototype 3.

Overall checklist readiness: live site 60/100, prototype 75/100 (29 checks). Opportunity counts as partial credit because the prototype is a review copy; the launch items are listed in the Gap report.

What this redesign unlocks

Every prototype page already has a unique title, a single clear H1, and alt text on its images. The 10 location pages carry the correct physical and mailing addresses, hours, and a tap-to-call number, which is the base that local search and AI assistants need.

What still has to happen at launch is the technical plumbing: robots.txt, a working XML sitemap, canonical tags, and LocalBusiness schema on each location page. Several local items also need the client's Google Business Profile access before they can be verified.

Check
Live site
Prototype
Why it matters

Sources

  • L-HTML: Live homepage HTML capture, www.ncutility.com (browser capture 2026-09-16, Nancy archive raw/home.html)
  • L-ROBOTS: Live robots.txt via WebFetch (2026-09-27)
  • L-SITEMAP: Live /sitemap.xml via WebFetch: HTTP 500 (2026-09-27); /sitemap_index.xml and /wp-sitemap.xml 404 (crawl notes 2026-09-15)
  • L-HOME: Live homepage text via WebFetch (2026-09-27)
  • L-LOC: Live /locations/eau-claire-wi/ via WebFetch (2026-09-27)
  • L-CRAWL: Live crawl notes and discovered-URL list (Nancy archive, 2026-09-15/16)
  • L-MEDIA: Live WordPress media library listing (live-media-all.json, 354 images)
  • L-CRIT: Nancy CRITICAL findings for the live site (references/nancy-critical.md)
  • L-NONE: No live source available: needs client or Google Business Profile access
  • P-HTML: Prototype HTML audit of all 48 root pages (repo main, 2026-09-27)
  • P-LOC: Prototype location pages (10 x locations-*.html)
  • P-GUIDE: Prototype PROJECT_GUIDE.md / SCOPE.md

How to read this. Scores are checklist readiness only (Pass = 2, Needs work or Opportunity = 1, Gap = 0; Not verified is excluded). They are not rankings, traffic, or search-volume estimates, and none are claimed here.

Live findings come from the sources named on each check. Anything we could not check directly is marked Not verified. Prototype items marked "Designed for go-live, add at launch" are technical plumbing (robots.txt, sitemap, schema, canonicals) that belongs on the production domain, not the review copy.