Website review, no card needed

floydhome.com logo

floydhome.com website review

Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 79 checks

This review found 29 issues worth fixing on floydhome.com, 6 of them high impact, across 79 checks. The most urgent: page weight: 4.6 MB in 430 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
1.6 s1.1 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
149 ms123 msMay 16Oct 31128 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026140 ms
May 23, 2026139 ms
May 30, 2026137 ms
Jun 6, 2026136 ms
Jun 13, 2026138 ms
Jun 20, 2026137 ms
Jun 27, 2026137 ms
Jul 4, 2026132 ms
Jul 11, 2026131 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026126 ms
Aug 8, 2026128 ms
Aug 15, 2026130 ms
Aug 22, 2026134 ms
Aug 29, 2026141 ms
Sep 5, 2026143 ms
Sep 12, 2026146 ms
Sep 19, 2026146 ms
Sep 26, 2026144 ms
Oct 3, 2026142 ms
Oct 10, 2026139 ms
Oct 17, 2026137 ms
Oct 24, 2026133 ms
Oct 31, 2026128 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 floydhome.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix69
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Klarna and others), adding 1.7 MB and 992 ms of main-thread time.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Google Tag Manager adds 536 ms

    536 ms

    Google Tag Manager costs a phone 536 ms of main-thread work and 687 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.

  • Reduce unused JavaScript

    591 KiB

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

  • Improve image delivery

    150 ms · 418 KiB

    6 images could be 418 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.

  • Use efficient cache lifetimes

    150 ms · 401 KiB

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

  • Main-thread work: 3.3 s

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

  • Shopify adds 51 ms

    51 ms

    Shopify costs a phone 51 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 long tasks on the main thread

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

  • Legacy JavaScript

    81 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    11 KiB

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

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

    10 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 21.9 s

    21.9 s

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

  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • Total Blocking Time: 445 ms

    445 ms

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

  • Speed Index: 3.9 s

    3.9 s

    Visually, the page fills in at 3.9 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) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.3 s 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.2 s

    1.2 s

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

  • Real-user INP: 100 ms

    100 ms

    Real visitors wait 100 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.0 s

    1.0 s

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

  • Real-user TTFB: 520 ms

    520 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 4.6 MB in 430 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 430 requests on a phone: scripts 1.9 MB (118), other files 1.4 MB (262) and images 915 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    12 KiB

    1 image is downloaded at several times the size a phone draws it, for example 20231024_POST_Floyd_Edited-15-_1.jpg at 1,100 px wide, shown at 350 px. Resized copies would save about 12 KiB.

  • 2 images in older formats

    2 images (131 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (130 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 156.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

3 to fixGoogle 10096
  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is short (10 characters)

    Your title is only 10 characters: “Floyd Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 128 internal links, 2 external

    The homepage links to 128 pages on floydhome.com and 2 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Hi, we're Floyd. We make furniture for keeping. Simple to assemble, easy to move, shipped to your door. A timeless solu…”.

  • One H1 headline

    Your main headline reads: “Floyd Home”.

  • Canonical URL set

    The canonical URL is https://floydhome.com/.

  • Structured data in place

    Structured data found: Organization 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://floydhome.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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 (939 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://floydhome.com/pages/member-program has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://floydhome.com/blogs/livedin/floyd-what-s-behind-the-name, whose canonical is https://floydhome.com/blogs/stories/floyd-what-s-behind-the-name. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://floydhome.com/collections/systems-for-living has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://floydhome.com/collections/systems-for-living has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

    2 of 10 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 “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

  • 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 391 words of copy

    The homepage carries about 391 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop”, “Contact” and “Shop All”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Heap.

Privacy and tracking

  • 10 trackers load before any consent

    10

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

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).

  • 48 other companies contacted

    Loading the homepage contacts 48 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 floydhome.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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Lucky Orange · Inveterate · Uppromote Affiliate · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Affliate By Secomapp · rise-ai.com · getmulberry.com · cloudfront.net · trafficmanager.net · shareasale.com · gorgias.chat · 9gtb.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

E-commerce
Shopify
Analytics
Google Tag Manager | Heap
Hosting
Shopify

Company

Headquarters
Detroit

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on floydhome.com, including 14 speed issues, 1 SEO issue 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

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