3ds.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: 2.7 s

  2.7 s

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

• Real-user INP: 246 ms

  246 ms

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

• Real-user FCP: 2.3 s

  2.3 s

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

• Real-user TTFB: 1.4 s

  1.4 s

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

• Tap response (INP) held steady for real visitors

  +5%

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

• Largest content (LCP) held steady for real visitors

  +7%

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

• Page weight: 3.2 MB

  3.2 MB

  Your homepage downloads 3.2 MB on a phone, 484 KiB of it images (15%). Under 2 MB keeps phones on slow connections fast.

• About 0.9 g of CO₂ per visit

  0.92 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.3 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 (1 element)

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

  Elements (1)

• 4 text elements with low contrast

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

  Elements (3)

• ARIA dialog and alertdialog nodes should have an accessible name (1 element)

  ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• ARIA role should be appropriate for the element (3 elements)

  ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Structured data has 6 problems

  Structured data found (Service and WebSite) but with 6 problems, for example “WebSite: missing name”.

  View source

• 26 internal links, 8 external

  The homepage links to 26 pages on 3ds.com and 8 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

• 3 pages slow to respond

  /products, /insights/customer-stories/hd-hyundai-xitesolution and /edu took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 2 small tap targets

  2 of 10 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: the server responded with a status of 404 ()”.

• Short HSTS lifetime

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

• No security.txt

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

• No CAA record

  3ds.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

  3ds.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: “more than 290,000 customers”. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  The homepage carries about 752 words of visible text.

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

• 3 trackers load before any consent

  3

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

• 10 cookies set on arrival

  10

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

• 11 other companies contacted

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