Tools & Wizards About Us
follistim.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

follistim.com

FOLLISTIM® AQ Cartridge (follitropin beta injection) ǀ Official Site

Page Load Speed

1.4 sec in total

First Response

64 ms

Resources Loaded

726 ms

Page Rendered

658 ms

follistim.com screenshot

About Website

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

Patients can learn more about FOLLISTIM® AQ Cartridge (follitropin beta injection). Talk to your doctor to see if FOLLISTIM may be right for you.

Visit follistim.com

Key Findings

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

Performance Metrics

follistim.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

follistim.com

64 ms

follistim.com

16 ms

www.follistim.com

262 ms

gtm.js

202 ms

otSDKStub.js

48 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 80% of them (35 requests) were addressed to the original Follistim.com, 14% (6 requests) were made to Cdn.cookielaw.org and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (292 ms) belongs to the original domain Follistim.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 379.1 kB (29%)

Content Size

1.3 MB

After Optimization

909.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Follistim.com main page is 1.3 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. 80% 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. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-33%

Potential reduce by 378.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 774.2 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 378.9 kB or 33% of the original size.

JavaScript Optimization

-0%

Potential reduce by 57 B

  • Original 130.8 kB
  • After minification 130.8 kB
  • After compression 130.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 72 B

  • Original 4.5 kB
  • After minification 4.5 kB
  • After compression 4.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. Follistim.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

37

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

follistim.com

follistim.com

64 ms

follistim.com

follistim.com

16 ms

www.follistim.com

www.follistim.com

262 ms

gtm.js

gtm.js

202 ms

otSDKStub.js

otSDKStub.js

48 ms

fb76919e-9379-4a18-8697-3285f4cdc8de.css

fb76919e-9379-4a18-8697-3285f4cdc8de.css

130 ms

684d5a9ec2edd504.css

684d5a9ec2edd504.css

124 ms

4c87c9160699a9fe.css

4c87c9160699a9fe.css

126 ms

a7e4c9c705b8110e.css

a7e4c9c705b8110e.css

131 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

133 ms

webpack-baf1955396c18d30.js

webpack-baf1955396c18d30.js

132 ms

framework-2c79e2a64abdb08b.js

framework-2c79e2a64abdb08b.js

215 ms

main-953152719f4c64fe.js

main-953152719f4c64fe.js

289 ms

_app-69a9c1ba4a00849a.js

_app-69a9c1ba4a00849a.js

201 ms

586-7d0c1f7c4465a06a.js

586-7d0c1f7c4465a06a.js

201 ms

84-1338b056a9d2aef5.js

84-1338b056a9d2aef5.js

214 ms

374-171873db3cb58a77.js

374-171873db3cb58a77.js

222 ms

index-f996ea723fe2b0f0.js

index-f996ea723fe2b0f0.js

292 ms

_buildManifest.js

_buildManifest.js

261 ms

_ssgManifest.js

_ssgManifest.js

261 ms

d5f3d6b1-933b-4e46-ad63-b42fd51cf136.json

d5f3d6b1-933b-4e46-ad63-b42fd51cf136.json

148 ms

follistim_logo.svg

follistim_logo.svg

153 ms

follistim-pen-hero.82661727.webp

follistim-pen-hero.82661727.webp

158 ms

follistim-pen-hero-mobile.1a058574.webp

follistim-pen-hero-mobile.1a058574.webp

157 ms

follistim-pen-vertical.114511b2.webp

follistim-pen-vertical.114511b2.webp

179 ms

follistim-pen-DS-small.b6dc2245.webp

follistim-pen-DS-small.b6dc2245.webp

175 ms

cartridges.d9cc5c42.webp

cartridges.d9cc5c42.webp

169 ms

follistim-device.1488296f.webp

follistim-device.1488296f.webp

170 ms

follistim-device-mobile.7eb6d73b.webp

follistim-device-mobile.7eb6d73b.webp

179 ms

designed-pen-mobile.8a71d4c3.webp

designed-pen-mobile.8a71d4c3.webp

106 ms

white-logo-follistim.webp

white-logo-follistim.webp

107 ms

organon-logo.svg

organon-logo.svg

106 ms

seal.svg

seal.svg

161 ms

essential-accessibility-icon.svg

essential-accessibility-icon.svg

163 ms

otBannerSdk.js

otBannerSdk.js

92 ms

feature-blob.webp

feature-blob.webp

93 ms

gtm.js

gtm.js

60 ms

en.json

en.json

26 ms

AvenirNextRegular_normal_normal.woff

AvenirNextRegular_normal_normal.woff

75 ms

AvenirNextBold_normal_normal.woff

AvenirNextBold_normal_normal.woff

151 ms

FSNerudaBlack_normal_normal.woff

FSNerudaBlack_normal_normal.woff

75 ms

FSNerudaBold_normal_normal.woff

FSNerudaBold_normal_normal.woff

75 ms

otFloatingFlat.json

otFloatingFlat.json

20 ms

otCommonStyles.css

otCommonStyles.css

23 ms

Accessibility Review

follistim.com accessibility score

97

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

follistim.com SEO score

92

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

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

follistim.com

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