Website review, no card needed
thepicklr.com website review
Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 90 checks
This review found 42 issues worth fixing on thepicklr.com, 16 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 117 ms |
| May 9, 2026 | 117 ms |
| May 16, 2026 | 119 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 141 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 140 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 146 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
Speed
Render-blocking requests
3.2 s55 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 68). 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.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
300 ms · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 3.4 MB and 1.8 s of main-thread time.
Use efficient cache lifetimes
861 KiB29 files are served with short cache lifetimes, so returning visitors download them again (861 KiB).
Google Tag Manager adds 681 ms
681 msGoogle Tag Manager costs a phone 681 ms of main-thread work and 1.2 MB 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.
YouTube adds 439 ms
439 msYouTube costs a phone 439 ms of main-thread work and 974 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.
Facebook adds 199 ms
199 msFacebook costs a phone 199 ms of main-thread work and 368 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.
Hubspot adds 166 ms
166 msHubspot costs a phone 166 ms of main-thread work and 364 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.
Reduce unused CSS
150 ms · 122 KiBAbout 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.
Legacy JavaScript
99 KiBPolyfills for old browsers add 99 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 35.1 s
35.1 sThe page becomes fully interactive after 35.1 s. Good is under 3.8 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 117 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 575 ms
575 msScripts block taps and scrolling for 575 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.137
0.137The layout shifts by 0.137 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.0 MB in 212 requests
5.0 MBYour homepage downloads 5.0 MB in 212 requests on a phone: scripts 3.9 MB (80), images 435 KiB (22) and fonts 273 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.43 g of CO₂e: 171.7 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
Unlabelled dropdowns
2 dropdowns have no label.
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 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 (6 elements)
All page content should be contained by landmarks: 6 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.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 13 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 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
55 internal links, 11 external
The homepage links to 55 pages on thepicklr.com and 11 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Join The Picklr community today and enjoy unlimited pickleball at nationwide indoor clubs, catered to help all age grou…”.
Title: 56 characters
Your title is a healthy 56 characters: “Indoor Pickleball Court: Elevate Your Game at The Picklr”.
Canonical URL set
The canonical URL is https://thepicklr.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://thepicklr.com/sitemap_index.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (620 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://thepicklr.com/llms.txt (3 KiB, 20 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://thepicklr.com/30-for-15-locations and https://thepicklr.com/30-for-10 all use the title “Enjoy Indoor Pickleball with The Picklr's 30 for 15 Offer”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://thepicklr.com/academy/junior-academy, https://thepicklr.com/leagues-and-socials and https://thepicklr.com/press have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://thepicklr.com/30-for-15-locations and https://thepicklr.com/30-for-10 use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://thepicklr.com/adult, whose canonical is https://thepicklr.com/academy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 660 words of copy
The homepage carries about 660 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: “START A TRIAL” and “Membership and Pricing”.
13 calls to action
The homepage has 13 calls to action, for example “START A TRIAL”, “Membership and Pricing” and “Shop”.
Social proof on the page
Social proof on the homepage: 34 testimonial or review blocks and 9 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, HubSpot and LinkedIn Insight.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).
62 other companies contacted
Loading the homepage contacts 62 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 thepicklr.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on thepicklr.com, including 22 speed issues, 2 SEO issues and 1 conversion gap. 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.