Website review, no card needed

adda.io logo

adda.io website review

Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 69 checks

This review found 38 issues worth fixing on adda.io, 20 of them high impact, across 69 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
5.7 s3.6 sApr 25Oct 104.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.4 s
May 2, 20265.5 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.0 s
Jul 18, 20264.0 s
Jul 25, 20264.0 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.6 s
Aug 22, 20264.5 s
Aug 29, 20264.2 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
119 ms103 msSep 12Oct 10109 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 2026116 ms
Sep 19, 2026117 ms
Sep 26, 2026113 ms
Oct 3, 2026105 ms
Oct 10, 2026109 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

Full-page screenshot of adda.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adda.io at 0.6 s0.6 s
  2. adda.io at 1.3 s1.3 s
  3. adda.io at 1.9 s1.9 s
  4. adda.io at 2.5 s2.5 s
  5. adda.io at 3.2 s3.2 s
  6. adda.io at 3.8 s3.8 s
  7. adda.io at 4.4 s4.4 s
  8. adda.io at 5.0 s5.0 s

Speed

5 to fix63
  • Improve image delivery

    14.3 s · 18.0 MB

    22 images could be 18.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.3 s faster on a phone.

  • Use efficient cache lifetimes

    3.0 s · 1.4 MB

    3 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Render-blocking requests

    2.7 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    320 ms · 60 KiB

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

  • Reduce unused CSS

    160 ms · 39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 64 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 102 KiB and 0 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

9 to fix67
  • 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 LCP: 4.2 s

    4.2 s

    Real visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.3 s

    3.3 s

    Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 18.6 s

    18.6 s

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

  • Time to Interactive: 18.6 s

    18.6 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.4 s

    5.4 s

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

  • 37 images without width and height

    37 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 116 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.4 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 14 ms

    14 ms

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

Images and page weight

5 to fix18
  • Page weight: 20.3 MB in 37 requests

    20.3 MB

    Your homepage downloads 20.3 MB in 37 requests on a phone: images 19.9 MB (26), fonts 212 KiB (7) and scripts 132 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 16 images over 500 KB

    16 images weigh 17.2 MB together. On a phone connection a single image that size takes seconds.

  • 19 images far larger than shown

    12.4 MB

    19 images are downloaded at several times the size a phone draws them, for example community-02-kdVsYuB9.png at 1,010 px wide, shown at 190 px. Resized copies would save about 12.4 MB.

  • 22 images in older formats

    22 images (18.6 MB) 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.

  • 17 images below the first screen load straight away

    17 images further down the page (16.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.8 g of CO₂ per visit

    5.76 g

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

Accessibility

5 to fixGoogle 8490
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

1 checks passed
  • 35 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: 35 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 10070
  • 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (162 characters)

    Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://usa.adda.io/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “Best HOA Management Software for Self-Managed HOAs | ADDA”.

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 426 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

  • No llms.txt

    There is no https://usa.adda.io/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.

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

Best practices

1 to fixGoogle 10093
  • 2 small tap targets

    2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 426 words of copy

    The homepage carries about 426 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Demo” and “See Pricing”.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 adda.io, 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
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 38 issues on adda.io, including 14 speed issues, 7 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