Website review, no card needed
oomphhome.com website review
Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 86 checks
This review found 34 issues worth fixing on oomphhome.com, 13 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
82B- #33,153 of 117,610 reviewed websitesbeats 66%
- #22,156 of 66,923 online storesbeats 60%
- #21,424 of 61,018 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 145 ms |
| May 23, 2026 | 131 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 116 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 131 ms |
| Jul 4, 2026 | 133 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 132 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 97 ms |
| Oct 31, 2026 | 97 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
Improve image delivery
5.8 s · 1.3 MB25 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.
Reduce unused JavaScript
1.8 s · 471 KiBAbout 471 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and csell.co and others), adding 897 KiB and 964 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
550 ms · 242 KiB29 files are served with short cache lifetimes, so returning visitors download them again (242 KiB).
Render-blocking requests
600 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 319 ms
319 msGoogle Tag Manager costs a phone 319 ms of main-thread work and 342 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Reduce unused CSS
120 ms · 40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 120 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 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.
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: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 24.8 s
24.8 sThe page becomes fully interactive after 24.8 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 325 ms
325 msScripts block taps and scrolling for 325 ms in total while the page loads. Good is under 200 ms.
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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 97 ms
97 msReal visitors wait 97 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 599 ms
599 msReal visitors wait 599 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 54% faster for real visitors
-54%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 333 requests
4.9 MBYour homepage downloads 4.9 MB in 333 requests on a phone: images 2.3 MB (61), scripts 1.3 MB (90) and other files 861 KiB (140). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
carousel_0000_Layer_1_6d2e612c-38c3-4acc-9e3d-3fc98d87c569.j 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
52 KiB1 image is downloaded at several times the size a phone draws it, for example carousel_bedroom_1be1b014-1302-46f5-a1fa-c1633842edc3.jpg at 390 px wide, shown at 50 px. Resized copies would save about 52 KiB.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.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
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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
35 images without alt text
35 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 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: 50 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
162 internal links, 9 external
The homepage links to 162 pages on oomphhome.com and 9 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “American-made designer furnishings for every room in the house. Shop our classic yet modern accent pieces, side and cof…”.
Title: 65 characters
Your title is a healthy 65 characters: “High-End Online Furniture Store | Chic & Vibrant Luxury Furniture”.
Canonical URL set
The canonical URL is https://oomphhome.com/.
Structured data in place
Structured data found: FurnitureStore, Organization, WebPage 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://oomphhome.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://oomphhome.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.
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: 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 (520 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://oomphhome.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://oomphhome.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://oomphhome.com/customer_authentication/redirect and https://oomphhome.com/a/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://oomphhome.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://oomphhome.com/collections/tables, https://oomphhome.com/collections/side-tables-nightstands and https://oomphhome.com/collections/coffee-tables took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.
3 checks passed
Linked pages load
9 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.
Titles are unique
Every page we checked has its own title.
Best practices
4 broken images
4 images failed to load on a phone, for example https://d.adroll.com/uev/6LCVCEELYVHGNGHYVJSFBD/A5T6LKBGYBCOBEDXFAWR2G/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=fe296d469e454f55b832df061d7f8879-1794174614651.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
2 checks passed
Tap targets are thumb-sized
30 of 35 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.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 380 words of copy
The homepage carries about 380 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: “Start Here” and “Shop Now”.
9 calls to action
The homepage has 9 calls to action, for example “Order Samples”, “CONTACT” and “Start Here”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
41 other companies contacted
Loading the homepage contacts 41 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 oomphhome.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Klaviyo Email Marketing Sms · chimpstatic.com · csell.co · covet.pics · adroll.com · webmarked.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- New Canaan
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on oomphhome.com, including 13 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.