Website review, no card needed
wishpond.com website review
Visit site (opens in a new tab)Reviewed 26 October 202635 issues · 80 checks
This review found 35 issues worth fixing on wishpond.com, 10 of them high impact, across 80 checks. The most urgent: mobile performance score: 37. 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
71CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.4 s |
| May 16, 2026 | 5.4 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 4.0 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 280 ms |
| May 16, 2026 | 281 ms |
| May 23, 2026 | 274 ms |
| May 30, 2026 | 297 ms |
| Jun 6, 2026 | 265 ms |
| Jun 13, 2026 | 262 ms |
| Jun 20, 2026 | 232 ms |
| Jun 27, 2026 | 225 ms |
| Jul 4, 2026 | 237 ms |
| Jul 11, 2026 | 237 ms |
| Jul 18, 2026 | 251 ms |
| Jul 25, 2026 | 273 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 206 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 192 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 215 ms |
| Oct 24, 2026 | 215 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
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
900 ms · 143 KiB35 files are served with short cache lifetimes, so returning visitors download them again (143 KiB).
Reduce unused JavaScript
760 ms · 167 KiBAbout 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and vector.co and others), adding 489 KiB and 513 ms of main-thread time.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 543 ms. During a long task the page ignores taps.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 935 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 331 ms
331 msGoogle Tag Manager costs a phone 331 ms of main-thread work and 324 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.
Improve image delivery
300 ms · 37 KiB2 images could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
2,955 HTML elements
The page has 2,955 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 161 KiBAbout 161 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.
Legacy JavaScript
150 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 178 ms
178 msYour server sent the HTML in 178 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.
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 14.8 s
14.8 sThe page becomes fully interactive after 14.8 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 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.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
6 checks passed
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user TTFB: 781 ms
781 msReal visitors wait 781 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 280 ms to 215 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.4 s to 4.2 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).
Images and page weight
Page weight: 2.1 MB in 66 requests
2.1 MBYour homepage downloads 2.1 MB in 66 requests on a phone: HTML 886 KiB (2), fonts 500 KiB (13) and scripts 487 KiB (14). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
HomepageHeroImage-768x264.webp 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.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.5 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
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.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 91 images in the HTML carry an alt attribute.
27 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 6 failed. 2 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.
Title is short (23 characters)
Your title is only 23 characters: “HomePage - wishpond.com”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://wishpond.com/sitemap_index.xml, so Google discovers your pages only by following links.
114 internal links, 0 external
The homepage links to 114 pages on wishpond.com and 0 external pages.
5 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Launch Faster, Scale Smarter AI-Powered MarketingWishpond is your intelligent marketing hub, leveraging AI to streamlin…”.
Canonical URL set
The canonical URL is https://wishpond.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,218 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share a meta description
https://wishpond.com/marketing-automation, https://wishpond.com/industries, https://wishpond.com/marketing-funnels, https://wishpond.com/social-promotions, https://wishpond.com/website-builder and https://wishpond.com/appointment and 2 others use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://wishpond.com/sales-automation, https://wishpond.com/marketing-automation, https://wishpond.com/industries, https://wishpond.com/healthcare-marketing-industry, https://wishpond.com/marketing-funnels and https://wishpond.com/blog/how-to-create-a-facebook-business-page and 8 others 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 45 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 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 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “LS: Error 1793002090275 run: Error during initialization or linking: TypeError: opportunities is not iterable”.
2 checks passed
Tap targets are thumb-sized
6 of 6 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 768 words of copy
The homepage carries about 768 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: “Get Started” and “Book a Demo”.
11 calls to action
The homepage has 11 calls to action, for example “Try Wishpond for FREE ->”, “Pricing” and “Contact”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
18 other companies contacted
Loading the homepage contacts 18 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 wishpond.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 Tag Manager
Hiring
- Hiring
- 2 open roles
- Teams
- SALESCLOSER.AI - Customer Success (1), WISHPOND - Account Management (1)
- Job board
- lever
- Careers page
- wishpond.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on wishpond.com, including 17 speed issues, 3 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.