Website review, no card needed

sbrslapbumproll.com logo

sbrslapbumproll.com website review

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

This review found 29 issues worth fixing on sbrslapbumproll.com, 6 of them high impact, across 73 checks. The most urgent: 1 text element with low contrast. 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 sbrslapbumproll.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix74
  • Reduce unused JavaScript

    900 ms · 179 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    950 ms

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

  • Use efficient cache lifetimes

    600 ms · 113 KiB

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

  • Main-thread work: 2.2 s

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

  • Shopify adds 143 ms

    143 ms

    Shopify costs a phone 143 ms of main-thread work and 624 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.

  • 1,509 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, pop-convert.com and shop.app and others), adding 803 KiB and 222 ms of main-thread time.

  • Improve image delivery

    150 ms · 54 KiB

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

  • Reduce unused CSS

    160 ms · 23 KiB

    About 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 2 long tasks on the main thread

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

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

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

    13 ms

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

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 11.4 s

    11.4 s

    Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SBR Black Butter Hoodie in black with cursive Slap Bump Rol…”.

  • Time to Interactive: 11.5 s

    11.5 s

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

  • Speed Index: 3.5 s

    3.5 s

    Visually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 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.

3 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 21 ms

    21 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 255 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 255 requests on a phone: other files 1.0 MB (118), scripts 714 KiB (81) and images 562 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.5 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

5 to fixGoogle 9693
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 4 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

4 to fixGoogle 10083
  • Title is short (8 characters)

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

  • Meta description is long (172 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 94 internal links, 4 external

    The homepage links to 94 pages on sbrslapbumproll.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “:root { --header-logo-width: 135px; }”.

  • Canonical URL set

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

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

AI search readiness

100
4 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 (934 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://sbrslapbumproll.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://sbrslapbumproll.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://sbrslapbumproll.com/collections/all, https://sbrslapbumproll.com/collections/gi, https://sbrslapbumproll.com/pages/contact, https://sbrslapbumproll.com/pages/collab and https://sbrslapbumproll.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://sbrslapbumproll.com/collections/all, https://sbrslapbumproll.com/collections/tees, https://sbrslapbumproll.com/collections/hoodies-outerwear, https://sbrslapbumproll.com/collections/youth, https://sbrslapbumproll.com/collections/gi and https://sbrslapbumproll.com/collections/no-gi-jiu-jitsu and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://sbrslapbumproll.com/collections/youth took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were 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

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

  • About 359 words of copy

    The homepage carries about 359 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop All”, “Contact” and “SHOP SBR”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

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

  • 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 Google Tag Manager (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.

  • 16 other companies contacted

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

Apps your storefront loads

Sami B2b Lock · Judge Me Reviews · Sami Wholesale · Wholesale Lock Hide Price · Pop Convert · Restockrocket

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
jQuery
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 sbrslapbumproll.com, including 10 speed issues, 4 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