Website Speed Audit Checklist for Better Enquiries.

A fast website gives a potential customer time to focus on your service, not the loading spinner. This website speed audit checklist helps you check the pages that generate enquiries, bookings and sales, then make practical improvements without chasing meaningless test scores.

For a Tauranga trades business, that might be the quote form and service-area pages. For a professional practice, it may be the team page, booking path and contact details. The right audit starts with the actions your customers need to complete.

Website speed audit checklist: start with the customer path

Before opening a performance tool, write down the three to five routes that matter most. Include the homepage, a key service page, a location page if it attracts local search traffic, and the contact, booking or checkout path.

Test each route as a first-time visitor would. Use mobile data as well as Wi-Fi, open the page in a private browser window, and note when the useful content appears. A page can earn a respectable automated score while its enquiry form is delayed by a script, or its hero image pushes the call to action below the fold.

Record a starting point for each important page. Capture the load time, page weight, number of requests and any obvious layout movement. Screenshots and a short screen recording can be useful too, particularly when explaining priorities to a manager or developer.

Check the experience on a real mobile

Most local service searches begin on a mobile. Test on at least one current Android handset and one iPhone where possible. Use your own connection, then try a throttled mobile connection in browser developer tools to see how the page behaves outside ideal office Wi-Fi.

Check whether the business name, service message and primary action appear quickly. Phone buttons should be easy to tap, forms should not jump as the page loads, and cookie notices or chat widgets should not cover key content. Speed is not only the moment the browser reports a finished load. It is the point at which a visitor can confidently take the next step.

Measure the right signals, not just one score

Use performance testing tools to identify trends, then validate the findings in a browser. Pay attention to how quickly the largest visible item loads, how soon the page responds to taps and clicks, and whether content shifts unexpectedly.

These measures are useful because they reflect a visitor's experience. They are not a pass-or-fail test. A content-heavy article may load more resources than a simple landing page, while an online booking system may need scripts that a brochure site does not. The goal is to remove unnecessary delay from the pages that support the business.

Run several tests at different times. One result can be affected by a temporary server load, a cold cache or a third-party service. Look for repeatable patterns before approving major changes.

Check hosting, caching and delivery

A well-built page still needs a prompt response from the server. Review the initial server response on both logged-out and logged-in visits. If the server is slow before it starts sending the page, investigate hosting resources, database queries, heavy plugins or extensions, and whether page caching is operating correctly.

For most public pages, cached HTML gives the best result. Pages that change for each visitor, such as account areas, carts and some booking screens, need different handling. Do not force caching onto a dynamic page without testing it properly. Showing one customer's details to another is far worse than a modest performance gain.

A content delivery network can serve static files closer to visitors and reduce repeated work at the origin server. Confirm that images, style sheets, scripts and fonts are being delivered through the expected cache layer. Also check cache headers after a site update. Old files held in cache can cause broken layouts or prevent visitors from seeing an important change.

For WordPress and October CMS websites, keep the platform, theme and extensions current. Updates improve more than security. They can reduce compatibility issues and remove inefficient code, although every update should be tested against the website's key customer paths.

Review images, video and fonts

Large media files are often the quickest place to save time. Check the file size and displayed dimensions of every image above the fold. A 3000-pixel image used in a 600-pixel card wastes data, especially on mobile.

Use modern image formats where they suit the browser support you need, provide correctly sized versions for different screens, and compress files without making a service photo look rough. Product detail, portfolio and tourism websites may need higher image quality than a simple office website. The answer is controlled quality, not blindly reducing every image.

Set below-the-fold images to load later, but do not lazy-load the main image a visitor sees first. That can delay the very element intended to make the page feel quick. For video, use a lightweight preview image and load the player only after the visitor chooses to play it, unless the video is essential to the first screen.

Fonts deserve the same attention. Multiple font families and weights add requests and can cause text to shift. Keep the type system simple, preload only the files needed immediately, and ensure a sensible fallback font appears while a custom font loads.

Remove script weight with purpose

Open the network panel and identify scripts that load on every page. Common examples include chat tools, booking widgets, social feeds, advertising tags, heatmaps and embedded maps. Each may be useful, but every one has a cost in download size, processing time or both.

Ask a direct question of each script: does it help a customer complete an action or give the business information it actively uses? If the answer is unclear, remove it, limit it to the relevant pages, or delay it until consent or interaction.

Avoid combining or deferring files by rule alone. Modern browsers and server protocols handle files differently from older setups, and aggressive optimisation can break menus, forms or tracking. After each change, test the desktop and mobile customer path rather than relying on a green score.

Check forms, maps and third-party tools

A contact form that appears quickly but fails to submit is not a successful page. Test required fields, validation messages, spam protection, confirmation emails and the destination inbox. If a form uses external scripts, check whether they delay rendering or block interaction on slower mobiles.

Interactive maps, reviews and social media feeds can be heavy. A static map image with an address and directions button is often enough for a business that simply needs customers to find its premises. If live reviews support trust on a key page, load them after the primary content rather than ahead of it.

Audit layout stability and interaction

Speed work should make the page easier to use, not just lighter. Watch for banners, images, form fields and embedded tools moving after a visitor has started reading or tapping. Set image and embed dimensions so the browser reserves space before they load.

Review menus on small screens. A large animated navigation, oversized sticky header or delayed hamburger icon can make a fast page feel awkward. Keep the phone number, contact action and main navigation accessible, but avoid filling half the screen with fixed elements.

Also check accessibility basics. Clear button labels, readable text, visible keyboard focus and sensible contrast make the site more usable for everyone. They can reduce friction without adding unnecessary code.

Prioritise fixes by business impact

Not every finding needs immediate work. Start with items that affect an important page, a large share of visitors or a key conversion action. A poorly sized homepage hero image may be worth fixing this week. A minor delay in a rarely visited archive page can wait.

Create a short action list with the issue, page affected, expected benefit, owner and test method. For example, replace an oversized banner image, defer a non-essential chat widget, repair page caching, then retest the homepage and contact form on mobile. Small, verified changes are easier to manage than a broad rebuild based on assumptions.

After changes go live, compare the new results with your starting record and check analytics for meaningful outcomes such as form completions, phone taps and booking starts. Performance improvement is valuable when it helps more people reach the right action.

Set a realistic review schedule

A speed audit is most useful as a regular maintenance task. Review key pages after a redesign, new campaign, plugin update, major content upload or third-party integration. For an established business website, a monthly check of uptime, updates and core performance is usually practical, with a deeper audit every quarter.

Keep the checklist attached to normal website operations, not filed away after one round of fixes. When new images, tools and content are reviewed before publishing, the website stays quicker by default and customers keep getting a clear path from search to enquiry.