What to Check Before Approving Your New Website

Before you approve a new website and pay the final invoice, check six things. It should work on a real phone, load fast on Google's PageSpeed Insights, and have every link and form working. The Google basics should be in place, you should own the domain, hosting, and code, and there should be a backup and handover.

Approval is your strongest moment. Faults are quick to fix before sign-off and slow, sometimes costly, to fix after.

Walk the site yourself before you approve it. A designer's polished desktop demo is not the same as a customer's phone, and the gaps usually show up there.

Check	What good looks like	How to test it
Mobile	Readable and tappable on a phone	Open it on your own phone
Speed	A fast score, not a red one	Run PageSpeed Insights
Links and forms	Every link works, forms reach you	Click and submit each one
Google basics	Indexable, secure, titled	Check the padlock and page titles
Ownership	Registered in your name	Confirm the domain and hosting accounts
Backup	A copy exists before launch	Ask for it in writing

Test it on a real phone, not just the desktop

Open the site on your own phone before anything else, because most Malaysian visitors will. A site that looks perfect on a wide monitor can break on a phone. Text turns too small, buttons sit too close, or images spill off the screen.

This is what responsive design is meant to guarantee, and it is the easiest thing to verify yourself. Scroll every page, tap every button, and fill in the contact form with your thumb, the way a real customer would.

If anything is awkward on the phone, flag it now. Mobile problems are quick to fix during the build and painful to chase once the invoice is paid.

Check that it loads fast

Run the finished site through Google's free PageSpeed Insights before you approve it. A slow site quietly loses visitors you paid to attract. The tool gives a score and tells you what is dragging it down.

Google's own bands make the number easy to read. A score of 90 or above is good, 50 to 89 needs improvement, and below 50 is poor (Google's PageSpeed Insights documentation, 2026). Aim for green, and treat a red score as a reason to ask questions before sign-off.

How to read a PageSpeed report explains which numbers matter, and the Core Web Vitals behind them. Speed is not a nicety you bolt on later. It is part of what you are paying for, so it belongs on the acceptance list.

Click every link and submit every form

Click every link and submit every form yourself. A broken contact form is the most expensive fault a new site can ship with.

A pattern we see often is a page that looks finished but whose form emails nowhere. It is the single most common thing we are later asked to fix.

Test the real path a customer takes. Send yourself a message through the contact form and confirm it arrives. Tap the WhatsApp button and check it opens a chat to the right number. Tap the phone number and confirm it dials.

Then check what happens after acting. A form that confirms nothing leaves a customer unsure their message went through. A clear thank-you message and a working call to action are part of a finished site, not extras.

Confirm the Google basics are in place

Confirm the site is secure, indexable, and properly titled. These are the foundations Google needs, and they are easy to leave half-done. None are visible at a glance, so they get skipped on a rushed launch.

Check the padlock shows in the browser bar, meaning the site loads over a secure connection. Confirm each page has its own descriptive title, not a generic "Home."

Then make sure the live site is not accidentally blocking search engines. That is a real risk when a staging site's no-index setting gets carried across to launch, which how indexing works explains.

These are five-minute checks that prevent months of invisibility. A brand-new site that quietly told Google to ignore it is a failure we have seen more than once.

Confirm you own everything, then get a backup

Confirm the domain, hosting, and code are registered in your name. Then get a backup and handover before you release the final payment. This is the point most owners miss, and it never comes back once the invoice is settled.

Ownership is where businesses get trapped. Many clients do not know whether they own their own domain or hosting until the day they need to, and the answer arrives too late. Insist on owning your domain, hosting, and code, with the logins in your hands.

Then secure a safety net. Ask for a full backup of the finished site and a written handover of every account and login. A site handed over with no care plan and no backup is one incident away from trouble.

Whether you keep a maintenance plan afterward is your call, but the backup and access should be non-negotiable at handover.

Frequently asked questions

What is the single most important thing to check before a website goes live?

That the contact path actually works. A beautiful site whose form emails nowhere, or whose WhatsApp button points at the wrong number, loses every lead silently.

Submit the form, tap the button, and confirm the message reaches you before you approve anything. Everything else on the site matters, but a broken way to contact you wastes all of it.

How do I test my new website on mobile?

Open it on your own phone and use it as a customer would. Scroll each page, tap every button and link, and fill in the contact form with your thumb.

Try it on both a phone and, if you can, a tablet. You are checking that text is readable without zooming, buttons are easy to tap, and nothing runs off the edge of the screen.

Should my website pass PageSpeed Insights before launch?

It should score well, ideally in the green, before you approve it. Google's bands put 90 and above as good, 50 to 89 as needs improvement, and below 50 as poor.

A poor score means real visitors wait, and some leave. Ask your provider to explain and improve a low score before sign-off, because speed is far harder to retrofit once the site is live and paid for.

What files and accounts should I receive at handover?

You should receive the logins to your domain, hosting, and content system, a full backup of the finished site, and any design files agreed in the contract. These prove you own what you paid for and let you move providers later without starting over.

A provider slow to hand over access at the end is showing you a problem you want to know about before the final payment, not after.

Do I need a backup before the site goes live?

Yes, and it should exist before launch, not after the first problem. A backup is a saved copy you can restore if an update, a hack, or a mistake breaks the site.

Restoring a good backup takes minutes. Rebuilding a site without one takes days. Confirm a backup exists, and that you or your provider can restore it, before you approve the launch.

Can I still ask for changes after I approve the website?

You can, but your bargaining position drops sharply once you approve and pay. Before sign-off, fixing faults is the provider's job under the agreed scope. After it, changes often become billable work.

That is exactly why the walk-through matters. Use the approval step to get every fault fixed while it still costs you nothing.

Approval is your strongest moment, so use it well

Storming Solutions builds and maintains websites for Malaysian businesses from Kuala Lumpur. We hand over the logins, the backup, and a clear checklist at the end, because a site you cannot control is not really yours. Our stance: the approval step is the owner's strongest moment, and a good provider welcomes the scrutiny.

Approving a new site and want a second pair of eyes before you sign off? Send us the link on WhatsApp, or request a pre-launch review, and we will run it against the list above. If the site is already live, a full website audit does the same job in reverse.