Website review, no card needed

atworkaustralia.com.au logo

atworkaustralia.com.au website review

Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 86 checks

This review found 42 issues worth fixing on atworkaustralia.com.au, 19 of them high impact, across 86 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

Real-visitor load time (LCP)75th percentile, phones
4.8 s3.5 sMay 2Oct 174.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.0 s
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20263.9 s
Jul 4, 20264.1 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.4 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.6 s
Oct 17, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
248 ms189 msMay 2Oct 17222 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026200 ms
May 9, 2026196 ms
May 16, 2026196 ms
May 23, 2026199 ms
May 30, 2026205 ms
Jun 6, 2026204 ms
Jun 13, 2026205 ms
Jun 20, 2026207 ms
Jun 27, 2026205 ms
Jul 4, 2026210 ms
Jul 11, 2026219 ms
Jul 18, 2026225 ms
Jul 25, 2026231 ms
Aug 1, 2026241 ms
Aug 8, 2026241 ms
Aug 15, 2026232 ms
Aug 22, 2026237 ms
Aug 29, 2026225 ms
Sep 5, 2026220 ms
Sep 12, 2026223 ms
Sep 19, 2026217 ms
Sep 26, 2026217 ms
Oct 3, 2026222 ms
Oct 10, 2026222 ms
Oct 17, 2026222 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 atworkaustralia.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. atworkaustralia.com.au at 1.9 s1.9 s
  2. atworkaustralia.com.au at 3.8 s3.8 s
  3. atworkaustralia.com.au at 5.6 s5.6 s
  4. atworkaustralia.com.au at 7.5 s7.5 s
  5. atworkaustralia.com.au at 9.4 s9.4 s
  6. atworkaustralia.com.au at 11.3 s11.3 s
  7. atworkaustralia.com.au at 13.1 s13.1 s
  8. atworkaustralia.com.au at 15.0 s15.0 s

Speed

14 to fix29
  • Reduce unused JavaScript

    28.0 s · 5.4 MB

    About 5.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 28.0 s faster on a phone.

  • Google CDN adds 2.8 s

    2.8 s

    Google CDN costs a phone 2.8 s of main-thread work and 7.8 MB 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.

  • Render-blocking requests

    2.6 s

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

  • Main-thread work: 16.3 s

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

  • Reduce unused CSS

    1.1 s · 189 KiB

    About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • mypurecloud.com.au adds 1.0 s

    1.0 s

    mypurecloud.com.au costs a phone 1.0 s of main-thread work and 1.2 MB 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.

  • Mobile performance score: 29

    29/100

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

  • 3,823 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, mypurecloud.com.au and Google Tag Manager and others), adding 10.9 MB and 5.6 s of main-thread time.

  • Google Tag Manager adds 992 ms

    992 ms

    Google Tag Manager costs a phone 992 ms of main-thread work and 1.1 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

    700 ms · 260 KiB

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

  • Other Google APIs/SDKs adds 531 ms

    531 ms

    Other Google APIs/SDKs costs a phone 531 ms of main-thread work and 332 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.

  • Minify JavaScript

    450 ms · 88 KiB

    88 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 52 KiB

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

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

  • Improve image delivery

    5 KiB

    1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 checks passed
  • Server response: 409 ms

    409 ms

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

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 53.3 s

    53.3 s

    Your largest element takes 53.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 20.1 s

    20.1 s

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

  • Time to Interactive: 78.8 s

    78.8 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 317 ms

    317 ms

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

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

    +12%

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

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

    +14%

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

2 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.073

    0.073

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

Images and page weight

1 to fix70
  • Page weight: 17.2 MB in 380 requests

    17.2 MB

    Your homepage downloads 17.2 MB in 380 requests on a phone: scripts 10.5 MB (123), other files 3.5 MB (80) and images 1.4 MB (68). Under 2 MB keeps phones on slow connections fast.

  • About 4.9 g of CO₂ per visit

    4.88 g

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

6 to fixGoogle 9390
  • 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.

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 11 images without alt text

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

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

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

  • 9 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 8588
  • Meta description is long (223 characters)

    Your meta description is 223 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.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 207 internal links, 7 external

    The homepage links to 207 pages on atworkaustralia.com.au and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “atWork Australia”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “atWork Australia | Employment Services Provider”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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.atworkaustralia.com.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

4 to fix78
  • 4 pages share 2 titles

    https://www.atworkaustralia.com.au/enquire-now and https://www.atworkaustralia.com.au/employer-online-enquiry all use the title “Enquire now - atWork Australia”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.atworkaustralia.com.au/enquire-now and https://www.atworkaustralia.com.au/employer-online-enquiry have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.atworkaustralia.com.au/employer-online-enquiry, whose canonical is https://www.atworkaustralia.com.au/enquire-now. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://www.atworkaustralia.com.au/enquire-now, https://www.atworkaustralia.com.au/help-looking-for-work, https://www.atworkaustralia.com.au/recruiting-people-with-disability, https://www.atworkaustralia.com.au/employer-online-enquiry and https://www.atworkaustralia.com.au/finding-the-right-person-for-your-vacancy 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 71 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.

  • 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

Google 92100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 31-field form

    Your longest form asks for 31 fields (14 required). Every extra field lowers completion.

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

    The homepage carries about 407 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 18 calls to action

    The homepage has 18 calls to action, for example “Enquire”, “Enquire now” and “Enquire today”.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

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

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, LinkedIn Insight and Meta Pixel 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.

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 atworkaustralia.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
Analytics
Google Analytics | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on atworkaustralia.com.au, including 24 speed issues, 4 SEO issues and 2 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