Tools & Wizards About Us
prolaryn.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% 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

prolaryn.com

PROLARYN® GEL and PROLARYN® PLUS for Vocal Fold Insufficiency

Page Load Speed

574 ms in total

First Response

22 ms

Resources Loaded

275 ms

Page Rendered

277 ms

prolaryn.com screenshot

About Website

Welcome to prolaryn.com homepage info - get ready to check PROLARYN best content right away, or after learning these important things about prolaryn.com

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

Visit prolaryn.com

Key Findings

We analyzed Prolaryn.com page load time and found that the first response time was 22 ms and then it took 552 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

prolaryn.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

prolaryn.com

22 ms

otSDKStub.js

39 ms

css2

45 ms

css2

61 ms

main.css

13 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 50% of them (15 requests) were addressed to the original Prolaryn.com, 30% (9 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (154 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.2 kB (53%)

Content Size

439.3 kB

After Optimization

205.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prolaryn.com main page is 439.3 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. 60% of websites need less resources to load. Javascripts take 175.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 48.4 kB

  • Original 56.0 kB
  • After minification 44.5 kB
  • After compression 7.6 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 11.4 kB, which is 20% 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 48.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 119.5 kB
  • After minification 119.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. PROLARYN images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 112.4 kB

  • Original 175.1 kB
  • After minification 175.1 kB
  • After compression 62.7 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.4 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 73.3 kB

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

Requests Breakdown

Number of requests can be reduced by 4 (20%)

Requests Now

20

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prolaryn.com

prolaryn.com

22 ms

otSDKStub.js

otSDKStub.js

39 ms

css2

css2

45 ms

css2

css2

61 ms

main.css

main.css

13 ms

js

js

154 ms

main.js

main.js

21 ms

8853c393-b997-477c-8a6e-ac41977d10ab.json

8853c393-b997-477c-8a6e-ac41977d10ab.json

114 ms

gtm.js

gtm.js

140 ms

icon-arrow-right.svg

icon-arrow-right.svg

87 ms

icon-circle-close-blue.svg

icon-circle-close-blue.svg

91 ms

prolaryn-gel.svg

prolaryn-gel.svg

89 ms

prolaryn-plus.svg

prolaryn-plus.svg

91 ms

icon-menu.svg

icon-menu.svg

93 ms

doctor-patient.png

doctor-patient.png

98 ms

what-does.png

what-does.png

98 ms

who-is.png

who-is.png

103 ms

icon-arrow-up-blue.svg

icon-arrow-up-blue.svg

99 ms

prolaryn-gel-white.svg

prolaryn-gel-white.svg

101 ms

prolaryn-plus-white.svg

prolaryn-plus-white.svg

103 ms

merz-white.svg

merz-white.svg

100 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

63 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

66 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

65 ms

Accessibility Review

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

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prolaryn.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 Prolaryn.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

prolaryn.com

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