Website review, no card needed
spaorder.com website review
Visit site (opens in a new tab)Reviewed 16 November 202630 issues · 85 checks
This review found 30 issues worth fixing on spaorder.com, 7 of them high impact, across 85 checks. The most urgent: page weight: 4.7 MB in 458 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
88B- #5,438 of 113,487 reviewed websitesbeats 93%
- #3,058 of 65,458 online storesbeats 93%
- #2,967 of 59,879 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 165 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 153 ms |
| Nov 7, 2026 | 146 ms |
| Nov 14, 2026 | 146 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.9 s
1.9 s
2.8 s
3.8 s
4.7 s
5.7 s
6.6 s
7.6 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Facebook and mediadelivery.net and others), adding 2.6 MB and 901 ms of main-thread time.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 827 KiBAbout 827 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.
Render-blocking requests
950 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Improve image delivery
100 ms · 354 KiB6 images could be 354 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Use efficient cache lifetimes
421 KiB22 files are served with short cache lifetimes, so returning visitors download them again (421 KiB).
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 78 KiBAbout 78 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.
Shopify adds 182 ms
182 msShopify costs a phone 182 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.
2,693 HTML elements
The page has 2,693 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
mediadelivery.net adds 135 ms
135 msmediadelivery.net costs a phone 135 ms of main-thread work and 647 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Minify JavaScript
151 KiB151 KiB could be saved by minifying JavaScript.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “DERMVŪ: Your Color Services Got Smarter”.
Cumulative Layout Shift: 0.211
0.211The layout shifts by 0.211 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 153 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 760 ms
760 msReal visitors wait 760 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 89 ms
89 msScripts block the page for only 89 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.7 MB in 458 requests
4.7 MBYour homepage downloads 4.7 MB in 458 requests on a phone: scripts 2.3 MB (232), other files 1,015 KiB (143) and images 970 KiB (40). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Subscribe_and_Save_Mobile.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).
1 image far larger than shown
46 KiB1 image is downloaded at several times the size a phone draws it, for example D209_1.png at 900 px wide, shown at 180 px. Resized copies would save about 46 KiB.
1 image below the first screen load straight away
1 image further down the page (71 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 160.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
16 elements hidden from screen readers can still receive keyboard focus.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
57 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 57 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
231 internal links, 8 external
The homepage links to 231 pages on spaorder.com and 8 external pages.
8 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Shop professional spa and esthetician supplies, Dermwax hard wax beads, soft wax, skincare, lash and brow essentials, a…”.
One H1 headline
Your main headline reads: “Professional Spa & Esthetician Supplies”.
Title: 54 characters
Your title is a healthy 54 characters: “Professional Spa Supplies & Hard Wax Beads | Spa Order”.
Canonical URL set
The canonical URL is https://www.spaorder.com/.
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://www.spaorder.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://www.spaorder.com/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.
2 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,379 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 97 found) and read each the way a search engine does.
7 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
41 of 42 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 548 words of copy
The homepage carries about 548 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop DERMVŪ” and “Shop Bundles”.
34 calls to action
The homepage has 34 calls to action, for example “Subscribe”, “Shop all Learn” and “Buy More, Save More”.
19 short forms
19 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot 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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 4 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.
54 other companies contacted
Loading the homepage contacts 54 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 spaorder.com, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Shopiens · Regios Discounts · Wisepops Popup Builder Cro · Judge Me Reviews · Avada Order Limit · Free Gift · boldapps.net · salesreps.io · nfcube.com · mfyz.app · hubapi.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
- jQuery
- 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 30 issues on spaorder.com, including 15 speed 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.