medable.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and website-files.com and others), adding 1.6 MB and 997 ms of main-thread time.

Google Tag Manager costs a phone 422 ms of main-thread work and 504 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 3.4 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

website-files.com costs a phone 120 ms of main-thread work and 679 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 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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 wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A new model for clinical development is taking shape where …”.

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

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

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

Scripts block taps and scrolling for 697 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 164 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 126 requests on a phone: scripts 1.5 MB (39), images 559 KiB (27) and other files 245 KiB (49). Under 2 MB keeps phones on slow connections fast.

6a7baaca04d2d5a5bac6934e_Tufts agent eNPV-p-500.jpg 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).

1 image (40 KiB) is 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 0.71 g of CO₂e: 84.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “Medable Clinical Trial Platform (Agentic AI, eCOA, and DCT solutions)”.

There are 2 <h1> headlines (“Clinical development, meet agentic AI.” and “Medable's 1:1:1 vision”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

Structured data found (Corporation and WebSite) but with 1 problem, for example “WebSite: missing name”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 71 pages on medable.com and 9 external pages.

There is no https://www.medable.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.

https://www.medable.com/platform/studio is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

1 image failed to load on a phone, for example https://www.medable.com/.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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.

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

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.

The homepage carries about 771 words of visible text.

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

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

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