Tools & Wizards About Us
responsumforpf.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

responsumforpf.com

Responsum for Pulmonary Fibrosis - Responsum Health

Page Load Speed

3.1 sec in total

First Response

59 ms

Resources Loaded

2.9 sec

Page Rendered

101 ms

responsumforpf.com screenshot

About Website

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

Responsum for Pulmonary Fibrosis, or Responsum for PF, is a one-stop-shop for personalized patient information and resources on pulmonary fibrosis.

Visit responsumforpf.com

Key Findings

We analyzed Responsumforpf.com page load time and found that the first response time was 59 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

responsumforpf.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

responsumforpf.com

59 ms

531 ms

jquery.min.js

98 ms

jquery-migrate.min.js

132 ms

1703085798-js0b988595649c49af26174c6a70e07ee03618cd800487f019d2c7f37354438f.js

181 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Responsumforpf.com, 69% (57 requests) were made to Cdn.responsumhealth.com and 4% (3 requests) were made to Cdn.taboola.com. The less responsive or slowest element that took the longest time to load (531 ms) relates to the external source Responsumhealth.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (73%)

Content Size

1.8 MB

After Optimization

478.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Responsumforpf.com main page is 1.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 40.9 kB

  • Original 53.5 kB
  • After minification 53.4 kB
  • After compression 12.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 40.9 kB or 76% of the original size.

JavaScript Optimization

-42%

Potential reduce by 243.6 kB

  • Original 574.7 kB
  • After minification 567.4 kB
  • After compression 331.1 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 243.6 kB or 42% of the original size.

CSS Optimization

-88%

Potential reduce by 995.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 134.7 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. Responsumforpf.com needs all CSS files to be minified and compressed as it can save up to 995.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (81%)

Requests Now

62

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

responsumforpf.com

responsumforpf.com

59 ms

531 ms

jquery.min.js

jquery.min.js

98 ms

jquery-migrate.min.js

jquery-migrate.min.js

132 ms

1703085798-js0b988595649c49af26174c6a70e07ee03618cd800487f019d2c7f37354438f.js

1703085798-js0b988595649c49af26174c6a70e07ee03618cd800487f019d2c7f37354438f.js

181 ms

1703085798-js9b5ad06bb900124edda277431b3f6798209e051c2ab6040e972d3ce3e30eb7.js

1703085798-js9b5ad06bb900124edda277431b3f6798209e051c2ab6040e972d3ce3e30eb7.js

156 ms

rh-critical.css

rh-critical.css

156 ms

style.min.css

style.min.css

166 ms

classic-themes.min.css

classic-themes.min.css

161 ms

rh-fonts.css

rh-fonts.css

146 ms

style.css

style.css

197 ms

js_composer.min.css

js_composer.min.css

247 ms

833a60f0393f6b9ee8ff4420ebc29e37.css

833a60f0393f6b9ee8ff4420ebc29e37.css

198 ms

ad01ceb476bc87de8488ec3f7e31e00b.css

ad01ceb476bc87de8488ec3f7e31e00b.css

198 ms

icon-custom.css

icon-custom.css

219 ms

font-awesome.min.css

font-awesome.min.css

226 ms

bootstrap.css

bootstrap.css

269 ms

7dd21e4313bbbcf70a5a791a791bc99b.css

7dd21e4313bbbcf70a5a791a791bc99b.css

237 ms

custom_script.css

custom_script.css

231 ms

waypoint.js

waypoint.js

262 ms

jquery.cookie.js

jquery.cookie.js

263 ms

jquery.typer.js

jquery.typer.js

265 ms

gtm.js

gtm.js

70 ms

amazonpolly-public.css

amazonpolly-public.css

326 ms

styles.css

styles.css

260 ms

index.js

index.js

263 ms

index.js

index.js

327 ms

main.js

main.js

327 ms

myscript.js

myscript.js

325 ms

api.js

api.js

39 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

328 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

329 ms

wp-polyfill.min.js

wp-polyfill.min.js

325 ms

index.js

index.js

329 ms

imagesloaded.min.js

imagesloaded.min.js

328 ms

js_composer_front.min.js

js_composer_front.min.js

381 ms

RH-logo-new-website.jpg.webp

RH-logo-new-website.jpg.webp

94 ms

Responsum-Health-Logo.png.webp

Responsum-Health-Logo.png.webp

42 ms

bg-header.jpg.webp

bg-header.jpg.webp

41 ms

pf-banner.png.webp

pf-banner.png.webp

94 ms

pf-just-diagnosed.png.webp

pf-just-diagnosed.png.webp

95 ms

pf-stages.png.webp

pf-stages.png.webp

95 ms

pf-prognosis.png.webp

pf-prognosis.png.webp

93 ms

Lato-Regular.woff

Lato-Regular.woff

52 ms

Lato-Light.woff

Lato-Light.woff

50 ms

Lato-Bold.woff

Lato-Bold.woff

104 ms

Lato-Black.woff

Lato-Black.woff

103 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

105 ms

Lora-Bold.woff

Lora-Bold.woff

149 ms

Lora-Medium.woff

Lora-Medium.woff

102 ms

Lora-Regular.woff

Lora-Regular.woff

104 ms

Montserrat-Regular.woff

Montserrat-Regular.woff

188 ms

Montserrat-Medium.woff

Montserrat-Medium.woff

189 ms

Montserrat-Light.woff

Montserrat-Light.woff

211 ms

Montserrat-ExtraLight.woff

Montserrat-ExtraLight.woff

148 ms

Montserrat-Thin.woff

Montserrat-Thin.woff

228 ms

Montserrat-SemiBold.woff

Montserrat-SemiBold.woff

287 ms

Montserrat-Bold.woff

Montserrat-Bold.woff

286 ms

Montserrat-ExtraBold.woff

Montserrat-ExtraBold.woff

309 ms

Montserrat-Black.woff

Montserrat-Black.woff

309 ms

icon.ttf

icon.ttf

465 ms

hotjar-1758019.js

hotjar-1758019.js

151 ms

uwt.js

uwt.js

207 ms

insight.min.js

insight.min.js

146 ms

tfa.js

tfa.js

227 ms

fbevents.js

fbevents.js

220 ms

recaptcha__en.js

recaptcha__en.js

303 ms

js

js

102 ms

analytics.js

analytics.js

165 ms

insight_tag_errors.gif

insight_tag_errors.gif

388 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

225 ms

insight_tag_errors.gif

insight_tag_errors.gif

463 ms

json

json

149 ms

collect

collect

60 ms

collect

collect

55 ms

adsct

adsct

183 ms

adsct

adsct

254 ms

adsct

adsct

193 ms

adsct

adsct

104 ms

cds-pips.js

cds-pips.js

3 ms

eid.es5.js

eid.es5.js

14 ms

pips.taboola.com

pips.taboola.com

22 ms

ga-audiences

ga-audiences

25 ms

Accessibility Review

responsumforpf.com accessibility score

66

Accessibility Issues

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

SEO Factors

responsumforpf.com SEO score

76

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

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

responsumforpf.com

Open Graph data is detected on the main page of Responsum Forpf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: