Website review, no card needed

intesols.com.au logo

intesols.com.au website review

Visit site (opens in a new tab)Reviewed 24 October 202627 issues · 82 checks

This review found 27 issues worth fixing on intesols.com.au, 7 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.7 s2.2 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.8 s
May 23, 20263.0 s
May 30, 20263.3 s
Jun 6, 20263.6 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.0 s
Jul 4, 20262.8 s
Jul 11, 20262.6 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.4 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
313 ms111 msMay 2Oct 17162 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026177 ms
May 9, 2026167 ms
May 16, 2026191 ms
May 23, 2026193 ms
May 30, 2026227 ms
Jun 6, 2026290 ms
Jun 13, 2026218 ms
Jun 20, 2026229 ms
Jun 27, 2026200 ms
Jul 4, 2026174 ms
Jul 11, 2026163 ms
Jul 18, 2026173 ms
Jul 25, 2026186 ms
Aug 1, 2026171 ms
Aug 8, 2026175 ms
Aug 15, 2026153 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026134 ms
Sep 12, 2026157 ms
Sep 19, 2026200 ms
Sep 26, 2026207 ms
Oct 3, 2026200 ms
Oct 10, 2026183 ms
Oct 17, 2026162 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 intesols.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. intesols.com.au at 0.6 s0.6 s
  2. intesols.com.au at 1.1 s1.1 s
  3. intesols.com.au at 1.7 s1.7 s
  4. intesols.com.au at 2.2 s2.2 s
  5. intesols.com.au at 2.8 s2.8 s
  6. intesols.com.au at 3.4 s3.4 s
  7. intesols.com.au at 3.9 s3.9 s
  8. intesols.com.au at 4.5 s4.5 s

Speed

7 to fix64
  • Document request latency

    950 ms · 296 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Reduce initial server response time

    927 ms

    Reduce initial server response time. Google estimates savings of 927 ms on a phone.

  • Reduce unused CSS

    269 KiB

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

  • 2,126 HTML elements

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

  • Server response: 1.0 s

    1.0 s

    Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • nitrocdn.com adds 0 ms

    0 ms

    nitrocdn.com costs a phone 0 ms of main-thread work and 500 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.

  • Use efficient cache lifetimes

    150 ms · 118 KiB

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

  • 2 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (trustindex.io, Google Fonts and nitrocdn.com and others), adding 702 KiB and 29 ms of main-thread time.

  • Improve image delivery

    10 KiB

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

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

1 checks passed
  • Main-thread work: 1.5 s

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile-banner”.

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Time to Interactive: 6.4 s

    6.4 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

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

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

    +16%

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

4 checks passed
  • Real-user INP: 186 ms

    186 ms

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

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

    0.018

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

  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.54 g

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

4 checks passed
  • Page weight: 1.9 MB in 111 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 111 requests on a phone: other files 728 KiB (73), HTML 444 KiB (1) and stylesheets 269 KiB (7). That is a lean page.

  • 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

8 to fixGoogle 8891
  • 12 text elements with low contrast

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

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 32 links without text

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

  • 15 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 155 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 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 9290
  • Title is long (95 characters)

    Your title is 95 characters, so Google will cut it off around 60: “#1 Rated SEO, AI Solutions & Web Design Agency in Melbourne - Intesols Moorabbin & Hampto…”.

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

  • 309 internal links, 42 external

    The homepage links to 309 pages on intesols.com.au and 42 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “We are more than just a professional SEO Agency in Melbourne. We also offer AI Solutions, Website design & development,…”.

  • One H1 headline

    Your main headline reads: “Our Services”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://www.intesols.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 (1,483 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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 1,089 words of copy

    The homepage carries about 1,089 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “Get In Touch”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Get In Touch” and “Call Us”.

  • 4 short forms

    4 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 43 testimonial or review blocks, 13 customer or partner logos and 66 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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.

  • 9 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on intesols.com.au, including 16 speed issues and 2 SEO issues. 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