Website review, no card needed

ewe.com.au logo

ewe.com.au website review

Visit site (opens in a new tab)Reviewed 24 October 202625 issues · 70 checks

This review found 25 issues worth fixing on ewe.com.au, 9 of them high impact, across 70 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of ewe.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ewe.com.au at 0.9 s0.9 s
  2. ewe.com.au at 1.9 s1.9 s
  3. ewe.com.au at 2.8 s2.8 s
  4. ewe.com.au at 3.8 s3.8 s
  5. ewe.com.au at 4.7 s4.7 s
  6. ewe.com.au at 5.6 s5.6 s
  7. ewe.com.au at 6.6 s6.6 s
  8. ewe.com.au at 7.5 s7.5 s

Speed

5 to fix59
  • Reduce unused JavaScript

    2.3 s · 456 KiB

    About 456 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Improve image delivery

    850 ms · 283 KiB

    10 images could be 283 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 99 KiB

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

  • Document request latency

    143 KiB

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

  • 1 long task on the main thread

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Shopify), adding 64 KiB and 13 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 514 ms of it running JavaScript. That is comfortably low.

  • Server response: 559 ms

    559 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EWE - Global express”.

  • Speed Index: 11.7 s

    11.7 s

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

  • Time to Interactive: 16.8 s

    16.8 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

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

    0.021

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

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

2 to fix75
  • Page weight: 3.3 MB in 130 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 130 requests on a phone: scripts 1.0 MB (40), images 910 KiB (32) and other files 656 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    39 KiB

    1 image is downloaded at several times the size a phone draws it, for example dcs_img_5e4979d96837cf6eb85b84f97b1fe1c3_480x.webp at 389 px wide, shown at 60 px. Resized copies would save about 39 KiB.

  • 1 image in older formats

    1 image (50 KiB) is 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.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

1 checks passed
  • Images load when needed

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

Accessibility

1 to fixGoogle 9698
  • 4 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 9278
  • Title is short (9 characters)

    Your title is only 9 characters: “EWE Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Elevating Supply Chains for Boundless Growth” and “Elevating Supply Chains for Boundless Growth”). One clear main headline is easier for people and search engines.

  • Meta description is long (206 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 49 internal links, 4 external

    The homepage links to 49 pages on ewe.com.au and 4 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.ewe.com.au/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://www.ewe.com.au/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 15 pages without a meta description

    https://ewe.com.au/pages/go-green, https://ewe.com.au/blogs/job, https://ewe.com.au/pages/international-delivery, https://ewe.com.au/pages/3pl-business-unit, https://ewe.com.au/pages/domestic-delivery and https://ewe.com.au/pages/ecommerce and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://ewe.com.au/customer_authentication/redirect has 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 17 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 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • 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 analytics detected

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

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

    The homepage carries about 896 words of visible text.

5 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Pricing”, “Tracking Order” and “Talk To an Expert”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 47 testimonial or review blocks and 1 trust badge.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 ewe.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on ewe.com.au, including 9 speed issues, 5 SEO issues 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