Website review, no card needed

corehalo.com.au logo

corehalo.com.au website review

Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 70 checks

This review found 28 issues worth fixing on corehalo.com.au, 7 of them high impact, across 70 checks. The most urgent: render-blocking 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
2.7 s2.3 sAug 8Sep 192.7 s
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.7 s

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 corehalo.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. corehalo.com.au at 0.4 s0.4 s
  2. corehalo.com.au at 0.8 s0.8 s
  3. corehalo.com.au at 1.1 s1.1 s
  4. corehalo.com.au at 1.5 s1.5 s
  5. corehalo.com.au at 1.9 s1.9 s
  6. corehalo.com.au at 2.3 s2.3 s
  7. corehalo.com.au at 2.6 s2.6 s
  8. corehalo.com.au at 3.0 s3.0 s

Speed

5 to fix83
  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 83

    83/100

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

  • Improve image delivery

    500 ms · 99 KiB

    3 images could be 99 KiB 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.

  • Main-thread work: 2.2 s

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

  • 2,026 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, JSDelivr CDN and cloudlift.app and others), adding 466 KiB and 165 ms of main-thread time.

  • Reduce unused JavaScript

    192 KiB

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

  • Reduce unused CSS

    150 ms · 41 KiB

    About 41 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.

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    21 KiB

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

  • 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

4 to fix83
  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (1.9 s).

  • Time to Interactive: 6.0 s

    6.0 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.063

    0.063

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 251 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 251 requests on a phone: other files 837 KiB (119), images 765 KiB (18) and scripts 582 KiB (99). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.66 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8693
  • Scrollable region must have keyboard access (12 elements)

    Scrollable region must have keyboard access: 12 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • 6 images without alt text

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

  • 19 links without text

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “CORE HALO | Apparel | Made for Me. – Core Halo| Apparel Made for me.”.

  • 9 H1 headlines

    There are 9 <h1> headlines (“CORE33 COLLECTION”, “I AM77 COLLECTION” and “HALO99 COLLECTION”). One clear main headline is easier for people and search engines.

  • 74 internal links, 5 external

    The homepage links to 74 pages on corehalo.com.au and 5 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Limited-edition hoodies, crewnecks and T-shirts personalised in Australia. Custom coded designs. Refined streetwear. Co…”.

  • Canonical URL set

    The canonical URL is https://corehalo.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://corehalo.com.au/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://corehalo.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 11 pages without a meta description

    https://corehalo.com.au/collections/varsity99-collection, https://corehalo.com.au/collections/core33-collection, https://corehalo.com.au/collections/lexa144-crewneck-copy, https://corehalo.com.au/collections/iam77-collection, https://corehalo.com.au/collections/halo99-collection and https://corehalo.com.au/collections/all and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://corehalo.com.au/products/bubblegum-hoodie-relaxed-core33, https://corehalo.com.au/products/onyx-hoodie-relaxed-core33, https://corehalo.com.au/products/sky-hoodie-relaxed-core33-copy and https://corehalo.com.au/products/shadow-hoodie-relaxed-core33 use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://corehalo.com.au/collections/varsity99-collection, https://corehalo.com.au/collections/core33-collection, https://corehalo.com.au/collections/lexa144-crewneck-copy, https://corehalo.com.au/collections/iam77-collection, https://corehalo.com.au/collections/halo99-collection and https://corehalo.com.au/collections/all and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10093
  • 1 JavaScript error while loading

    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 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    15 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

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

  • No social proof

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

  • No analytics detected

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

  • 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 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 499 words of copy

    The homepage carries about 499 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP COLLECTION”, “Shop Collection” and “Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 corehalo.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Live Product Options · Optis Color Swatch

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 28 issues on corehalo.com.au, including 9 speed issues, 2 SEO issues and 4 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