Website review, no card needed
inaessentials.au website review
Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 81 checks
This review found 38 issues worth fixing on inaessentials.au, 15 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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
70C- #91,530 of 109,350 reviewed websitesbeats 14%
- #55,605 of 61,859 online storesbeats 8%
- #51,544 of 56,401 Shopify storesbeats 7%
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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Avoid multiple page redirects
17.0 sThe page goes through 2 redirects before it starts loading, costing about 17.0 s. Link and advertise the final URL directly.
Reduce unused JavaScript
3.0 s · 712 KiBAbout 712 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Main-thread work: 30.3 s
A phone's processor spends 30.3 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.3 s
1.3 sShopify costs a phone 1.3 s of main-thread work and 690 KiB 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.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,386 HTML elements
The page has 3,386 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, inaessentials.us and Klaviyo and others), adding 3.8 MB and 3.5 s of main-thread time.
inaessentials.us adds 919 ms
919 msinaessentials.us costs a phone 919 ms of main-thread work and 2.4 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.
Klaviyo adds 592 ms
592 msKlaviyo costs a phone 592 ms of main-thread work and 361 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.
recart.com adds 587 ms
587 msrecart.com costs a phone 587 ms of main-thread work and 222 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.
Render-blocking requests
550 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Minify JavaScript
450 ms · 36 KiB36 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 482 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
250 ms · 96 KiB8 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 155 KiB18 files are served with short cache lifetimes, so returning visitors download them again (155 KiB).
Document request latency
150 msThe HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
37 KiBPolyfills for old browsers add 37 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
10 KiB10 KiB JavaScript is shipped twice across bundles.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 19.0 s
19.0 sYour largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 25.6 s
25.6 sThe page becomes fully interactive after 25.6 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image 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
Page weight: 6.2 MB in 600 requests
6.2 MBYour homepage downloads 6.2 MB in 600 requests on a phone: scripts 2.0 MB (167), images 1.9 MB (66) and other files 1.7 MB (323). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
banner-2_mob_uk.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images far larger than shown
98 KiB2 images are downloaded at several times the size a phone draws them, for example v1copy_1.png at 500 px wide, shown at 50 px. Resized copies would save about 98 KiB.
3 images in older formats
3 images (266 KiB) are 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.
About 1.8 g of CO₂ per visit
1.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
1 checks passed
52 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: 52 passed and 5 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
96 internal links, 13 external
The homepage links to 96 pages on inaessentials.au and 13 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Certified Organic cosmetics produced in Bulgaria and loved in 26 countries! Find here your favorite natural product and…”.
Title: 65 characters
Your title is a healthy 65 characters: “Family Online Store for 100% Organic Cosmetics | InaEssentials.AU”.
Canonical URL set
The canonical URL is https://inaessentials.au/.
Structured data in place
Structured data found: Organization 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://inaessentials.au/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,728 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://inaessentials.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://inaessentials.au/collections/floral-waters has no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://inaessentials.au/collections/all-products, https://inaessentials.au/collections/face-care, https://inaessentials.au/collections/hair-care, https://inaessentials.au/collections/body-care, https://inaessentials.au/collections/floral-waters and https://inaessentials.au/collections/routina and 2 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 38 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 broken images
2 images failed to load on a phone, for example https://public-images.judge.me/judgeme/medals-v2/ver_rev/gold.svg?auto=format.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
24 of 24 tappable elements near the top are at least 24 px.
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.
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 1,714 words of copy
The homepage carries about 1,714 words of visible text.
5 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact us”, “buy now” and “LEARN MORE”.
32 short forms
32 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 78 testimonial or review blocks, a star rating and “more than 500,000 satisfied 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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 12 of them by other companies (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.
37 other companies contacted
Loading the homepage contacts 37 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 inaessentials.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Recart Sms List Growth · Judge Me Reviews · Hulk Form Builder · Zipchat Ai Chatbot · Xapps Geo · Dealeasy · Countdown Timer
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
- Bootstrap
- 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 38 issues on inaessentials.au, including 20 speed issues, 2 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.