Website review, no card needed
futureglass.com.au website review
Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 81 checks
This review found 27 issues worth fixing on futureglass.com.au, 4 of them high impact, across 81 checks. The most urgent: page weight: 5.6 MB in 303 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
90A- #2,416 of 120,865 reviewed websitesbeats 97%
- #1,171 of 68,427 online storesbeats 97%
- #1,133 of 62,354 Shopify storesbeats 97%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 139 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 141 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 81
81/100Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Klaviyo and others), adding 2.8 MB and 638 ms of main-thread time.
Render-blocking requests
900 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
150 ms · 569 KiBAbout 569 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 295 ms
295 msGoogle Tag Manager costs a phone 295 ms of main-thread work and 550 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 934 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 42 ms
42 msShopify costs a phone 42 ms of main-thread work and 1.6 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.
1,507 HTML elements
The page has 1,507 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 96 ms
96 msKlaviyo costs a phone 96 ms of main-thread work and 314 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
231 KiB15 files are served with short cache lifetimes, so returning visitors download them again (231 KiB).
Reduce unused CSS
150 ms · 57 KiBAbout 57 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need.
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Largest Contentful Paint: 4.0 s
4.0 sYour largest element takes 4.0 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: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 225 ms
225 msScripts block taps and scrolling for 225 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 551 ms
551 msReal visitors wait 551 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 303 requests
5.6 MBYour homepage downloads 5.6 MB in 303 requests on a phone: images 2.9 MB (43), scripts 1.6 MB (83) and other files 949 KiB (150). Under 2 MB keeps phones on slow connections fast.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 191.3 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
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (286 characters)
Your meta description is 286 characters; Google truncates after about 160, so the end of your pitch is cut.
196 internal links, 3 external
The homepage links to 196 pages on futureglass.com.au and 3 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Future Glass”.
Title: 49 characters
Your title is a healthy 49 characters: “Future Glass | Luxurious Mirrors & Shower Screens”.
Canonical URL set
The canonical URL is https://www.futureglass.com.au/.
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.futureglass.com.au/sitemap.xml.
AI search readiness
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.
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 (806 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.futureglass.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://www.futureglass.com.au/collections/on-sale-items, https://www.futureglass.com.au/collections/on-sale, https://www.futureglass.com.au/collections/bathroom-mirrors, https://www.futureglass.com.au/pages/shower-screens, https://www.futureglass.com.au/collections/50-off-clearance-mirrors and https://www.futureglass.com.au/collections/fixed-panel-shower-screens-tinted and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.futureglass.com.au/collections/on-sale-items, https://www.futureglass.com.au/collections/on-sale, https://www.futureglass.com.au/collections/bathroom-mirrors, https://www.futureglass.com.au/pages/shower-screens, https://www.futureglass.com.au/collections/50-off-clearance-mirrors and https://www.futureglass.com.au/collections/outlet and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.futureglass.com.au/collections/on-sale, https://www.futureglass.com.au/collections/bathroom-mirrors, https://www.futureglass.com.au/collections/mirror-cabinets, https://www.futureglass.com.au/collections/led-mirrors, https://www.futureglass.com.au/collections/natural-stone-collection and https://www.futureglass.com.au/collections/wall-mirrors took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 80 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
20 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 397 words of copy
The homepage carries about 397 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: “30– 60% OFF MIRRORS SHOP ALL”.
23 calls to action
The homepage has 23 calls to action, for example “Shop All Clearance Items”, “Shop All” and “Shop By Shape”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and “75,000+ Happy Customers”.
Analytics in place
Analytics detected: Google Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
38 other companies contacted
Loading the homepage contacts 38 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 futureglass.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Hulk Product Options · Swatch King · Gorgias Live Chat Helpdesk · Yotpo Product Reviews · Xo Gallery · nfcube.com · rebuyengine.com · 9gtb.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
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
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 futureglass.com.au, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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.