exemplify.com.au website review

4 images could be 8.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.8 s faster on a phone.

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

60 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

hsappstatic.net costs a phone 1.4 s of main-thread work and 2.6 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.

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

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

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

8 third-party services load with your homepage (hsappstatic.net, Hubspot and Google Tag Manager and others), adding 3.5 MB and 2.0 s of main-thread time.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

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

Hubspot costs a phone 251 ms of main-thread work and 382 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 49.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hero_image”.

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

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

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

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

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.

Your homepage downloads 13.1 MB in 148 requests on a phone: images 9.0 MB (15), scripts 2.8 MB (64) and fonts 852 KiB (19). Under 2 MB keeps phones on slow connections fast.

2 images weigh 7.7 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example chase-chappell-ZzsQ3I2h88U-unsplash.jpg at 5,635 px wide, shown at 310 px. Resized copies would save about 7.5 MB.

2 images further down the page (7.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (2.2 MB) 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Your title is only 19 characters: “Grow With Exemplify”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“We Make HubSpot Work For Your Business”, “We Make HubSpot Work For Saas” and “Our Services”). One clear main headline is easier for people and search engines.

The homepage links to 28 pages on exemplify.com.au and 0 external pages.

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.

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.

Your homepage links to /hubspot-for-saas-2, which answers with an error. Visitors hit a dead end and search engines drop it.

/home-v2 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /home-v2 all use the title “Grow With Exemplify”. Search engines can't tell which page to show for a search, so each competes with the others.

/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

/contact-us has 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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'previousElementSibling')”.

Chrome logged issues while loading the page (“Cookie”).

1 link from your homepage to your own site is broken, for example https://www.exemplify.com.au/hubspot-for-saas-2 (404).

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://www.exemplify.com.au/home-v2.

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

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 44 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 884 words of visible text.

DMARC is set to p=none, so mail pretending to be exemplify.com.au is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies, 9 of them by other companies (measured from a US location before any click).

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