Website review, no card needed

infinitymassagechairs.com logo

infinitymassagechairs.com website review

Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 94 checks

This review found 40 issues worth fixing on infinitymassagechairs.com, 15 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
1.5 s1.1 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
106 ms83 msMay 2Oct 1796 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202687 ms
May 9, 202686 ms
May 16, 202687 ms
May 23, 202688 ms
May 30, 202688 ms
Jun 6, 202691 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202688 ms
Jul 4, 202688 ms
Jul 11, 202694 ms
Jul 18, 202688 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202689 ms
Aug 22, 202692 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202697 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 202696 ms
Oct 10, 202697 ms
Oct 17, 202696 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 infinitymassagechairs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. infinitymassagechairs.com at 0.4 s0.4 s
  2. infinitymassagechairs.com at 0.8 s0.8 s
  3. infinitymassagechairs.com at 1.1 s1.1 s
  4. infinitymassagechairs.com at 1.5 s1.5 s
  5. infinitymassagechairs.com at 1.9 s1.9 s
  6. infinitymassagechairs.com at 2.3 s2.3 s
  7. infinitymassagechairs.com at 2.6 s2.6 s
  8. infinitymassagechairs.com at 3.0 s3.0 s

Speed

6 to fix61
  • Reduce unused JavaScript

    1.9 s · 375 KiB

    About 375 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 234 KiB

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

  • Render-blocking requests

    1.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Trust Pilot and others), adding 15.0 MB and 221 ms of main-thread time.

  • Cloudinary adds 0 ms

    0 ms

    Cloudinary costs a phone 0 ms of main-thread work and 14.5 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.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    150 ms · 32 KiB

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

  • Improve image delivery

    150 ms · 27 KiB

    2 images could be 27 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.

  • Minify JavaScript

    150 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Document request latency

    29 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Phones get a much slower page than desktops

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

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 468 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.9 s

    9.9 s

    Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Time to Interactive: 9.9 s

    9.9 s

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Speed Index: 5.3 s

    5.3 s

    Visually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 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) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 96 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.4 s

    1.4 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 619 ms

    619 ms

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

  • Total Blocking Time: 114 ms

    114 ms

    Scripts block the page for only 114 ms while loading. Good is under 200 ms.

  • 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: 15.8 MB in 62 requests

    15.8 MB

    Your homepage downloads 15.8 MB in 62 requests on a phone: media 14.4 MB (12), scripts 713 KiB (18) and stylesheets 266 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 4.5 g of CO₂ per visit

    4.47 g

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

11 to fixGoogle 7784
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 14 tap targets too small

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

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

9 to fixGoogle 8259
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://infinitymassagechairs.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at infinitymassagechairs.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 85 internal links, 12 external

    The homepage links to 85 pages on infinitymassagechairs.com and 12 external pages.

1 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Massage Chairs & Recliners | Infinity Massage Chairs”.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://infinitymassagechairs.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (373 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://infinitymassagechairs.com/massage-chairs, https://infinitymassagechairs.com/massage-chairs/massagers, https://infinitymassagechairs.com/massage-chairs/accessories, https://infinitymassagechairs.com/locations, https://infinitymassagechairs.com/health-benefits and https://infinitymassagechairs.com/savings-calculator and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://infinitymassagechairs.com/massage-chairs, https://infinitymassagechairs.com/massage-chairs/massagers, https://infinitymassagechairs.com/massage-chairs/accessories and https://infinitymassagechairs.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://infinitymassagechairs.com/massage-chairs took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

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

  • 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 9287
  • 9 small tap targets

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

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • About 310 words of copy

    The homepage carries about 310 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP MASSAGE CHAIRS”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Service Request” and “SHOP MASSAGE CHAIRS”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • 12 other companies contacted

    Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 infinitymassagechairs.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
Bootstrap
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on infinitymassagechairs.com, including 12 speed issues, 9 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

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