Tools & Wizards About Us
amp.flo.health screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

amp.flo.health

Flo - ovulation calendar, period tracker, and pregnancy app

Page Load Speed

984 ms in total

First Response

106 ms

Resources Loaded

355 ms

Page Rendered

523 ms

amp.flo.health screenshot

About Website

Welcome to amp.flo.health homepage info - get ready to check Amp Flo best content for United States right away, or after learning these important things about amp.flo.health

At Flo, we aim to improve the health and wellbeing of every girl, woman, and person who menstruates worldwide.

Visit amp.flo.health

Key Findings

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

Performance Metrics

amp.flo.health performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

flo.health

106 ms

8977-track-mobile-223x454.png

25 ms

8750-ttc-mobile-223x454.png

40 ms

8749-pregnancy-mobile-223x454.png

51 ms

7669-icon-accurate-predictions.svg

55 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 648.4 kB (57%)

Content Size

1.1 MB

After Optimization

495.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Amp.flo.health main page is 1.1 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. 40% of websites need less resources to load. HTML takes 832.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 614.1 kB

  • Original 832.7 kB
  • After minification 778.6 kB
  • After compression 218.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. 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 614.1 kB or 74% of the original size.

Image Optimization

-13%

Potential reduce by 34.3 kB

  • Original 266.3 kB
  • After minification 232.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. Obviously, Amp Flo needs image optimization as it can save up to 34.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 12 B

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

Requests Breakdown

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

Requests Now

17

After Optimization

14

  • Images
  • JavaScript

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amp 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 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

flo.health

flo.health

106 ms

8977-track-mobile-223x454.png

8977-track-mobile-223x454.png

25 ms

8750-ttc-mobile-223x454.png

8750-ttc-mobile-223x454.png

40 ms

8749-pregnancy-mobile-223x454.png

8749-pregnancy-mobile-223x454.png

51 ms

7669-icon-accurate-predictions.svg

7669-icon-accurate-predictions.svg

55 ms

7671-icon-medical-credibility.svg

7671-icon-medical-credibility.svg

31 ms

7670-icon-privacy.svg

7670-icon-privacy.svg

52 ms

7676-img_yt.jpg

7676-img_yt.jpg

46 ms

7675-xn9pq8it_qr_code.png

7675-xn9pq8it_qr_code.png

48 ms

9854-01_1006x755.jpg

9854-01_1006x755.jpg

68 ms

9838-Woman%20looking%20in%20the%20mirror%2001_1006x755.jpg

9838-Woman%20looking%20in%20the%20mirror%2001_1006x755.jpg

64 ms

9749-11%20DPO%20on%20a%20menstrual%20cycle1006x755.jpg

9749-11%20DPO%20on%20a%20menstrual%20cycle1006x755.jpg

80 ms

app-store.svg

app-store.svg

70 ms

google-play.svg

google-play.svg

68 ms

rocket-loader.min.js

rocket-loader.min.js

54 ms

gtm.js

gtm.js

110 ms

allPolyfill.js

allPolyfill.js

59 ms

roboto-regular.b685fa1c.woff

roboto-regular.b685fa1c.woff

51 ms

roboto-medium.a1ef02df.woff

roboto-medium.a1ef02df.woff

30 ms

roboto-bold.e3bb53ba.woff

roboto-bold.e3bb53ba.woff

25 ms

roboto-black.ecb4af06.woff

roboto-black.ecb4af06.woff

51 ms

sentry.js

sentry.js

27 ms

Accessibility Review

amp.flo.health accessibility score

96

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

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

amp.flo.health SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Document doesn't have a valid hreflang

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

amp.flo.health

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