Website review, no card needed

raghouse.com logo

raghouse.com website review

Visit site (opens in a new tab)Reviewed 8 November 202612 issues · 57 checks

This review found 12 issues worth fixing on raghouse.com, 3 of them high impact, across 57 checks. The most urgent: page weight: 4.4 MB in 163 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
1.8 s574 msMay 16Oct 31719 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Oct 24, 2026889 ms
Oct 31, 2026719 ms
Real-visitor tap response (INP)75th percentile, phones
125 ms90 msMay 16Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202695 ms
May 23, 202696 ms
May 30, 202697 ms
Jun 6, 2026103 ms
Jun 13, 2026103 ms
Jun 20, 2026103 ms
Jun 27, 2026107 ms
Jul 4, 2026107 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026114 ms
Aug 1, 2026121 ms
Aug 8, 2026120 ms
Aug 15, 2026121 ms
Aug 22, 2026119 ms
Aug 29, 2026112 ms
Sep 5, 2026111 ms
Sep 12, 2026108 ms
Sep 19, 2026103 ms
Sep 26, 2026104 ms
Oct 3, 2026106 ms
Oct 10, 2026107 ms
Oct 17, 2026104 ms
Oct 24, 202698 ms
Oct 31, 202694 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 raghouse.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. raghouse.com at 0.4 s0.4 s
  2. raghouse.com at 0.8 s0.8 s
  3. raghouse.com at 1.1 s1.1 s
  4. raghouse.com at 1.5 s1.5 s
  5. raghouse.com at 1.9 s1.9 s
  6. raghouse.com at 2.3 s2.3 s
  7. raghouse.com at 2.6 s2.6 s
  8. raghouse.com at 3.0 s3.0 s

Speed

2 to fix
  • Google Tag Manager adds 229 ms

    229 ms

    Google Tag Manager costs a phone 229 ms of main-thread work and 410 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.

  • 2,580 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 500 KiB and 253 ms of main-thread time.

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

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

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

1 to fix100
  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

9 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: 0.8 s

    0.8 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 443 ms

    443 ms

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

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

    -41%

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

  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.4 MB in 163 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 163 requests on a phone: images 2.5 MB (38), scripts 980 KiB (38) and other files 714 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 148.0 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 9696
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

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

  • Alternative text of images should not be repeated as text (29 elements)

    Alternative text of images should not be repeated as text: 29 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 58 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

    No XML sitemap at https://raghouse.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 135 internal links, 8 external

    The homepage links to 135 pages on raghouse.com and 8 external pages.

7 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Shop vintage and modern used clothing from Raghouse, trusted by store owners and online resellers for 30+ years. New in…”.

  • One H1 headline

    Your main headline reads: “Raghouse”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Vintage & Used Clothing Shop Online | Raghouse”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://raghouse.com/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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,335 words), so crawlers that don't run JavaScript still read it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    61 of 67 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • 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 1,018 words of copy

    The homepage carries about 1,018 words of visible text.

4 checks passed
  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop icon-chevron Expand submenu”, “icon-chevron Shop” and “Quick shop”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 11 other companies contacted

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

Apps your storefront loads

Rh Storefront · Raghouse Ai Search

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

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 12 issues on raghouse.com, including 3 speed issues, 2 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