Access researcher.life. AI Tools For Research & Expert Publication Services

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

researcher.life

11 ms

researcher.life

79 ms

70 ms

r-new-logo-desktop.svg

282 ms

trending-up-fill.svg

254 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Researcher.life, 92% (56 requests) were made to Cdn.researcher.life and 2% (1 request) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Researcher.life.

Content Size

269.6 kB

After Optimization

64.2 kB

In fact, the total size of Researcher.life main page is 269.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 246.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 205.4 kB

Original 246.3 kB
After minification 244.9 kB
After compression 40.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. 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 205.4 kB or 83% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 23.3 kB
After minification 23.3 kB
After compression 23.3 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. Researcher.life has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Researcher. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

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

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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 Researcher.life 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 Researcher.life 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 data is detected on the main page of Researcher. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: