Website review, no card needed
ultimate3dprintingstore.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 96 checks
This review found 43 issues worth fixing on ultimate3dprintingstore.com, 13 of them high impact, across 96 checks. The most urgent: render-blocking requests. 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
81B- #39,745 of 117,865 reviewed websitesbeats 61%
- #26,560 of 67,000 online storesbeats 54%
- #25,619 of 61,088 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 90 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 99 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 97 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 100 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
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.3 s
2.8 s
3.4 s
4.0 s
4.6 s
Speed
Render-blocking requests
2.1 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
6,388 HTML elements
The page has 6,388 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
750 ms · 522 KiBAbout 522 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Improve image delivery
450 ms · 555 KiB33 images could be 555 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Affirm and others), adding 2.1 MB and 664 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 305 KiB20 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 143 ms
143 msShopify costs a phone 143 ms of main-thread work and 842 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.
Klaviyo adds 89 ms
89 msKlaviyo costs a phone 89 ms of main-thread work and 307 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.
smile.io adds 61 ms
61 mssmile.io costs a phone 61 ms of main-thread work and 458 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 44 KiBAbout 44 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bambu Lab X2D Combo”.
Time to Interactive: 20.8 s
20.8 sThe page becomes fully interactive after 20.8 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 267 ms
267 msScripts block taps and scrolling for 267 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 90 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 416 ms
416 msReal visitors wait 416 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.076
0.076The layout barely moves while loading (CLS 0.076, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 365 requests
5.1 MBYour homepage downloads 5.1 MB in 365 requests on a phone: scripts 1.8 MB (147), images 988 KiB (53) and other files 841 KiB (117). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BambuLab-X2D-Combo-1200x1200.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 173.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
155 tap targets too small
155 tap targets are too small or too close together to hit reliably with a finger.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 2 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
191 internal links, 6 external
The homepage links to 191 pages on ultimate3dprintingstore.com and 6 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Find the best 3D printers, 3D printer parts, and Accessories with 24/7 customer support. Shop now over 3,000 products! …”.
Title: 59 characters
Your title is a healthy 59 characters: “Ultimate 3D Printing Store I 3D Printers I 3D Printer Parts”.
Canonical URL set
The canonical URL is https://ultimate3dprintingstore.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://ultimate3dprintingstore.com/sitemap.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.
3 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 (1,057 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ultimate3dprintingstore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://ultimate3dprintingstore.com/collections/3d-printers and https://ultimate3dprintingstore.com/products/kodak-portrait-3d-printer all use the title “3D Printers | Ultimate 3D Printing Store”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://ultimate3dprintingstore.com/pages/wish-list has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://ultimate3dprintingstore.com/collections/3d-printers and https://ultimate3dprintingstore.com/products/kodak-portrait-3d-printer use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://ultimate3dprintingstore.com/products/kodak-portrait-3d-printer, whose canonical is https://ultimate3dprintingstore.com/collections/3d-printers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://ultimate3dprintingstore.com/pages/wish-list, https://ultimate3dprintingstore.com/collections/3d-printers, https://ultimate3dprintingstore.com/products/kodak-portrait-3d-printer, https://ultimate3dprintingstore.com/collections/modix-3d-printers, https://ultimate3dprintingstore.com/collections/3d-printer-parts and https://ultimate3dprintingstore.com/collections/cnc-parts 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 127 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 broken image
1 image failed to load on a phone, for example https://ultimate3dprintingstore.com/.
25 small tap targets
25 of 44 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 509 words of copy
The homepage carries about 509 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “click here to learn more!”, “Shop The Sale >>” and “Contact Us”.
37 short forms
37 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Klaviyo and Meta Pixel and 4 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 1 of them by other companies (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.
50 other companies contacted
Loading the homepage contacts 50 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 ultimate3dprintingstore.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Epa Easy Product Addons · Buddha Mega Menu Navigation · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Conversionbear Salespop · smile.io · quotify.dev · gorgias.chat · hextom.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Odessa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on ultimate3dprintingstore.com, including 16 speed issues, 4 SEO issues and 3 conversion gaps. 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.