Website review, no card needed
universityradiology.com website review
Visit site (opens in a new tab)Reviewed 28 October 202649 issues · 91 checks
This review found 49 issues worth fixing on universityradiology.com, 20 of them high impact, across 91 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 89 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 92 ms |
| Jun 6, 2026 | 93 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 97 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 98 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 98 ms |
| Oct 24, 2026 | 97 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
22.2 s · 15.1 MB59 files are served with short cache lifetimes, so returning visitors download them again (15.1 MB).
Render-blocking requests
22.2 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 22.2 s.
Reduce unused JavaScript
12.4 s · 2.4 MBAbout 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.4 s faster on a phone.
Minify JavaScript
7.5 s · 1.5 MB1.5 MB could be saved by minifying JavaScript.
Reduce unused CSS
1.6 s · 301 KiBAbout 301 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
800 ms · 219 KiB10 images could be 219 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 941 KiB and 638 ms of main-thread time.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Google Tag Manager adds 423 ms
423 msGoogle Tag Manager costs a phone 423 ms of main-thread work and 629 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 185 ms. During a long task the page ignores taps.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 697 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
First Contentful Paint: 22.0 s
22.0 sThe first text or image appears after 22.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 30.3 s
30.3 sYour largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “University Radiology”.
Speed Index: 22.0 s
22.0 sVisually, the page fills in at 22.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 30.3 s
30.3 sThe page becomes fully interactive after 30.3 s. Good is under 3.8 s.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.139
0.139The layout shifts by 0.139 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 89 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 385 ms
385 msReal visitors wait 385 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 103 ms
103 msScripts block the page for only 103 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.8 MB in 80 requests
15.8 MBYour homepage downloads 15.8 MB in 80 requests on a phone: images 11.0 MB (41), scripts 4.0 MB (21) and fonts 532 KiB (5). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.
19 images in older formats
19 images (10.9 MB) 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.
1 image below the first screen load straight away
1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.5 g of CO₂ per visit
4.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.49 g of CO₂e: 538.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Active <area> elements must have alternative text (6 elements)
Active <area> elements must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.
15 tap targets too small
15 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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
39 images without alt text
39 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
26 links without text
26 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (343 characters)
Your meta description is 343 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
214 internal links, 52 external
The homepage links to 214 pages on universityradiology.com and 52 external pages.
3 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “University Radiology | NJ Imaging Center & Diagnostic Radiology”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.universityradiology.com/sitemap.xml.
AI search readiness
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.universityradiology.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 (624 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
/ and https://www.universityradiology.com/heartflow_analysis all use the title “University Radiology | NJ Imaging Center & Diagnostic Radiology”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://www.universityradiology.com/directory, https://www.universityradiology.com/prep, https://www.universityradiology.com/reports_and_images, https://www.universityradiology.com/preauth, https://www.universityradiology.com/heartflow_analysis and https://www.universityradiology.com/body_composition_dxa use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.universityradiology.com/walk-in-hours, https://www.universityradiology.com/directory, https://www.universityradiology.com/locations, https://www.universityradiology.com/prep, https://www.universityradiology.com/insurance and https://www.universityradiology.com/reports_and_images and 9 others 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 77 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
103 small tap targets
103 of 182 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.universityradiology.com/stylesheets/slick-theme.min.css' because its MIME type…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 422 words of copy
The homepage carries about 422 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “SCHEDULE YOUR VISIT >”.
5 calls to action
The homepage has 5 calls to action, for example “SCHEDULE YOUR VISIT >”, “Contact” and “CONTACT”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Xandr (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 universityradiology.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Comcast
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on universityradiology.com, including 19 speed issues, 6 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.