Website review, no card needed
apparatusstudio.com website review
Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 73 checks
This review found 35 issues worth fixing on apparatusstudio.com, 13 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
80B- #45,917 of 116,363 reviewed websitesbeats 55%
- #30,816 of 66,764 online storesbeats 47%
- #29,658 of 60,925 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 991 ms |
| May 23, 2026 | 948 ms |
| May 30, 2026 | 941 ms |
| Jun 6, 2026 | 921 ms |
| Jun 13, 2026 | 943 ms |
| Jun 20, 2026 | 959 ms |
| Jun 27, 2026 | 954 ms |
| Jul 4, 2026 | 963 ms |
| Jul 11, 2026 | 949 ms |
| Jul 18, 2026 | 931 ms |
| Jul 25, 2026 | 943 ms |
| Aug 1, 2026 | 937 ms |
| Aug 8, 2026 | 887 ms |
| Aug 15, 2026 | 850 ms |
| Aug 22, 2026 | 831 ms |
| Aug 29, 2026 | 831 ms |
| Sep 5, 2026 | 853 ms |
| Sep 12, 2026 | 923 ms |
| Sep 19, 2026 | 943 ms |
| Sep 26, 2026 | 962 ms |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 991 ms |
| Oct 17, 2026 | 970 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 66 ms |
| May 9, 2026 | 66 ms |
| May 16, 2026 | 66 ms |
| May 23, 2026 | 66 ms |
| May 30, 2026 | 63 ms |
| Jun 6, 2026 | 63 ms |
| Jun 13, 2026 | 63 ms |
| Jun 20, 2026 | 64 ms |
| Jun 27, 2026 | 68 ms |
| Jul 4, 2026 | 68 ms |
| Jul 11, 2026 | 69 ms |
| Jul 18, 2026 | 65 ms |
| Jul 25, 2026 | 64 ms |
| Aug 1, 2026 | 64 ms |
| Aug 8, 2026 | 58 ms |
| Aug 15, 2026 | 55 ms |
| Aug 22, 2026 | 54 ms |
| Aug 29, 2026 | 54 ms |
| Sep 5, 2026 | 58 ms |
| Sep 12, 2026 | 62 ms |
| Sep 19, 2026 | 62 ms |
| Sep 26, 2026 | 65 ms |
| Oct 3, 2026 | 70 ms |
| Oct 10, 2026 | 70 ms |
| Oct 17, 2026 | 70 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
Reduce unused JavaScript
8.7 s · 975 KiBAbout 975 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Avoid multiple page redirects
6.9 sThe page goes through 2 redirects before it starts loading, costing about 6.9 s. Link and advertise the final URL directly.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 0 ms
0 msGoogle CDN costs a phone 0 ms of main-thread work and 348 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 663 KiB and 126 ms of main-thread time.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
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
First Contentful Paint: 10.0 s
10.0 sThe first text or image appears after 10.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.4 s
18.4 sYour largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 18.4 s
18.4 sThe page becomes fully interactive after 18.4 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 331 ms
331 msScripts block taps and scrolling for 331 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 66 ms to 70 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-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 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: 798 ms
798 msReal visitors wait 798 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 222 requests
4.4 MBYour homepage downloads 4.4 MB in 222 requests on a phone: scripts 2.4 MB (104), other files 1.4 MB (87) and images 303 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 149.1 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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (1 element)
Banner 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 banner landmark (1 element)
Document should not have more than one banner 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 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.
3 H1 headlines
There are 3 <h1> headlines (“”, “” and “STEP THROUGH THE VEIL”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
49 internal links, 3 external
The homepage links to 49 pages on apparatusstudio.com and 3 external pages.
5 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “OUR LIMITED ASSORTMENT OF IN STOCK LIGHTING, FURNITURE, OBJECTS AND INCENSE ARE AVAILABLE TO SHIP WITHIN TWO WEEKS.”.
Title: 35 characters
Your title is a healthy 35 characters: “www.apparatusstudio.com – APPARATUS”.
Canonical URL set
The canonical URL is https://apparatusstudio.com/.
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://apparatusstudio.com/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 (370 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://apparatusstudio.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://apparatusstudio.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://apparatusstudio.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
https://apparatusstudio.com/collections/objects/EXPEDITED-OBJECTS and https://apparatusstudio.com/collections/objects all use the title “OBJECTS – APPARATUS”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://apparatusstudio.com/customer_authentication/redirect, https://apparatusstudio.com/collections/in-stock-lighting/EXPEDITED-LIGHTING, https://apparatusstudio.com/collections/in-stock-furniture, https://apparatusstudio.com/collections/objects/EXPEDITED-OBJECTS, https://apparatusstudio.com/collections/incense/EXPEDITED-INCENSE and https://apparatusstudio.com/collections/catalog-lighting and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://apparatusstudio.com/collections/in-stock-lighting/EXPEDITED-LIGHTING, whose canonical is https://apparatusstudio.com/collections/in-stock-lighting. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://apparatusstudio.com/customer_authentication/redirect, https://apparatusstudio.com/collections/in-stock-lighting/EXPEDITED-LIGHTING, https://apparatusstudio.com/collections/in-stock-furniture, https://apparatusstudio.com/collections/objects/EXPEDITED-OBJECTS, https://apparatusstudio.com/collections/incense/EXPEDITED-INCENSE and https://apparatusstudio.com/collections/catalog-lighting and 9 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 32 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 broken image
1 image failed to load on a phone, for example https://apparatusstudio.com/?_su_rec=hgEhs7t3St4a9pcSATd_kxAJY9bJ6suB9V0TRbWInN3nA0cmFz7atmrCl51fvpTcNAEtKtM4DFOPxYUqNMfB4UmrMtlLsqDb_nbC_9qm4ikrMRUy0IZwyBLh3VdxPP9_Rq-rXjzPypZYcrKzpYhlWa4i8wr0n5poyJO.
1 JavaScript error while loading
1 error was 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
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 247 words
The homepage has only about 247 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER (0)”.
4 calls to action
The homepage has 4 calls to action, for example “order (0)”, “Contact” and “Subscribe”.
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
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 Klaviyo (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, 1 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.
11 other companies contacted
Loading the homepage contacts 11 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 apparatusstudio.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics
Hiring
- Hiring
- 9 open roles
- Teams
- PRODUCTION (4), SALES (2), INTERIORS (1), PRODUCT DEVELOPMENT (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on apparatusstudio.com, including 10 speed issues, 3 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.