Website review, no card needed

radsource.com logo

radsource.com website review

Visit site (opens in a new tab)Reviewed 23 October 202644 issues · 92 checks

This review found 44 issues worth fixing on radsource.com, 18 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
5.1 s3.2 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.9 s
May 9, 20263.9 s
May 16, 20264.3 s
May 23, 20264.4 s
May 30, 20264.0 s
Jun 6, 20263.7 s
Jun 13, 20263.5 s
Jun 20, 20263.4 s
Jun 27, 20264.2 s
Jul 4, 20264.7 s
Jul 11, 20264.7 s
Jul 18, 20264.9 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.7 s
Aug 15, 20264.7 s
Aug 22, 20264.7 s
Aug 29, 20264.7 s
Sep 5, 20264.4 s
Sep 12, 20264.5 s
Sep 19, 20264.1 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
114 ms85 msMay 2Oct 17104 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202692 ms
May 9, 202694 ms
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026107 ms
Jun 6, 2026110 ms
Jun 13, 2026101 ms
Jun 20, 2026100 ms
Jun 27, 2026100 ms
Jul 4, 202688 ms
Jul 11, 202690 ms
Jul 18, 202699 ms
Jul 25, 2026108 ms
Aug 1, 2026111 ms
Aug 8, 2026106 ms
Aug 15, 202696 ms
Aug 22, 202695 ms
Aug 29, 2026104 ms
Sep 5, 2026102 ms
Sep 12, 2026102 ms
Sep 19, 202699 ms
Sep 26, 202695 ms
Oct 3, 202691 ms
Oct 10, 202698 ms
Oct 17, 2026104 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 radsource.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix43
  • Reduce unused JavaScript

    3.8 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Use efficient cache lifetimes

    1.1 s · 381 KiB

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

  • Mobile performance score: 43

    43/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.7 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 811 ms

    811 ms

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

  • Reduce unused CSS

    750 ms · 134 KiB

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

  • Legacy JavaScript

    400 ms · 34 KiB

    Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • Improve image delivery

    418 KiB

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

  • Main-thread work: 3.2 s

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

  • 16 long tasks on the main thread

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

  • Font display

    100 ms

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

  • 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.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 44 ms

    44 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 19.0 s

    19.0 s

    Your largest element takes 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A New Day In X-Ray View Research Citations Solutions Custom…”.

  • Time to Interactive: 24.3 s

    24.3 s

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

  • First Contentful Paint: 7.1 s

    7.1 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Total Blocking Time: 546 ms

    546 ms

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

  • Tap response (INP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 159 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 159 requests on a phone: scripts 2.1 MB (52), images 1,011 KiB (38) and fonts 350 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    106 KiB

    1 image is downloaded at several times the size a phone draws it, for example RS-2000-Q2-Transparent-web.png at 845 px wide, shown at 166 px. Resized copies would save about 106 KiB.

  • 4 images in older formats

    4 images (473 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 1.1 g of CO₂ per visit

    1.06 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7387
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 16 tap targets too small

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

  • 14 text elements with low contrast

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

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 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.

  • Zoom is disabled

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

  • 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.

  • 4 links without text

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

4 to fixGoogle 8586
  • 3 H1 headlines

    There are 3 <h1> headlines (“Useful Industry Links”, “Literature & References” and “Biological IrradiatorsDesigned for Life Science™”). One clear main headline is easier for people and search engines.

  • Meta description is long (193 characters)

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

  • 9 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 90 internal links, 6 external

    The homepage links to 90 pages on radsource.com and 6 external pages.

6 checks passed
  • Title: 57 characters

    Your title is a healthy 57 characters: “Rad Source Technologies | X-Ray Designed for Life Science”.

  • Canonical URL set

    The canonical URL is https://radsource.com/.

  • Structured data in place

    Structured data found: ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://radsource.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 (1,369 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix76
  • 2 pages point its canonical at the homepage

    https://radsource.com/difference-us-uv-blood-irradiation and https://radsource.com/our-clients declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 3 pages share a title

    /, https://radsource.com/difference-us-uv-blood-irradiation and https://radsource.com/our-clients all use the title “Rad Source Technologies | X-Ray Designed for Life Science”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://radsource.com/solutions, https://radsource.com/solutions/blood-irradiation, https://radsource.com/solutions/small-animal-research, https://radsource.com/solutions/cell-research, https://radsource.com/solutions/cannabis-decontamination and https://radsource.com/solutions/sterile-insect-technique-sit and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://radsource.com/difference-us-uv-blood-irradiation and https://radsource.com/our-clients use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://radsource.com/products/rs-2000-small-animal-irradiator, https://radsource.com/products/rs-2400-irradiator and https://radsource.com/products/rs-3400-blood-irradiator took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9678
  • 1 broken image

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

  • 2 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 558 words of copy

    The homepage carries about 558 words of visible text.

5 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact”, “Learn More >” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 13 cookies set on arrival

    13

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

  • 36 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 radsource.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on radsource.com, including 19 speed issues, 4 SEO issues and 3 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