Website review, no card needed

slimjimsthings.com logo

slimjimsthings.com website review

Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 77 checks

This review found 30 issues worth fixing on slimjimsthings.com, 7 of them high impact, across 77 checks. The most urgent: orphan list items. 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 slimjimsthings.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix91
  • Reduce unused JavaScript

    524 KiB

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

  • Render-blocking requests

    500 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (YouTube, Shopify and Other Google APIs/SDKs and others), adding 1.1 MB and 382 ms of main-thread time.

  • YouTube adds 344 ms

    344 ms

    YouTube costs a phone 344 ms of main-thread work and 992 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

    124 KiB

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

  • Improve image delivery

    115 KiB

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

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 82 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).

  • Use efficient cache lifetimes

    13 KiB

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

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

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.8 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

3 to fix94
  • Time to Interactive: 13.9 s

    13.9 s

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

  • Speed Index: 5.6 s

    5.6 s

    Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A COLLECTION OF SLIM JIM'S JIMS PUT ONTO SLIM JIM'S THINGS”.

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

3 checks passed
  • Cumulative Layout Shift: 0.004

    0.004

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.6 MB in 152 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 152 requests on a phone: scripts 1.1 MB (39), other files 736 KiB (90) and images 383 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    20 KiB

    1 image is downloaded at several times the size a phone draws it, for example ramon-vloon-FGFwWTpVzBg-unsplash_1_1296x.jpg at 1,264 px wide, shown at 390 px. Resized copies would save about 20 KiB.

  • About 0.7 g of CO₂ per visit

    0.73 g

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

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

Accessibility

6 to fixGoogle 8891
  • Orphan list items

    Some list items are not inside a list.

  • 2 text elements with low contrast

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

  • 2 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271
  • No meta description

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

  • Title is short (10 characters)

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

  • 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 (“SLIM JIM'S JIMS ON THINGS” and “GIBBONFLIX COMING SOON ALSO”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 60 internal links, 6 external

    The homepage links to 60 pages on slimjimsthings.com and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • 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://slimjimsthings.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://slimjimsthings.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://slimjimsthings.com/collections/clothing, https://slimjimsthings.com/collections/accessories, https://slimjimsthings.com/collections, https://slimjimsthings.com/collections/jog-collection, https://slimjimsthings.com/collections/blake-pog-collection and https://slimjimsthings.com/collections/big-bk-collection and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://slimjimsthings.com/collections has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://slimjimsthings.com/collections, https://slimjimsthings.com/collections/blake-pog-collection, https://slimjimsthings.com/collections/big-bk-collection and https://slimjimsthings.com/pages/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 7397
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    15 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No social proof

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

  • 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 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 329 words of copy

    The homepage carries about 329 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Subscribe”.

  • 2 short forms

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

ecommergency.com · printful.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

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 30 issues on slimjimsthings.com, including 7 speed issues, 5 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

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