dexis.com website review

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

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

Your mobile performance score is 47 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

The page has 2,396 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

4 third-party services load with your homepage (Google Tag Manager, Optanon and Google Fonts and others), adding 640 KiB and 488 ms of main-thread time.

7 images could be 159 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

Desktop scores 80 but mobile only 47. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “New Technology Just Revealed Explore innovations in imaging…”.

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

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

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

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

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

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

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

Your homepage downloads 2.4 MB in 81 requests on a phone: images 1.2 MB (51), scripts 671 KiB (11) and fonts 390 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example DEXIS-Brands_timeline_white_3500x1150.png.webp at 1,360 px wide, shown at 366 px. Resized copies would save about 42 KiB.

3 images (208 KiB) are 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.

3 images further down the page (114 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

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

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 7 <h1> headlines (“New Technology Just Revealed”, “Practical Learning for Real Digital Dentistry” and “10x less”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://dexis.com/sitemap.xml, so Google discovers your pages only by following links.

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

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 199 pages on dexis.com and 26 external pages.

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.

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.

/en-us, /en-ca and /fr-ca all use the title “DEXIS”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en-us/contact-us, /en-ca, /fr-ca, /es-mx, /es-cl and /pt-br and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/es-mx, /es-cl, /pt-br, /it-it, /es-es and /de-de have no <h1> headline, so visitors and search engines get no clear main topic.

/es-mx, /es-cl, /it-it, /es-es and /de-de have 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.

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

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

Large scripts ship without source maps.

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

1 link go through two or more redirects, for example https://to.dexis.com/dexis-illuminate-new-technology-just-revealed.

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.

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

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

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

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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 Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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