Website review, no card needed

d-matrix.ai logo

d-matrix.ai website review

Visit site (opens in a new tab)Reviewed 31 October 202634 issues · 80 checks

This review found 34 issues worth fixing on d-matrix.ai, 13 of them high impact, across 80 checks. The most urgent: page weight: 24.9 MB in 72 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
3.1 s1.8 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.7 s
Sep 5, 20262.4 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
212 ms89 msMay 9Oct 24109 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026198 ms
May 16, 2026191 ms
May 23, 2026192 ms
May 30, 2026193 ms
Jun 6, 2026194 ms
Jun 13, 2026170 ms
Jun 20, 2026150 ms
Jun 27, 2026142 ms
Jul 4, 2026137 ms
Jul 11, 2026151 ms
Jul 18, 2026150 ms
Jul 25, 2026151 ms
Aug 1, 2026150 ms
Aug 8, 2026158 ms
Aug 15, 2026155 ms
Aug 22, 2026155 ms
Aug 29, 2026135 ms
Sep 5, 2026114 ms
Sep 12, 2026113 ms
Sep 19, 2026107 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 2026104 ms
Oct 17, 2026107 ms
Oct 24, 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 d-matrix.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. d-matrix.ai at 0.4 s0.4 s
  2. d-matrix.ai at 0.8 s0.8 s
  3. d-matrix.ai at 1.1 s1.1 s
  4. d-matrix.ai at 1.5 s1.5 s
  5. d-matrix.ai at 1.9 s1.9 s
  6. d-matrix.ai at 2.3 s2.3 s
  7. d-matrix.ai at 2.6 s2.6 s
  8. d-matrix.ai at 3.0 s3.0 s

Speed

6 to fix65
  • Reduce unused JavaScript

    2.0 s · 312 KiB

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

  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and LinkedIn Ads and others), adding 11.4 MB and 561 ms of main-thread time.

  • wpenginepowered.com adds 0 ms

    0 ms

    wpenginepowered.com costs a phone 0 ms of main-thread work and 10.8 MB 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.

  • Mobile performance score: 65

    65/100

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

  • Google Tag Manager adds 469 ms

    469 ms

    Google Tag Manager costs a phone 469 ms of main-thread work and 482 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.

  • Improve image delivery

    150 ms · 42 KiB

    2 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 12 KiB

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

  • Minify JavaScript

    150 ms · 8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    20 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • Largest Contentful Paint: 13.2 s

    13.2 s

    Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Announcing d-Matrix Partners with NVIDIA on NVLink Fusion N…”.

  • Time to Interactive: 13.6 s

    13.6 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 212 ms

    212 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 11 images without width and height

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 106 ms

    106 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -44%

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

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

    -30%

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

Images and page weight

3 to fix43
  • Page weight: 24.9 MB in 72 requests

    24.9 MB

    Your homepage downloads 24.9 MB in 72 requests on a phone: media 21.7 MB (2), images 2.4 MB (26) and scripts 634 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    1.0 MB

    9 images are downloaded at several times the size a phone draws them, for example engineering-pipeline-copy.webp at 1,920 px wide, shown at 271 px. Resized copies would save about 1.0 MB.

  • 10 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (66 KiB) is 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.

  • About 7.1 g of CO₂ per visit

    7.05 g

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

Accessibility

5 to fixGoogle 8191
  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • 2 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 4 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “NO LATENCY”). One clear main headline is easier for people and search engines.

  • 66 internal links, 3 external

    The homepage links to 66 pages on d-matrix.ai and 3 external pages.

7 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “d-Matrix is redefining AI inference with memory-centric compute built for ultra-low latency, greater efficiency, and sc…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “d-Matrix - Memory-Centric Compute for AI Inference”.

  • Canonical URL set

    The canonical URL is https://www.d-matrix.ai/.

  • Structured data in place

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

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.d-matrix.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: 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 (884 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.d-matrix.ai/llms.txt (3 KiB, 29 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix79
  • 1 linked page hidden from search

    https://www.d-matrix.ai/product/aviator is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.d-matrix.ai/product and https://www.d-matrix.ai/product/aviator all use the title “d-Matrix Corsair AI Platform | In-Memory Computing for AI”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://www.d-matrix.ai/announcements/squadron-compute-clusters, https://www.d-matrix.ai/solutions, https://www.d-matrix.ai/solutions/voice, https://www.d-matrix.ai/solutions/security, https://www.d-matrix.ai/solutions/inference-optimization and https://www.d-matrix.ai/solutions/code-generation and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.d-matrix.ai/product and https://www.d-matrix.ai/product/aviator use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 35 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 668 words of copy

    The homepage carries about 668 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Request Early Access”, “Contact Sales” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 8 cookies set on arrival

    8

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 d-matrix.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 Analytics | Google Tag Manager | Microsoft Clarity
Hosting
WP Engine

Hiring

Hiring
41 open roles
Teams
Software Engineering (15), G&A (9), Hardware Engineering (7), Architecture (3)
Job board
ashby

Company

Founded
2018

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on d-matrix.ai, including 15 speed issues, 1 SEO issue and 3 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