I make Web3 and fintech sites load fast and show up in AI answers.
Whether you have a site or a blank domain, I make it load fast, show up in ChatGPT and Claude, and sit on the right platform for your team.
Before and after, on sites I shipped.
35 97
Mobile PageSpeed
Median across the last five projects
4.1s 1.2s
Largest contentful paint
Moto G4, 4G throttled
14
Sites optimized
Since 2022
You landed here for one of four reasons.
Your site takes four seconds to load.
A visitor on a phone waits, gives up, and taps back to the search results. You paid to get that person to the page, and you lose them before your product appears.
ChatGPT and Claude cannot see you.
You ask an AI about your own category and it names three competitors. Your pages carry no structure a model can lift an answer from, so the model quotes someone who does.
You vibe coded it, and it broke.
The site went live in a weekend and looked fine at launch. Traffic grew, the content piled up, and the pages started to buckle under both.
You have no site yet, and you need one.
You are launching, or the current page is a form and a logo. You want a site built right the first time, fast on a phone and readable to an AI from day one, instead of one you pay to fix a year later.
Four ways I make a site earn its traffic.
You name the problem. I take the work from first measurement to shipped result, and I send you the numbers when it lands.
Performance optimization
I strip render blocking scripts, compress your hero media, and cut the JavaScript your visitors download without ever running. You get a mobile score above 90 and a page that paints before a thumb reaches the scroll.
Answer engine optimization
I structure your pages so ChatGPT, Claude, Perplexity, and Google AI Overviews can lift a clean answer out of them. You land inside the answer with your name on it, instead of on page two of a link list.
Migration into Webflow
Your marketing team waits on an engineer to fix a typo. I move the site into Webflow, map every URL before anything changes, and hand your team a CMS they run without a ticket.
Migration out of Webflow
You outgrew the platform. I rebuild your site as code your team owns, keep the design you paid for, keep the URLs that earn traffic, and hand your engineers a repo.
From audit to measured result, in four steps.
Audit
I profile your site on a real phone and list what costs you speed, traffic, and visibility.
Plan
You get a fix list ranked by what each line earns, with the effort it takes next to it.
Ship
I do the work in Webflow or in code, and you review all of it on a staging URL first.
Measure
I run the same tests again and send you the before and after, with the raw reports.
You work with me, from the first email to the last test.
I read your first message, run the audit, optimise your website, and send you the before and after. No account manager sits between us and no handoff loses the detail you mentioned on the first call. I have built in Webflow since 2022, and I reach for custom code when a project earns it.
Mateja Velinovic, founder of WaveWeb. LinkedIn
Answers before the first call.
The questions teams ask most, answered without the sales detour.
Yes. If you have nothing yet, or a landing page holding the spot, I build the site from the ground up in Webflow or in code, and it ships fast on a phone and readable to an AI on day one. Most of my work is still sites that already exist and underperform, and that experience is what a new build gets you.
90 or above on mobile. Most Web3 landing pages I audit score between 40 and 65. The causes repeat: uncompressed hero video, wallet connect scripts loading before anything renders, animation libraries pulled in on every page. All three get fixed without touching the design.
SEO puts you in Google’s ranked list. AEO gets you quoted inside the answer that ChatGPT, Perplexity, and Google AI Overviews write. The work overlaps, though AEO leans harder on structured data, semantic HTML, and content shaped so a model can lift a clean answer out of it.
Both. I have built in Webflow since 2022, and I use Ship Studio with Claude Code where the project calls for code I own outright. The tool follows the project. Agencies that sell one stack will recommend that stack no matter what you need.
By who edits the site after launch. A marketing team shipping pages every week belongs in Webflow. A product team with engineers who own the repo belongs in custom code. Traffic, CMS depth, and budget move the answer around, but that one question settles most projects on the first call.
Not when the redirect map holds. Ranking drops after migration trace back to broken URLs, dropped metadata, and pages that vanish without a replacement. I map every existing URL before anything moves, keep the structure that earns traffic, and watch Search Console through the first month.
I do. WaveWeb stays small on purpose, so you talk to the person writing the code instead of an account manager passing messages along. When a project needs a designer or a second developer, I bring one in and keep responsibility for the result.
Tell me about your site.
Send the URL and the part that bothers you. I reply within a day with what I would fix first.