Website review, no card needed

houseoferrors.org logo

houseoferrors.org website review

Visit site (opens in a new tab)Reviewed 7 November 202629 issues · 73 checks

This review found 29 issues worth fixing on houseoferrors.org, 7 of them high impact, across 73 checks. The most urgent: page weight: 18.3 MB in 274 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.8 s882 msMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 2026989 ms
Jun 13, 2026996 ms
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.5 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
106 ms91 msMay 16Oct 3193 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202698 ms
May 23, 202696 ms
May 30, 202695 ms
Jun 6, 202694 ms
Jun 13, 202696 ms
Jun 20, 202697 ms
Jun 27, 2026101 ms
Jul 4, 2026104 ms
Jul 11, 2026103 ms
Jul 18, 2026103 ms
Jul 25, 2026100 ms
Aug 1, 2026100 ms
Aug 8, 2026101 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 202698 ms
Sep 5, 2026100 ms
Sep 12, 202699 ms
Sep 19, 2026103 ms
Sep 26, 2026102 ms
Oct 3, 202699 ms
Oct 10, 2026100 ms
Oct 17, 202695 ms
Oct 24, 202694 ms
Oct 31, 202693 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 houseoferrors.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. houseoferrors.org at 0.4 s0.4 s
  2. houseoferrors.org at 0.8 s0.8 s
  3. houseoferrors.org at 1.2 s1.2 s
  4. houseoferrors.org at 1.5 s1.5 s
  5. houseoferrors.org at 1.9 s1.9 s
  6. houseoferrors.org at 2.3 s2.3 s
  7. houseoferrors.org at 2.7 s2.7 s
  8. houseoferrors.org at 3.1 s3.1 s

Speed

6 to fix82
  • Mobile performance score: 82

    82/100

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

  • Render-blocking requests

    600 ms

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

  • Reduce unused JavaScript

    300 ms · 201 KiB

    About 201 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 97 KiB

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

  • Improve image delivery

    381 KiB

    8 images could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1,933 HTML elements

    The page has 1,933 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 (Klaviyo, one.store and Shopify and others), adding 545 KiB and 182 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 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).

  • Reduce unused CSS

    32 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix100
  • 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: 10.0 s

    10.0 s

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

  • Speed Index: 7.0 s

    7.0 s

    Visually, the page fills in at 7.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.

  • Real-user TTFB: 845 ms

    845 ms

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and other technologies to personalize your e…”. Most of its time is element render delay (2.6 s).

  • Tap response (INP) held steady for real visitors

    -4%

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

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

    +19%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 104 ms

    104 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 2 ms

    2 ms

    Scripts block the page for only 2 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 18.3 MB in 274 requests

    18.3 MB

    Your homepage downloads 18.3 MB in 274 requests on a phone: media 15.3 MB (4), images 1.3 MB (46) and other files 936 KiB (143). Under 2 MB keeps phones on slow connections fast.

  • About 5.2 g of CO₂ per visit

    5.19 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9594
  • 6 images without alt text

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

  • Zoom is disabled

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

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 31 automated accessibility rules passed

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

SEO

3 to fixGoogle 8581
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • 104 internal links, 1 external

    The homepage links to 104 pages on houseoferrors.org and 1 external page.

5 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “House of Errors – HOUSE OF ERRORS”.

  • Canonical URL set

    The canonical URL is https://www.houseoferrors.org/en-us.

  • 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://www.houseoferrors.org/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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://www.houseoferrors.org/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.houseoferrors.org/en-us/collections/new-arrivals, https://www.houseoferrors.org/en-us/collections/knitwear, https://www.houseoferrors.org/en-us/collections/tees-shirts, https://www.houseoferrors.org/en-us/collections/outerwear, https://www.houseoferrors.org/en-us/collections/trousers-and-denim and https://www.houseoferrors.org/en-us/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.houseoferrors.org/en-us/collections/new-arrivals, https://www.houseoferrors.org/en-us/collections/knitwear, https://www.houseoferrors.org/en-us/collections/tees-shirts, https://www.houseoferrors.org/en-us/collections/outerwear, https://www.houseoferrors.org/en-us/collections/trousers-and-denim and https://www.houseoferrors.org/en-us/collections/accessories 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 50 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 25 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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 117 words

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

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

3 checks passed
  • Clear next step on the first screen

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

  • 17 calls to action

    The homepage has 17 calls to action, for example “Shop”, “Book” and “Shop Outerwear”.

  • 15 short forms

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.

  • 4 cookies set on arrival

    4

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 houseoferrors.org, 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 · one.store · chimpstatic.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
Hosting
Shopify

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 houseoferrors.org, including 12 speed issues, 3 SEO 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