Website review, no card needed
pso-rite.com.au website review
Visit site (opens in a new tab)Reviewed 16 November 202632 issues · 73 checks
This review found 32 issues worth fixing on pso-rite.com.au, 10 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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
75C- #76,316 of 115,444 reviewed websitesbeats 30%
- #49,348 of 66,497 online storesbeats 22%
- #46,727 of 60,778 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideOne 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.1 s
3.6 s
4.1 s
Speed
Reduce unused JavaScript
1.4 s · 277 KiBAbout 277 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
900 ms · 155 KiB5 images could be 155 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 64 KiB12 files are served with short cache lifetimes, so returning visitors download them again (64 KiB).
Google Tag Manager adds 256 ms
256 msGoogle Tag Manager costs a phone 256 ms of main-thread work and 185 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.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 972 ms 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 (Google Tag Manager, Shopify and userway.org and others), adding 512 KiB and 376 ms of main-thread time.
Render-blocking requests
250 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 196 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.3 s
8.3 sThe page becomes fully interactive after 8.3 s. Good is under 3.8 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 265 ms
265 msScripts block taps and scrolling for 265 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image far larger than shown
82 KiB1 image is downloaded at several times the size a phone draws it, for example Desktop.jpg at 1,974 px wide, shown at 390 px. Resized copies would save about 82 KiB.
About 0.5 g of CO₂ per visit
0.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 59.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.7 MB in 161 requests
1.7 MBYour homepage downloads 1.7 MB in 161 requests on a phone: other files 826 KiB (94), scripts 544 KiB (41) and images 254 KiB (16). 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.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (86 characters)
Your title is 86 characters, so Google will cut it off around 60: “PSO-RITE | PSO-MINI | PSOAS MASSAGER | MUSCLE RELEASE | BACK PAIN – Pso-Rite Australia”.
2 H1 headlines
There are 2 <h1> headlines (“Pso-Rite Australia” and “"THANK YOU FOR MAKING PSO-RITE SUCH A MASSIVE VIR…”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and Product) but with 1 problem, for example “Organization: url points at a different host (https://pso-rite.com)”.
48 internal links, 10 external
The homepage links to 48 pages on pso-rite.com.au and 10 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Better athletes need better recovery. Introducing the Pso-Rite, the first and only self massage tool designed to releas…”.
Canonical URL set
The canonical URL is https://pso-rite.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://pso-rite.com.au/sitemap.xml.
AI search readiness
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://pso-rite.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://pso-rite.com.au/products/pso-rite and https://pso-rite.com.au/collections/all/products/pso-rite all use the title “PSO-RITE | PSOAS RELIEF | MASSAGE TOOL | BACK PAIN | MUSCLE RELEASE –…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://pso-rite.com.au/policies/privacy-policy and https://pso-rite.com.au/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://pso-rite.com.au/products/pso-rite, https://pso-rite.com.au/products/pso-mini and https://pso-rite.com.au/collections/all/products/pso-rite use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://pso-rite.com.au/collections/all/products/pso-everything-combo-pack, whose canonical is https://pso-rite.com.au/products/pso-everything-combo-pack. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://pso-rite.com.au/pages/videos has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://pso-rite.com.au/pages/videos and https://pso-rite.com.au/policies/refund-policy have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Invalid or unexpected token”.
2 checks passed
Tap targets are thumb-sized
16 of 17 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.
Only about 135 words
The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER NOW” and “SHOP NOW”.
9 calls to action
The homepage has 9 calls to action, for example “CONTACT”, “ORDER NOW” and “SHOP NOW”.
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: 9 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
14 other companies contacted
Loading the homepage contacts 14 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 pso-rite.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Uppromote Affiliate · Affliate By Secomapp · amazonaws.com · nfcube.com · cloudfront.net
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
- jQuery
- 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 32 issues on pso-rite.com.au, including 12 speed issues, 3 SEO issues and 2 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.