Tools & Wizards About Us

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

radiesse-voice.com

PROLARYN® GEL and PROLARYN® PLUS for Vocal Fold Insufficiency

Page Load Speed

588 ms in total

First Response

125 ms

Resources Loaded

351 ms

Page Rendered

112 ms

About Website

Visit radiesse-voice.com now to see the best up-to-date Radiesse Voice content for United States and also check out these interesting facts you probably never knew about radiesse-voice.com

Learn more about PROLARYN® GEL (injectable implant) and PROLARYN® PLUS (injectable implant), used to treat vocal fold insufficiency.

Visit radiesse-voice.com

Key Findings

We analyzed Radiesse-voice.com page load time and found that the first response time was 125 ms and then it took 463 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

radiesse-voice.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

www.prolaryn.com

125 ms

css

34 ms

vendor.min.css

19 ms

prolaryn.min.css

32 ms

vendor.min.js

44 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Radiesse-voice.com, 14% (2 requests) were made to Google-analytics.com and 14% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (125 ms) relates to the external source Prolaryn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.4 kB (63%)

Content Size

395.2 kB

After Optimization

144.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Radiesse-voice.com main page is 395.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 195.3 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 13.7 kB

  • Original 20.1 kB
  • After minification 17.3 kB
  • After compression 6.4 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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.7 kB or 68% of the original size.

Image Optimization

-12%

Potential reduce by 4.3 kB

  • Original 35.8 kB
  • After minification 31.5 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. Obviously, Radiesse Voice needs image optimization as it can save up to 4.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 112.3 kB

  • Original 195.3 kB
  • After minification 195.3 kB
  • After compression 83.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.3 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 120.1 kB

  • Original 144.0 kB
  • After minification 144.0 kB
  • After compression 24.0 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. Radiesse-voice.com needs all CSS files to be minified and compressed as it can save up to 120.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (27%)

Requests Now

11

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

radiesse-voice.com accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

Best Practices

radiesse-voice.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

radiesse-voice.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Radiesse-voice.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Radiesse-voice.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

Open Graph description is not detected on the main page of Radiesse Voice. 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: