Website review, no card needed

actdigital.com logo

actdigital.com website review

Visit site (opens in a new tab)Reviewed 18 October 202626 issues · 83 checks

This review found 26 issues worth fixing on actdigital.com, 6 of them high impact, across 83 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
5.3 s2.0 sApr 25Oct 104.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.8 s
May 2, 20262.8 s
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20264.0 s
Sep 12, 20264.7 s
Sep 19, 20264.9 s
Sep 26, 20264.9 s
Oct 3, 20264.9 s
Oct 10, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
225 ms102 msApr 25Oct 10156 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026137 ms
May 2, 2026132 ms
May 9, 2026135 ms
May 16, 2026127 ms
May 23, 2026132 ms
May 30, 2026137 ms
Jun 6, 2026144 ms
Jun 13, 2026146 ms
Jun 20, 2026136 ms
Jun 27, 2026129 ms
Jul 4, 2026128 ms
Jul 11, 2026124 ms
Jul 18, 2026127 ms
Jul 25, 2026127 ms
Aug 1, 2026121 ms
Aug 8, 2026120 ms
Aug 15, 2026116 ms
Aug 22, 2026117 ms
Aug 29, 2026119 ms
Sep 5, 2026157 ms
Sep 12, 2026209 ms
Sep 19, 2026211 ms
Sep 26, 2026205 ms
Oct 3, 2026189 ms
Oct 10, 2026156 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 actdigital.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. actdigital.com at 0.6 s0.6 s
  2. actdigital.com at 1.2 s1.2 s
  3. actdigital.com at 1.8 s1.8 s
  4. actdigital.com at 2.4 s2.4 s
  5. actdigital.com at 3.0 s3.0 s
  6. actdigital.com at 3.7 s3.7 s
  7. actdigital.com at 4.3 s4.3 s
  8. actdigital.com at 4.9 s4.9 s

actdigital.com does not allow embedding, so this is Google's rendering of the page.

Speed

4 to fix63
  • Render-blocking requests

    1.5 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.5 s.

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    410 KiB

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

  • Reduce unused CSS

    300 ms · 58 KiB

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

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • Use efficient cache lifetimes

    150 ms · 4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 12 KiB and 6 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.6 s

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

  • Server response: 140 ms

    140 ms

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

Core Web Vitals

12 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 CLS: 0.36

    0.36

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.5 s).

  • Speed Index: 8.0 s

    8.0 s

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

  • Time to Interactive: 8.2 s

    8.2 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

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

    +28%

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

  • Largest content (LCP) got 68% slower for real visitors

    +68%

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

  • Real-user FCP: 2.8 s

    2.8 s

    Real visitors see the first content after 2.8 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.

  • 65 images without width and height

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

3 checks passed
  • Real-user INP: 114 ms

    114 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix50
  • Page weight: 2.1 MB in 98 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 98 requests on a phone: images 1.8 MB (86), fonts 162 KiB (5) and stylesheets 71 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

Accessibility

1 to fix87
  • 13 links without text

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 142 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 9290
  • 6 H1 headlines

    There are 6 <h1> headlines (“Press”, “AI-first technology present in13 countries with g…” and “A new phase of enterprise AI: companies must deli…”). 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.

  • 10 links with vague text

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

  • 142 internal links, 7 external

    The homepage links to 142 pages on actdigital.com and 7 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “We design and deploy AI solutions, intelligent agents, and digital transformation strategies. 7,000+ impactors across 1…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “act digital – AI-first Tech Company in 12 Countries”.

  • Canonical URL set

    The canonical URL is https://actdigital.com/en/.

  • 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://actdigital.com/sitemap_index.xml.

AI search readiness

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

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 51 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 2 pages share a title

    /en and / all use the title “act digital – AI-first Tech Company in 12 Countries”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    /en/solucoes/act-prosperi-ai-en, /en/solutions/data-ai-en, /en/solutions/intelligent-automation-en, /en/solutions/agile-development-quality-en, /en/solutions/digital-experience-en and /en/solutions/enterprise-platforms-en and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is /en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages slow to respond

    /, /en/solucoes/act-prosperi-ai-en, /en/solutions/agile-development-quality-en, /en/solutions/digital-experience-en, /en/solutions/enterprise-platforms-en and /en/solutions/digital-architecture-modernization-platforms-en and 2 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 57 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

Google 100100
1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 30 days; one year is the recommended minimum.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (actdigital.com).

  • Valid certificate (39 days left)

    The certificate from Google Trust Services · WE1 verifies for actdigital.com and is valid for another 39 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://actdigital.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 47 links work

    All 47 links checked from your homepage (40 internal, 7 external) answered without errors.

Domain and trust

  • No CAA record

    actdigital.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    actdigital.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 30 years old

    30 years

    actdigital.com was registered in Jul 1996 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Jul 2029

    actdigital.com is registered until Jul 2029.

Content and conversion

2 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 603 words of visible text.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Join us”, “Contact” and “Download”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Email authentication

90
  • Email authentication score: 90/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:_spfcf1.actdigital.com include:_spfcf2.actdigital.com include:_spfcf3.actdigital.com include:_spfcf4.act…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

CMS
WordPress
Framework
jQuery
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 free review found 26 issues on actdigital.com, including 16 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

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