Website review, no card needed

11six24.com logo

11six24.com website review

Visit site (opens in a new tab)Reviewed 27 October 202630 issues · 81 checks

This review found 30 issues worth fixing on 11six24.com, 12 of them high impact, across 81 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
1.8 s1.5 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
135 ms109 msMay 9Oct 24132 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026114 ms
May 30, 2026120 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026126 ms
Jun 27, 2026129 ms
Jul 4, 2026129 ms
Jul 11, 2026130 ms
Jul 18, 2026129 ms
Jul 25, 2026129 ms
Aug 1, 2026128 ms
Aug 8, 2026124 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026120 ms
Sep 5, 2026121 ms
Sep 12, 2026123 ms
Sep 19, 2026128 ms
Sep 26, 2026129 ms
Oct 3, 2026130 ms
Oct 10, 2026132 ms
Oct 17, 2026132 ms
Oct 24, 2026132 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 11six24.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix45
  • Reduce unused JavaScript

    1.9 s · 517 KiB

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 4.5 s

    A phone's processor spends 4.5 s on main-thread work while loading, 2.1 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 (Shopify, Hubspot and postscript.io and others), adding 1.3 MB and 826 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 74 KiB

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

  • Render-blocking requests

    450 ms

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

  • Shopify adds 383 ms

    383 ms

    Shopify costs a phone 383 ms of main-thread work and 632 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.

  • 11 long tasks on the main thread

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

  • 2,136 HTML elements

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

  • Improve image delivery

    150 ms · 206 KiB

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

  • Use efficient cache lifetimes

    150 ms · 203 KiB

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

  • Legacy JavaScript

    200 ms · 33 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 80 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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

8 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 12.8 s

    12.8 s

    Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three Vapor pickleball paddles with black textured faces an…”.

  • Time to Interactive: 19.6 s

    19.6 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 548 ms

    548 ms

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

  • 15 images without width and height

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • 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 TTFB: 561 ms

    561 ms

    Real visitors wait 561 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

1 to fix85
  • Page weight: 3.4 MB in 245 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 245 requests on a phone: scripts 1.5 MB (108), other files 921 KiB (95) and images 539 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.96 g

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

4 to fixGoogle 8994
  • 28 text elements with low contrast

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

  • ARIA progressbar nodes must have an accessible name (2 elements)

    ARIA progressbar nodes must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 8 images without alt text

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

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

SEO

4 to fixGoogle 8582
  • Title is long (80 characters)

    Your title is 80 characters, so Google will cut it off around 60: “11SIX24 The Best Value in Pickleball | Carbon fiber paddles – 11SIX24 Pickleball”.

  • Meta description is long (168 characters)

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

  • No XML sitemap

    No XML sitemap at https://11six24.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

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

  • 73 internal links, 9 external

    The homepage links to 73 pages on 11six24.com and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “PRO-GRADE. NOT PRO-PRICED.”.

  • Canonical URL set

    The canonical URL is https://11six24.com/.

  • Structured data in place

    Structured data found: FAQPage and Organization.

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

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: 6 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,625 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    12 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 12 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://11six24.com' has been blocked …”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    18 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

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

  • 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 1,410 words of copy

    The homepage carries about 1,410 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: “SHOP PADDLES →” and “Contact Us”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP PADDLES →”, “SHOP POWER 2 →” and “SHOP POWER 1 →”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 158 testimonial or review blocks and a star rating.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 of them by other companies (measured from a US location before any click).

  • 46 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 11six24.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

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 30 issues on 11six24.com, including 17 speed issues, 4 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