Website review, no card needed
creodental.com website review
Visit site (opens in a new tab)Reviewed 25 October 202633 issues · 62 checks
This review found 33 issues worth fixing on creodental.com, 13 of them high impact, across 62 checks. The most urgent: improve image delivery. 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
73C- #91,730 of 124,214 reviewed websitesbeats 23%
- #57,118 of 69,818 online storesbeats 15%
- #1,787 of 2,907 WooCommerce storesbeats 33%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.8 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
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
Improve image delivery
31.8 s · 6.1 MB1 image could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 31.8 s faster on a phone.
Use efficient cache lifetimes
18.3 s · 3.7 MB57 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Render-blocking requests
2.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
1.4 s · 445 KiBAbout 445 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 50). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 139 KiBAbout 139 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
300 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
1,937 HTML elements
The page has 1,937 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Facebook and others), adding 673 KiB and 432 ms of main-thread time.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
Minify JavaScript
22 KiB22 KiB could be saved by minifying JavaScript.
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: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 47.5 s
47.5 sYour largest element takes 47.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 49.9 s
49.9 sThe page becomes fully interactive after 49.9 s. Good is under 3.8 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.116
0.116The layout shifts by 0.116 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.7 MB in 103 requests
9.7 MBYour homepage downloads 9.7 MB in 103 requests on a phone: images 8.1 MB (22), scripts 1.1 MB (35) and fonts 250 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 2.8 g of CO₂ per visit
2.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.76 g of CO₂e: 330.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
65 images without alt text
65 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
13 links without text
13 links have no text or label, so screen readers cannot say where they go.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings skip levels
Headings skip levels (h3 → h5, h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Home - Creodent”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 H1 headlines
There are 6 <h1> headlines (“Creodent: Now & The Future of Dentistry”, “WHAT SETS US APART” and “Learn How We Have Helped Other Dentists & Labs Wi…”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://creodental.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at creodental.com/robots.txt, the first file search crawlers ask for.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
125 internal links, 28 external
The homepage links to 125 pages on creodental.com and 28 external pages.
4 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Creodent is a full-service dental lab & digital solution provider with CAD/CAM custom abutment technology with price va…”.
Canonical URL set
The canonical URL is https://creodental.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
No llms.txt
There is no https://creodental.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.
1 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
15 pages without a title
https://creodental.com/download-center, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/crown-bridge, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/implant, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/removable and https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/orthodontics and 9 others have no <title>, so Google invents the link text in results.
15 linked pages hidden from search
https://creodental.com/download-center, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/crown-bridge, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/implant, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/removable and https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/orthodontics and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages without a meta description
https://creodental.com/download-center, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/crown-bridge, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/implant, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/removable and https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/orthodontics and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://creodental.com/download-center, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/crown-bridge, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/implant, https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/removable and https://creodental.com/creodent-full-service-dentistry-solutions-in-ny/orthodontics and 9 others 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 37 found) and read each the way a search engine does.
2 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.
Best practices
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (6 required). Every extra field lowers completion.
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 587 words of copy
The homepage carries about 587 words of visible text.
3 checks passed
17 calls to action
The homepage has 17 calls to action, for example “Download Center”, “Contact” and “Shop Now”.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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 creodental.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 © 2013.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on creodental.com, including 15 speed issues, 5 SEO 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.