Website review, no card needed
ballparkpal.com website review
Visit site (opens in a new tab)Reviewed 11 October 202626 issues · 76 checks
This review found 26 issues worth fixing on ballparkpal.com, 10 of them high impact, across 76 checks. The most urgent: 121 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.3 s |
| Apr 25, 2026 | 1.2 s |
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 981 ms |
| Aug 8, 2026 | 974 ms |
| Aug 15, 2026 | 988 ms |
| Aug 22, 2026 | 999 ms |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 86 ms |
| Apr 25, 2026 | 85 ms |
| May 2, 2026 | 83 ms |
| May 9, 2026 | 83 ms |
| May 16, 2026 | 83 ms |
| May 23, 2026 | 83 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 84 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 79 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
Use efficient cache lifetimes
10 KiB3 files are served with short cache lifetimes, so returning visitors download them again (10 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.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99 (desktop: 100). That is in Google's “good” band (90 and up).
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 7 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 86 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 53 ms
53 msReal visitors wait 53 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 742 ms
742 msReal visitors wait 742 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website is using a security service to protect itself …”.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 0.8 s
0.8 sThe page is fully interactive after 0.8 s.
Images and page weight
1 image far larger than shown
105 KiB1 image is downloaded at several times the size a phone draws it, for example MainLogo.png at 1,000 px wide, shown at 160 px. Resized copies would save about 105 KiB.
3 images in older formats
3 images (291 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images below the first screen load straight away
2 images further down the page (111 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.00 g of CO₂ per visit
0.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.00 g of CO₂e: 0.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 12 KiB in 4 requests
12 KiBYour homepage downloads 12 KiB in 4 requests on a phone: stylesheets 5 KiB (1), images 5 KiB (2) and HTML 2 KiB (1). That is a lean page.
Accessibility
121 text elements with low contrast
121 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (64 elements)
All page content should be contained by landmarks: 64 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Blocked from indexing
Google's crawler is blocked from indexing this page.
Error status code
The page answers with an error status, so search engines may drop it.
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “Ballpark Pal | Daily MLB Park Factors, Game Simulations, and Player Projections”.
2 H1 headlines
There are 2 <h1> headlines (“Ballpark Pal Log InSubscribe” and “Today's Outlook”). One clear main headline is easier for people and search engines.
64 internal links, 0 external
The homepage links to 64 pages on ballparkpal.com and 0 external pages.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Ballpark Pal is an MLB research platform based on game simulations. Dive into today's slate with insights across every …”.
Canonical URL set
The canonical URL is https://www.ballparkpal.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.ballparkpal.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
35%The HTML your server sends has 199 of the 563 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.ballparkpal.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Other pages
10 linked pages are broken
Your homepage links to https://www.ballparkpal.com/Batter-Projections.php, https://www.ballparkpal.com/Batter-Odds.php, https://www.ballparkpal.com/Batter-Summary.php, https://www.ballparkpal.com/Batter-Over-Under.php, https://www.ballparkpal.com/Batter-Play-Log.php and https://www.ballparkpal.com/Batter-Game-Log.php and 4 others, which answer with an error. Visitors hit a dead end and search engines drop them.
5 linked pages hidden from search
https://www.ballparkpal.com/Park-Factors.php, https://www.ballparkpal.com/Game-Simulations.php, https://www.ballparkpal.com/Starting-Pitchers.php, https://www.ballparkpal.com/Matchups.php and https://www.ballparkpal.com/Matchup-Machine.php are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
5 pages share a title
https://www.ballparkpal.com/Park-Factors.php, https://www.ballparkpal.com/Game-Simulations.php, https://www.ballparkpal.com/Starting-Pitchers.php, https://www.ballparkpal.com/Matchups.php and https://www.ballparkpal.com/Matchup-Machine.php all use the title “Secure Checkout | BallparkPal”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://www.ballparkpal.com/Park-Factors.php, https://www.ballparkpal.com/Game-Simulations.php, https://www.ballparkpal.com/Starting-Pitchers.php, https://www.ballparkpal.com/Matchups.php and https://www.ballparkpal.com/Matchup-Machine.php use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.ballparkpal.com/Park-Factors.php, https://www.ballparkpal.com/Game-Simulations.php, https://www.ballparkpal.com/Starting-Pitchers.php, https://www.ballparkpal.com/Matchups.php and https://www.ballparkpal.com/Matchup-Machine.php 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 55 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
142 of 162 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 563 words of copy
The homepage carries about 563 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe”.
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta 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.
6 cookies set on arrival
6Opening 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.
10 other companies contacted
Loading the homepage contacts 10 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 ballparkpal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
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 ballparkpal.com, including 1 speed issue, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.