orthocenterillinois.com website review

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

About 1.7 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.0 s faster on a phone.

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

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

YouTube costs a phone 1.4 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (YouTube, hipaatizer.com and medchatapp.com and others), adding 6.5 MB and 2.1 s of main-thread time.

hipaatizer.com costs a phone 467 ms of main-thread work and 903 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.

medchatapp.com costs a phone 180 ms of main-thread work and 1.7 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.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

12 KiB could be saved by minifying CSS.

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

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.

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

Your largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “If your life has been disrupted by a bone, joint or muscle …”. Most of its time is element render delay (6.8 s).

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

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

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

Real visitors see the first content after 1.9 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.

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-17, real Chrome visitors' tap response (inp) went from 88 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 10.1 MB in 289 requests on a phone: scripts 6.5 MB (148), stylesheets 1.9 MB (20) and fonts 693 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example hv_logo.png at 1,668 px wide, shown at 198 px. Resized copies would save about 104 KiB.

1 image (119 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.

1 image further down the page (119 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

1 link inside paragraphs relies on colour alone to stand out.

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

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

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

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

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

Headings skip levels (h2 → h4, h3 → h5 and h2 → 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.

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

The homepage links to 188 pages on orthocenterillinois.com and 1 external page.

There is no https://orthocenterillinois.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://orthocenterillinois.com/online-pay, https://orthocenterillinois.com/nominate-an-employee, https://orthocenterillinois.com/fracture-and-injury-walk-in-clinic, https://orthocenterillinois.com/request-an-appointment, https://orthocenterillinois.com/about-oci and https://orthocenterillinois.com/oci-foundation and 9 others use the same meta description. A description written for each page earns more clicks.

https://orthocenterillinois.com/nominate-an-employee and https://orthocenterillinois.com/fracture-and-injury-walk-in-clinic have no <h1> headline, so visitors and search engines get no clear main topic.

https://orthocenterillinois.com/nominate-an-employee, https://orthocenterillinois.com/fracture-and-injury-walk-in-clinic, https://orthocenterillinois.com/request-an-appointment, https://orthocenterillinois.com/about-oci, https://orthocenterillinois.com/oci-foundation and https://orthocenterillinois.com/blog and 7 others took over 3 s to send their HTML from our server.

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

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

3 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

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

Before a visitor clicks anything, the page loads Google Ads and The Trade Desk (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 1 cookie, 1 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.