Website review, no card needed
3ddx.com website review
Visit site (opens in a new tab)Reviewed 28 October 202653 issues · 93 checks
This review found 53 issues worth fixing on 3ddx.com, 25 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.8 s |
| May 16, 2026 | 6.6 s |
| May 23, 2026 | 6.7 s |
| May 30, 2026 | 6.9 s |
| Jun 6, 2026 | 6.5 s |
| Jun 13, 2026 | 6.2 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.1 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 5.1 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 5.4 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 122 ms |
| May 16, 2026 | 124 ms |
| May 23, 2026 | 131 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 170 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 130 ms |
| Jun 27, 2026 | 185 ms |
| Jul 4, 2026 | 133 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 118 ms |
| Sep 19, 2026 | 158 ms |
| Sep 26, 2026 | 150 ms |
| Oct 3, 2026 | 150 ms |
| Oct 10, 2026 | 120 ms |
| Oct 17, 2026 | 113 ms |
| Oct 24, 2026 | 113 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
Speed
Use efficient cache lifetimes
27.8 s · 11.2 MB96 files are served with short cache lifetimes, so returning visitors download them again (11.2 MB).
Reduce unused CSS
13.3 s · 2.6 MBAbout 2.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 13.3 s faster on a phone.
Render-blocking requests
15.3 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 15.3 s.
Reduce unused JavaScript
11.1 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.1 s faster on a phone.
Mobile performance score: 9
9/100Your mobile performance score is 9. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.8 s
A phone's processor spends 8.8 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
350 ms · 1.4 MB11 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.4 MB and 1.6 s of main-thread time.
Minify JavaScript
750 ms · 146 KiB146 KiB could be saved by minifying JavaScript.
Google CDN adds 758 ms
758 msGoogle CDN costs a phone 758 ms of main-thread work and 741 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.
Google Tag Manager adds 570 ms
570 msGoogle Tag Manager costs a phone 570 ms of main-thread work and 375 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.
Legacy JavaScript
350 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 374 ms. During a long task the page ignores taps.
1,617 HTML elements
The page has 1,617 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 39 KiB39 KiB could be saved by minifying CSS.
Document request latency
146 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
1 checks passed
Server response: 89 ms
89 msYour server sent the HTML in 89 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 6.8 s
6.8 sReal visitors wait 6.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 23.7 s
23.7 sThe first text or image appears after 23.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 51.0 s
51.0 sYour largest element takes 51.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 23.7 s
23.7 sVisually, the page fills in at 23.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 51.6 s
51.6 sThe page becomes fully interactive after 51.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 1
1The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 995 ms
995 msScripts block taps and scrolling for 995 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 981 ms
981 msReal visitors wait 981 ms for your server to start answering (75th percentile). Good is under 800 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 122 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.8 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 15.0 MB in 169 requests
15.0 MBYour homepage downloads 15.0 MB in 169 requests on a phone: images 7.0 MB (56), scripts 4.3 MB (66) and stylesheets 2.7 MB (8). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 5.6 MB together. On a phone connection a single image that size takes seconds.
7 images in older formats
7 images (6.3 MB) 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.
4 images below the first screen load straight away
4 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.2 g of CO₂ per visit
4.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.24 g of CO₂e: 508.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
ARIA toggle fields must have an accessible name (4 elements)
ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 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 (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 65 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 12 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (11 characters)
Your title is only 11 characters: “Home - 3DDX”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
97 internal links, 25 external
The homepage links to 97 pages on 3ddx.com and 25 external pages.
5 checks passed
Meta description: 123 characters
Your meta description is 123 characters: “"3DDX streamlines your journey from scan to surgery. Find all of the information you need to get things done faster her…”.
Canonical URL set
The canonical URL is https://www.3ddx.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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.3ddx.com/sitemap_index.xml.
AI search readiness
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.
No llms.txt
There is no https://www.3ddx.com/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (739 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.3ddx.com/promotions/hot-promotion, https://www.3ddx.com/promotions/promotions-3ddx-iplan, https://www.3ddx.com/promotions/promotions-3ddx-ireport, https://www.3ddx.com/company/referrals and https://www.3ddx.com/company/direct-integrations have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.3ddx.com/services/surgical-guides, https://www.3ddx.com/services/digital-design-services, https://www.3ddx.com/products/3ddx-kits, https://www.3ddx.com/products/3ddx-sleeves, https://www.3ddx.com/promotions/hot-promotion and https://www.3ddx.com/company/referrals and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 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 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
39 of 44 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 773 words of copy
The homepage carries about 773 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER SERVICES” and “PRODUCT SHOP”.
14 calls to action
The homepage has 14 calls to action, for example “Contact Us”, “ORDER SERVICES” and “PRODUCT SHOP”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 32 testimonial or review blocks and 10 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
13 other companies contacted
Loading the homepage contacts 13 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 3ddx.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- React
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on 3ddx.com, including 26 speed issues and 4 SEO issues. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.