3tandai.com website review

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

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

The page goes through 1 redirect before it starts loading, costing about 902 ms. Link and advertise the final URL directly.

A phone's processor spends 3.0 s on main-thread work while loading, 746 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 38 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.

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

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

Your homepage downloads 27.1 MB in 160 requests on a phone: media 15.8 MB (8), images 5.7 MB (84) and other files 4.2 MB (17). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example cdc-logo-R11WjwxS.webp at 1,920 px wide, shown at 71 px. Resized copies would save about 69 KiB.

1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 5 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is 92 characters, so Google will cut it off around 60: “Gut Microbiome & Genetics based Care for Obesity and chronic illness – Digbi Health - Foo…”.

Your meta description is 367 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 37 pages on 3tandai.com and 16 external pages.

Your homepage links to /pages/reviews, /blogs/published-research, /a/careers, /blogs/humans-of-digbi/james-d, /blogs/humans-of-digbi/ofelia and /blogs/humans-of-digbi/arlene and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.

/pages/partner, /blogs/humans-of-digbi, /blogs/science-talk, /pages/about-us and /pages/help all use the title “Digbi Health | Precision Biology Care”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/partner, /blogs/humans-of-digbi, /blogs/science-talk, /pages/about-us and /pages/help use the same meta description. A description written for each page earns more clicks.

/pages/partner, /blogs/humans-of-digbi, /blogs/science-talk, /pages/about-us, /pages/digbi-live and /pages/help have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

5 links from your homepage to your own site are broken, for example https://digbihealth.com/blogs/press-release (503).

1 link to other sites is dead, for example https://news.blueshieldca.com/2024/07/09/blue-shield-of-california-celebrates-5th-anniv[%E2%80%A6]-platform-adds-new-weight-and-diabetes-management-programs (404).

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

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

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

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

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

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

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

3tandai.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:servers.mcsv.net ?all”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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

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

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.

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