Website review, no card needed

asset-technology.com logo

asset-technology.com website review

Visit site (opens in a new tab)Reviewed 2 November 202637 issues · 83 checks

This review found 37 issues worth fixing on asset-technology.com, 13 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
12.1 s2.4 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 202610.3 s
May 23, 202610.2 s
May 30, 202610.2 s
Jun 6, 20269.4 s
Jun 13, 20268.7 s
Jun 20, 20267.3 s
Jun 27, 20267.5 s
Jul 4, 20267.6 s
Jul 11, 20268.3 s
Jul 18, 20268.3 s
Jul 25, 20269.6 s
Aug 1, 202611.0 s
Aug 8, 202610.2 s
Aug 15, 202610.4 s
Aug 22, 20269.6 s
Aug 29, 20268.4 s
Sep 5, 20264.8 s
Sep 12, 20264.9 s
Sep 19, 20264.6 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20263.5 s
Oct 17, 20263.6 s
Oct 24, 20263.5 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
202 ms131 msMay 16Oct 31147 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026194 ms
May 23, 2026194 ms
May 30, 2026187 ms
Jun 6, 2026158 ms
Jun 13, 2026141 ms
Jun 20, 2026141 ms
Jun 27, 2026157 ms
Jul 4, 2026149 ms
Jul 11, 2026150 ms
Jul 18, 2026146 ms
Jul 25, 2026139 ms
Aug 1, 2026139 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026174 ms
Sep 5, 2026166 ms
Sep 12, 2026169 ms
Sep 19, 2026173 ms
Sep 26, 2026156 ms
Oct 3, 2026158 ms
Oct 10, 2026161 ms
Oct 17, 2026152 ms
Oct 24, 2026148 ms
Oct 31, 2026147 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 asset-technology.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. asset-technology.com at 0.8 s0.8 s
  2. asset-technology.com at 1.7 s1.7 s
  3. asset-technology.com at 2.5 s2.5 s
  4. asset-technology.com at 3.4 s3.4 s
  5. asset-technology.com at 4.2 s4.2 s
  6. asset-technology.com at 5.1 s5.1 s
  7. asset-technology.com at 5.9 s5.9 s
  8. asset-technology.com at 6.8 s6.8 s

Speed

12 to fix58
  • Reduce unused JavaScript

    5.7 s · 792 KiB

    About 792 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Reduce unused CSS

    1.4 s · 201 KiB

    About 201 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 2.1 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 (Hotjar, Google CDN and Google Tag Manager and others), adding 1.7 MB and 920 ms of main-thread time.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    600 ms · 117 KiB

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

  • Google CDN adds 296 ms

    296 ms

    Google CDN costs a phone 296 ms of main-thread work and 736 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.

  • Font display

    350 ms

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

  • Hotjar adds 316 ms

    316 ms

    Hotjar costs a phone 316 ms of main-thread work and 232 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.

  • Google Tag Manager adds 200 ms

    200 ms

    Google Tag Manager costs a phone 200 ms of main-thread work and 477 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,793 HTML elements

    The page has 1,793 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 13 long tasks on the main thread

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

  • 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: 217 ms

    217 ms

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

Core Web Vitals

11 to fix33
  • 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: 6.5 s

    6.5 s

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 17.1 s

    17.1 s

    Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You bring the challenges, ideas, and goals. We bridge the g…”.

  • Time to Interactive: 18.9 s

    18.9 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • Real-user CLS: 0.11

    0.11

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 281 ms

    281 ms

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

  • 1 image without width and height

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

4 checks passed
  • Real-user INP: 177 ms

    177 ms

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

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

    -24%

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

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

    -64%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 10.3 s to 3.8 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).

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 117 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 117 requests on a phone: scripts 1.9 MB (55), other files 363 KiB (15) and fonts 335 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.89 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.6 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

4 to fixGoogle 8995
  • 3 images without alt text

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

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

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

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

SEO

4 to fixGoogle 8583
  • Title is short (29 characters)

    Your title is only 29 characters: “ASSET Technology Group | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Empowering Visions, Empowering Visions,”, “Delivering Impact. Delivering Impact.” and “Empowering Visions, Empowering Visions,”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 127 internal links, 3 external

    The homepage links to 127 pages on asset-technology.com and 3 external pages.

5 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “At ASSET, we empower organizations of all sizes and industries to scale new operational heights through tailored techno…”.

  • Canonical URL set

    The canonical URL is https://asset-technology.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://asset-technology.com/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: 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 (833 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://asset-technology.com/llms.txt (5 KiB, 67 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://asset-technology.com/products/ainova and https://asset-technology.com/products-lab/ainova all use the title “AINOVA | ASSET Technology Group”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://asset-technology.com/products/ainova and https://asset-technology.com/products-lab/ainova use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://asset-technology.com/products-lab/ainova, whose canonical is https://asset-technology.com/products/ainova. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages slow to respond

    https://asset-technology.com/products/arrow-cms, https://asset-technology.com/products/jupiter-ecm, https://asset-technology.com/products/aamaly, https://asset-technology.com/products/qiyas, https://asset-technology.com/products/mms and https://asset-technology.com/products-lab/ainova and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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

Google 92100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    27 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 620 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact”, “Contact us” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 25 other companies contacted

    Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 asset-technology.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on asset-technology.com, including 23 speed issues, 4 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

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