Access fettle.health. Sexual Health Tests | Treatment | Contraception

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

fettle.health

155 ms

fettle.health

431 ms

polyfills-c67a75d1b6f99dc8.js

89 ms

webpack-38c7b9b7ff960477.js

181 ms

framework-560765ab0625ba27.js

411 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 78% of them (18 requests) were addressed to the original Fettle.health, 22% (5 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (699 ms) belongs to the original domain Fettle.health.

Content Size

208.9 kB

After Optimization

56.1 kB

In fact, the total size of Fettle.health main page is 208.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 186.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 152.8 kB

Original 186.4 kB
After minification 186.4 kB
After compression 33.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 152.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 22.5 kB
After minification 22.5 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. Fettle images are well optimized though.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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/).

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

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