Tools & Wizards About Us
isoray.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

isoray.com

Brachytherapy Inquiries – Theragenics

Page Load Speed

1.6 sec in total

First Response

53 ms

Resources Loaded

1.2 sec

Page Rendered

374 ms

isoray.com screenshot

About Website

Visit isoray.com now to see the best up-to-date Isoray content and also check out these interesting facts you probably never knew about isoray.com

Visit isoray.com

Key Findings

We analyzed Isoray.com page load time and found that the first response time was 53 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

isoray.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value3,690 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

isoray.com

53 ms

66 ms

137 ms

elegant-icons.min.css

34 ms

all.min.css

91 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Isoray.com, 82% (86 requests) were made to Theragenics.com and 10% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (586 ms) relates to the external source Marity.qodeinteractive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.1 kB (11%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Isoray.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 722.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 125.3 kB

  • Original 154.0 kB
  • After minification 150.3 kB
  • After compression 28.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 125.3 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 53.7 kB

  • Original 722.6 kB
  • After minification 668.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Isoray images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 8.3 kB

  • Original 635.7 kB
  • After minification 635.7 kB
  • After compression 627.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 6.8 kB

  • Original 192.9 kB
  • After minification 192.6 kB
  • After compression 186.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Isoray.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (87%)

Requests Now

84

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Isoray. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

isoray.com

isoray.com

53 ms

66 ms

137 ms

elegant-icons.min.css

elegant-icons.min.css

34 ms

all.min.css

all.min.css

91 ms

styles.css

styles.css

76 ms

grid.min.css

grid.min.css

78 ms

helper-parts.min.css

helper-parts.min.css

82 ms

main.min.css

main.min.css

112 ms

swiper.min.css

swiper.min.css

100 ms

main.min.css

main.min.css

136 ms

marity-core.min.css

marity-core.min.css

153 ms

css

css

60 ms

style.css

style.css

135 ms

elementor.min.css

elementor.min.css

132 ms

elementor-icons.min.css

elementor-icons.min.css

129 ms

frontend-lite.min.css

frontend-lite.min.css

177 ms

post-6.css

post-6.css

170 ms

frontend-lite.min.css

frontend-lite.min.css

171 ms

global.css

global.css

172 ms

post-16340.css

post-16340.css

173 ms

post-17981.css

post-17981.css

186 ms

css

css

58 ms

fontawesome.min.css

fontawesome.min.css

187 ms

solid.min.css

solid.min.css

192 ms

script.min.js

script.min.js

206 ms

jquery.min.js

jquery.min.js

210 ms

jquery-migrate.min.js

jquery-migrate.min.js

208 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

207 ms

add-to-cart.min.js

add-to-cart.min.js

208 ms

js.cookie.min.js

js.cookie.min.js

208 ms

woocommerce.min.js

woocommerce.min.js

248 ms

select2.full.min.js

select2.full.min.js

505 ms

js

js

99 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

246 ms

wc-blocks.css

wc-blocks.css

499 ms

brands.min.css

brands.min.css

498 ms

regular.min.css

regular.min.css

500 ms

animations.min.css

animations.min.css

499 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

503 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

502 ms

js

js

117 ms

api.js

api.js

63 ms

wp-polyfill.min.js

wp-polyfill.min.js

502 ms

hooks.min.js

hooks.min.js

486 ms

i18n.min.js

i18n.min.js

443 ms

index.js

index.js

441 ms

index.js

index.js

439 ms

core.min.js

core.min.js

424 ms

main.min.js

main.min.js

422 ms

gsap.min.js

gsap.min.js

448 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

392 ms

hoverIntent.min.js

hoverIntent.min.js

390 ms

modernizr.js

modernizr.js

373 ms

jquery.parallax-scroll.js

jquery.parallax-scroll.js

374 ms

particles.min.js

particles.min.js

405 ms

main.min.js

main.min.js

405 ms

underscore.min.js

underscore.min.js

402 ms

custom-marker.js

custom-marker.js

400 ms

markerclusterer.js

markerclusterer.js

400 ms

google-map.js

google-map.js

424 ms

marity-core.min.js

marity-core.min.js

420 ms

swiper.min.js

swiper.min.js

425 ms

MorphSVGPlugin.min.js

MorphSVGPlugin.min.js

404 ms

sourcebuster.min.js

sourcebuster.min.js

404 ms

order-attribution.min.js

order-attribution.min.js

402 ms

index.js

index.js

427 ms

MotionPathPlugin.min.js

MotionPathPlugin.min.js

426 ms

en.png

en.png

586 ms

webpack.runtime.min.js

webpack.runtime.min.js

388 ms

frontend-modules.min.js

frontend-modules.min.js

438 ms

waypoints.min.js

waypoints.min.js

348 ms

xMQOuFFYT72X5wkB_18qmnndmSdSnk-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmSdSnk-DKQc.ttf

318 ms

xMQOuFFYT72X5wkB_18qmnndmSdgnk-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmSdgnk-DKQc.ttf

375 ms

xMQOuFFYT72X5wkB_18qmnndmScMnk-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmScMnk-DKQc.ttf

375 ms

xMQOuFFYT72X5wkB_18qmnndmSeMmU-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmSeMmU-DKQc.ttf

376 ms

xMQOuFFYT72X5wkB_18qmnndmSe1mU-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmSe1mU-DKQc.ttf

501 ms

xMQOuFFYT72X5wkB_18qmnndmSfSmU-DKQc.ttf

xMQOuFFYT72X5wkB_18qmnndmSfSmU-DKQc.ttf

375 ms

frontend.min.js

frontend.min.js

368 ms

elementor.js

elementor.js

187 ms

elementor.min.js

elementor.min.js

184 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

184 ms

frontend.min.js

frontend.min.js

182 ms

elements-handlers.min.js

elements-handlers.min.js

273 ms

home-3-rev-img-3a-blue.png

home-3-rev-img-3a-blue.png

314 ms

theragenics-logo-198x40-1.png

theragenics-logo-198x40-1.png

270 ms

theragenics-blue.png

theragenics-blue.png

268 ms

brachytherapy-page-bg-test1.png

brachytherapy-page-bg-test1.png

315 ms

landing-blog-bg-img.png

landing-blog-bg-img.png

267 ms

brachy-contact-pic1.jpg

brachy-contact-pic1.jpg

375 ms

theragenics-logo-white.png

theragenics-logo-white.png

308 ms

309 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

258 ms

fa-regular-400.ttf

fa-regular-400.ttf

261 ms

fa-brands-400.ttf

fa-brands-400.ttf

325 ms

fa-solid-900.ttf

fa-solid-900.ttf

322 ms

ElegantIcons.woff

ElegantIcons.woff

321 ms

LDI2apCSOBg7S-QT7pa8FvOleeI.ttf

LDI2apCSOBg7S-QT7pa8FvOleeI.ttf

73 ms

LDI2apCSOBg7S-QT7pbYF_OleeI.ttf

LDI2apCSOBg7S-QT7pbYF_OleeI.ttf

89 ms

LDI2apCSOBg7S-QT7pb0EPOleeI.ttf

LDI2apCSOBg7S-QT7pb0EPOleeI.ttf

90 ms

LDIxapCSOBg7S-QT7p4JM-M.ttf

LDIxapCSOBg7S-QT7p4JM-M.ttf

90 ms

LDI2apCSOBg7S-QT7pasEfOleeI.ttf

LDI2apCSOBg7S-QT7pasEfOleeI.ttf

120 ms

fa-solid-900.woff

fa-solid-900.woff

319 ms

fa-brands-400.woff

fa-brands-400.woff

281 ms

recaptcha__en.js

recaptcha__en.js

64 ms

Accessibility Review

isoray.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

isoray.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

isoray.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Isoray.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Isoray.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

isoray.com

Open Graph description is not detected on the main page of Isoray. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: