astaresort.com.au website review

route.com costs a phone 1.1 s of main-thread work and 717 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

The page has 3,695 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (route.com, rebuyengine.com and Klaviyo and others), adding 1.7 MB and 2.0 s of main-thread time.

34 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

About 772 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

rebuyengine.com costs a phone 421 ms of main-thread work and 300 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 109 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

Klaviyo costs a phone 244 ms of main-thread work and 311 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.

Polyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

104 KiB JavaScript is shipped twice across bundles.

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

13 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Your homepage downloads 11.9 MB in 353 requests on a phone: media 5.4 MB (2), images 3.3 MB (62) and scripts 1.7 MB (81). Under 2 MB keeps phones on slow connections fast.

000844480028_52c125a2-4e6c-439f-b3a0-60b13dd51bcd.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example 2d053446-7e13-4c5e-a1f6-da304ef1c9a2.png at 1,256 px wide, shown at 130 px. Resized copies would save about 73 KiB.

3 images (290 KiB) 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.

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

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

32 tap targets are too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (26 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “ASTA RESORT AU”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 202 pages on astaresort.com.au and 6 external pages.

https://www.astaresort.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.astaresort.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.astaresort.com.au/collections/all, https://www.astaresort.com.au/customer_authentication/redirect, https://www.astaresort.com.au/policies/shipping-policy, https://www.astaresort.com.au/collections/harbour-island-heaven-resort-27, https://www.astaresort.com.au/collections/signature-hand-beading and https://www.astaresort.com.au/collections/signature-paillette-knitwear and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.astaresort.com.au/customer_authentication/redirect, https://www.astaresort.com.au/pages/the-asta-story and https://www.astaresort.com.au/pages/the-sydney-boutique have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.astaresort.com.au/collections/all, https://www.astaresort.com.au/customer_authentication/redirect, https://www.astaresort.com.au/collections/most-loved and https://www.astaresort.com.au/policies/shipping-policy took over 3 s to send their HTML from our server.

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

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

33 of 75 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetHeight')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 900 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, FullStory, Google Ads, Google Analytics and Google Tag Manager and 2 mores (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 16 cookies (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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.