Website review, no card needed

advancedradiology.com logo

advancedradiology.com website review

Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 86 checks

This review found 39 issues worth fixing on advancedradiology.com, 12 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s1.3 sApr 25Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.4 s
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
122 ms90 msApr 25Oct 10116 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202694 ms
May 2, 202696 ms
May 9, 202698 ms
May 16, 2026103 ms
May 23, 2026103 ms
May 30, 2026103 ms
Jun 6, 2026103 ms
Jun 13, 2026102 ms
Jun 20, 2026102 ms
Jun 27, 2026100 ms
Jul 4, 2026100 ms
Jul 11, 2026100 ms
Jul 18, 202699 ms
Jul 25, 202699 ms
Aug 1, 2026103 ms
Aug 8, 2026105 ms
Aug 15, 2026112 ms
Aug 22, 2026115 ms
Aug 29, 2026118 ms
Sep 5, 2026117 ms
Sep 12, 2026118 ms
Sep 19, 2026118 ms
Sep 26, 2026116 ms
Oct 3, 2026117 ms
Oct 10, 2026116 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of advancedradiology.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. advancedradiology.com at 0.4 s0.4 s
  2. advancedradiology.com at 0.8 s0.8 s
  3. advancedradiology.com at 1.1 s1.1 s
  4. advancedradiology.com at 1.5 s1.5 s
  5. advancedradiology.com at 1.9 s1.9 s
  6. advancedradiology.com at 2.3 s2.3 s
  7. advancedradiology.com at 2.6 s2.6 s
  8. advancedradiology.com at 3.0 s3.0 s

Speed

7 to fix56
  • Render-blocking requests

    3.6 s

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

  • Use efficient cache lifetimes

    1.4 s · 408 KiB

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

  • Improve image delivery

    650 ms · 1.2 MB

    26 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    600 ms · 133 KiB

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

  • Reduce unused CSS

    300 ms · 52 KiB

    About 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • site.com adds 14 ms

    14 ms

    site.com costs a phone 14 ms of main-thread work and 732 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (monsido.com, site.com and AddToAny and others), adding 891 KiB and 35 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 103 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • First Contentful Paint: 9.7 s

    9.7 s

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

  • Largest Contentful Paint: 13.9 s

    13.9 s

    Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You deserve more. Put the Power of Artificial Intelligence …”.

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • 25 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 120 ms

    120 ms

    Real visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 542 ms

    542 ms

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

  • Cumulative Layout Shift: 0.022

    0.022

    The layout barely moves while loading (CLS 0.022, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix48
  • 6 images far larger than shown

    513 KiB

    6 images are downloaded at several times the size a phone draws them, for example ADV New Items 3T MRI Quarry Lake (1).png at 1,200 px wide, shown at 165 px. Resized copies would save about 513 KiB.

  • Page weight: 3.2 MB in 81 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 81 requests on a phone: images 1.6 MB (38), scripts 838 KiB (20) and fonts 493 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 15 images below the first screen load straight away

    15 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 9 images in older formats

    9 images (908 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.

  • About 0.9 g of CO₂ per visit

    0.89 g

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

Accessibility

10 to fixGoogle 7186
  • 2 buttons without a name

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

  • Invalid ARIA attributes

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

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

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

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

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

  • 1 link without text

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

  • ARIA role should be appropriate for the element (7 elements)

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7785
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“You deserve more.” and “Advanced Radiology Imaging Center”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 6 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 58 internal links, 18 external

    The homepage links to 58 pages on advancedradiology.com and 18 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Advanced Radiology is Maryland's largest provider of outpatient imaging services. Contact us for MRI, mammography and o…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Advanced Radiology | Maryland Imaging (MRI, Mammography, etc.)”.

  • Canonical URL set

    The canonical URL is https://www.advancedradiology.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.advancedradiology.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (472 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 2 pages without a meta description

    https://www.advancedradiology.com/your-experience-matters and https://www.advancedradiology.com/providers/beyond-radiology have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

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

  • 5 pages without an H1

    https://www.advancedradiology.com/content/contact-us, https://www.advancedradiology.com/for-patients/request-appointment, https://www.advancedradiology.com/for-patients/billing-insurance, https://www.advancedradiology.com/frequently-asked-radiology-questions and https://www.advancedradiology.com/our-services have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://radnetprm.my.site.com/ESWCustomMessagingForInAp1762357821483/assets/styles/bootstr…”.

2 checks passed
  • Tap targets are thumb-sized

    38 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 446 words of copy

    The homepage carries about 446 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SCHEDULE” and “SCHEDULE NOW”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SCHEDULE”, “Request an Appointment” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • No consent tool detected

    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.

  • 8 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at advancedradiology.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on advancedradiology.com, including 13 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25