Website review, no card needed
lifesizecutouts.com.au website review
Visit site (opens in a new tab)Reviewed 6 November 202645 issues · 90 checks
This review found 45 issues worth fixing on lifesizecutouts.com.au, 14 of them high impact, across 90 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #91,598 of 124,013 reviewed websitesbeats 23%
- #57,064 of 69,747 online storesbeats 15%
- #53,379 of 63,441 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 184 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 201 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 197 ms |
| Oct 31, 2026 | 205 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Render-blocking requests
2.5 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, tailwindcss.com and Shopify and others), adding 3.3 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
450 ms · 911 KiBAbout 911 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
hcaptcha.com adds 950 ms
950 mshcaptcha.com costs a phone 950 ms of main-thread work and 1.2 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.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
tailwindcss.com adds 652 ms
652 mstailwindcss.com costs a phone 652 ms of main-thread work and 124 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
300 ms · 270 KiB13 files are served with short cache lifetimes, so returning visitors download them again (270 KiB).
Shopify adds 327 ms
327 msShopify costs a phone 327 ms of main-thread work and 1.7 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.
2,603 HTML elements
The page has 2,603 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 65 KiBAbout 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
86 KiBPolyfills for old browsers add 86 KiB JavaScript that modern phones do not need.
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
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 29.1 s
29.1 sThe page becomes fully interactive after 29.1 s. Good is under 3.8 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 617 ms
617 msScripts block taps and scrolling for 617 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 236 ms
236 msReal visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 184 ms to 205 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 605 ms
605 msReal visitors wait 605 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.031
0.031The layout barely moves while loading (CLS 0.031, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 479 requests
5.0 MBYour homepage downloads 5.0 MB in 479 requests on a phone: scripts 2.7 MB (226), other files 1.1 MB (164) and HTML 575 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 168.5 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 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (2 elements).
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA toggle fields do not have accessible names
ARIA toggle fields do not have accessible names (1 element).
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
SVG elements with an img role do not have an accessible text alternative
SVG elements with an img role do not have an accessible text alternative (2 elements).
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Lifesize Cutouts - Australia's Largest Range of Cardboard Cutouts – LifesizeCutouts”.
2 H1 headlines
There are 2 <h1> headlines (“” and “Custom Acrylic Cutout Standee 30cm - Full Colour …”). One clear main headline is easier for people and search engines.
Meta description is long (247 characters)
Your meta description is 247 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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
245 internal links, 5 external
The homepage links to 245 pages on lifesizecutouts.com.au and 5 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.lifesizecutouts.com.au/.
Structured data in place
Structured data found: Organization 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.lifesizecutouts.com.au/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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,078 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.lifesizecutouts.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.lifesizecutouts.com.au/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.lifesizecutouts.com.au/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.lifesizecutouts.com.au/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.lifesizecutouts.com.au/customer_authentication/redirect, https://www.lifesizecutouts.com.au/collections/custom-cutouts, https://www.lifesizecutouts.com.au/collections/custom-large-cutouts, https://www.lifesizecutouts.com.au/collections/custom-cartoon-cutouts, https://www.lifesizecutouts.com.au/collections/head-swap-cutouts and https://www.lifesizecutouts.com.au/collections/custom-cutouts-custom-masks-and-big-heads and 3 others 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 139 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.
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.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.lifesizecutouts.com.au/.
7 small tap targets
7 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “$ is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 994 words of copy
The homepage carries about 994 words of visible text.
6 checks passed
6 calls to action
The homepage has 6 calls to action, for example “SHOP NOW”, “Shop now” and “Shop Now”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
34 other companies contacted
Loading the homepage contacts 34 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 lifesizecutouts.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Warnify Pro Warnings · Ymq Product Options · Judge Me Reviews · Apippa Custom Price Calc · Prod Master Fad8e300 · Forms · Selleasy · Customily Options · File Uploads By Uploadkit · jsdelivr.net · getuploadkit.com · kxcdn.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Gatsby
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on lifesizecutouts.com.au, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.