Website review, no card needed

houseofknives.us logo

houseofknives.us website review

Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 76 checks

This review found 36 issues worth fixing on houseofknives.us, 13 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of houseofknives.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix47
  • Reduce unused JavaScript

    1.5 s · 1.1 MB

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

  • Mobile performance score: 47

    47/100

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

  • Improve image delivery

    300 ms · 884 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, instant.one and Google CDN and others), adding 1.0 MB and 887 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 545 KiB

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

  • Render-blocking requests

    750 ms

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

  • Google/Doubleclick Ads adds 475 ms

    475 ms

    Google/Doubleclick Ads costs a phone 475 ms of main-thread work and 404 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.

  • Main-thread work: 3.8 s

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

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    29 KiB

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

  • Reduce unused CSS

    18 KiB

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

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

    107 ms

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

Core Web Vitals

5 to fix44
  • Largest Contentful Paint: 9.7 s

    9.7 s

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

  • Time to Interactive: 12.0 s

    12.0 s

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

  • Cumulative Layout Shift: 0.323

    0.323

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 105 ms

    105 ms

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

Images and page weight

3 to fix40
  • Page weight: 13.4 MB in 260 requests

    13.4 MB

    Your homepage downloads 13.4 MB in 260 requests on a phone: media 8.4 MB (2), images 2.3 MB (55) and scripts 1.0 MB (65). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    571 KiB

    3 images are downloaded at several times the size a phone draws them, for example 87863_4376138547298_11337d1d_14c3_4443_97b6_5539db41a051.png at 952 px wide, shown at 147 px. Resized copies would save about 571 KiB.

  • 13 images in older formats

    13 images (1.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.

  • About 3.8 g of CO₂ per visit

    3.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.78 g of CO₂e: 454.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 load when needed

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

Accessibility

9 to fixGoogle 8490
  • 13 text elements with low contrast

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

  • 4 tap targets too small

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

  • 2 images without alt text

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

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • 3 form fields without a label

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

  • 3 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

6 to fixGoogle 6977
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Knives Australia, Knives for Sale - Australia’s Best Knife Shop – House of Knives”.

  • 2 H1 headlines

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

  • Meta description is long (302 characters)

    Your meta description is 302 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.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 105 internal links, 10 external

    The homepage links to 105 pages on houseofknives.us and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.houseofknives.us/.

  • 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.houseofknives.us/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.houseofknives.us/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

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

Other pages

1 to fix95
  • 14 pages without an H1

    https://www.houseofknives.us/collections/ryda-knives, https://www.houseofknives.us/collections/butcher-meat-industry, https://www.houseofknives.us/collections/for-home-cooks-chefs, https://www.houseofknives.us/collections/all-purpose-knives, https://www.houseofknives.us/collections/knife-sets and https://www.houseofknives.us/collections/whetstone and 8 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 42 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

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://www.houseofknives.us/cdn/shop/files/87863_2137929154658_38679365_c00d_4e9c_9292_908cdde01734.webp?v=1718818199&width=600.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 405 ()”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 651 words of copy

    The homepage carries about 651 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact Support”, “Your Order” and “Track My Order”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 71 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 7 cookies set on arrival

    7

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 houseofknives.us, 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 · Essential Countdown · gropulse.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

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
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 36 issues on houseofknives.us, including 13 speed issues, 6 SEO issues and 1 conversion gap. 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