Website review, no card needed

lacrosseplayground.com logo

lacrosseplayground.com website review

Visit site (opens in a new tab)Reviewed 13 November 202626 issues · 65 checks

This review found 26 issues worth fixing on lacrosseplayground.com, 6 of them high impact, across 65 checks. The most urgent: 4 text elements with low contrast. 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 lacrosseplayground.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix74
  • Mobile performance score: 74

    74/100

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

  • Improve image delivery

    350 ms · 67 KiB

    1 image could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Render-blocking requests

    400 ms

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

  • Reduce unused JavaScript

    300 ms · 57 KiB

    About 57 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Legacy JavaScript

    50 ms · 19 KiB

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

  • Use efficient cache lifetimes

    50 ms · 9 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, Cloudflare and Cloudflare CDN and others), adding 115 KiB and 41 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 211 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix70
  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 2 images without width and height

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

3 checks passed
  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    lpg-home-banner.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.3 g of CO₂ per visit

    0.33 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 40.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Page weight: 1.2 MB in 142 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 142 requests on a phone: other files 735 KiB (83), scripts 257 KiB (36) and images 116 KiB (6). That is a lean page.

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 9276
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 18 internal links, 0 external

    The homepage links to 18 pages on lacrosseplayground.com and 0 external pages.

5 checks passed
  • Title: 34 characters

    Your title is a healthy 34 characters: “Lacrosse Playground – Epoch Sports”.

  • Canonical URL set

    The canonical URL is https://epochsports.com/pages/lacrosse-playground.

  • 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://epochsports.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 7 pages without a meta description

    https://epochsports.com/pages/wolf-athletics, https://epochsports.com/customer_authentication/redirect, https://epochsports.com/pages/lacrosse-playground-blog, https://epochsports.com/pages/about-lacrosse-playground, https://epochsports.com/policies/privacy-policy and https://epochsports.com/policies/refund-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://epochsports.com/customer_authentication/redirect, https://epochsports.com/pages/lacrosse-playground-blog, / and https://epochsports.com/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://epochsports.com/pages/wolf-athletics, https://epochsports.com/pages/lacrosse-playground-blog, https://epochsports.com/pages/about-lacrosse-playground, / and https://epochsports.com/pages/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 10 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cloudflareinsights.com/cdn-cgi/rum' from origin 'https://epochsports.com' has been…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 57 words

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

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

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Information”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

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
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on lacrosseplayground.com, including 8 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