Website review, no card needed
pawfecthouse.com website review
Visit site (opens in a new tab)Reviewed 4 November 202653 issues · 98 checks
This review found 53 issues worth fixing on pawfecthouse.com, 21 of them high impact, across 98 checks. The most urgent: page weight: 11.4 MB in 477 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70C- #96,321 of 114,977 reviewed websitesbeats 14%
- #59,696 of 66,353 online storesbeats 8%
- #55,486 of 60,691 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 238 ms |
| May 23, 2026 | 230 ms |
| May 30, 2026 | 220 ms |
| Jun 6, 2026 | 208 ms |
| Jun 13, 2026 | 202 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 187 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 178 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
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.9 s
Speed
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,601 HTML elements
The page has 3,601 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
650 ms · 2.1 MB43 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and Clarity and others), adding 5.0 MB and 861 ms of main-thread time.
Reduce unused JavaScript
150 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Use efficient cache lifetimes
150 ms · 669 KiB18 files are served with short cache lifetimes, so returning visitors download them again (669 KiB).
Shopify adds 155 ms
155 msShopify costs a phone 155 ms of main-thread work and 3.2 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.
Klaviyo adds 205 ms
205 msKlaviyo costs a phone 205 ms of main-thread work and 633 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.
teeinblue.com adds 107 ms
107 msteeinblue.com costs a phone 107 ms of main-thread work and 426 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.
ZenDesk adds 102 ms
102 msZenDesk costs a phone 102 ms of main-thread work and 386 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 CSS
150 ms · 97 KiBAbout 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 125 ms. During a long task the page ignores taps.
Legacy JavaScript
68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 39.7 s
39.7 sThe page becomes fully interactive after 39.7 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.425
0.425The layout shifts by 0.425 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 238 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 11.4 MB in 477 requests
11.4 MBYour homepage downloads 11.4 MB in 477 requests on a phone: images 7.2 MB (127), scripts 2.6 MB (150) and other files 1.3 MB (161). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
pfh26_ornament-main-hero-mobile-oct22.webp weighs 604 KiB. On a phone connection a single image that size takes seconds.
26 images in older formats
26 images (4.8 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.
10 images below the first screen load straight away
10 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.24 g of CO₂e: 388.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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid names (1 element)
ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<svg> elements with an img or image role must have alternative text (15 elements)
<svg> elements with an img or image role must have alternative text: 15 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
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.
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 (26 elements)
All page content should be contained by landmarks: 26 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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 links without text
3 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.
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Pawfect House™ - Personalized Gifts | Deliver Happiness, Personally!”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
791 internal links, 15 external
The homepage links to 791 pages on pawfecthouse.com and 15 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Pawfect House™ helps you create unique custom gifts and keepsakes that bring smiles, happy tears, and unforgettable mem…”.
Canonical URL set
The canonical URL is https://pawfecthouse.com/.
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://pawfecthouse.com/sitemap.xml.
AI search readiness
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.
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 (2,402 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pawfecthouse.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://pawfecthouse.com/pages/gift-finder, https://pawfecthouse.com/pages/track-order, https://pawfecthouse.com/pages/christmas, https://pawfecthouse.com/pages/ornament, https://pawfecthouse.com/pages/america-250 and https://pawfecthouse.com/pages/graduation-2026 and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://pawfecthouse.com/collections/best-sellers, https://pawfecthouse.com/collections/wedding-engagement-gifts, https://pawfecthouse.com/collections/housewarming-gifts, https://pawfecthouse.com/collections/new-baby-gifts and https://pawfecthouse.com/collections/retirement-gifts use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://pawfecthouse.com/pages/gift-finder, https://pawfecthouse.com/pages/track-order, https://pawfecthouse.com/pages/happy-customers, https://pawfecthouse.com/pages/christmas, https://pawfecthouse.com/pages/ornament and https://pawfecthouse.com/collections/best-sellers and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://pawfecthouse.com/pages/america-250, https://pawfecthouse.com/pages/graduation-2026 and https://pawfecthouse.com/collections/wedding-engagement-gifts took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
5 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.
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
3 broken images
3 images failed to load on a phone, for example https://pawfecthouse.com/.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.
2 checks passed
Tap targets are thumb-sized
36 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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.
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 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.
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 468 words of copy
The homepage carries about 468 words of visible text.
3 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Track Order”, “National Book Lovers Day” and “Engraved Book Page Holder”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks and 5 trust badges.
Privacy and tracking
12 trackers load before any consent
12Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 7 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.
33 cookies set on arrival
33Opening the homepage sets 33 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.
51 other companies contacted
Loading the homepage contacts 51 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 pawfecthouse.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
- jQuery
- 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 53 issues on pawfecthouse.com, including 20 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.