How a rebuild took MotionLasers' product listing pages from PageSpeed 30 to 90+.
MotionLasers, in Austin, Texas, sells laser systems for productions, events and performances. Its old store was slow and lacked marketing tools. Provis rebuilt the front end in Next.js on the existing PHP backend, and still supports the store.
- Next.js storefront
- PHP backend and APIs
Client: MotionLasersLaser systems, software and accessories · Austin, TexasWhat changed after the rebuild.
PageSpeed scores measured by Provis with Google PageSpeed, before and after the rebuild, on desktop and mobile. Sales and conversions as reported by MotionLasers.
- 30 → 90+
- PageSpeed on product listing pages
- the pages where buyers filter and compare lasers
- 70+
- PageSpeed on the other pages measured
- the home page and product pages included
- Kept selling
- through the switch-over
- URLs kept or redirected, so buyers' links kept working
- More sales
- and conversions since launch
- reported by MotionLasers; the figure itself isn't published
At a glance
- Problem
An old store on deprecated technology: product listing pages scored 30 on PageSpeed, and campaigns were hard to run and measure.
- Solution
A mobile-first Next.js front end, designed in Figma, on the existing PHP backend with its APIs reworked, plus GA4 and Google Ads.
- Result
A faster, mobile-first store on the backend MotionLasers already had. MotionLasers reports more sales and conversions since the new store went live.
- Client
- MotionLasers (motionlasers.com)
- Industry
- Event and stage equipment (laser systems)
- Market
- United States; ships worldwide
- Platform
- Web store, desktop and mobile
- Services
- eCommerce development, speed, analytics and ads set-up
- Built with
- Next.js, PHP, AWS, Figma, Google Analytics 4, Google Ads
- Engagement
- Ongoing: live since late 2024, still supported by Provis
A strong name in the industry, on a decade-old store.
MotionLasers helps buyers find the laser system that fits their space and application, and it had a strong name in the industry. Its store was a decade old, built on deprecated technology, slow to load, and hard to run marketing from. A buyer's route ran like this.
How a buyer reached a laser on the old store
- Ad or searchcampaigns hard to run and measureFixed in 01 below
- Product listingPageSpeed 30Fixed in 02 below
- Product page and checkouton the old, deprecated front endFixed in 03 below
Each step on the old store, and the fix that answered it.
The products were never the problem. It was the store in front of them.
Speed was one problem of four.
Campaigns were hard to measure, the listing pages were slow, the old front end held back every change, and design, development and support were not moving together.
-
Campaigns that were hard to run and measure
The store lacked marketing tools, so campaigns were hard to run and harder to measure.
What Provis builtGoogle Analytics 4 and Google Ads, set up in the buildTracking and ad accounts went in with the new store, so MotionLasers can see which campaigns bring buyers and target the next ones.
-
Product listing pages that scored 30
The listing pages, where buyers filter and compare lasers, scored 30 on PageSpeed, on desktop and on mobile.
What Provis builtServer-rendered pages, lighter images, faster APIsThe listing pages are rendered on the server, images are optimised, and the PHP API responses behind them were reworked to come back faster. PageSpeed was measured before and after, on desktop and mobile.
-
An old codebase on deprecated technology
Product pages and checkout ran on the old front end: every change was slow and risky, and it could not take a modern, mobile-first design.
What Provis builtA new Next.js front end on the existing backendThe whole storefront, checkout included, was redesigned in Figma and rebuilt in Next.js. The Core PHP backend stayed: key components were restructured and new features added, rather than starting again.
-
A store that needed one owner
Improving the store had been slow, with design, development and support not moving together.
What Provis builtOne team, from design to supportProvis ran design, front end, backend, QA and launch, then took on the store's support.
Built in five agile phases.
- PlanSeveral rounds of discussion to agree the problems and the plan
- Design and front endDesigned in Figma, built mobile first in Next.js
- Backend and APIsCore PHP restructured, API logic reworked, new features added
- Test and switch overQA, user feedback and fixes from performance analysis
- Support after launchProvis took on the store's support at launch
-
Plan: several rounds of discussion to agree the problems and the plan.
-
Design and front end: designed in Figma and built mobile first in Next.js, checkout included.
-
Backend and APIs: the Core PHP backend was restructured and its API logic reworked, with new features added.
-
After launch: Google Analytics 4 and Google Ads went in with the new store, and Provis took on the store's support.
The switch-over:
Customers kept buying throughout.
The new front end was built alongside the live store, on the backend MotionLasers already had, so nothing had to be started again.
URLs kept or redirected, so buyers' links and search rankings carried over.
QA and user feedback came before the switch.
How Provis builds online storesThe old store, and the new one.
The old home page as the Internet Archive saved it in September 2024, and the new store, captured on 8 October 2026. Below them: a product listing page, the page type that went from 30 to 90+, and a product page, one of the pages now scoring 70+.
Product listing page · PageSpeed 30 → 90+ · filters, prices and add to cart
Product page · now scoring 70+ · specs, stock and price
Listing page · PageSpeed 30 → 90+
Product page · now scoring 70+
Live, and shipping worldwide.
MotionLasers sells lasers, accessories, software and complete packages on the new store, and ships worldwide.
After launch
Provis still supports it.
The team that rebuilt the store has supported it since it went live in late 2024.
How every Provis project runs
- One project leadyour single point of contact
- A written weekly update and a demoof what was built that week
- A staging link and your repoyou see the work as it is built; the code goes straight into your repo
- QA before launchour QA team tests every feature
- Live until switch-overreplatforming? Your current store, app or platform keeps running until the new one takes over
- Yours from day onecode repo, cloud account and domain in your company's name; our team joins as collaborators, and you can remove access at any time
- Our team works in India, on ISTUTC+5:30: 1.5 hours ahead of Dubai, 4.5 ahead of London (5.5 in winter), 9.5 ahead of New York (10.5 in winter), 10.5 ahead of Austin (11.5 in winter)
Is your store slow, or hard to run campaigns from?
Send us your store's address, or bring your PageSpeed report to the call. We will come back within two working days with an approach, a rough timeline and a rough cost range. No charge, no commitment.
On Shopify, WooCommerce or a custom store? What carries over: a faster front end without replacing the backend, a switch-over that keeps your URLs, and tracking set up in the build.
Running a SaaS product on an older backend? The same pattern: a new front end on the backend you keep, built alongside the live product. Building something new? Get a free MVP estimate.
WhatsApp usSend us a message
indicates a required field