Tools & Wizards About Us

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

identity.org

Identity.com: User-Centric Digital Identity

Page Load Speed

1.2 sec in total

First Response

35 ms

Resources Loaded

774 ms

Page Rendered

416 ms

About Website

Click here to check amazing Identity content. Otherwise, check out these important facts you probably never knew about identity.org

Empowering you with trust, privacy, and simplicity. We are building a future in which users truly own their digital identity.

Visit identity.org

Key Findings

We analyzed Identity.org page load time and found that the first response time was 35 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

identity.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value1,070 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

identity.org

35 ms

www.identity.com

64 ms

style.min.css

18 ms

all.min.css

27 ms

slick.min.css

32 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Identity.org, 78% (50 requests) were made to Identity.com and 14% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (298 ms) relates to the external source Identity.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.5 kB (20%)

Content Size

823.8 kB

After Optimization

660.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Identity.org main page is 823.8 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. 60% of websites need less resources to load. Javascripts take 393.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 154.1 kB

  • Original 187.5 kB
  • After minification 184.4 kB
  • After compression 33.4 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 154.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 68 B
  • After minification 68 B

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. Identity images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

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

-2%

Potential reduce by 6.0 kB

  • Original 242.8 kB
  • After minification 242.8 kB
  • After compression 236.8 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. Identity.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

52

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Identity. 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 28 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

identity.org accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

identity.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

identity.org SEO score

90

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Identity.org 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 Identity.org 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 Identity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: