Website review, no card needed

personalhouse.com logo

personalhouse.com website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 87 checks

This review found 34 issues worth fixing on personalhouse.com, 11 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.5 s3.7 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.0 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20264.1 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.2 s
Aug 15, 20264.3 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.2 s
Oct 3, 20263.9 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
158 ms95 msMay 16Oct 31144 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026106 ms
Jun 6, 2026107 ms
Jun 13, 2026113 ms
Jun 20, 2026112 ms
Jun 27, 2026109 ms
Jul 4, 2026102 ms
Jul 11, 2026103 ms
Jul 18, 2026111 ms
Jul 25, 2026112 ms
Aug 1, 2026121 ms
Aug 8, 2026140 ms
Aug 15, 2026130 ms
Aug 22, 2026151 ms
Aug 29, 2026138 ms
Sep 5, 2026129 ms
Sep 12, 2026134 ms
Sep 19, 2026123 ms
Sep 26, 2026118 ms
Oct 3, 2026112 ms
Oct 31, 2026144 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 personalhouse.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. personalhouse.com at 0.8 s0.8 s
  2. personalhouse.com at 1.7 s1.7 s
  3. personalhouse.com at 2.5 s2.5 s
  4. personalhouse.com at 3.3 s3.3 s
  5. personalhouse.com at 4.2 s4.2 s
  6. personalhouse.com at 5.0 s5.0 s
  7. personalhouse.com at 5.8 s5.8 s
  8. personalhouse.com at 6.6 s6.6 s

Speed

4 to fix81
  • 3,561 HTML elements

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

  • Mobile performance score: 81

    81/100

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

  • Improve image delivery

    350 ms · 231 KiB

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

  • Render-blocking requests

    450 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Key CDN and Klaviyo and others), adding 689 KiB and 299 ms of main-thread time.

  • Reduce unused JavaScript

    221 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    28 KiB

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

  • Use efficient cache lifetimes

    25 KiB

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

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 52 ms

    52 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Time to Interactive: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 4.6 s

    4.6 s

    Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “61fa5cd0 a6ed 4738 96f6 623b0bddc33c”.

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 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 14% slower for real visitors

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Total Blocking Time: 71 ms

    71 ms

    Scripts block the page for only 71 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

2 to fix81
  • Page weight: 3.6 MB in 295 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 295 requests on a phone: images 1.6 MB (67), other files 963 KiB (150) and scripts 720 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Personal-Chic-gifts-for-pet-lovers.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).

  • About 1.0 g of CO₂ per visit

    1.03 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

10 to fixGoogle 8786
  • 9 text elements with low contrast

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

  • 6 tap targets too small

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

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

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

2 checks passed
  • Every image has alt text

    All 99 images in the HTML carry an alt attribute.

  • 43 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: 43 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 258 internal links, 0 external

    The homepage links to 258 pages on personalhouse.com and 0 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Personalized Gifts: Find unique &amp; customized gifts and ideas for every occasion on the best unique gift websites fo…”.

  • One H1 headline

    Your main headline reads: “Personalized Gifts For Everyone”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Personalized Gifts - Beyond Just A Present - Personal House”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    25%

    A phone browser shows 3,809 words, but the HTML your server sends has only 938. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, logo and sameAs (social profiles). These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://personalhouse.com/pages/wishlist and https://personalhouse.com/collections/all use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://personalhouse.com/collections/personalized-fathers-day-gifts, https://personalhouse.com/collections/bestsellers, https://personalhouse.com/collections/all, https://personalhouse.com/collections/personalized-apparel, https://personalhouse.com/collections/personalized-t-shirts and https://personalhouse.com/collections/personalized-sweatshirts and 1 other 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 159 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

1 to fixGoogle 9693
  • 26 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix78
  • 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 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.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 3,809 words of copy

    The homepage carries about 3,809 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop Now”, “Shop” and “Shop for Him”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 13 cookies set on arrival

    13

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

  • 20 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews · Searchanise Search Filter

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

  • The footer still says © 2024.

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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 personalhouse.com, including 12 speed issues and 4 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