Website review, no card needed

sparks-merch.com logo

sparks-merch.com website review

Visit site (opens in a new tab)Reviewed 10 November 202636 issues · 76 checks

This review found 36 issues worth fixing on sparks-merch.com, 12 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
6.7 s1.9 sMay 23Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.9 s
Aug 15, 20264.3 s
Aug 22, 20265.2 s
Aug 29, 20266.1 s
Sep 5, 20264.9 s
Sep 12, 20263.9 s
Sep 19, 20263.3 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.7 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
117 ms92 msMay 23Oct 3114 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026112 ms
May 30, 202695 ms
Aug 8, 2026112 ms
Aug 15, 2026114 ms
Aug 22, 2026113 ms
Aug 29, 2026114 ms
Sep 5, 2026104 ms
Sep 12, 2026112 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026114 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 sparks-merch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sparks-merch.com at 0.5 s0.5 s
  2. sparks-merch.com at 1.0 s1.0 s
  3. sparks-merch.com at 1.5 s1.5 s
  4. sparks-merch.com at 2.0 s2.0 s
  5. sparks-merch.com at 2.5 s2.5 s
  6. sparks-merch.com at 3.1 s3.1 s
  7. sparks-merch.com at 3.6 s3.6 s
  8. sparks-merch.com at 4.1 s4.1 s

Speed

12 to fix29
  • Reduce unused JavaScript

    2.0 s · 696 KiB

    About 696 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 4.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Hubspot and others), adding 1.7 MB and 1.2 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 250 KiB

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

  • Google Tag Manager adds 504 ms

    504 ms

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

  • Improve image delivery

    450 ms · 59 KiB

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

  • Render-blocking requests

    500 ms

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

  • hsappstatic.net adds 386 ms

    386 ms

    hsappstatic.net costs a phone 386 ms of main-thread work and 720 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.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 88 KiB

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

  • 1,636 HTML elements

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    24 KiB

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

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

    25 ms

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

Core Web Vitals

7 to fix33
  • Largest Contentful Paint: 15.2 s

    15.2 s

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

  • Time to Interactive: 21.5 s

    21.5 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Total Blocking Time: 980 ms

    980 ms

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

  • Cumulative Layout Shift: 0.169

    0.169

    The layout shifts by 0.169 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

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

1 checks passed
  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

Images and page weight

1 to fix67
  • Page weight: 3.6 MB in 232 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 232 requests on a phone: scripts 2.0 MB (66), other files 829 KiB (131) and HTML 475 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 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: 123.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 8987
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    5 dropdowns have no label.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 text elements with low contrast

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “SPARKS Merch- Company Merchandise, Swag, Event Gifts Singapore & APAC — Sparks Merch”.

  • Meta description is long (171 characters)

    Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 103 internal links, 10 external

    The homepage links to 103 pages on sparks-merch.com and 10 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.sparks-merch.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.sparks-merch.com/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.sparks-merch.com/pages/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.sparks-merch.com/pages/contact-us, https://www.sparks-merch.com/pages/contactus, https://www.sparks-merch.com/collections/cotton-t-shirts-promotional-products, https://www.sparks-merch.com/collections/caps-hats-corporate-merchandise, https://www.sparks-merch.com/collections/activewear-as-promotional-item-company-tshirt and https://www.sparks-merch.com/collections/headgear and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 7389
  • 1 third-party cookie

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Only about 10 words

    The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

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

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Book A Call” and “Sign up”.

  • 12 short forms

    12 short forms (7 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 73 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 sparks-merch.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Mp Size Chart · Sa Request A Quote · Powerful Form Builder · avada.io · mailmunch.co

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on sparks-merch.com, including 19 speed issues, 4 SEO issues and 3 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