mirvac.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.

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

194 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

Your mobile performance score is 40 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.9 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Vimeo and Azure Web Services and others), adding 20.6 MB and 1.9 s of main-thread time.

Azure Web Services costs a phone 291 ms of main-thread work and 10.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Vimeo costs a phone 299 ms of main-thread work and 8.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

176 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 848 ms of main-thread work and 1,021 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

Facebook costs a phone 261 ms of main-thread work and 310 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

userway.org costs a phone 58 ms of main-thread work and 469 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

2 KiB could be saved by minifying CSS.

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 wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DRIVEN BY IMAGINATION In the imagine nation, we see what ca…”.

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

Visually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.

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

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

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

Real visitors wait 221 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-24, real Chrome visitors' tap response (inp) went from 154 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 21.2 MB in 299 requests on a phone: images 9.1 MB (79), other files 8.0 MB (64) and scripts 3.3 MB (133). Under 2 MB keeps phones on slow connections fast.

5 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example hero3-3.webp at 12,288 px wide, shown at 390 px. Resized copies would save about 2.6 MB.

28 images (6.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

14 images further down the page (6.2 MB) 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 6.00 g of CO₂e: 720.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

2 images have no alt text, which hurts accessibility and image search.

4 visible links have no text or label, so screen readers cannot say where they go.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 222 pages on mirvac.com and 31 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.mirvac.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.mirvac.com/Residential/projects and https://www.mirvac.com/Residential/projects/all-projects all use the title “All Projects | Mirvac”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mirvac.com/Residential/why-mirvac has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mirvac.com/Residential/projects and https://www.mirvac.com/Residential/projects/all-projects use the same meta description. A description written for each page earns more clicks.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.mirvac.com/Residential/projects, whose canonical is https://www.mirvac.com/residential/projects/all-projects. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mirvac.com/Residential/projects, https://www.mirvac.com/Residential/projects/all-projects, https://www.mirvac.com/Residential/projects/nsw-projects, https://www.mirvac.com/Residential/projects/vic-projects, https://www.mirvac.com/Residential/projects/qld-projects and https://www.mirvac.com/Residential/projects/wa-projects and 4 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.mirvac.com/.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'validator')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 818 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 17 cookies, 2 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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