Website review, no card needed

lastst.com.au logo

lastst.com.au website review

Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 89 checks

This review found 32 issues worth fixing on lastst.com.au, 9 of them high impact, across 89 checks. The most urgent: page weight: 8.1 MB in 242 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.0 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.3 s
Jul 4, 20261.5 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
152 ms99 msMay 16Oct 31146 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026107 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026112 ms
Jun 20, 2026114 ms
Jun 27, 2026117 ms
Jul 4, 2026120 ms
Jul 11, 2026120 ms
Jul 18, 2026117 ms
Jul 25, 2026114 ms
Aug 1, 2026113 ms
Aug 8, 2026119 ms
Aug 15, 2026121 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026132 ms
Sep 26, 2026137 ms
Oct 3, 2026140 ms
Oct 10, 2026145 ms
Oct 17, 2026146 ms
Oct 24, 2026146 ms
Oct 31, 2026146 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lastst.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lastst.com.au at 0.7 s0.7 s
  2. lastst.com.au at 1.4 s1.4 s
  3. lastst.com.au at 2.1 s2.1 s
  4. lastst.com.au at 2.8 s2.8 s
  5. lastst.com.au at 3.5 s3.5 s
  6. lastst.com.au at 4.2 s4.2 s
  7. lastst.com.au at 4.9 s4.9 s
  8. lastst.com.au at 5.7 s5.7 s

Speed

7 to fix74
  • 4,744 HTML elements

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

  • Improve image delivery

    50 ms · 1.9 MB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    800 ms

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

  • Main-thread work: 3.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Amazon Web Services, LinkedIn Ads and juniphq.com and others), adding 2.0 MB and 119 ms of main-thread time.

  • Shopify adds 17 ms

    17 ms

    Shopify costs a phone 17 ms of main-thread work and 1.6 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.

  • Reduce unused JavaScript

    240 KiB

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

  • Reduce unused CSS

    150 ms · 31 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    42 KiB

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

  • Legacy JavaScript

    29 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 13 ms

    13 ms

    Your server sent the HTML in 13 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Time to Interactive: 18.2 s

    18.2 s

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

  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Santa holding a bottle of Last St Christmas Liqueur in fron…”.

  • Tap response (INP) got 38% slower for real visitors

    +38%

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

  • Speed Index: 5.5 s

    5.5 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 149 ms

    149 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 689 ms

    689 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.033

    0.033

    The layout barely moves while loading (CLS 0.033, good is under 0.1).

  • Total Blocking Time: 8 ms

    8 ms

    Scripts block the page for only 8 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix64
  • Page weight: 8.1 MB in 242 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 242 requests on a phone: images 6.2 MB (101), other files 702 KiB (66) and scripts 573 KiB (56). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    felicity-and-nathan-below-the-tower.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).

  • About 2.3 g of CO₂ per visit

    2.29 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8691
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 12 text elements with low contrast

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

  • 6 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (2 elements)

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

  • 43 links without text

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

  • 10 form fields without a label

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 281 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No XML sitemap

    No XML sitemap at https://lastst.com.au/sitemap.xml, so Google discovers your pages only by following links.

  • 291 internal links, 5 external

    The homepage links to 291 pages on lastst.com.au and 5 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Welcome to Last St, where flavour always comes first. Proudly Australian family owned. Visit, sample, dine & stay with …”.

  • One H1 headline

    Your main headline reads: “It’s Christmas at Last”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Last St Brewery | Handcrafted in Beechworth”.

  • Canonical URL set

    The canonical URL is https://lastst.com.au/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://lastst.com.au/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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,612 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 1 page without a meta description

    https://lastst.com.au/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://lastst.com.au/collections/shop-all and https://lastst.com.au/collections/christmas use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://lastst.com.au/customer_authentication/redirect and https://lastst.com.au/products/pick-and-mix have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://lastst.com.au/customer_authentication/redirect and https://lastst.com.au/collections/shop-all took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 8 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • No direct contact details

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

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

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

  • About 657 words of copy

    The homepage carries about 657 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “(T&Cs Apply)”, “Shop” and “Shop all”.

  • 50 short forms

    50 short forms (6 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 110 testimonial or review blocks and 28 trust badges.

  • Analytics in place

    Analytics detected: LinkedIn Insight.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight 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.

  • 14 cookies set on arrival

    14

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

  • No consent tool detected

    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.

  • 24 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lastst.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

nfcube.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on lastst.com.au, including 12 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25