Website review, no card needed

ninjapatches.com logo

ninjapatches.com website review

Visit site (opens in a new tab)Reviewed 8 November 202645 issues · 100 checks

This review found 45 issues worth fixing on ninjapatches.com, 16 of them high impact, across 100 checks. The most urgent: page weight: 19.5 MB in 395 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s2.0 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
231 ms135 msMay 16Oct 31220 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026146 ms
May 23, 2026147 ms
May 30, 2026148 ms
Jun 6, 2026154 ms
Jun 13, 2026156 ms
Jun 20, 2026156 ms
Jun 27, 2026156 ms
Jul 4, 2026154 ms
Jul 11, 2026155 ms
Jul 18, 2026156 ms
Jul 25, 2026157 ms
Aug 1, 2026158 ms
Aug 8, 2026154 ms
Aug 15, 2026155 ms
Aug 22, 2026155 ms
Aug 29, 2026162 ms
Sep 5, 2026170 ms
Sep 12, 2026179 ms
Sep 19, 2026187 ms
Sep 26, 2026187 ms
Oct 3, 2026191 ms
Oct 10, 2026195 ms
Oct 17, 2026203 ms
Oct 24, 2026212 ms
Oct 31, 2026220 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 ninjapatches.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ninjapatches.com at 0.7 s0.7 s
  2. ninjapatches.com at 1.4 s1.4 s
  3. ninjapatches.com at 2.2 s2.2 s
  4. ninjapatches.com at 2.9 s2.9 s
  5. ninjapatches.com at 3.6 s3.6 s
  6. ninjapatches.com at 4.3 s4.3 s
  7. ninjapatches.com at 5.0 s5.0 s
  8. ninjapatches.com at 5.7 s5.7 s

Speed

13 to fix36
  • Render-blocking requests

    1.8 s

    19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Main-thread work: 10.9 s

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

  • Mobile performance score: 36

    36/100

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

  • 4,008 HTML elements

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

  • Improve image delivery

    500 ms · 2.9 MB

    31 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Use efficient cache lifetimes

    750 ms · 2.1 MB

    23 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, printflyone.com and Wistia and others), adding 2.6 MB and 2.1 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Google Tag Manager adds 567 ms

    567 ms

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

  • printflyone.com adds 389 ms

    389 ms

    printflyone.com costs a phone 389 ms of main-thread work and 782 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.

  • 20 long tasks on the main thread

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

  • Wistia adds 285 ms

    285 ms

    Wistia costs a phone 285 ms of main-thread work and 248 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.

  • rebuyengine.com adds 181 ms

    181 ms

    rebuyengine.com costs a phone 181 ms of main-thread work and 370 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.

  • Legacy JavaScript

    150 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    92 KiB

    About 92 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 11.8 s

    11.8 s

    Your largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Premium Custom Patches with Low 10-Piece Minimums”.

  • Time to Interactive: 34.0 s

    34.0 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Tap response (INP) got 47% slower for real visitors

    +47%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 11 images without width and height

    11 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    +4%

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

7 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: 2.2 s

    2.2 s

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

  • Real-user INP: 180 ms

    180 ms

    Real visitors wait 180 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

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

    447 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix50
  • Page weight: 19.5 MB in 395 requests

    19.5 MB

    Your homepage downloads 19.5 MB in 395 requests on a phone: media 10.8 MB (2), images 4.0 MB (54) and scripts 3.2 MB (160). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    1.2 MB

    7 images are downloaded at several times the size a phone draws them, for example original.png at 808 px wide, shown at 160 px. Resized copies would save about 1.2 MB.

  • 1 image below the first screen load straight away

    1 image further down the page (139 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 5.5 g of CO₂ per visit

    5.53 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 7687
  • 12 buttons without a name

    12 buttons have no accessible name, so screen readers announce just “button”.

  • 54 text elements with low contrast

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

  • 24 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 21 images without alt text

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

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

    All page content should be contained by landmarks: 99 elements on the page fail 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.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

  • Headings skip levels

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

1 checks passed
  • 46 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: 46 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7788
  • 2 H1 headlines

    There are 2 <h1> headlines (“Premium Custom Patches with Low 10-Piece Minimums” and “We clean up after ourselves.”). 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.

  • 3 links with vague text

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

  • 1 link crawlers can't follow

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

  • 312 internal links, 21 external

    The homepage links to 312 pages on ninjapatches.com and 21 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “We're the ultimate choice for custom patches! Choose from embroidered, sublimated, and more. 5-day production & free sh…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Custom Patches Perfect for Hats & Apparel, Shipped Fast!”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://ninjapatches.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages share a title

    https://ninjapatches.com/products/pvc-rubber-patches and https://ninjapatches.com/products/glow-in-the-dark-pvc-rubber-patches all use the title “PVC Rubber Patches | Design Custom PVC Patches Online”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://ninjapatches.com/products/pvc-rubber-patches and https://ninjapatches.com/products/glow-in-the-dark-pvc-rubber-patches use the same meta description. A description written for each page earns more clicks.

  • 2 pages slow to respond

    https://ninjapatches.com/products/silicone-patches and https://ninjapatches.com/collections/ninja-flex-patches took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://ninjapatches.com/.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    80 of 85 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,976 words of copy

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

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Shop Patches”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “Order DTF By Size →”, “Shop Ninja Transfers →” and “Get Started →”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 232 testimonial or review blocks, 25 customer or partner logos and “Trusted by 30,000+ businesses”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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

    5

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

  • 23 cookies set on arrival

    23

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

  • 48 other companies contacted

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

Apps your storefront loads

Logrocket · Pandectes Gdpr · Yotpo Product Reviews · Bevy Share Cart Social Link · Mntn · Triplewhale · Gdpr Cookie Consent · Planet · Quantity Break Limit Purchase · rebuyengine.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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on ninjapatches.com, including 20 speed issues, 4 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