Website review, no card needed

alliedexpress.com.au logo

alliedexpress.com.au website review

Visit site (opens in a new tab)Reviewed 20 November 202626 issues · 81 checks

This review found 26 issues worth fixing on alliedexpress.com.au, 8 of them high impact, across 81 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
1.3 s1.0 sMay 30Nov 141.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
115 ms88 msMay 30Nov 14104 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 202694 ms
Jun 27, 202692 ms
Jul 4, 202691 ms
Jul 11, 202692 ms
Jul 18, 202693 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 202698 ms
Aug 15, 2026102 ms
Aug 22, 2026103 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026107 ms
Oct 17, 2026110 ms
Oct 24, 2026110 ms
Oct 31, 2026112 ms
Nov 7, 2026108 ms
Nov 14, 2026104 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 alliedexpress.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix95
  • Render-blocking requests

    1.3 s

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

  • Improve image delivery

    300 ms · 737 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Maps, Facebook and pcdn.co and others), adding 3.6 MB and 534 ms of main-thread time.

  • Google Maps adds 287 ms

    287 ms

    Google Maps costs a phone 287 ms of main-thread work and 493 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.

  • Reduce unused JavaScript

    335 KiB

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

  • pcdn.co adds 32 ms

    32 ms

    pcdn.co costs a phone 32 ms of main-thread work and 2.9 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.

  • Use efficient cache lifetimes

    220 KiB

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

  • Legacy JavaScript

    150 ms · 32 KiB

    Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. 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 182 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

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

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 7.7 s

    7.7 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

10 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.3 s

    1.3 s

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

  • Real-user INP: 104 ms

    104 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 776 ms

    776 ms

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

  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “Allied Express Transport”.

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 128 ms

    128 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix60
  • Page weight: 9.2 MB in 33 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 33 requests on a phone: media 5.5 MB (1), images 2.8 MB (6) and scripts 720 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    43 KiB

    1 image is downloaded at several times the size a phone draws it, for example allied_logo-high-res.png at 675 px wide, shown at 150 px. Resized copies would save about 43 KiB.

  • 1 image in older formats

    1 image (78 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 2.6 g of CO₂ per visit

    2.60 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.60 g of CO₂e: 312.4 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

4 to fixGoogle 9293
  • 14 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

  • No social preview image

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

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 39 internal links, 5 external

    The homepage links to 39 pages on alliedexpress.com.au and 5 external pages.

4 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “Home - Allied Express Transport”.

  • Canonical URL set

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

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at http://www.alliedexpress.com.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.alliedexpress.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: 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 (278 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.alliedexpress.com.au/services/track-trace, https://www.alliedexpress.com.au/about-us, https://www.alliedexpress.com.au/about-us/freightways-supplier-code-of-conduct, https://www.alliedexpress.com.au/faq, https://www.alliedexpress.com.au/customers and https://www.alliedexpress.com.au/existing-customers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.alliedexpress.com.au/services/track-trace, https://www.alliedexpress.com.au/about-us, https://www.alliedexpress.com.au/customers, https://www.alliedexpress.com.au/services/courier-service, https://www.alliedexpress.com.au/services/taxi-truck-service and https://www.alliedexpress.com.au/services/local-distribution-services and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.alliedexpress.com.au/existing-customers and https://www.alliedexpress.com.au/recruitment have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.alliedexpress.com.au/services/local-distribution-services took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    8 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 fix78
  • No social proof

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

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

  • Only about 157 words

    The homepage has only about 157 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Re-book delivery” and “Book”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Contact Us” and “Re-book delivery”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 alliedexpress.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

CMS
WordPress
Framework
jQuery
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on alliedexpress.com.au, including 8 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