Website review, no card needed
ormco.com website review
Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 86 checks
This review found 34 issues worth fixing on ormco.com, 12 of them high impact, across 86 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 128 ms |
| May 16, 2026 | 124 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 124 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 93 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 99 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 97 ms |
| Oct 10, 2026 | 99 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 95 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
Render-blocking requests
10.9 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.9 s.
Reduce unused CSS
6.6 s · 1.3 MBAbout 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 320 KiB51 files are served with short cache lifetimes, so returning visitors download them again (320 KiB).
Reduce unused JavaScript
1.2 s · 250 KiBAbout 250 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 43). Pages that score under 90 lose visitors before the first paint.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Optanon and VWO), adding 604 KiB and 300 ms of main-thread time.
Improve image delivery
150 ms · 24 KiB1 image could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.
Document request latency
73 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 475 ms of it running JavaScript. That is comfortably low.
Server response: 16 ms
16 msYour server sent the HTML in 16 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.
First Contentful Paint: 11.0 s
11.0 sThe first text or image appears after 11.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners use cookies and similar tools (“Cookies…”.
Time to Interactive: 18.7 s
18.7 sThe page becomes fully interactive after 18.7 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Largest content (LCP) got 34% slower for real visitors
+34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 965 ms
965 msReal visitors wait 965 ms for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 128 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 154 ms
154 msScripts block the page for only 154 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.038
0.038The layout barely moves while loading (CLS 0.038, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 64 requests
3.2 MBYour homepage downloads 3.2 MB in 64 requests on a phone: stylesheets 1.4 MB (2), scripts 527 KiB (5) and images 504 KiB (39). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (7 elements)
Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.
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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (6 elements)
Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (FAQPage, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:description), 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.
93 internal links, 91 external
The homepage links to 93 pages on ormco.com and 91 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Explore Ormco’s full range of orthodontic solutions, including brackets, clear aligners, scanners, bonding systems and …”.
One H1 headline
Your main headline reads: “Proven tools for faster, smarter orthodontics”.
Title: 54 characters
Your title is a healthy 54 characters: “Ormco | 60 Years of Expertise in Orthodontic Solutions”.
Canonical URL set
The canonical URL is https://ormco.com/en-us.
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://ormco.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://ormco.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,660 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://ormco.com/en-au and https://ormco.com/en-in all use the title “Orthodontics Supply Company | Brackets, Wires & More | Ormco Supplies”. 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://ormco.com/en-us/mini-twin has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://ormco.com/en-au and https://ormco.com/en-in use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://ormco.com/pt-br, https://ormco.com/en-in and https://ormco.com/en-us/mini-twin have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://ormco.com/en-us/mini-twin has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
4 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.
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 small tap targets
4 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Thin social proof
Social proof on the homepage: 13 testimonial or review blocks. 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 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.
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 1,904 words of copy
The homepage carries about 1,904 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Track Order” and “Order History”.
25 calls to action
The homepage has 25 calls to action, for example “LEARN MORE ABOUT OUR BRACKETS”, “LEARN MORE ABOUT OUR WIRES” and “LEARN MORE ABOUT OUR BUCCAL TUBES”.
1 short form
A short form (1 field at most) is right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 ormco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal 10 (https://www.drupal.org)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ormco.com, including 16 speed issues, 3 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.