Tools & Wizards About Us
opendatalei.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

opendatalei.com

OpenDateLEI: LEI Lookup — Legal Entity Identifier Database

Page Load Speed

1.3 sec in total

First Response

133 ms

Resources Loaded

857 ms

Page Rendered

349 ms

opendatalei.com screenshot

About Website

Welcome to opendatalei.com homepage info - get ready to check Open Data LEI best content right away, or after learning these important things about opendatalei.com

opendatalei.com provides open access to Legal Entity Identifier (LEI) database of the Global Legal Entity Identifier Foundation (GLEIF).

Visit opendatalei.com

Key Findings

We analyzed Opendatalei.com page load time and found that the first response time was 133 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

opendatalei.com performance score

0

Network Requests Diagram

opendatalei.com

133 ms

bootstrap.min.css

102 ms

adsbygoogle.js

289 ms

ads.js

290 ms

jquery.min.js

178 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Opendatalei.com, 15% (2 requests) were made to Pagead2.googlesyndication.com and 15% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (304 ms) belongs to the original domain Opendatalei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.4 kB (6%)

Content Size

189.5 kB

After Optimization

178.1 kB

  • HTML
  • JavaScript

In fact, the total size of Opendatalei.com main page is 189.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 173.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 11.1 kB

  • Original 15.9 kB
  • After minification 15.8 kB
  • After compression 4.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 11.1 kB or 70% of the original size.

JavaScript Optimization

-0%

Potential reduce by 257 B

  • Original 173.5 kB
  • After minification 173.5 kB
  • After compression 173.3 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.

Requests Breakdown

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

Requests Now

11

After Optimization

5

  • AJAX
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Data 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

opendatalei.com

opendatalei.com

133 ms

bootstrap.min.css

bootstrap.min.css

102 ms

adsbygoogle.js

adsbygoogle.js

289 ms

ads.js

ads.js

290 ms

jquery.min.js

jquery.min.js

178 ms

bootstrap.min.js

bootstrap.min.js

214 ms

visual-count-linechart

visual-count-linechart

304 ms

analytics.js

analytics.js

250 ms

show_ads_impl.js

show_ads_impl.js

171 ms

zrt_lookup.html

zrt_lookup.html

107 ms

cookie.js

cookie.js

92 ms

ads

ads

68 ms

collect

collect

57 ms

SEO Factors

opendatalei.com SEO score

0

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 Opendatalei.com 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 Opendatalei.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

opendatalei.com

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