dyadtech.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.8 s

  3.8 s

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

• Real-user TTFB: 2.1 s

  2.1 s

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

• Tap response (INP) held steady for real visitors

  -1%

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

• Largest content (LCP) held steady for real visitors

  +1%

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

• Page weight: 2.8 MB

  2.8 MB

  Your homepage downloads 2.8 MB on a phone, 749 KiB of it images (27%). Under 2 MB keeps phones on slow connections fast.

• 1 image in older formats

  1 image (37 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.

  Elements (1)

• About 0.8 g of CO₂ per visit

  0.78 g

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

• 14 text elements with low contrast

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

  Elements (3)

• 9 tap targets too small

  9 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

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

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

  Elements (3)

• No main landmark

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

  Elements (1)

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

  Elements (1)

• Zoom is disabled

  The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 16 links without text

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

  Elements (3)

• 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 (h2 → h4), which makes the page harder to scan with a screen reader.

  View sourceElements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Structured data has 5 problems

  Structured data found (BreadcrumbList, Organization, Service and SoftwareApplication) but with 5 problems, for example “SoftwareApplication: no offers (price) block”.

  View source

• No social preview image

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

  View source

• 108 internal links, 12 external

  The homepage links to 108 pages on dyadtech.com and 12 external pages.

• 1 page without an H1

  /dyad-and-imperial-pfs-bring-embedded-premium-finance-and-digital-payments-to-alis-dx has no <h1> headline, so visitors and search engines get no clear main topic.

• 3 pages slow to respond

  /dyad-and-imperial-pfs-bring-embedded-premium-finance-and-digital-payments-to-alis-dx, /solutions/agency-management and /solutions/mga-platforms took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://dyadtech.com/.

• 5 small tap targets

  5 of 11 tappable elements near the top of the page are 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”.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No CAA record

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

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

• Thin social proof

  Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  The homepage carries about 315 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.

• 4 trackers load before any consent

  4

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

• 6 cookies set on arrival

  6

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

• 23 other companies contacted

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