mednet.com website review

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

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

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

12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and JSDelivr CDN and others), adding 499 KiB and 166 ms of main-thread time.

17 KiB could be saved by minifying CSS.

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

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

5 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Health Journey, Simplified. Seamless Access to Your He…”.

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

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

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

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

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

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

Your homepage downloads 5.1 MB in 90 requests on a phone: images 4.4 MB (41), scripts 287 KiB (7) and stylesheets 178 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

13 buttons have no accessible name, so screen readers announce just “button”.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

14 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 13 characters: “Mednet I Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Driving Regional Growth Through Smarter TPA Solut…” and “Who We Are!”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

16 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 48 pages on mednet.com and 8 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://mednet.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://mednet.com/thirtyYearsAnniversary has 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.

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css2?family=DM+Sans:ital,opsz,wght@0,9..40,100..1000;1,9..40,100..1000&disp…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

Before a visitor clicks anything, the page loads 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.

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