firstpage.com.au website review

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

Your mobile performance score is 80. Pages that score under 90 lose visitors before the first paint.

The page goes through 1 redirect before it starts loading, costing about 758 ms. Link and advertise the final URL directly.

About 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.

About 318 KiB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (Google Tag Manager, Clarity and reddit and others), adding 421 KiB and 350 ms of main-thread time.

17 files are served with short cache lifetimes, so returning visitors download them again (192 KiB).

11 KiB could be saved by minifying CSS.

6 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

2 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

The page becomes fully interactive after 10.4 s. Good is under 3.8 s.

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

15 images have no width and height attributes, so the layout jumps as each one loads.

Scripts block taps and scrolling for 205 ms in total while the page loads. Good is under 200 ms.

7 images are downloaded at several times the size a phone draws them, for example case-study-pokebox.webp at 1,080 px wide, shown at 308 px. Resized copies would save about 404 KiB.

2 images further down the page (95 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 97 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

24 form fields have no label, so screen readers announce an empty box and autofill guesses.

Google's crawler is blocked from indexing this page.

The page answers with an error status, so search engines may drop it.

The homepage links to 131 pages on firstpage.com.au and 28 external pages.

/google-display-network, /facebook-advertising, /instagram-advertising, /tiktok-advertising, /youtube-advertising and /landing-page-agency and 6 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134610310&tm=gtm002&Ver=2&mid=66b417f4-0211-4494-b7eb-9830e8020c3c&bo=1&sid=fa924c60d7e111f18086b906a5daa699&vid=fa927e70d7e111f18fc2178fabac00c7&vids=1&msclkid=N&pi=9.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

Large scripts ship without source maps.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

The homepage shows no opening hours. If customers visit or call, show when.

The homepage carries about 3,003 words of visible text.

DMARC is set to p=none, so mail pretending to be firstpage.com.au is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 21 cookies (measured from a US location before any click).

Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.