Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

daysy.me

Your fertility tracker Daysy - 100 % natural and reliable!

Page Load Speed

2.7 sec in total

First Response

300 ms

Resources Loaded

1.6 sec

Page Rendered

807 ms

daysy.me screenshot

About Website

Visit daysy.me now to see the best up-to-date Daysy content for United States and also check out these interesting facts you probably never knew about daysy.me

Track your cycle with Daysy to know your fertile and non-fertile days ✓ Natural family planning ✓ easy & over 99% accurate ✓ Medical Device ✓ Over 35 years of experience!

Visit daysy.me

Key Findings

We analyzed Daysy.me page load time and found that the first response time was 300 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

daysy.me performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

daysy.me

300 ms

daysy.me

612 ms

OtAutoBlock.js

377 ms

otSDKStub.js

393 ms

bundle.e284c9bc624a.css

32 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Daysy.me, 79% (26 requests) were made to Dfxyyqidohkoi.cloudfront.net and 9% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (683 ms) relates to the external source Seal.excellent.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.9 kB (3%)

Content Size

2.0 MB

After Optimization

1.9 MB

In fact, the total size of Daysy.me main page is 2.0 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 62.7 kB

  • Original 74.3 kB
  • After minification 53.6 kB
  • After compression 11.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 20.7 kB, which is 28% 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 62.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 448 B

  • Original 1.7 MB
  • After minification 1.7 MB

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. Daysy images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

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

CSS Optimization

-0%

Potential reduce by 83 B

  • Original 28.2 kB
  • After minification 28.2 kB
  • After compression 28.1 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. Daysy.me has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (30%)

Requests Now

30

After Optimization

21

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

Accessibility Review

daysy.me accessibility score

66

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

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

daysy.me best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

daysy.me SEO score

75

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 Daysy.me 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 Daysy.me 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

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