Example package
Speed audit
Your five most important pages tested, with a ranked list of what to change and the expected gain.
You get
- Tests on mobile and desktop
- Ranked list of causes
- Effort for each change
- Written report
Sound familiar?
What we hear from businesses before a project like this starts.
- Google Search Console says our pages fail Core Web Vitals.
- The site takes several seconds to load on a phone.
- We installed a speed plugin and it broke the layout.
- Our ads are paying for clicks that leave before the page appears.
- Every app and plugin we added made the store a little slower.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
Pass Core Web Vitals
Largest Contentful Paint, layout shift and responsiveness measured on real pages and brought into the green where the platform allows.
02
Faster mobile pages
Images resized and compressed, fonts and scripts loaded only where needed.
03
A leaner Shopify store
Unused app code removed from the theme and heavy sections rebuilt.
04
A leaner WordPress site
Plugins audited, caching set up properly, and the database cleaned.
05
Better hosting or a CDN
A recommendation, and the move if wanted, when the server is the real bottleneck.
06
Proof it worked
The same tests run before and after, on the same pages, so the result is measured rather than claimed.
Tools that come up most: PageSpeed Insights, Lighthouse, WebPageTest, Search Console, Cloudflare, WordPress caching plugins, Shopify theme code and image CDNs.
What you get
Concrete pieces, each one something you can open and check when it's done.
A speed audit
Your key pages tested, with the biggest causes of slowness ranked by impact.
Lighthouse, WebPageTest, Search ConsoleImage and media work
Modern formats, correct sizes and lazy loading for everything below the fold.
WebP and AVIF, responsive imagesScript and font clean-up
Third-party scripts deferred or removed, fonts subset and preloaded.
Theme code, tag managerCaching and CDN
Page and asset caching configured, and a CDN added where it helps.
Cloudflare, caching pluginsTheme and template changes
Heavy sections rebuilt so they render faster without changing how they look.
Liquid, PHP, HTML and CSSA before and after report
The same measurements repeated on the same pages after the work.
Report, screenshotsTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Core Web Vitals pass
The changes made on a staging copy, checked, then applied to the live site.
You get
- Audit of key templates
- Images, scripts and fonts optimized
- Caching configured
- Before and after report
Example package
Shopify store speed
App leftovers removed and heavy theme sections made lighter.
You get
- Theme code audit
- Unused app code removed
- Sections optimized
- Before and after scores
Example package
WordPress speed and clean-up
Plugins, caching and database tidied for a faster, more stable site.
You get
- Plugin audit and removal list
- Caching and CDN set up
- Database cleaned
- Before and after scores
How we approach it
The habits that keep this kind of project from going wrong.
1
Measure first
We test before changing anything, so every change is chosen by its measured effect.
2
Staging before live
Changes are made and checked on a copy of the site before they reach customers.
3
Looks the same
The goal is a faster page that looks and works exactly as it did, unless you ask for changes.
4
Numbers, not adjectives
The handover report shows the same tests before and after.
How we work
A written scope first, then working progress you can check, then a proper handover.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- Which platform the site runs on
- How many templates or page types
- How many third-party scripts and apps
- Whether hosting needs to change
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
Questions people ask first
Can you guarantee a perfect score?
No one honestly can; some platform and third-party code is outside anyone's control. We tell you after the audit what is realistic for your site.
Will my site look different?
No, unless you ask for it. Changes are checked on a staging copy against the current site first.
Do you need my login?
We need admin or theme access for the platform, added as a separate user you can remove at handover.
Will it help my Google ranking?
Page experience is one of many signals. A faster site mainly helps visitors stay; any ranking effect is a bonus, not a promise.
How long does it take?
An audit takes a few days; the full optimization one to two weeks from the signed scope.
What happens after handover?
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com