Website review, no card needed
apriahome.com website review
Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 89 checks
This review found 35 issues worth fixing on apriahome.com, 5 of them high impact, across 89 checks. The most urgent: page weight: 5.7 MB in 278 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,876 of 124,300 reviewed websitesbeats 93%
- #3,181 of 69,848 online storesbeats 93%
- #3,081 of 63,521 Shopify storesbeats 93%
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.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 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 | 117 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 139 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 100 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
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Yotpo and rebuyengine.com and others), adding 1.6 MB and 945 ms of main-thread time.
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
890 KiBAbout 890 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 463 KiB20 files are served with short cache lifetimes, so returning visitors download them again (463 KiB).
Google Tag Manager adds 299 ms
299 msGoogle Tag Manager costs a phone 299 ms of main-thread work and 332 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: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Yotpo adds 184 ms
184 msYotpo costs a phone 184 ms of main-thread work and 459 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.
rebuyengine.com adds 177 ms
177 msrebuyengine.com costs a phone 177 ms of main-thread work and 363 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.
1,917 HTML elements
The page has 1,917 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Improve image delivery
111 KiB5 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
86 KiBAbout 86 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.6 s
20.6 sThe page becomes fully interactive after 20.6 s. Good is under 3.8 s.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 415 ms
415 msScripts block taps and scrolling for 415 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.
Largest content (LCP) held steady for real visitors
-1%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).
10 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 682 ms
682 msReal visitors wait 682 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 117 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.024
0.024The layout barely moves while loading (CLS 0.024, good is under 0.1).
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.
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Enjoy a wider selection of home healthcare products and an …”.
Images and page weight
Page weight: 5.7 MB in 278 requests
5.7 MBYour homepage downloads 5.7 MB in 278 requests on a phone: media 2.0 MB (1), scripts 1.7 MB (94) and other files 823 KiB (114). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Rove6-with-backpack.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).
About 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 192.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 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.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
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.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (240 characters)
Your meta description is 240 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
102 internal links, 5 external
The homepage links to 102 pages on apriahome.com and 5 external pages.
5 checks passed
Title: 33 characters
Your title is a healthy 33 characters: “ApriaHome | Home Medical Supplies”.
Canonical URL set
The canonical URL is https://apriahome.com/.
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://apriahome.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.
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 (997 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://apriahome.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://apriahome.com/collections/diabetes and https://apriahome.com/blogs/diabetes all use the title “Diabetes – Apria Home”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://apriahome.com/pages/resources, https://apriahome.com/blogs/diabetes, https://apriahome.com/pages/living-with-diabetes, https://apriahome.com/pages/respiratory-diseases and https://apriahome.com/pages/living-with-respiratory have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://apriahome.com/collections/respiratory, https://apriahome.com/collections/womens-health, https://apriahome.com/collections/mobility-support, https://apriahome.com/collections/health-wellness, https://apriahome.com/collections/diabetes and https://apriahome.com/pages/resources and 3 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 68 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 735 words of copy
The homepage carries about 735 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: “Buy Here” and “Learn more.”.
15 calls to action
The homepage has 15 calls to action, for example “Buy Here”, “Shop By Products” and “Shop By Room”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Hotjar.
Phone number on the homepage
Your phone number is on the homepage.
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, Hotjar and Klaviyo and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
19 cookies set on arrival
19Opening the homepage sets 19 cookies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 apriahome.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Elevar Conversion Tracking · Rebuy Personalization Engine · yotpo.com · klaviyo.com · rebuyengine.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
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 apriahome.com, including 14 speed issues, 5 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.