Website review, no card needed

hofthome.com logo

hofthome.com website review

Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 84 checks

This review found 34 issues worth fixing on hofthome.com, 13 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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.1 s867 msMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 2026935 ms
May 30, 2026925 ms
Jun 6, 2026929 ms
Jun 13, 2026945 ms
Jun 20, 2026952 ms
Jun 27, 2026953 ms
Jul 4, 2026934 ms
Jul 11, 2026904 ms
Jul 18, 2026893 ms
Jul 25, 2026901 ms
Aug 1, 2026924 ms
Aug 8, 2026933 ms
Aug 15, 2026954 ms
Aug 22, 2026967 ms
Aug 29, 2026972 ms
Sep 5, 2026980 ms
Sep 12, 2026967 ms
Sep 19, 2026959 ms
Sep 26, 2026984 ms
Oct 3, 2026989 ms
Oct 10, 20261.0 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
122 ms105 msMay 23Nov 7113 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026107 ms
May 30, 2026107 ms
Jun 6, 2026110 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026114 ms
Jul 4, 2026113 ms
Jul 11, 2026114 ms
Jul 18, 2026113 ms
Jul 25, 2026113 ms
Aug 1, 2026113 ms
Aug 8, 2026113 ms
Aug 15, 2026114 ms
Aug 22, 2026116 ms
Aug 29, 2026118 ms
Sep 5, 2026116 ms
Sep 12, 2026116 ms
Sep 19, 2026115 ms
Sep 26, 2026115 ms
Oct 3, 2026115 ms
Oct 10, 2026119 ms
Oct 17, 2026120 ms
Oct 24, 2026119 ms
Oct 31, 2026118 ms
Nov 7, 2026113 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 hofthome.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hofthome.com at 1.0 s1.0 s
  2. hofthome.com at 1.9 s1.9 s
  3. hofthome.com at 2.9 s2.9 s
  4. hofthome.com at 3.8 s3.8 s
  5. hofthome.com at 4.8 s4.8 s
  6. hofthome.com at 5.7 s5.7 s
  7. hofthome.com at 6.7 s6.7 s
  8. hofthome.com at 7.6 s7.6 s

Speed

10 to fix54
  • Use efficient cache lifetimes

    4.3 s · 2.4 MB

    13 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

  • Reduce unused JavaScript

    3.3 s · 2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Minify JavaScript

    800 ms · 584 KiB

    584 KiB could be saved by minifying JavaScript.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Lucky Orange, Google CDN and Klaviyo and others), adding 3.3 MB and 953 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Main-thread work: 3.0 s

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

  • Lucky Orange adds 275 ms

    275 ms

    Lucky Orange costs a phone 275 ms of main-thread work and 101 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.

  • empirerender.com adds 49 ms

    49 ms

    empirerender.com costs a phone 49 ms of main-thread work and 2.3 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.

  • Google CDN adds 244 ms

    244 ms

    Google CDN costs a phone 244 ms of main-thread work and 331 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.

  • Improve image delivery

    150 ms · 97 KiB

    4 images could be 97 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.

  • 10 long tasks on the main thread

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

  • Reduce unused CSS

    160 ms · 22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • Font display

    50 ms

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 28.4 s

    28.4 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Total Blocking Time: 504 ms

    504 ms

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

  • Tap response (INP) held steady for real visitors

    +8%

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

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

    +14%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 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.3 s

    1.3 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 657 ms

    657 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.03

    0.03

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

Images and page weight

2 to fix69
  • Page weight: 5.0 MB in 140 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 140 requests on a phone: scripts 3.4 MB (76), images 1.1 MB (21) and fonts 356 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Untitleddesign-2026-03-07T142054.073.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).

  • 1 image in older formats

    1 image (161 KiB) is 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 (161 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.43 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 7990
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 10 text elements with low contrast

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

  • 8 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 checks passed
  • Every image has alt text

    All 36 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 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 10092
  • Meta description is long (162 characters)

    Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 52 internal links, 11 external

    The homepage links to 52 pages on hofthome.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Hoft Home”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Modern & Scandinavian Furniture | Hoft Home”.

  • Canonical URL set

    The canonical URL is https://www.hofthome.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://www.hofthome.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • llms.txt published

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

Other pages

1 to fix95
  • 8 pages without an H1

    https://www.hofthome.com/collections/sofas-loveseats, https://www.hofthome.com/collections/lounge-arm-chairs-1, https://www.hofthome.com/collections/beds, https://www.hofthome.com/collections/nightstands, https://www.hofthome.com/collections/dressers and https://www.hofthome.com/pages/contactus and 2 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 21 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 13 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 “Refused to apply style from 'https://www.hofthome.com/cdn/shop/t/147/assets/new-header.css?v=60592369723889685681727316…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • Thin social proof

    Social proof on the homepage: 117 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Contact Us” and “Apply/Login”.

  • 8 short forms

    8 short forms (1 field at most) are right 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

1 to fix
  • 3 trackers load before any consent

    3

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies, 1 of them by other companies (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.

  • 30 other companies contacted

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

Apps your storefront loads

Gorgias Live Chat Helpdesk · Disable Right Click · Okendo · Glood Product Recommendations · Klaviyo Email Marketing Sms · Orderlogic Min Max Limits · Recommendation Kit · trustpilot.com · getmulberry.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
Hosting
Cloudflare

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 hofthome.com, including 14 speed issues, 2 SEO issues and 5 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