Website review, no card needed

device.com.au logo

device.com.au website review

Visit site (opens in a new tab)Reviewed 4 November 202620 issues · 68 checks

This review found 20 issues worth fixing on device.com.au, 8 of them high impact, across 68 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
5.1 s2.4 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.1 s
May 23, 20263.0 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.0 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.7 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20264.7 s
Sep 26, 20264.5 s
Oct 3, 20264.8 s
Oct 10, 20264.8 s
Oct 17, 20264.7 s
Oct 24, 20264.8 s
Oct 31, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
188 ms111 msMay 16Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026137 ms
May 23, 2026136 ms
May 30, 2026131 ms
Jun 6, 2026136 ms
Jun 13, 2026121 ms
Jun 20, 2026135 ms
Jun 27, 2026136 ms
Jul 4, 2026133 ms
Jul 11, 2026137 ms
Jul 18, 2026136 ms
Jul 25, 2026134 ms
Aug 1, 2026148 ms
Aug 8, 2026124 ms
Aug 15, 2026122 ms
Aug 22, 2026121 ms
Aug 29, 2026120 ms
Sep 5, 2026123 ms
Sep 12, 2026145 ms
Sep 19, 2026179 ms
Sep 26, 2026178 ms
Oct 3, 2026176 ms
Oct 10, 2026166 ms
Oct 17, 2026134 ms
Oct 24, 2026138 ms
Oct 31, 2026138 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

5 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 3.3 s

    3.3 s

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

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

    +44%

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

  • Tap response (INP) held steady for real visitors

    +1%

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

2 checks passed
  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.18 g

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

1 checks passed
  • Page weight: 644 KiB

    644 KiB

    Your homepage downloads 644 KiB on a phone, 15 KiB of it images (2%). That is a lean page.

Accessibility

5 to fix65
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • Headings skip levels

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

1 checks passed
  • 5 automated accessibility rules passed

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

SEO

2 to fix93
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 155 internal links, 7 external

    The homepage links to 155 pages on device.com.au and 7 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Medical devices and supplies for Australia, New Zealand and Asia. Complete healthcare solutions, medical equipment and …”.

  • One H1 headline

    Your main headline reads: “Pioneering Possibility ®”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Medical Devices & Supplies | Device Technologies AU”.

  • Canonical URL set

    The canonical URL is https://www.device.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 https://www.device.com.au/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no /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.

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

Other pages

3 to fix75
  • 6 pages without a title

    /our-brands, /news, /deviceonline, /our-directors, /c/gastroenterology and /c/hospital-infrastructure have no <title>, so Google invents the link text in results.

  • 10 pages without a meta description

    /our-brands, /support-services, /device-assure, /digital-education, /news and /deviceonline and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    /our-brands, /news, /deviceonline, /our-directors, /c/gastroenterology and /c/hospital-infrastructure have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages slow to respond

    /contact-us, /our-brands, /support-services, /device-assure, /digital-education and /news and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

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

Security and trust

1 to fix92
  • 1 broken external link

    1 link to other sites is dead, for example https://devicetechnologiesgroup.com/ (520).

  • HTTP/1.1 only

    The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

  • Short HSTS lifetime

    HSTS is set, but max-age is 182 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

5 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (device.com.au).

  • Valid certificate (154 days left)

    The certificate from Sectigo Limited · Sectigo Public Server Authentication CA DV R36 verifies for device.com.au and is valid for another 154 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://device.com.au redirects to the secure version.

Domain and trust

  • No CAA record

    device.com.au has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 18 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 819 words of visible text.

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Join our Team” and “Learn more”.

  • Direct contact links

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

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf1.device.com.au include:_spf2.device.com.au ~all”.

  • DKIM signing found

    A DKIM key is published (selector “s1”, “s2” and “hs1”), so receivers can verify mail really came from you.

Privacy and tracking

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

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

Upkeep, stack and company

Stack

Framework
Angular
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on device.com.au, including 5 speed issues, 2 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