Example package
Fix list
Your list of broken things repaired in one pass.
You get
- Each issue reproduced and repaired
- The cause written down for each
- Tested on mobile and desktop
- A backup taken before changes
Sound familiar?
What we hear from businesses before a project like this starts.
- The contact form stopped sending and we only noticed because a customer called.
- The site looks fine on desktop and falls apart on a phone.
- A plugin update broke the layout and our developer is gone.
- Google says our pages are slow and our ads cost more because of it.
- Our emails from the website go to spam.
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
Broken links, buttons and forms across several pages
Each one found, repaired and tested, with form submissions checked end to end.
02
Mobile layout fixes
Pages checked on real phone sizes and repaired so nothing overlaps or runs off the screen.
03
Small changes to an existing site
Image replacements, section changes, favicon, spacing and copy updates in the builder you already use.
04
Speed and Core Web Vitals
Measured, then improved with image, caching, plugin and script changes.
05
Email deliverability
SMTP set up properly with SPF, DKIM and DMARC, so form and order emails arrive.
06
Errors after updates or migrations
White screens, plugin conflicts and broken pages traced to the cause and repaired.
Tools that come up most: WordPress, Elementor, Divi, WooCommerce, Shopify, Webflow, Squarespace, Wix, SMTP, Cloudflare, Google Search Console.
What you get
Concrete pieces, each one something you can open and check when it's done.
Form fixes
Forms that submit, arrive, and go where they should, including CRM and email connections.
Form plugins, SMTP, webhooksLayout and mobile fixes
Pages repaired on phone, tablet and desktop.
Builder settings, CSSSpeed fixes
Images, caching, scripts and plugins sorted, measured before and after.
Lighthouse, PageSpeed Insights, caching pluginsEmail deliverability
SMTP and DNS records set up so site emails reach inboxes.
SPF, DKIM, DMARC, SMTP servicesUpdates and conflicts
Core, theme and plugin updates done safely, with conflicts repaired.
Staging sites, backupsSmall changes
Copy, images, sections and settings changed in the builder you already use.
Elementor, Divi, Webflow, Squarespace, WixTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Mobile clean-up
Every key page made to work properly on phones.
You get
- Pages checked at common phone and tablet sizes
- Layout, menu and button fixes
- Forms tested on mobile
- Before and after screenshots
Example package
Speed pass
A measured speed improvement on your most important pages.
You get
- Before and after measurements
- Images, caching and scripts sorted
- Unused plugins removed with your approval
- A list of anything left and why
Example package
Email that arrives
Website and form emails set up to reach inboxes.
You get
- SMTP service connected
- SPF, DKIM and DMARC records set
- Test emails checked in major inboxes
- Notes on what was changed in DNS
Example projects
Website speed and bug fixes for a craft brewery
Copperline Brewing's website was slow on phones, its menu didn't open in iPhone Safari, and contact-form emails went to spam. An age-gate popup was also blocking Google from indexing the site. We worked through a fix list over two weeks and took the mobile Lighthouse performance score from 31 to 96. Images were converted and resized, render-blocking scripts were deferred, layout shift was repaired and the site moved fully to HTTPS. Email authentication was set up so form mail gets delivered.
- Mobile menu rebuilt and tested on iOS and Android
- Performance: page weight 11.2 MB → 1.4 MB, LCP 7.9 s → 1.6 s
- Crawler-safe age gate, so pages are indexed again
- SPF, DKIM and DMARC for reliable form email
WordPress, PHP, JavaScript, CSS, Cloudflare, Google Search Console, Lighthouse
Sample build
A working example we built to show this kind of work. It is a demonstration, not a client project.
Sample build
Website bug fixes: before and after
A small business site with four common bugs repaired: plan cards overflowing the layout on desktop and mobile, a mobile menu that throws a JavaScript error, a broken image path and a contact form that silently fails. Each bug is documented with its cause and fix, the full diff is included, and a headless-browser check confirms 0 console errors and 0px sideways overflow after the fix.
HTML, CSS grid / media queries, Vanilla JavaScript, Playwright (Chromium), Docker
About the screenshots: A sample site built for this demonstration, shown after and before the fixes.
How we approach it
The habits that keep this kind of project from going wrong.
1
Backup first
A full backup or staging copy is taken before anything is changed.
2
Find the cause
We fix the cause, not just the symptom, and write down what it was so it doesn't come back.
3
Test like a visitor
Fixes are checked on real phone and desktop sizes, and forms are submitted end to end.
4
Work in your builder
Changes are made in the tools your team already uses, so they can keep editing the site.
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
- How many issues and pages
- Which platform and builder
- Whether a staging site exists
- Access to hosting and DNS
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
What access do you need?
An admin login for the site created for us (not yours), and hosting or DNS access only if the fix needs it. Remove them when we're done.
Will the site go down while you work?
No. We take a backup first and use a staging copy where the platform allows it.
Can you fix sites you didn't build?
Yes, that's what this service is for.
Do you offer ongoing maintenance?
We scope each batch of fixes separately and agree it with you before starting. If you need regular work, we can agree a set list at a time.
How long does it take?
Most fix lists take a few days to a week from the signed scope.
What if it breaks again?
In the 30 days after handover we fix anything we repaired that breaks again, at no charge.
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