accelalpha.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.4 s

  4.4 s

  Real visitors wait 4.4 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 INP: 369 ms

  369 ms

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

• Real-user CLS: 0.14

  0.14

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

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

  +29%

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

• Real-user TTFB: 1.7 s

  1.7 s

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

• Largest content (LCP) held steady for real visitors

  -8%

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

• Page weight: 6.4 MB

  6.4 MB

  Your homepage downloads 6.4 MB on a phone, 1.2 MB of it images (18%). Under 2 MB keeps phones on slow connections fast.

• About 1.8 g of CO₂ per visit

  1.83 g

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

• Certain ARIA roles must be contained by particular parents (10 elements)

  Certain ARIA roles must be contained by particular parents: 10 elements on the page fail this check, rated critical by axe-core.

  Elements (3)

• Certain ARIA roles must contain particular children (1 element)

  Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• <svg> elements with an img or image role must have alternative text (9 elements)

  <svg> elements with an img or image role must have alternative text: 9 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• Hidden but focusable

  1 element hidden from screen readers can still receive keyboard focus.

  Elements (1)

• Links look like plain text

  1 link inside paragraphs relies on colour alone to stand out.

  Elements (1)

• 1 tap target too small

  1 tap target is too small or too close together to hit reliably with a finger.

  Elements (1)

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

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

  Elements (3)

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

  Elements (1)

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

  Elements (1)

• No main landmark

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

  Elements (1)

• 4 links without text

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

  Elements (1)

• Headings should not be empty (4 elements)

  Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View sourceElements (3)

• Title is short (14 characters)

  Your title is only 14 characters: “IBM Accelalpha”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“IBM Accelalpha” and “Value that we deliver”). One clear main headline is easier for people and search engines.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 21 internal links, 0 external

  The homepage links to 21 pages on accelalpha.com and 0 external pages.

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

  View source

• No llms.txt

  There is no /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.

• 4 pages without a title

  /downloads/documents/us-en/1443d5c92ec02bbc, /downloads/documents/us-en/1443d5c92ec02bc4, /downloads/documents/us-en/1443d5c92ec02bbe and /downloads/documents/us-en/1443d5c92ec02bc6 have no <title>, so Google invents the link text in results.

  Elements (4)

• 1 linked page hidden from search

  /campaign/ibm-oracle-partnership is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 4 pages without a meta description

  /downloads/documents/us-en/1443d5c92ec02bbc, /downloads/documents/us-en/1443d5c92ec02bc4, /downloads/documents/us-en/1443d5c92ec02bbe and /downloads/documents/us-en/1443d5c92ec02bc6 have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 5 links to non-canonical URLs

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

  Elements (5)

• 5 pages without an H1

  /forms/mkt-whitepaper-164c1, /downloads/documents/us-en/1443d5c92ec02bbc, /downloads/documents/us-en/1443d5c92ec02bc4, /downloads/documents/us-en/1443d5c92ec02bbe and /downloads/documents/us-en/1443d5c92ec02bc6 have no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page with very little text

  /forms/mkt-whitepaper-164c1 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

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

• 2 broken images

  2 images failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

• 6 small tap targets

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

• 5 JavaScript errors while loading

  5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No CAA record

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

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

• 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 social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  The homepage carries about 1,265 words of visible text.

• Email authentication score: 100/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.

• 7 trackers load before any consent

  7

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity 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.

• 44 cookies set on arrival

  44

  Opening the homepage sets 44 cookies, 3 of them by other companies (measured from a US location before any click).

• 53 other companies contacted

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