intermed.com website review

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

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

741 KiB could be saved by minifying JavaScript.

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

7 third-party services load with your homepage (Google Tag Manager, ecwcloud.com and Hubspot and others), adding 2.9 MB and 280 ms of main-thread time.

ecwcloud.com costs a phone 113 ms of main-thread work and 2.4 MB 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.

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

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

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

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

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.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to InterMed Serving Portland and its surrounding co…”.

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

5 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 88 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 66 requests on a phone: scripts 2.9 MB (17), images 1.0 MB (20) and fonts 129 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images (363 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.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 10 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: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have 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 (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 8 characters: “Intermed”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No XML sitemap at https://www.intermed.com/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 73 pages on intermed.com and 5 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://www.intermed.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.intermed.com/provider-search, https://www.intermed.com/practices-and-treatments, https://www.intermed.com/resources/forms-policies, https://www.intermed.com/pediatrics, https://www.intermed.com/additional-billing-information and https://www.intermed.com/community-support-group and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.intermed.com/practices-and-treatments, whose canonical is https://www.intermed.com/practices-and-services. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.intermed.com/get-care-now, https://www.intermed.com/practices-and-treatments, https://www.intermed.com/resources/forms-policies, https://www.intermed.com/community-support-group and https://www.intermed.com/hours-of-operation have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

8 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 image is served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 276 words of visible text.

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

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

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