Website review, no card needed

artfulhome.com logo

artfulhome.com website review

Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 85 checks

This review found 38 issues worth fixing on artfulhome.com, 16 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
2.4 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.2 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
175 ms133 msMay 16Oct 31155 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026138 ms
May 23, 2026139 ms
May 30, 2026146 ms
Jun 6, 2026150 ms
Jun 13, 2026154 ms
Jun 20, 2026162 ms
Jun 27, 2026163 ms
Jul 4, 2026166 ms
Jul 11, 2026162 ms
Jul 18, 2026160 ms
Jul 25, 2026157 ms
Aug 1, 2026155 ms
Aug 8, 2026155 ms
Aug 15, 2026158 ms
Aug 22, 2026160 ms
Aug 29, 2026162 ms
Sep 5, 2026165 ms
Sep 12, 2026169 ms
Sep 19, 2026170 ms
Sep 26, 2026170 ms
Oct 3, 2026165 ms
Oct 10, 2026163 ms
Oct 17, 2026162 ms
Oct 24, 2026155 ms
Oct 31, 2026155 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 artfulhome.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. artfulhome.com at 0.5 s0.5 s
  2. artfulhome.com at 1.0 s1.0 s
  3. artfulhome.com at 1.5 s1.5 s
  4. artfulhome.com at 2.1 s2.1 s
  5. artfulhome.com at 2.6 s2.6 s
  6. artfulhome.com at 3.1 s3.1 s
  7. artfulhome.com at 3.6 s3.6 s
  8. artfulhome.com at 4.1 s4.1 s

Speed

9 to fix42
  • Improve image delivery

    1.4 s · 679 KiB

    20 images could be 679 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 4.8 s

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

  • 4,212 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Intercom, Klaviyo and Clarity and others), adding 974 KiB and 699 ms of main-thread time.

  • Reduce unused JavaScript

    661 KiB

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

  • Reduce unused CSS

    310 ms · 62 KiB

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

  • Klaviyo adds 164 ms

    164 ms

    Klaviyo costs a phone 164 ms of main-thread work and 319 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.

  • Use efficient cache lifetimes

    150 ms · 77 KiB

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

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 214 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).

  • Legacy JavaScript

    25 KiB

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

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

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

    31 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 17.7 s

    17.7 s

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

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Cumulative Layout Shift: 0.272

    0.272

    The layout shifts by 0.272 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.0 s

    6.0 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 360 ms

    360 ms

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

  • 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-31, real Chrome visitors' tap response (inp) went from 138 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    1.8 s

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

  • Real-user INP: 139 ms

    139 ms

    Real visitors wait 139 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.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: 783 ms

    783 ms

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

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

    -16%

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

Images and page weight

4 to fix45
  • Page weight: 5.7 MB in 259 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 259 requests on a phone: images 3.2 MB (51), scripts 1.2 MB (100) and other files 696 KiB (84). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    how_to_measure.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (1.9 MB) 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.

  • An image on the first screen is lazy-loaded

    261030_HP_Festive_New_Arrivals_mobile.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).

  • 3 images below the first screen load straight away

    3 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.4 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 9692
  • 3 tap targets too small

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

  • 3 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • 3 form fields without a label

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 10075
  • No H1 headline

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

  • Title is short (25 characters)

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

  • Meta description is short (11 characters)

    Your meta description is only 11 characters: “Artful Home”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 652 internal links, 0 external

    The homepage links to 652 pages on artfulhome.com and 0 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

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

  • llms.txt published

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

Other pages

3 to fix86
  • 3 pages share a title

    /, https://www.artfulhome.com/pages/artful-home and https://www.artfulhome.com/apps/wishlist all use the title “Artful Home · Artful Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.artfulhome.com/pages/artful-clothing, https://www.artfulhome.com/pages/artful-home, https://www.artfulhome.com/apps/wishlist and https://www.artfulhome.com/pages/contact use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    https://www.artfulhome.com/collections/promotions, https://www.artfulhome.com/collections/mieko-mintz-trunk-show-collection, https://www.artfulhome.com/pages/artful-clothing, https://www.artfulhome.com/pages/artful-home, https://www.artfulhome.com/apps/wishlist and https://www.artfulhome.com/pages/contact and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.artfulhome.com/collections/mieko-mintz-trunk-show-collection, https://www.artfulhome.com/collections/new-arrivals, https://www.artfulhome.com/collections/new-clothing-shoes, https://www.artfulhome.com/collections/new-jewelry, https://www.artfulhome.com/collections/new-wall-art and https://www.artfulhome.com/collections/new-furniture-lighting and 1 other have 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 189 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    12 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 12 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 297 words of copy

    The homepage carries about 297 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE TRUNK SHOW”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “SHOP NOW”, “SHOP THE TRUNK SHOW” and “Contact Us”.

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 52 other companies contacted

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

Apps your storefront loads

Judge Me Reviews · Boost Ai Search Filter · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Microsoft Clarity · Swish Wishlist King · Back In Stock · amazonaws.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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Employees
140
Headquarters
Madison

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on artfulhome.com, including 16 speed issues, 4 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