Website review, no card needed

abchome.com logo

abchome.com website review

Visit site (opens in a new tab)Reviewed 18 October 202637 issues · 88 checks

This review found 37 issues worth fixing on abchome.com, 14 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.5 s3.0 sApr 25Oct 103.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.8 s
May 2, 20265.1 s
May 9, 20265.2 s
May 16, 20265.0 s
May 23, 20264.4 s
May 30, 20263.9 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.6 s
Sep 26, 20263.5 s
Oct 3, 20263.4 s
Oct 10, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
259 ms205 msApr 25Oct 10242 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026215 ms
May 2, 2026251 ms
May 9, 2026251 ms
May 16, 2026250 ms
May 23, 2026243 ms
May 30, 2026232 ms
Jun 6, 2026239 ms
Jun 13, 2026239 ms
Jun 20, 2026246 ms
Jun 27, 2026253 ms
Jul 4, 2026238 ms
Jul 11, 2026231 ms
Jul 18, 2026221 ms
Jul 25, 2026220 ms
Aug 1, 2026228 ms
Aug 8, 2026237 ms
Aug 15, 2026246 ms
Aug 22, 2026242 ms
Aug 29, 2026232 ms
Sep 5, 2026218 ms
Sep 12, 2026212 ms
Sep 19, 2026211 ms
Sep 26, 2026213 ms
Oct 3, 2026231 ms
Oct 10, 2026242 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

Full-page screenshot of abchome.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abchome.com at 1.3 s1.3 s
  2. abchome.com at 2.7 s2.7 s
  3. abchome.com at 4.0 s4.0 s
  4. abchome.com at 5.3 s5.3 s
  5. abchome.com at 6.7 s6.7 s
  6. abchome.com at 8.0 s8.0 s
  7. abchome.com at 9.3 s9.3 s
  8. abchome.com at 10.7 s10.7 s

Speed

13 to fix32
  • Render-blocking requests

    2.3 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 711 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.

  • Reduce unused CSS

    1.2 s · 86 KiB

    About 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 9.2 s

    A phone's processor spends 9.2 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Kameleoon and others), adding 1.8 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    661 KiB

    About 661 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    551 KiB

    22 files are served with short cache lifetimes, so returning visitors download them again (551 KiB).

  • Facebook adds 419 ms

    419 ms

    Facebook costs a phone 419 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 409 ms. During a long task the page ignores taps.

  • Kameleoon adds 312 ms

    312 ms

    Kameleoon costs a phone 312 ms of main-thread work and 54 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.

  • alia-prod.com adds 284 ms

    284 ms

    alia-prod.com costs a phone 284 ms of main-thread work and 258 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,545 HTML elements

    The page has 1,545 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 206 KiB

    2 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 57 but mobile only 32. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 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.

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

  • 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: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Time to Interactive: 30.6 s

    30.6 s

    The page becomes fully interactive after 30.6 s. Good is under 3.8 s.

  • Speed Index: 10.9 s

    10.9 s

    Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 6.8 s

    6.8 s

    Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Fall Dining Sale”.

  • Total Blocking Time: 2.1 s

    2.1 s

    Scripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 215 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 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.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 194 ms

    194 ms

    Real visitors wait 194 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 577 ms

    577 ms

    Real visitors wait 577 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 33% faster for real visitors

    -33%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.8 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 315 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 315 requests on a phone: scripts 2.3 MB (135), media 955 KiB (2) and other files 863 KiB (141). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 177.9 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

4 to fixGoogle 9494
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Structured data has 1 problem

    Structured data found (Organization, VideoObject and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://abchome.com/search?q={search_term_string}")”.

  • One H1 headline

    Your <h1> is empty.

  • 269 internal links, 6 external

    The homepage links to 269 pages on abchome.com and 6 external pages.

6 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “"Explore curated rugs, modern furniture, & unique home decor online. Find one-of-a-kind pieces and the best prices at a…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Rugs, Furniture & Home Decor Online: abc carpet & home”.

  • Canonical URL set

    The canonical URL is https://abchome.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://abchome.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://abchome.com/llms.txt (8 KiB, 80 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 10 pages share a meta description

    https://abchome.com/collections/fall-dining-sale, https://abchome.com/pages/promotions, https://abchome.com/pages/wishlist, https://abchome.com/collections/new-arrivals-1, https://abchome.com/collections/new-arrivals-rugs-carpet and https://abchome.com/collections/new-arrivals-lighting-1 and 4 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://abchome.com/pages/promotions and https://abchome.com/pages/wishlist 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 124 found) and read each the way a search engine does.

6 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 to fixGoogle 9687
  • 5 small tap targets

    5 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix65
  • 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.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 87 words

    The homepage has only about 87 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

4 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop the Fall Collection”, “Shop by Size” and “Shop By Style”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 50 other companies contacted

    Loading the homepage contacts 50 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 abchome.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on abchome.com, including 19 speed issues, 2 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25