Tools & Wizards About Us
in.lei.report screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

in.lei.report

India Business Directory : LEI Search - Legal Entity Identifier Lookup

Page Load Speed

4.1 sec in total

First Response

1.3 sec

Resources Loaded

1.6 sec

Page Rendered

1.2 sec

in.lei.report screenshot

About Website

Click here to check amazing In LEI content for Israel. Otherwise, check out these important facts you probably never knew about in.lei.report

A free and open database of Legal Entities Identifiers, which is based on the International Standard for the identification of corporates : LEI.

Visit in.lei.report

Key Findings

We analyzed In.lei.report page load time and found that the first response time was 1.3 sec and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

in.lei.report performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value1,410 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

in.lei.report

1265 ms

bootstrap.css

30 ms

js

76 ms

adsbygoogle.js

256 ms

js

121 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 36% of them (4 requests) were addressed to the original In.lei.report, 36% (4 requests) were made to Googletagmanager.com and 18% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain In.lei.report.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.8 kB (31%)

Content Size

180.6 kB

After Optimization

123.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In.lei.report main page is 180.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. 40% of websites need less resources to load. Javascripts take 87.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 55.3 kB

  • Original 69.8 kB
  • After minification 69.8 kB
  • After compression 14.5 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 55.3 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.2 kB
  • After minification 2.2 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. In LEI images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 92 B

  • Original 87.2 kB
  • After minification 87.2 kB
  • After compression 87.2 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

-7%

Potential reduce by 1.4 kB

  • Original 21.3 kB
  • After minification 21.3 kB
  • After compression 19.9 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. In.lei.report has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (60%)

Requests Now

10

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

in.lei.report

in.lei.report

1265 ms

bootstrap.css

bootstrap.css

30 ms

js

js

76 ms

adsbygoogle.js

adsbygoogle.js

256 ms

js

js

121 ms

instant.page.1.2.2.js

instant.page.1.2.2.js

207 ms

lei-logo.png

lei-logo.png

27 ms

js

js

92 ms

analytics.js

analytics.js

37 ms

js

js

87 ms

collect

collect

50 ms

Accessibility Review

in.lei.report accessibility score

100

Accessibility Issues

Best Practices

in.lei.report 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

General

Impact

Issue

High

Page has valid source maps

SEO Factors

in.lei.report SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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 In.lei.report 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 In.lei.report 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

in.lei.report

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