Website review, no card needed

sugarstitch.com logo

sugarstitch.com website review

Visit site (opens in a new tab)Reviewed 13 November 202627 issues · 76 checks

This review found 27 issues worth fixing on sugarstitch.com, 6 of them high impact, across 76 checks. The most urgent: improve image delivery. 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 sugarstitch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sugarstitch.com at 0.6 s0.6 s
  2. sugarstitch.com at 1.2 s1.2 s
  3. sugarstitch.com at 1.8 s1.8 s
  4. sugarstitch.com at 2.4 s2.4 s
  5. sugarstitch.com at 3.0 s3.0 s
  6. sugarstitch.com at 3.6 s3.6 s
  7. sugarstitch.com at 4.2 s4.2 s
  8. sugarstitch.com at 4.8 s4.8 s

Speed

8 to fix72
  • Improve image delivery

    1.1 s · 746 KiB

    25 images could be 746 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 72

    72/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (faire.com, Shopify and FontAwesome CDN and others), adding 989 KiB and 623 ms of main-thread time.

  • Render-blocking requests

    600 ms

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

  • faire.com adds 420 ms

    420 ms

    faire.com costs a phone 420 ms of main-thread work and 723 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 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • 1,587 HTML elements

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

  • Reduce unused JavaScript

    147 KiB

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

  • Font display

    100 ms

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

  • Reduce unused CSS

    96 KiB

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

  • Use efficient cache lifetimes

    57 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (57 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix71
  • Time to Interactive: 10.1 s

    10.1 s

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

  • Largest Contentful Paint: 4.6 s

    4.6 s

    Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 5.7 s

    5.7 s

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

  • Total Blocking Time: 295 ms

    295 ms

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

  • 1 image without width and height

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

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

2 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 279 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 279 requests on a phone: images 1.5 MB (34), other files 965 KiB (149) and scripts 641 KiB (48). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    79 KiB

    1 image is downloaded at several times the size a phone draws it, for example The_Trends_You_ve_Been_Looking_For_8cff4faf-1454-4cc0-afb7-8 at 1,600 px wide, shown at 360 px. Resized copies would save about 79 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (222 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    1.03 g

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

4 to fixGoogle 8995
  • 27 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (3 elements).

2 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 10091
  • 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.

  • One H1 headline

    Your <h1> is empty.

  • 170 internal links, 1 external

    The homepage links to 170 pages on sugarstitch.com and 1 external page.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Look no further than Sugar Stitch for a trendy graphic tee shop. We deliver affordable, custom-designed T-shirts, hoodi…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Wholesale Graphic Tees | Sugar Stitch – Sugar Stitch Wholesale”.

  • Canonical URL set

    The canonical URL is https://sugarstitch.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://sugarstitch.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 (1,195 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without a meta description

    https://sugarstitch.com/collections/all, https://sugarstitch.com/collections/new-arrivals, https://sugarstitch.com/collections/bows-collection, https://sugarstitch.com/collections/brunch-collection, https://sugarstitch.com/collections/cowboy and https://sugarstitch.com/collections/flock and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 7391
  • 2 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Identifier 'tbCustomerNameCheck' has already been declared”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    21 of 23 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 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 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 712 words of copy

    The homepage carries about 712 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Register”, “Shop All” and “Shop today”.

  • 5 short forms

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

  • Direct contact links

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

Privacy and tracking

  • 18 cookies set on arrival

    18

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

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

targetbay.com · bayengage.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 27 issues on sugarstitch.com, including 13 speed issues, 3 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
sugarstitch.com website review: scores and fixes