Front End Developer / Full Stack Developer for a marketplace storefront rebuild (Vue Inertia)

Hi, I run a niche marketplace built on Laravel and Vue. It has been live for most of this year - sellers list, buyers pay, payouts go out through Stripe, and the back office has a plan of its own. What has not been touched since launch is the part buyers and sellers actually look at. The storefront and the seller dashboard were built for the first release, quickly and for a desktop screen, and they now hold the product back. Sellers have grown, the catalogue has grown, listings carry more photos than ever, and the pages were never built for that load. More than half of my buyers arrive on a phone, most of them from a search engine and straight onto a listing page. Listing pages are heavy with photos and slow on mobile data. Category pages reload in full every time someone changes a filter. Sellers, who more and more run their shops from a phone, tell me the dashboard only works at a desk. I am not technical - I only see people leave, and I see sellers ask me for a page of their own to send to customers. The terms below are the ones I was given when I asked what was wrong. I am looking for a senior front end developer to rebuild the buyer side and the seller side of the marketplace, starting with a written plan before anything gets built. The back office is being planned separately, so this work is the customer-facing side only, and I want to fund it one stage at a time. What the rebuild has to cover: listing pages fast on a phone - server-side rendering for public pages, a performance budget, Core Web Vitals measured on real visitors the photo gallery - responsive images, lazy loading, swipe and full-screen view, sizes made for a phone rather than the full upload an image pipeline - resized copies generated on upload, existing photos processed once, served through a CDN category browse with filters and sorting that update without a reload, result counts before applying, and a link someone can share public seller storefronts, cut from the first build and requested by sellers ever since a mobile-first seller dashboard - step-by-step listing creation with drafts, photo upload that survives a weak signal, orders and payout status from a phone one component library with design tokens taken from the current brand, so the buyer side and the seller side stop looking like two products SEO on public pages - titles, structured data for listings, clean URLs, a sitemap accessibility I can defend - keyboard navigation, contrast, forms a screen reader can get through checkout working exactly as today, moved onto the same components and checked on small screens What the written plan should give me: every public URL today and what happens to it, so search traffic survives the move the order of work in stages that each ship on their own, with hours per stage how page speed is measured before and after, so I see the change in numbers the backend developer side - what changes in how Laravel serves listings, filters and images the risks, including what happens if the rendering breaks Stack I want to keep: Laravel, Vue 3 with Inertia, Tailwind CSS, MySQL, Stripe. No separate front-end app, no new framework, no redesign from a blank page - the brand and the look stay. What changes is how pages are built and how they behave on a phone. Who I am looking for: someone who has shipped a customer-facing Vue 3 front end on Laravel and Inertia, ideally an image-heavy marketplace or catalogue, with before-and-after page speed numbers. Inertia SSR, Vite, Tailwind, responsive images and component libraries should be familiar ground. I would rather hire a full stack developer than a pure front-end specialist, because part of this sits in how the back end serves the pages, and I do not want it split between two people. Structured data and search visibility for listing pages are a strong plus. The product is live, but the brand and a link stay out of a public post - my sellers read everything I publish. The URL, the repository, the analytics and the current screens go to the person I hire, under NDA, after the contract is signed. Nobody needs access to apply. I am not technical, so I want someone who drives this: the plan first, the build in stages I approve one at a time, and pushback when I ask for something that looks good and slows the page down. Format: 8-12 pages, structured, no fluff. To apply, share: 2-3 Vue or Laravel front ends you have shipped, at least one with public pages that had to be fast on mobile which of the pieces above you would do first and why