Tools & Wizards About Us
loomx.io screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

loomx.io

Loom Network – Production-Ready, Multichain Interop Platform for Serious Dapp Developers

Page Load Speed

1.9 sec in total

First Response

33 ms

Resources Loaded

607 ms

Page Rendered

1.3 sec

loomx.io screenshot

About Website

Visit loomx.io now to see the best up-to-date Loom X content for United States and also check out these interesting facts you probably never knew about loomx.io

We provide the tools blockchain devs need to build high-performance dapps today. Future-proof your dapp by reaching the largest user base possible.

Visit loomx.io

Key Findings

We analyzed Loomx.io page load time and found that the first response time was 33 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

loomx.io performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

loomx.io

33 ms

loomx.io

88 ms

js

110 ms

fbevents.js

65 ms

8247700.js

159 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 74% of them (49 requests) were addressed to the original Loomx.io, 8% (5 requests) were made to Cdnjs.cloudflare.com and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (205 ms) belongs to the original domain Loomx.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.1 kB (11%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Loomx.io main page is 2.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 51.0 kB

  • Original 65.3 kB
  • After minification 51.2 kB
  • After compression 14.3 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 14.1 kB, which is 22% 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 51.0 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 162.0 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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

JavaScript Optimization

-0%

Potential reduce by 98 B

  • Original 244.4 kB
  • After minification 244.4 kB
  • After compression 244.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.

CSS Optimization

-0%

Potential reduce by 5 B

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 26.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. Loomx.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (25%)

Requests Now

61

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

loomx.io

loomx.io

33 ms

loomx.io

loomx.io

88 ms

js

js

110 ms

fbevents.js

fbevents.js

65 ms

8247700.js

8247700.js

159 ms

sg-widget-v2.js

sg-widget-v2.js

135 ms

prism-tomorrow.min.css

prism-tomorrow.min.css

107 ms

prism-line-numbers.min.css

prism-line-numbers.min.css

153 ms

main.bundle-1acb9ac9.css

main.bundle-1acb9ac9.css

31 ms

prism.min.js

prism.min.js

156 ms

prism-line-numbers.js

prism-line-numbers.js

154 ms

email-decode.min.js

email-decode.min.js

47 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

128 ms

popper.min.js

popper.min.js

154 ms

bootstrap.min.js

bootstrap.min.js

127 ms

all.js

all.js

151 ms

main.bundle-50eb798e.js

main.bundle-50eb798e.js

47 ms

ycn7hsp.css

ycn7hsp.css

68 ms

close-12e6ceb8.svg

close-12e6ceb8.svg

18 ms

logo-e28b304f.svg

logo-e28b304f.svg

13 ms

group-41-f18b6e55.png

group-41-f18b6e55.png

16 ms

group-28-7344990f.svg

group-28-7344990f.svg

20 ms

Loomy-85d5388d.png

Loomy-85d5388d.png

19 ms

01-743dc0fb.svg

01-743dc0fb.svg

25 ms

1-4-0b22dfa6.svg

1-4-0b22dfa6.svg

22 ms

04-623e7196.svg

04-623e7196.svg

38 ms

06-863dc68f.svg

06-863dc68f.svg

33 ms

1-2-e8e9565c.svg

1-2-e8e9565c.svg

31 ms

02-de34373d.svg

02-de34373d.svg

48 ms

2-1-10880838.svg

2-1-10880838.svg

34 ms

03-a339c978.svg

03-a339c978.svg

34 ms

05-452900f4.svg

05-452900f4.svg

41 ms

what_is_loom@2x-29d48e13.jpg

what_is_loom@2x-29d48e13.jpg

43 ms

what_is_loom_token@2x-b53b13ee.jpg

what_is_loom_token@2x-b53b13ee.jpg

44 ms

group-12-42988e10.svg

group-12-42988e10.svg

46 ms

group-14-cba8bc53.svg

group-14-cba8bc53.svg

49 ms

group-11-3ca37cb7.svg

group-11-3ca37cb7.svg

48 ms

group-16-a1e0c336.svg

group-16-a1e0c336.svg

53 ms

group-15-3dfbb124.svg

group-15-3dfbb124.svg

61 ms

group-13-0743827f.svg

group-13-0743827f.svg

59 ms

p.css

p.css

27 ms

Loom_Mainnet_Diagram_Fix_v2-1fc740a6.png

Loom_Mainnet_Diagram_Fix_v2-1fc740a6.png

130 ms

delegate-call-job-board-6af057af.png

delegate-call-job-board-6af057af.png

116 ms

delegate-call-job-board@2x-4447c115.png

delegate-call-job-board@2x-4447c115.png

129 ms

cz_screenshot-f684e24a.jpg

cz_screenshot-f684e24a.jpg

117 ms

loom_network_2021_revamp-23ed27a2.jpg

loom_network_2021_revamp-23ed27a2.jpg

116 ms

staking_live@2x-bcbd0cca.jpg

staking_live@2x-bcbd0cca.jpg

118 ms

bounties_and_rewards_banner-43884be0.png

bounties_and_rewards_banner-43884be0.png

118 ms

who_needs_lighting_network_banner-cf09f54f.png

who_needs_lighting_network_banner-cf09f54f.png

119 ms

enable_defi_banner-054b7763.png

enable_defi_banner-054b7763.png

119 ms

basechain_is_coming_banner-767c5972.png

basechain_is_coming_banner-767c5972.png

120 ms

bitmap-cnn@2x-d42d61aa.png

bitmap-cnn@2x-d42d61aa.png

118 ms

group-26@2x-a42c7c4c.png

group-26@2x-a42c7c4c.png

121 ms

bitmap-tech@2x-bb5fd472.png

bitmap-tech@2x-bb5fd472.png

121 ms

bitmap@2x-1ce4cd7e.png

bitmap@2x-1ce4cd7e.png

121 ms

axie-infinity-copy-2-2897167e.png

axie-infinity-copy-2-2897167e.png

121 ms

axie-infinity-copy-2@2x-1d28b203.png

axie-infinity-copy-2@2x-1d28b203.png

126 ms

consensys-copy-f3de2be3.png

consensys-copy-f3de2be3.png

122 ms

consensys-copy@2x-31fb04c2.png

consensys-copy@2x-31fb04c2.png

124 ms

group-27-6a68074e.png

group-27-6a68074e.png

122 ms

group-27@2x-8b6aee91.png

group-27@2x-8b6aee91.png

126 ms

mascot-0008@2x-b7d5fa22.png

mascot-0008@2x-b7d5fa22.png

205 ms

loom-logo-full-text-inverse-19fef1ed.png

loom-logo-full-text-inverse-19fef1ed.png

122 ms

d

d

82 ms

d

d

82 ms

d

d

83 ms

Accessibility Review

loomx.io accessibility score

54

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

loomx.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

loomx.io SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Loomx.io 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 Loomx.io 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

loomx.io

Open Graph data is detected on the main page of Loom X. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: