We migrated a Jimdo site to Neleto with a few Claude prompts, and the Lighthouse scores tell the whole story
A Jimdo one‑pager was migrated to Neleto using Claude and the MCP connector. The initial build improved performance but dropped accessibility. Targeted prompts fixed four accessibility issues, raising the score to 99/100. The process shows how owning the stack can deliver fast, high‑quality migrati…
A small business website built on Jimdo—a popular hosted site builder—was migrated to Neleto, a component‑driven CMS, using only natural‑language prompts sent to Claude. The migration was quick, but Lighthouse revealed an accessibility regression that had to be addressed. After a few targeted prompts, the site achieved a near‑perfect 99/100 score across all Lighthouse categories.
Why the Migration Matters
Hosted builders like Jimdo offer ease of use but lock users into a stack that is difficult to audit or modify. When a site needs to meet modern performance and accessibility standards, the lack of control can become a bottleneck. Neleto, on the other hand, exposes every component and style to the content editor, allowing rapid iteration and precise fixes.
Baseline Performance on Jimdo
Before any changes, the live Jimdo site was evaluated with Lighthouse on a desktop machine. The results were:
- Performance: 88
- Accessibility: 88
- Best Practices: 100
- SEO: incomplete
- LCP: 1.9 s
- FCP: 1.3 s
- Total page weight: ~1.18 MB
While the performance score was acceptable for a small business, the LCP and accessibility metrics indicated room for improvement. The SEO category was incomplete, a common issue with hosted builders that hide underlying code.
One Prompt, a Full Site Build
The migration began with a single, pre‑crafted prompt that instructed Claude to replicate the Jimdo site 1:1 on Neleto. The prompt leveraged a headless Chrome instance to capture screenshots and extract computed styles—font families, sizes, colors, spacing, and more—ensuring visual fidelity. It also instructed the system to create a single layout, one component per section, and one page per route, making every piece editable without touching code.
Claude communicated with Neleto through the MCP connector, a stateless JSON‑RPC endpoint. This allowed the entire build—layouts, components, pages, and content—to be created via a natural‑language interface, mimicking the workflow a developer would normally use.
Initial Lighthouse Results After Migration
After the first build, Lighthouse was run again on the Neleto staging domain. The metrics improved dramatically in most areas:
- Performance: 97 (+9)
- Accessibility: 81 (down from 88)
- Best Practices: 100
- SEO: 100 (complete)
- LCP: 1.1 s (nearly halved)
- FCP: 0.7 s (improved)
The drop in accessibility was unexpected. Lighthouse flagged four specific issues, confirmed by axe‑core:
- Missing
langattribute on thehtmlelement. - Form input without an associated label.
- Heading hierarchy not in sequential order.
- Insufficient color contrast between text and background.
These are common accessibility pitfalls that can slip through visual cloning, as pixel‑perfect replication does not guarantee semantic correctness.
Fixing the Accessibility Regression with Targeted Prompts
Because Neleto exposes every component and style, each issue could be addressed with a concise prompt:
- Add the
langattribute to the layout to inform screen readers that the page is in German. - Associate a label with the form input by editing the relevant component.
- Adjust heading levels to follow a logical descending order.
- Increase text color contrast, while preserving brand colors by requesting approval before changes.
Within twenty minutes, the final Lighthouse run produced the following scores:
- Performance: 99
- Accessibility: 100
- Best Practices: 100
- SEO: 100
- LCP: 0.9 s
- FCP: 0.5 s
- Total Blocking Time: 0 ms
- Cumulative Layout Shift: 0
The site now loads in roughly a third of the time it did on Jimdo, and the accessibility score is perfect—something that would have required manual code changes on a hosted platform.
What This Means for Site Owners
The migration demonstrates that owning the stack can deliver fast, high‑quality results. The entire process—from initial build to final audit—was completed in a single afternoon, with no hand‑coding or builder UI required. The key takeaways are:
- Visual cloning can expose hidden accessibility issues that need to be addressed.
- Component‑driven CMSs allow targeted, minimal edits that preserve brand integrity.
- AI prompts can automate the heavy lifting while leaving critical decisions to the human editor.
For anyone still on a hosted builder like Jimdo, Wix, or Squarespace, this case study shows the potential benefits of moving to a stack you control. The process is straightforward, the results measurable, and the long‑term maintenance easier.
Next Steps
If you’d like to see a similar migration for your site, simply reply with your URL. We’ll run the before‑and‑after Lighthouse reports, including any broken audits, and share the results. Start free at neleto.io, the only CMS with a native MCP server hosted in the EU.
Why it matters
Owning the underlying stack lets site owners fix accessibility and performance issues quickly, turning a hosted builder’s limitations into a competitive advantage.
Key points
- Jimdo baseline scored 88 on performance and 88 on accessibility. Neleto build improved performance to 97 but dropped accessibility to 81. Four accessibility issues were identified and fixed with targeted prompts. Final Lighthouse scores: 99/100/100/100. The migration took under two hours and required no hand‑coding.
Frequently asked questions
What is Neleto?
Neleto is a component‑driven CMS that exposes every element of a site to the editor, allowing rapid iteration and precise control over design and content.
How does the MCP connector work?
The MCP connector is a stateless JSON‑RPC endpoint that lets AI agents like Claude create, update, and manage Neleto content through natural language prompts.
Can I keep my existing domain?
Yes, once the site is fully built on Neleto you can point your domain to the new hosting environment without downtime.
