How to analyze the loading speed of a competitor's landing page

Competitive speed analysis is more than timing a page and declaring a winner. A competitor’s landing page can look fast in one browser, stall on a phone, and lose its largest element while the rest of the design still appears polished. To understand the difference, measure the full path from request to stable render, then relate the numbers to the devices and connections your Australian audience actually uses.

A useful audit separates evidence from assumption. It identifies the exact URL, repeats each test under known conditions, records lab and field measurements where available, and explains which assets or scripts consume time. The aim is not to interfere with a competitor’s server or collect private information; it is to perform a careful public-page review that reveals performance opportunities for your own campaign.

Set a fair testing baseline

Begin with the page a prospect would reach after an ad click. Capture the complete URL, including campaign parameters that change the creative or offer, and check whether the page redirects to another domain. Test the precise mobile landing page rather than assuming the homepage performs identically. A clean homepage can mask heavier applications, embedded forms, video or personalisation scripts used on a campaign page.

Build a repeatable test profile. Run both desktop and mobile modes, start with a cold cache, and apply the same network and processor limits each time. Choose one testing location and record it, because a result routed through Sydney differs from one measured closer to Melbourne or a regional centre. Note whether cookies, consent banners or login walls appear, since each can alter the first-load experience.

Repeat the run several times and use the median rather than the fastest result. Save screenshots, timestamps and the browser version, then test again during another part of the day. For a low-risk practice run, inspect the public Rewans homepage and document each step before applying the method to a competitor’s campaign.

Measure the metrics that matter

Start with Core Web Vitals because they connect technical delivery to visible stability and responsiveness. At the 75th percentile, Google considers a Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less good. These are page-level thresholds, not a promise that every visit feels identical.

Interpretation matters. Lab tests simulate a journey and are useful for diagnosis; field data shows what real visitors experienced. Time to First Byte and First Contentful Paint remain valuable supporting measures, particularly when a slow server response pushes every later stage late. For a static landing page, INP may be modest simply because nobody interacts with it, so inspect the page’s forms, menus and consent controls before assigning it a score.

Use Chrome DevTools, Lighthouse or a browser-based test to collect timings, then compare competitors with the same tool and settings. Web PageSpeed Insights can add field observations, while Webyzer can contribute domain, technology and loading statistics to the record. If a domain check returns an invalid or restricted message, retry with the canonical hostname and no query string; restricted pages can still be reviewed manually in DevTools when access is lawful.

Trace the request waterfall

The network panel turns a total score into a sequence of causes. Follow DNS lookup, connection and TLS setup, server response, request wait, content download and rendering. A long gap before the first byte points towards hosting, caching or a slow backend. A quick response followed by a crowded queue of assets points towards front-end delivery, with each blocked request able to delay the hero image or headline.

Record transferred and uncompressed sizes for HTML, CSS, JavaScript, images, fonts and third-party resources. A small-looking hero photograph may become a large mobile download when it lacks modern formats or sensible dimensions. Look for oversized campaign artwork, embedded videos, multiple font files and duplicated libraries. Compressed transfer size matters, but decoded size still affects parsing, memory use and the main thread.

Marketing tags can alter the result. Google Ads pixels, social trackers, chat widgets, heat maps and consent scripts may all compete for bandwidth and JavaScript execution time, even when a screenshot shows no obvious visual clutter. Check cache headers, CDN delivery and compression before blaming creative assets. Webyzer’s Houston analysis page provides a useful example of the sort of domain, loading and technology report to review before making a comparison.

Inspect HTML and render behaviour

Inspecting source and rendered DOM reveals why content appears when it does. Semantic headings, meaningful image alternative text, clean internal linking and scripts placed after essential content help browsers interpret the page efficiently. Webyzer’s guide to HTML structure signals explains how structure influences both discovery and rendering. A landing page should not depend on a late script to reveal its main offer.

Check responsive images, width and height attributes, modern formats and lazy loading below the fold. Give the main image an appropriately sized source, preload only when it is truly the Largest Contentful Paint element, and avoid loading several font weights that no one sees. Reserve space for embeds and banners so late-loading content does not create Cumulative Layout Shift.

Use DevTools Performance and Coverage panels to spot long tasks, repeated script work and unused code. Hydration frameworks can create a visible result quickly and then spend seconds making it interactive, while a single poorly timed tag can block the main thread. Judge these costs by their effect on the journey, not by the total number of requests alone.

Compare results with Australian conditions

Australian conditions make field checks especially valuable. People in Sydney, Melbourne, Brisbane and regional areas may alternate between fast fibre or NBN connections and variable LTE or 5G mobile data. Distance from the server, local network congestion and indoor coverage can each change response time. A server in another country may perform adequately for desktop users while adding noticeable wait for regional mobile visitors.

Mobile usage is central to campaigns aimed at commuters, shoppers and people comparing offers between visits to a store. In a competitive Australian market, fast pages can support trust and conversion when promotions from major retailers appear in the same feed. Local relevance matters too: a Brisbane customer should not download a Melbourne-sized campaign asset, and a page that handles Australian addresses, GST-inclusive prices and local delivery copy should do so without loading extra regional tools unnecessarily.

Test at times that reflect audience behaviour, not merely whenever convenient. During the local arvo, run one mobile check on a mobile network and another on fixed broadband, repeating the comparison across business days. Remember that business hours differ between AEST or AEDT in the eastern states and ACST in South Australia and the Northern Territory, which can change traffic patterns. A proper look means treating one unusually clean run as a clue, not gospel.

Turn the audit into a prioritised action plan

Convert each observation into an issue, an owner and a measurable outcome. A two-second Largest Contentful Paint might trace to slow image delivery, server response or client-side delay; those problems need different fixes. Rank work by user impact and effort, including mobile performance, visual stability and campaign readiness. Preserve the landing page’s offer and tracking while removing delays, since a faster page that breaks attribution is not a successful change.

Start with the largest bottlenecks: optimise hero media, defer non-essential scripts, reduce third-party tags, self-host or subset fonts where appropriate, improve caching and tune server response. Add preload only when evidence shows the browser discovered the key asset too late. Set a performance budget for page weight, LCP, INP and CLS, and make the budget part of publishing checks rather than a one-off remediation.

Validate every significant change under the same profile used in the baseline. Compare field and lab results, watch conversion and error data, and retain screenshots as evidence. Do not copy a competitor’s stack blindly; their CDN, theme and tag mix may depend on a different audience and budget. Your advantage comes from understanding the delay and choosing a solution that fits your own page.

Run the first check now: enter the competitor domain in Webyzer, capture its technology and loading results, then reproduce the exact landing-page test in your browser. Save the settings and repeat the audit after each priority change so the team can compare like with like and turn loading speed into a measurable part of the marketing plan.