Website review, no card needed
waveapps.com website review
Visit site (opens in a new tab)Reviewed 17 November 202630 issues · 79 checks
This review found 30 issues worth fixing on waveapps.com, 11 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
81BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.4 s |
| Oct 24, 2026 | 3.4 s |
| Oct 31, 2026 | 3.4 s |
| Nov 7, 2026 | 3.2 s |
| Nov 14, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 125 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 127 ms |
| Nov 7, 2026 | 127 ms |
| Nov 14, 2026 | 126 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
Use efficient cache lifetimes
2.6 s · 22.6 MB47 files are served with short cache lifetimes, so returning visitors download them again (22.6 MB).
Reduce unused JavaScript
1.9 s · 658 KiBAbout 658 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.
Improve image delivery
1.4 s · 381 KiB6 images could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.3 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 (website-files.com, Google Tag Manager and survicate-cdn.com and others), adding 2.5 MB and 1.2 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
website-files.com adds 520 ms
520 mswebsite-files.com costs a phone 520 ms of main-thread work and 1.4 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.
Reduce unused CSS
450 ms · 113 KiBAbout 113 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.
Google Tag Manager adds 262 ms
262 msGoogle Tag Manager costs a phone 262 ms of main-thread work and 372 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.
1,699 HTML elements
The page has 1,699 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 17.8 s
17.8 sYour largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Wave email confirms a payment, making an overdue invoice …”.
Time to Interactive: 17.9 s
17.9 sThe page becomes fully interactive after 17.9 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 509 ms
509 msScripts block taps and scrolling for 509 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 125 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 128 ms
128 msReal 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.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 425 ms
425 msReal visitors wait 425 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.7 MB in 138 requests
27.7 MBYour homepage downloads 27.7 MB in 138 requests on a phone: media 24.5 MB (17), scripts 2.0 MB (45) and images 724 KiB (36). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 7.8 g of CO₂ per visit
7.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.84 g of CO₂e: 941.1 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
Banner landmark should not be contained in another landmark (1 element)
Banner 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 banner landmark (1 element)
Document should not have more than one banner 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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 123 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Corporation) but with 1 problem, for example “Corporation: url is not an absolute URL ("/")”.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
156 internal links, 19 external
The homepage links to 156 pages on waveapps.com and 19 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Create beautiful invoices, accept online payments, and make accounting easy—all in one place—with Wave’s suite of money…”.
One H1 headline
Your main headline reads: “Clear books.Confident decisions.”.
Title: 46 characters
Your title is a healthy 46 characters: “Wave: Small Business Software - Wave Financial”.
Canonical URL set
The canonical URL is https://www.waveapps.com/.
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.waveapps.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.waveapps.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.
3 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 (2,155 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.waveapps.com/advisors/sale-tcs is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.waveapps.com/advisors/sale-tcs has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 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 “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
16 of 18 tappable elements near the top are at least 24 px.
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 1,184 words of copy
The homepage carries about 1,184 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: “Learn more” and “Get started now”.
15 calls to action
The homepage has 15 calls to action, for example “Learn more”, “Pricing” and “Get started nowGet started now”.
Social proof on the page
Social proof on the homepage: 41 testimonial or review blocks, 19 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics and Amplitude.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 2 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 6 of them by other companies (measured from a US location before any click).
31 other companies contacted
Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) 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 waveapps.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
- Webflow
- Analytics
- Google Analytics | Segment | Amplitude
- Hosting
- Webflow
Hiring
- Hiring
- 8 open roles
- Teams
- Product (2), Risk (2), Engineering (1), Machine Learning (1)
- Job board
- lever
Company
- Founded
- 2009
- Headquarters
- Toronto
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 waveapps.com, including 19 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.