Website review, no card needed

merchantofpickleball.com logo

merchantofpickleball.com website review

Visit site (opens in a new tab)Reviewed 13 November 202637 issues · 79 checks

This review found 37 issues worth fixing on merchantofpickleball.com, 7 of them high impact, across 79 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

Full-page screenshot of merchantofpickleball.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix64
  • Reduce unused JavaScript

    1.2 s · 249 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 64

    64/100

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

  • Improve image delivery

    650 ms · 137 KiB

    9 images could be 137 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.

  • Reduce unused CSS

    560 ms · 122 KiB

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

  • Use efficient cache lifetimes

    300 ms · 122 KiB

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

  • Main-thread work: 2.2 s

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

  • 2,020 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Key CDN and b-cdn.net and others), adding 494 KiB and 416 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    110 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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: 4 ms

    4 ms

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

Core Web Vitals

6 to fix61
  • Largest Contentful Paint: 10.9 s

    10.9 s

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

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • Total Blocking Time: 274 ms

    274 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.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.

  • 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
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 204 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 204 requests on a phone: other files 761 KiB (90), scripts 642 KiB (67) and fonts 515 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.65 g

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

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 5 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 22 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 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 10088
  • 2 H1 headlines

    There are 2 <h1> headlines (“Latest Arrivals” and “Featured Product”). One clear main headline is easier for people and search engines.

  • Structured data has 3 problems

    Structured data found (Organization, WebPage and WebSite) but with 3 problems, for example “Organization: logo is not an absolute URL ("//www.merchantofpickleball.com/cdn/shop/files/2023_sbra…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 277 internal links, 2 external

    The homepage links to 277 pages on merchantofpickleball.com and 2 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Retail & online store specializing in Pickleball gear from leading brands. Competitive pricing. Expert knowledge. Free …”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Merchant of Pickleball - Canada's Pickleball Store”.

  • Canonical URL set

    The canonical URL is https://www.merchantofpickleball.com/.

  • 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.merchantofpickleball.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, description and contact details; sameAs (social profiles) would complete it.

  • llms.txt published

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

Other pages

5 to fix67
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 1 page without a meta description

    https://www.merchantofpickleball.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages share a meta description

    https://www.merchantofpickleball.com/collections/pickleball-paddles, https://www.merchantofpickleball.com/collections/pickleball-paddles/head, https://www.merchantofpickleball.com/collections/pickleball-paddles/joola, https://www.merchantofpickleball.com/collections/pickleball-paddles/selkirk and https://www.merchantofpickleball.com/collections/pickleball-paddles/wilson use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.merchantofpickleball.com/customer_authentication/redirect has 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 198 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 9291
  • 26 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix78
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 142 words

    The homepage has only about 142 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.

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Sale” and “Shop Pickleball Balls”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop all Paddles”, “Shop Sale” and “Shop Pickleball Balls”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 3 email links.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics 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.

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

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

Apps your storefront loads

Persistent Cart · Cart Persistify · Iwish · chimpstatic.com · stamped.io · b-cdn.net · kxcdn.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on merchantofpickleball.com, including 14 speed issues, 3 SEO issues and 4 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