privatemedical.org website review

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

109 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

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

About 668 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Lucky Orange and others), adding 1.4 MB and 672 ms of main-thread time.

Google Tag Manager costs a phone 321 ms of main-thread work and 553 KiB 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.

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

Google CDN costs a phone 280 ms of main-thread work and 742 KiB 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “private medical concierge doctors”. Most of its time is resource load delay (11.6 s).

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 3.6 MB in 138 requests on a phone: scripts 1.5 MB (48), images 1.2 MB (21) and other files 357 KiB (12). Under 2 MB keeps phones on slow connections fast.

Private-Medical-Bag-Mobile-546x600.png.webp 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).

2 images (141 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.

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

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.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 391 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 79 pages on privatemedical.org and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://privatemedical.org/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.

https://privatemedical.org/membership-inquiry is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://privatemedical.org/greenwich-concierge-medicine-concierge-doctor and https://privatemedical.org/greenwich-ct all use the title “Concierge Medicine Greenwich - Find Primary Care Concierge Doctors”. Search engines can't tell which page to show for a search, so each competes with the others.

https://privatemedical.org/greenwich-concierge-medicine-concierge-doctor and https://privatemedical.org/greenwich-ct use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://privatemedical.org/greenwich-concierge-medicine-concierge-doctor, whose canonical is https://privatemedical.org/greenwich-ct. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://privatemedical.org/membership-inquiry and https://privatemedical.org/expert-concierge-health-network have no <h1> headline, so visitors and search engines get no clear main topic.

https://privatemedical.org/who-private-medical-serves, https://privatemedical.org/expert-concierge-health-network, https://privatemedical.org/practice-locations, https://privatemedical.org/the-physician, https://privatemedical.org/practice-locations/nyc-concierge-medicine-manhattan-new-york-city-doctors and https://privatemedical.org/greenwich-concierge-medicine-concierge-doctor took over 3 s to send their HTML from our server.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

Your longest form asks for 48 fields (9 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 146 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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.

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