Programmable

Website review, no card needed

summitortho.com logo

summitortho.com website review

Visit site (opens in a new tab)Reviewed 4 November 202618 issues · 75 checks

This review found 18 issues worth fixing on summitortho.com, 6 of them high impact, across 75 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

Site score

90A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.2 s1.1 sMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
86 ms78 msMay 16Oct 3179 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202680 ms
May 30, 202681 ms
Jun 6, 202681 ms
Jun 13, 202682 ms
Jun 20, 202682 ms
Jun 27, 202682 ms
Jul 4, 202683 ms
Jul 11, 202684 ms
Jul 18, 202685 ms
Jul 25, 202685 ms
Aug 1, 202683 ms
Aug 8, 202682 ms
Aug 15, 202681 ms
Aug 22, 202680 ms
Aug 29, 202680 ms
Sep 5, 202680 ms
Sep 12, 202680 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202680 ms
Oct 31, 202679 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

www.summitortho.com (opens in a new tab)
Full-page screenshot of summitortho.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. summitortho.com at 0.4 s0.4 s
  2. summitortho.com at 0.8 s0.8 s
  3. summitortho.com at 1.1 s1.1 s
  4. summitortho.com at 1.5 s1.5 s
  5. summitortho.com at 1.9 s1.9 s
  6. summitortho.com at 2.3 s2.3 s
  7. summitortho.com at 2.6 s2.6 s
  8. summitortho.com at 3.0 s3.0 s

Speed

5 to fix69

  • Reduce unused JavaScript

    1.9 s · 388 KiB

    About 388 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    2.2 s

    34 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    384 KiB

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

  • Reduce unused CSS

    300 ms · 64 KiB

    About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and Other Google APIs/SDKs and others), adding 741 KiB and 445 ms of main-thread time.

  • Improve image delivery

    247 KiB

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

  • Duplicated JavaScript

    150 ms · 8 KiB

    8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Minify CSS

    8 KiB

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

2 checks passed

  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 652 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix100

  • Largest Contentful Paint: 10.3 s

    10.3 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 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.4 s

    1.4 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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.0 s

    1.0 s

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

  • Real-user TTFB: 590 ms

    590 ms

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

  • Total Blocking Time: 169 ms

    169 ms

    Scripts block the page for only 169 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.055

    0.055

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

Images and page weight

100

  • About 0.5 g of CO₂ per visit

    0.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 59.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed

  • Page weight: 1.8 MB in 101 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 101 requests on a phone: scripts 898 KiB (33), images 603 KiB (25) and fonts 155 KiB (5). That is a lean page.

  • 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

3 to fixGoogle 9695

  • 2 tap targets too small

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9295

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

  • 92 internal links, 4 external

    The homepage links to 92 pages on summitortho.com and 4 external pages.

7 checks passed

  • Meta description: 160 characters

    Your meta description is 160 characters: “Summit Orthopedics guides you from evaluation and diagnosis to recovery—helping you prevent, treat, and heal so you can…”.

  • One H1 headline

    Your main headline reads: “Comprehensive Orthopedic Care”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Comprehensive Orthopedic Care | Summit Orthopedics”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

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

AI search readiness

1 to fix83

  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (660 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.summitortho.com/llms.txt (195 KiB, 903 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95

  • 1 page without a meta description

    https://www.summitortho.com/resources/news-events 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 44 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

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    18 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92

  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 471 words of copy

    The homepage carries about 471 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule Appointment” and “Schedule an Appointment”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Schedule An Appointment”, “Contact” and “Schedule Appointment”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 summitortho.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
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on summitortho.com, including 9 speed issues, 2 SEO issues and 1 conversion gap. 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