Website review, no card needed

swingjuice.com logo

swingjuice.com website review

Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 76 checks

This review found 32 issues worth fixing on swingjuice.com, 11 of them high impact, across 76 checks. The most urgent: render-blocking 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
1.4 s742 msMay 16Oct 31833 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 2026998 ms
Aug 1, 2026971 ms
Aug 8, 2026939 ms
Aug 15, 2026905 ms
Aug 22, 2026909 ms
Aug 29, 2026967 ms
Sep 5, 2026999 ms
Sep 12, 2026975 ms
Sep 19, 20261.0 s
Sep 26, 2026944 ms
Oct 3, 2026882 ms
Oct 10, 2026886 ms
Oct 24, 2026818 ms
Oct 31, 2026833 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms80 msMay 16Oct 1087 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202696 ms
May 30, 2026104 ms
Jun 6, 2026105 ms
Jun 13, 2026105 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026104 ms
Jul 11, 202695 ms
Jul 18, 202687 ms
Jul 25, 202684 ms
Aug 1, 202687 ms
Aug 8, 202693 ms
Aug 15, 202691 ms
Aug 29, 202693 ms
Sep 5, 202694 ms
Sep 12, 202697 ms
Oct 10, 202687 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 swingjuice.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swingjuice.com at 0.4 s0.4 s
  2. swingjuice.com at 0.8 s0.8 s
  3. swingjuice.com at 1.2 s1.2 s
  4. swingjuice.com at 1.6 s1.6 s
  5. swingjuice.com at 2.0 s2.0 s
  6. swingjuice.com at 2.4 s2.4 s
  7. swingjuice.com at 2.8 s2.8 s
  8. swingjuice.com at 3.2 s3.2 s

Speed

8 to fix61
  • Render-blocking requests

    1.1 s

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

  • 3,963 HTML elements

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

  • Improve image delivery

    650 ms · 529 KiB

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

  • Mobile performance score: 61

    61/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and cloudfront.net and others), adding 1.2 MB and 720 ms of main-thread time.

  • Reduce unused JavaScript

    529 KiB

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

  • Google Tag Manager adds 453 ms

    453 ms

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

  • Main-thread work: 2.7 s

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    39 KiB

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

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 22.5 s

    22.5 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Total Blocking Time: 305 ms

    305 ms

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

  • 8 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 87 ms 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: 1.0 s

    1.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 35% faster for real visitors

    -35%

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

  • Cumulative Layout Shift: 0.095

    0.095

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

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

Images and page weight

2 to fix63
  • Page weight: 5.4 MB in 344 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 344 requests on a phone: images 2.8 MB (92), scripts 1.3 MB (76) and other files 1.0 MB (135). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • About 1.5 g of CO₂ per visit

    1.53 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.6 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 are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9092
  • Hidden but focusable

    25 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 3 text elements with low contrast

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

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

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

  • ARIA role should be appropriate for the element (10 elements)

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

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

2 checks passed
  • Every image has alt text

    All 81 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “SwingJuice | A Fun Lifestyle Fashion Brand For Golf & More – SwingJuice LLC”.

  • Meta description is long (244 characters)

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or ']' after array element in JSON at position )”.

  • One H1 headline

    Your <h1> is empty.

  • 171 internal links, 14 external

    The homepage links to 171 pages on swingjuice.com and 14 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://swingjuice.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.

  • No llms.txt

    There is no https://swingjuice.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

1 to fix95
  • 5 pages without a meta description

    https://swingjuice.com/collections/all, https://swingjuice.com/policies/shipping-policy, https://swingjuice.com/collections/best-sellers, https://swingjuice.com/collections/made-for-legends and https://swingjuice.com/collections/golf-travel have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://swingjuice.com/collections/all, https://swingjuice.com/policies/shipping-policy, https://swingjuice.com/collections/best-sellers and https://swingjuice.com/collections/made-for-legends took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    5 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 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

2 checks passed
  • Tap targets are thumb-sized

    59 of 64 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 396 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All” and “Contact Us”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 TikTok Pixel (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.

  • 15 cookies set on arrival

    15

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

  • 23 other companies contacted

    Loading the homepage contacts 23 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 swingjuice.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

Loyalty Rewards And Referrals · perfectapps.io · cloudfront.net · googleapis.com · automizely.com · shipinsure.io

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

Company

Headquarters
Pawtucket

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on swingjuice.com, including 13 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