Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

rapier-loom.net

GitHub - wschult23/LOOM.NET: The LOOM.NET project aims to investigate and promote the usage of AOP in the context of the Microsoft .NET framework.

Page Load Speed

1.5 sec in total

First Response

286 ms

Resources Loaded

1.1 sec

Page Rendered

165 ms

About Website

Visit rapier-loom.net now to see the best up-to-date Rapier LOOM content and also check out these interesting facts you probably never knew about rapier-loom.net

The LOOM.NET project aims to investigate and promote the usage of AOP in the context of the Microsoft .NET framework. - wschult23/LOOM.NET

Visit rapier-loom.net

Key Findings

We analyzed Rapier-loom.net page load time and found that the first response time was 286 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

rapier-loom.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

rapier-loom.net

286 ms

LOOM.NET

501 ms

light-efd2f2257c96.css

50 ms

dark-6b1e37da2254.css

54 ms

primer-primitives-8500c2c7ce5f.css

52 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rapier-loom.net, 97% (85 requests) were made to Github.githubassets.com and 1% (1 request) were made to Github.com. The less responsive or slowest element that took the longest time to load (501 ms) relates to the external source Github.com.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

983.2 kB

In fact, the total size of Rapier-loom.net main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 854.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 266.9 kB

  • Original 318.5 kB
  • After minification 310.0 kB
  • After compression 51.6 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 266.9 kB or 84% of the original size.

JavaScript Optimization

-7%

Potential reduce by 56.1 kB

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

-45%

Potential reduce by 110.8 kB

  • Original 243.9 kB
  • After minification 243.2 kB
  • After compression 133.1 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. Rapier-loom.net needs all CSS files to be minified and compressed as it can save up to 110.8 kB or 45% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (97%)

Requests Now

86

After Optimization

3

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

Accessibility Review

rapier-loom.net accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

rapier-loom.net 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rapier-loom.net SEO score

91

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

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 Rapier-loom.net 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 Rapier-loom.net 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 Rapier LOOM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: