Tools & Wizards About Us
flo.health screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

flo.health

Period tracker, ovulation tracker, pregnancy app | Flo

Page Load Speed

1 sec in total

First Response

46 ms

Resources Loaded

495 ms

Page Rendered

504 ms

flo.health screenshot

About Website

Click here to check amazing Flo content for United States. Otherwise, check out these important facts you probably never knew about flo.health

Track your periods, ovulation, and pregnancy with the Flo app. Log your cycle symptoms so you can understand your body better.

Visit flo.health

Key Findings

We analyzed Flo.health page load time and found that the first response time was 46 ms and then it took 999 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

flo.health performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

flo.health

46 ms

flo.health

87 ms

flo.svg

35 ms

rocket-loader.min.js

24 ms

10270-9153-Frame%2029434.png

48 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 97% of them (33 requests) were addressed to the original Flo.health, 3% (1 request) were made to Tr.flo.health. The less responsive or slowest element that took the longest time to load (205 ms) relates to the external source Tr.flo.health.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

567.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Flo.health main page is 1.5 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. 30% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 962.0 kB

  • Original 1.2 MB
  • After minification 994.9 kB
  • After compression 277.9 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 245.0 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 962.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 149.6 kB
  • After minification 148.0 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. Flo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 76 B

  • Original 141.6 kB
  • After minification 141.6 kB
  • After compression 141.6 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.

Requests Breakdown

Number of requests can be reduced by 18 (64%)

Requests Now

28

After Optimization

10

  • Images
  • JavaScript

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

Network Requests Diagram

flo.health

flo.health

46 ms

flo.health

flo.health

87 ms

flo.svg

flo.svg

35 ms

rocket-loader.min.js

rocket-loader.min.js

24 ms

10270-9153-Frame%2029434.png

10270-9153-Frame%2029434.png

48 ms

app-store.svg

app-store.svg

46 ms

google-play.svg

google-play.svg

72 ms

8977-track-mobile-223x454.png

8977-track-mobile-223x454.png

48 ms

8750-ttc-mobile-223x454.png

8750-ttc-mobile-223x454.png

68 ms

8749-pregnancy-mobile-223x454.png

8749-pregnancy-mobile-223x454.png

77 ms

7669-icon-accurate-predictions.svg

7669-icon-accurate-predictions.svg

83 ms

7671-icon-medical-credibility.svg

7671-icon-medical-credibility.svg

85 ms

7670-icon-privacy.svg

7670-icon-privacy.svg

83 ms

7675-xn9pq8it_qr_code.png

7675-xn9pq8it_qr_code.png

98 ms

footer-fem-logo.svg

footer-fem-logo.svg

97 ms

downloadapp-btn.js

downloadapp-btn.js

101 ms

allPolyfill.js

allPolyfill.js

116 ms

sentry.js

sentry.js

109 ms

lazyLoadGeneral.js

lazyLoadGeneral.js

112 ms

black_linkedin.svg

black_linkedin.svg

114 ms

black_twitter.svg

black_twitter.svg

132 ms

black_tiktok.svg

black_tiktok.svg

131 ms

black_facebook.svg

black_facebook.svg

132 ms

black_instagram.svg

black_instagram.svg

136 ms

initialize.js

initialize.js

116 ms

gtm.js

gtm.js

205 ms

7676-img_yt.jpg

7676-img_yt.jpg

37 ms

10652-perimenopause-weight-gain-flo-01_1006x755.jpg

10652-perimenopause-weight-gain-flo-01_1006x755.jpg

42 ms

10651-ovulation-without-a-period-flo-01_1006x755.jpg

10651-ovulation-without-a-period-flo-01_1006x755.jpg

143 ms

10646-can%20ovulation%20make%20you%20tired.jpg

10646-can%20ovulation%20make%20you%20tired.jpg

37 ms

roboto-bold.e3bb53ba.woff

roboto-bold.e3bb53ba.woff

20 ms

roboto-black.ecb4af06.woff

roboto-black.ecb4af06.woff

50 ms

roboto-medium.a1ef02df.woff

roboto-medium.a1ef02df.woff

49 ms

roboto-regular.b685fa1c.woff

roboto-regular.b685fa1c.woff

23 ms

Accessibility Review

flo.health accessibility score

95

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

Best Practices

flo.health 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

flo.health SEO score

100

Search Engine Optimization Advices

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 Flo.health 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 Flo.health 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

flo.health

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