Website review, no card needed

rascalclothing.com logo

rascalclothing.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 62 checks

This review found 26 issues worth fixing on rascalclothing.com, 8 of them high impact, across 62 checks. The most urgent: main-thread work: 4.0 s. 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
2.0 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
146 ms117 msMay 23Nov 7120 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026138 ms
May 30, 2026139 ms
Jun 6, 2026135 ms
Jun 13, 2026135 ms
Jun 20, 2026135 ms
Jun 27, 2026135 ms
Jul 4, 2026143 ms
Jul 11, 2026141 ms
Jul 18, 2026139 ms
Jul 25, 2026135 ms
Aug 1, 2026129 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Aug 22, 2026134 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026138 ms
Sep 19, 2026135 ms
Sep 26, 2026126 ms
Oct 3, 2026121 ms
Oct 10, 2026122 ms
Oct 17, 2026121 ms
Oct 24, 2026122 ms
Oct 31, 2026121 ms
Nov 7, 2026120 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 rascalclothing.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix86
  • Main-thread work: 4.0 s

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

  • Mobile performance score: 86

    86/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, kiwisizing.com and Klaviyo and others), adding 580 KiB and 716 ms of main-thread time.

  • Improve image delivery

    537 KiB

    1 image could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    450 ms

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

  • Use efficient cache lifetimes

    301 KiB

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

  • 10 long tasks on the main thread

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

  • Reduce unused JavaScript

    189 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    28 KiB

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

  • Reduce unused CSS

    22 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

    4 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 9.7 s

    9.7 s

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

  • Total Blocking Time: 519 ms

    519 ms

    Scripts block taps and scrolling for 519 ms in total while the page loads. Good is under 200 ms.

10 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: 1.4 s

    1.4 s

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 704 ms

    704 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

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

    -11%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 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).

  • First Contentful Paint: 1.0 s

    1.0 s

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

  • Largest Contentful Paint: 1.0 s

    1.0 s

    Your largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “WE'RE TAKING A BREAK: STAY UPDATED WITH THE WINGROVE'S NEXT…”.

Images and page weight

3 to fix60
  • 1 image over 500 KB

    ezgif-optimized_3.gif weighs 547 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.1 MB in 166 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 166 requests on a phone: scripts 742 KiB (72), other files 706 KiB (82) and images 562 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (547 KiB) is 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 0.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • 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

1 to fixGoogle 9397
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

4 to fixGoogle 9277
  • No meta description

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

  • Title is short (15 characters)

    Your title is only 15 characters: “Rascal Clothing”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

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

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

4 checks passed
  • One H1 headline

    Your main headline reads: “Rascal Clothing”.

  • Canonical URL set

    The canonical URL is https://rascalclothing.com/password.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • robots.txt in place

    robots.txt is in place.

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.

  • No llms.txt

    There is no https://rascalclothing.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.

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

Best practices

1 to fixGoogle 9692
  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 33 words

    The homepage has only about 33 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.

1 checks passed
  • 2 short forms

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

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 Meta Pixel 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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 1 of them by other companies (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.

  • 38 other companies contacted

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

Apps your storefront loads

Triplewhale · Minmaxify Order Limits · Instafeed · Klaviyo Email Marketing Sms · Omnisend · Postco 360 Staging · trustpilot.com · afterpay.com · nice-team.net · thegoodapi.com · webgains.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
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Heywood

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on rascalclothing.com, including 9 speed issues, 4 SEO issues and 6 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