Website review, no card needed

apty.ai logo

apty.ai website review

Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 87 checks

This review found 42 issues worth fixing on apty.ai, 18 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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
4.1 s2.6 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.0 s
May 9, 20263.7 s
May 16, 20263.6 s
May 23, 20263.3 s
May 30, 20263.1 s
Jun 6, 20262.9 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.8 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.4 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.2 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
249 ms126 msMay 2Oct 17157 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026235 ms
May 9, 2026217 ms
May 23, 2026173 ms
May 30, 2026176 ms
Jun 6, 2026165 ms
Jun 13, 2026154 ms
Jun 20, 2026161 ms
Jun 27, 2026154 ms
Jul 4, 2026140 ms
Jul 11, 2026154 ms
Jul 18, 2026154 ms
Jul 25, 2026160 ms
Aug 1, 2026162 ms
Aug 8, 2026179 ms
Aug 15, 2026179 ms
Aug 22, 2026169 ms
Aug 29, 2026206 ms
Sep 5, 2026194 ms
Sep 12, 2026177 ms
Sep 19, 2026197 ms
Sep 26, 2026178 ms
Oct 3, 2026165 ms
Oct 10, 2026168 ms
Oct 17, 2026157 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 apty.ai (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apty.ai at 1.6 s1.6 s
  2. apty.ai at 3.2 s3.2 s
  3. apty.ai at 4.8 s4.8 s
  4. apty.ai at 6.4 s6.4 s
  5. apty.ai at 8.0 s8.0 s
  6. apty.ai at 9.6 s9.6 s
  7. apty.ai at 11.2 s11.2 s
  8. apty.ai at 12.8 s12.8 s

Speed

13 to fix31
  • Render-blocking requests

    3.3 s

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

  • Google Tag Manager adds 2.9 s

    2.9 s

    Google Tag Manager costs a phone 2.9 s of main-thread work and 743 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 15.2 s

    A phone's processor spends 15.2 s on main-thread work while loading, 7.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and Hotjar and others), adding 1.4 MB and 5.0 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Reduce unused CSS

    920 ms · 183 KiB

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

  • Improve image delivery

    953 KiB

    5 images could be 953 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Hubspot adds 758 ms

    758 ms

    Hubspot costs a phone 758 ms of main-thread work and 339 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 JavaScript

    594 KiB

    About 594 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    503 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (503 KiB).

  • Hotjar adds 409 ms

    409 ms

    Hotjar costs a phone 409 ms of main-thread work and 65 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 348 ms

    348 ms

    Facebook costs a phone 348 ms of main-thread work and 144 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.

  • Legacy JavaScript

    54 KiB

    Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 58 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify JavaScript

    6 KiB

    6 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: 7 ms

    7 ms

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

Core Web Vitals

10 to fix50
  • 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.0 s

    3.0 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Total Blocking Time: 5.2 s

    5.2 s

    Scripts block taps and scrolling for 5.2 s in total while the page loads. Good is under 200 ms.

  • Time to Interactive: 26.4 s

    26.4 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Apty is an AI-powered Digital Adoption Platform built to im…”. Most of its time is element render delay (3.4 s).

  • Real-user LCP: 3.0 s

    3.0 s

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

  • 31 images without width and height

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

4 checks passed
  • Real-user CLS: 0.07

    0.07

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

  • Tap response (INP) got 28% faster for real visitors

    -28%

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

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

    -19%

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

  • Cumulative Layout Shift: 0.056

    0.056

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

Images and page weight

4 to fix25
  • Page weight: 15.0 MB in 165 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 165 requests on a phone: media 9.9 MB (1), images 3.0 MB (32) and scripts 1.7 MB (53). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Apty-5.0-image-scaled.png weighs 927 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    771 KiB

    1 image is downloaded at several times the size a phone draws it, for example Apty-5.0-image-scaled.png at 2,560 px wide, shown at 350 px. Resized copies would save about 771 KiB.

  • 2 images in older formats

    2 images (972 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.

  • 1 image below the first screen load straight away

    1 image further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.25 g

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

Accessibility

7 to fixGoogle 8990
  • 5 text elements with low contrast

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

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

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

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

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • Structured data has 4 problems

    Structured data found (ImageObject, Organization, SoftwareApplication and VideoObject) but with 4 problems, for example “ImageObject: url is not an absolute URL ("https://apty.ai/wp-content/uploads/2026/03/apty-banner-background.svg")”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 83 internal links, 8 external

    The homepage links to 83 pages on apty.ai and 8 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Drive enterprise software adoption with Apty’s digital adoption platform. Improve onboarding, ensure compliance, and in…”.

  • One H1 headline

    Your main headline reads: “Digital adoption that's |”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Digital Adoption Platform for Enterprise Software | Apty”.

  • Canonical URL set

    The canonical URL is https://apty.ai/.

  • 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://apty.ai/sitemap_index.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (787 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://apty.ai/llms.txt (9 KiB, 1 link, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 9 pages without an H1

    https://apty.ai/digital-adoption-outcomes, https://apty.ai/application-categories/digital-adoption-for-erp, https://apty.ai/application-categories/digital-adoption-for-hrms, https://apty.ai/application-categories/digital-adoption-for-itsm, https://apty.ai/application-categories/digital-adoption-for-lms and https://apty.ai/application-categories/digital-adoption-for-supply-chain and 3 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 70 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=355050291&tm=gtm002&Ver=2&mid=0ab7f10f-50ba-4d80-b25b-511733f77190&bo=1&sid=71798fc0cfe611f1934ebfd246cb198b&vid=71797cf0cfe611f18e3c31f72b59ef2e&vids=1&msclkid=N&gtm_.

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

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

1 to fix90
  • 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 663 words of copy

    The homepage carries about 663 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: “Pricing” and “Book a demo”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Pricing”, “Contact us” and “Book a demo”.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks, 23 customer or partner logos and “7M+ users”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (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.

  • 17 cookies set on arrival

    17

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 apty.ai, 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

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 apty.ai, including 23 speed issues, 3 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

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