EVDevs.com

Portfolio / Case study

Case study · Our own project

A website that sells,
and knows where every lead comes from.

Our own site was a well-written brochure: it explained what we do, and then waited. Between 5 and 8 October 2026 we rebuilt it into a system that sells: every page leads to a next step, every lead arrives with its source, and a visitor can get real findings about their own website before anyone talks about money. 235 pages in two languages, six self-checks, an automated audit with its reports, and a review process: live in four days, because the method and the engineers are experienced, and AI does the repetition.

Professional services · Analytics & attribution · Platforms & migrations · Search & AI visibility · Custom software

New site engine

111/111

Pages proven identical on the new engine (address, text, links and search tags) before anything changed for visitors.

Moved in one day; the old site stayed ready as a fallback.

Lead source

Every lead

Each lead arrives with where the visitor first came from and the latest campaign that brought them back.

In the team email and in analytics, and ready for the CRM.

Free self-checks

6

Ten-question checks with a scored result and an emailed report, each next to its matching service.

Six services, each with its own check.

Mobile speed

72 → 81–87

Google Lighthouse performance score on a phone, after fixing what our own free audit found.

81–87 across runs; desktop 97.

First paint

1.7 s

Time until a phone shows the first content, down from 4.4 s.

Fonts served from our own site and loaded early; main script deferred.

Pages

235

Pages in English and Spanish, each leading to a service, a free check or a conversation.

Every page within two clicks of the home page.

This is EVDevs’ own website, so every figure is ours: from our dated build log and from Google Lighthouse (through PageSpeed Insights) on 8 October 2026. Lighthouse mobile scores vary from run to run, so we give the range. The results that matter most, leads per channel and conversion, don’t exist yet: the funnel went live on 8 October. We will add them here 60–90 days after launch.

What we built, in order

Six pieces,
each with its reason.

1 day

A site engine that can run a funnel

What was missing

  • The site was generated by a script and uploaded by hand, so every change had to go live before anyone could click through it
  • A static generator does badly what a funnel needs: a qualifying form, conversion events, booking, a CRM hand-off, lead magnets and follow-up email

What we built

  • Moved the site to Astro, with content in Markdown and data files whose titles, descriptions, categories and dates are checked at build time
  • Compared every page, old against new: address, visible text, links and search tags. All 111 matched before anything changed
  • Fixed a defect in the old site on the way: titles containing a colon showed stray quote marks
  • Every change now deploys with one command, with private previews to review first
Every lead

Every lead carries its source

What was missing

  • Without a source on each lead, you can’t tell which channel, article or offer produces clients
  • Without a conversion event, analytics can’t say which pages produce leads

What we built

  • Each visit records where it came from: campaign tags or the referring site, plus the first page seen. The first visit and the latest tagged visit are kept, in the visitor’s browser only
  • Each lead emails the team with its need, the page it came from and both sources, and gets an auto-reply in the visitor’s language. The CRM hand-off (contact, score, sources and a note) is built and tested, ready to switch on
  • Analytics records each stage: form opened, form started, lead, check started and completed
  • Links in reports, emails and share buttons carry their own tags, so forwarded reports and outreach can be told apart

Found in testing and fixed before launch: a campaign tag without a medium was being recorded as “direct”.

6

Free self-checks with reports worth forwarding

What was missing

  • Most visitors aren’t ready to talk. With only a contact form, they leave with nothing and we never learn who they were

What we built

  • Six interactive checks in English and Spanish, ten questions each, one per service, placed next to that service on the pages where the intent is
  • The result ranks the gaps by impact, each with a fix and an article
  • “Email me my result” sends a designed report: the top three priorities first, then step-by-step ways to check each gap yourself
  • The report holds no personal data, so it can be forwarded as is
  • The server recomputes the score from the raw answers and writes the email only from the site’s own copy, so the form can’t be used to send spam
2 steps

A free website audit, approved by people

What was missing

  • Our entry offer had to give real findings about a visitor’s own site before any sales talk
  • A fully automatic report, with nobody looking, could send something wrong or be abused

What we built

  • About 50 requests per site plus Google Lighthouse on mobile and desktop, using only what anyone can see on the website
  • Every finding comes with its evidence, in English or Spanish
  • A light summary email that offers the next level: a paid deep audit with the client’s own data
  • Four documents (website check, Lighthouse mobile, Lighthouse desktop, on-page keywords) as private links and PDF attachments
  • Two approval steps in a private admin: the team approves building each audit, then approves sending it
  • Limits of 3 requests a day and 10 a week per email; the free tier runs on free resources only

Sites that can’t be reached never get an automatic answer: they go to the team, to be handled by hand.

2 fields

A form that asks only what it needs

What was missing

  • Every field is a reason to give up: start date, name and message all stood between a visitor and a request
  • The hidden anti-bot field was named “website”. Browsers autofill that name, so real people using autofill were silently dropped

What we built

  • A free audit request needs two things: email and website. Required fields say so
  • The anti-bot field renamed, and bot screening moved to the server
  • No email address printed on pages: leads come through forms that are bot-protected and record the source
  • A limit on form posts per visitor, and a consent banner for visitors in Europe
  • Outgoing mail checked in a real inbox, with the domain’s sender checks passing
1.7 s

A faster site, found by auditing ourselves

What was missing

  • Our own free audit, run on evdevs.com first, found missing security headers and files that blocked the first paint
  • Mobile performance in Lighthouse: 72. First content on a phone after 4.4 s

What we built

  • Security headers added
  • Fonts served from our own site and loaded early; the main script deferred
  • The audit, run again: 0 findings
  • Mobile performance 81–87, first paint 1.7 s; desktop 97; accessibility, best practices and SEO 100

Day by day

Small releases,
each one checked.

5 October · Engine, funnel and launch

A new engine, live the same day.

AreaWhat shippedProof
EngineEvery page rebuilt on the new engine and compared with the old site111 of 111 matched
SourceEvery lead carries its first and latest source; qualifying questions; a thank-you page with a conversion eventA tagged visit traced to its lead
Lead pipelineTeam email and auto-reply in the visitor’s language; CRM hand-off built, ready to switch onTested end to end
Self-checksFirst checks live, with “Email me my result” and a report worth forwardingScore recomputed on the server
Launchevdevs.com switched to the new host; email left where it was115 pages verified over HTTPS

By the end of the first day, the site that used to be uploaded by hand was live on a system that deploys in one command.

6–7 October · The offer, complete

Offers, a method, and a voice for the people who decide.

AreaWhat shippedProof
MethodIngestion → Normalization → Trust → Value → Production, with its own page and a six-post seriesEach stage linked to its case studies
OffersService pages from one template, each with its matching self-check6 services, 6 checks
ReadingA series of guides in plain words, and a “what to ask” box on every technical postFor the people who decide
StructureEvery address under its menu category; header and footer from one definitionTwo clicks from home
TrustPrivacy policy, About page, share images, a bilingual not-found page, RSSPre-launch audit on every page

Every page now leads somewhere: a service, a free check or a conversation.

8 October · The free audit

The entry offer, automated and approved.

  • The free website audit built, tested end to end on the live site: request, approval, report with PDFs, private links
  • “Get a free audit” on the homepage, the revenue recovery service, the revenue leak check and the revenue, search and analytics articles
  • The contact form cut to what it needs
  • Our own site audited first: from security and speed findings to 0
  • Next: leads per channel and conversion, reviewed every Friday, published here 60–90 days after launch

Proven before it shipped

Fast,
because every step was checked.

Our own audit

0

Findings when we ran our free audit on evdevs.com after the fixes

The first run found missing security headers and files that blocked the first paint

Lighthouse

100

Accessibility, best practices and SEO

Desktop performance 97

Launch day

115

Pages in the sitemap, each loaded over HTTPS from the new host after the switch

Email stayed where it was, untouched

Way back

2

DNS records to restore to switch back to the previous site

The old site was kept running as the fallback

Pre-launch audit

Every page

Title, description, canonical, language pair, analytics tag and a single main heading, checked on every page

No broken links, no leftover old addresses, no confidential names

Next step

Every page

Every article, category and case study links to a service and its free check

So no reader reaches a dead end

How we work

  1. Built with AI, reviewed by engineers

    AI wrote much of the code and copy at machine speed; engineers set the rules, reviewed every change and decided what shipped.

  2. Prove each step before the next

    The new engine had to match the old site page for page before it went live. Every page passed an audit before launch.

  3. Ship small, keep a way back

    Small releases, each verified on the live site. The previous site stayed online as the fallback.

  4. Try it on ourselves first

    The free audit ran on evdevs.com before anyone else’s site. What it found, we fixed.

  5. Write it down as it happens

    A dated log of every decision, why it was made and what it changed. This case study is built from it.

The service behind this case

Offer

Website revenue recovery

For sites that used to earn and now do not. A one-month diagnosis first: every cause dated and proven, with its cost, before anything changes.

Self-check

Is your website leaking revenue?

For sites that used to earn: ten questions that show where the money is leaking and what to fix first.

Does your site sell,
or just explain?

Ask for a free audit of your website. You get real findings from what anyone can see, each with its evidence, before anyone talks about money.

Privacy

Talk to an engineer

No sales theater. Tell us where your operation feels slow, repetitive or difficult. An engineer reads every message and replies by email.

Prefer to talk? Pick a 15-minute slot →

Your message goes straight to our engineers.