Access blnkhlth.co.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

blnkhlth.co

22 ms

www.blinkhealth.com

107 ms

head

101 ms

7162d362f92ba410.css

29 ms

aa7dffbca22fc19e.css

38 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Blnkhlth.co, 77% (10 requests) were made to Blinkhealth.com and 8% (1 request) were made to Fecdn.user1st.info. The less responsive or slowest element that took the longest time to load (107 ms) relates to the external source Blinkhealth.com.

Content Size

69.3 kB

After Optimization

22.8 kB

In fact, the total size of Blnkhlth.co main page is 69.3 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. 70% of websites need less resources to load. HTML takes 69.3 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 46.5 kB

Original 69.3 kB
After minification 69.3 kB
After compression 22.8 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 46.5 kB or 67% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 5 B

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.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

button, link, and menuitem elements do not have accessible names.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blnkhlth.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Blnkhlth.co 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 Blnkhlth. 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: