Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

jaanus.com

Jaanus

Page Load Speed

993 ms in total

First Response

221 ms

Resources Loaded

653 ms

Page Rendered

119 ms

jaanus.com screenshot

About Website

Welcome to jaanus.com homepage info - get ready to check Jaanus best content for India right away, or after learning these important things about jaanus.com

Visit jaanus.com

Key Findings

We analyzed Jaanus.com page load time and found that the first response time was 221 ms and then it took 772 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

jaanus.com performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

jaanus.com

221 ms

css

23 ms

css

35 ms

entypo.css

70 ms

fonts.css

135 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 45% of them (10 requests) were addressed to the original Jaanus.com, 27% (6 requests) were made to Fonts.gstatic.com and 9% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (221 ms) belongs to the original domain Jaanus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.7 kB (60%)

Content Size

105.5 kB

After Optimization

41.7 kB

In fact, the total size of Jaanus.com main page is 105.5 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. 30% of websites need less resources to load. Javascripts take 63.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 4.7 kB

  • Original 6.6 kB
  • After minification 5.0 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 1.6 kB, which is 25% 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 4.7 kB or 71% of the original size.

JavaScript Optimization

-60%

Potential reduce by 38.0 kB

  • Original 63.6 kB
  • After minification 63.1 kB
  • After compression 25.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 38.0 kB or 60% of the original size.

CSS Optimization

-60%

Potential reduce by 21.0 kB

  • Original 35.3 kB
  • After minification 34.3 kB
  • After compression 14.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. Jaanus.com needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 60% of the original size.

Requests Breakdown

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

Requests Now

12

After Optimization

3

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

Accessibility Review

jaanus.com accessibility score

94

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

Best Practices

jaanus.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

jaanus.com SEO score

87

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jaanus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jaanus.com 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 Jaanus. 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: