larkinhealth.com website review

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

About 228 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 66 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

3 third-party services load with your homepage (Unpkg, userway.org and Google Fonts), adding 206 KiB and 49 ms of main-thread time.

20 KiB could be saved by minifying JavaScript.

Desktop scores 93 but mobile only 66. 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.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Larkin Health System is an integrated healthcare delivery s…”. Most of its time is element render delay (4.0 s).

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

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

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

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

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

26 images 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 74 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.1 MB in 42 requests on a phone: images 1.4 MB (19), scripts 345 KiB (9) and stylesheets 238 KiB (3). Under 2 MB keeps phones on slow connections fast.

10 images (758 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.

11 images further down the page (712 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example woman.jpg__1280x800_q85_crop_subsampling-2.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 16 KiB.

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

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

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

6 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 → h4), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 90 pages on larkinhealth.com and 16 external pages.

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.

There is no https://larkinhealth.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://larkinhealth.com/en/specialty-centers/cardiology and https://larkinhealth.com/en/treatments-services/cardiology all use the title “Cardiology | Larkin Health”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://larkinhealth.com/doctors, https://larkinhealth.com/covid-19-updates, https://larkinhealth.com/en/patients-visitors/patient-portal, https://larkinhealth.com/en/careers, https://larkinhealth.com/en/specialty-centers/orthopedics and https://larkinhealth.com/en/specialty-centers/neuroscience and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://larkinhealth.com/doctors, whose canonical is https://larkinhealth.com/en/doctors. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://larkinhealth.com/en/patients-visitors/patient-portal, https://larkinhealth.com/en/careers, https://larkinhealth.com/en/specialty-centers/orthopedics, https://larkinhealth.com/en/specialty-centers/internal-medicine, https://larkinhealth.com/en/specialty-centers/cardiology and https://larkinhealth.com/en/treatments-services/emergency-services and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://larkinhealth.com/covid-19-updates, https://larkinhealth.com/en/specialty-centers/orthopedics, https://larkinhealth.com/en/specialty-centers/neuroscience and https://larkinhealth.com/en/specialty-centers/mental-health took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,258 words of visible text.

Opening the homepage sets 1 cookie (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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.