Website review, no card needed

drcomfort.com logo

drcomfort.com website review

Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 91 checks

This review found 40 issues worth fixing on drcomfort.com, 19 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.1 sMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
176 ms134 msMay 2Oct 17139 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026171 ms
May 9, 2026163 ms
May 16, 2026161 ms
May 23, 2026161 ms
May 30, 2026161 ms
Jun 6, 2026162 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026162 ms
Jul 4, 2026157 ms
Jul 11, 2026154 ms
Jul 18, 2026150 ms
Jul 25, 2026150 ms
Aug 1, 2026147 ms
Aug 8, 2026141 ms
Aug 15, 2026140 ms
Aug 22, 2026145 ms
Aug 29, 2026148 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026150 ms
Oct 3, 2026145 ms
Oct 10, 2026142 ms
Oct 17, 2026139 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

Full-page screenshot of drcomfort.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drcomfort.com at 0.9 s0.9 s
  2. drcomfort.com at 1.9 s1.9 s
  3. drcomfort.com at 2.8 s2.8 s
  4. drcomfort.com at 3.7 s3.7 s
  5. drcomfort.com at 4.6 s4.6 s
  6. drcomfort.com at 5.6 s5.6 s
  7. drcomfort.com at 6.5 s6.5 s
  8. drcomfort.com at 7.4 s7.4 s

Speed

10 to fix37
  • Reduce unused JavaScript

    1.4 s · 884 KiB

    About 884 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.

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.4 s

    A phone's processor spends 6.4 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and rebuyengine.com and others), adding 2.3 MB and 2.0 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 443 KiB

    35 files are served with short cache lifetimes, so returning visitors download them again (443 KiB).

  • Improve image delivery

    686 KiB

    14 images could be 686 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    450 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 314 ms. During a long task the page ignores taps.

  • 1,657 HTML elements

    The page has 1,657 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 55 KiB

    Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    36 KiB

    About 36 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 62 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 28.2 s

    28.2 s

    The page becomes fully interactive after 28.2 s. Good is under 3.8 s.

  • Total Blocking Time: 1.3 s

    1.3 s

    Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.8 s

    3.8 s

    The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.8 s

    6.8 s

    Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

9 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.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 151 ms

    151 ms

    Real visitors wait 151 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 577 ms

    577 ms

    Real visitors wait 577 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 171 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 51% faster for real visitors

    -51%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix36
  • Page weight: 4.5 MB in 310 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 310 requests on a phone: scripts 2.6 MB (115), images 983 KiB (46) and other files 789 KiB (122). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Oct_25off_Ahtletic_HP_Banner_Mobile_839x1202_2c9ddb04-8478-4 weighs 595 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Oct_25off_Ahtletic_HP_Banner_Mobile_839x1202_2c9ddb04-8478-4 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).

  • 3 images in older formats

    3 images (927 KiB) 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.

  • About 1.3 g of CO₂ per visit

    1.28 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.2 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

13 to fixGoogle 7482
  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 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.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 13 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • 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.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 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.

  • 255 internal links, 8 external

    The homepage links to 255 pages on drcomfort.com and 8 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Dr. Comfort orthopedic shoes offer orthotic support, comfortable wear, and a secure fit to help relieve foot pain so wa…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Orthopedic Shoes, Footwear & Custom Orthotics – Dr. Comfort”.

  • Canonical URL set

    The canonical URL is https://www.drcomfort.com/.

  • 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.drcomfort.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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,243 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.drcomfort.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.drcomfort.com/collections/womens-slip-resistant has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 82 found) and read each the way a search engine does.

6 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5453597&tm=gtm002&Ver=2&mid=881e78b9-e90a-400d-8d25-e5bb41fc5b53&bo=1&sid=29d6be20cfd511f18e53e9e3af859d64&vid=29d6a200cfd511f18c15598fec3f5575&vids=1&msclkid=N&pi=918.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “sm_beacon is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    153 of 170 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 972 words of copy

    The homepage carries about 972 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Best Sellers” and “Shop by Foot Concern”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Talk to an expert: 866.922.5300”, “Shop Best Sellers” and “Shop by Foot Concern”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • 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

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 60 other companies contacted

    Loading the homepage contacts 60 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 drcomfort.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on drcomfort.com, including 15 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25