Website review, no card needed
coex3d.com website review
Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 79 checks
This review found 26 issues worth fixing on coex3d.com, 6 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
89B- #3,660 of 117,121 reviewed websitesbeats 95%
- #1,903 of 66,867 online storesbeats 95%
- #1,847 of 60,987 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 909 ms |
| May 23, 2026 | 924 ms |
| May 30, 2026 | 968 ms |
| Jun 6, 2026 | 942 ms |
| Jun 13, 2026 | 964 ms |
| Jun 20, 2026 | 946 ms |
| Jun 27, 2026 | 939 ms |
| Jul 4, 2026 | 922 ms |
| Jul 11, 2026 | 907 ms |
| Jul 18, 2026 | 955 ms |
| Jul 25, 2026 | 997 ms |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 998 ms |
| Aug 15, 2026 | 960 ms |
| Aug 22, 2026 | 947 ms |
| Aug 29, 2026 | 967 ms |
| Sep 5, 2026 | 993 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 996 ms |
| Oct 17, 2026 | 954 ms |
| Oct 24, 2026 | 941 ms |
| Oct 31, 2026 | 936 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 98 ms |
| Sep 19, 2026 | 103 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 96 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
Reduce unused JavaScript
1.7 s · 311 KiBAbout 311 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
600 ms · 319 KiB12 images could be 319 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Bing Ads and shop.app and others), adding 1.3 MB and 386 ms of main-thread time.
Shopify adds 338 ms
338 msShopify costs a phone 338 ms of main-thread work and 1.2 MB 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.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 946 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,335 HTML elements
The page has 2,335 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 36 KiB10 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 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.
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “COEX 3D filament extrusion line in Green Bay, WI”.
Time to Interactive: 11.4 s
11.4 sThe page becomes fully interactive after 11.4 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 826 ms
826 msReal visitors wait 826 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 80 ms
80 msReal visitors wait 80 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.3 MB in 433 requests
3.3 MBYour homepage downloads 3.3 MB in 433 requests on a phone: scripts 1.1 MB (180), other files 1.0 MB (186) and images 551 KiB (27). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Carbon_filled_PLA_Website_banner.png 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 0.9 g of CO₂ per visit
0.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 110.8 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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 form field without a label
1 form field has 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.
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
197 internal links, 22 external
The homepage links to 197 pages on coex3d.com and 22 external pages.
8 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “COEX 3D makes 3D printer filament in Green Bay, Wisconsin: PLA, PETG, PCTG, ABS, ASA, nylon and flexible TPE. Free ship…”.
One H1 headline
Your main headline reads: “3D printer filament made in Green Bay, WI”.
Title: 60 characters
Your title is a healthy 60 characters: “COEX 3D | High-Quality 3D Printer Filament | Made in the USA”.
Canonical URL set
The canonical URL is https://coex3d.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://coex3d.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://coex3d.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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,224 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 64 found) and read each the way a search engine does.
7 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
31 small tap targets
31 of 58 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: a.__fbeventsModules[e] is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,630 words of copy
The homepage carries about 1,630 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: “SHOP FILAMENT” and “GET BULK PRICING”.
25 calls to action
The homepage has 25 calls to action, for example “Subscribe”, “Shop Filament” and “Contact”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 testimonial or review blocks, 17 customer or partner logos and a star rating.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
21 other companies contacted
Loading the homepage contacts 21 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 coex3d.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Simprosys Google Shopping Feed · Judge Me Reviews · Dakaas Fraud Filter · Inbox · Army Man For Stores · V1 · Aftersell · Forms · trafficmanager.net
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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on coex3d.com, including 14 speed issues and 2 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.