Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

labrys.io

Labrys - Australia's Largest Blockchain & Web3 Development Agency

Page Load Speed

108 ms in total

First Response

22 ms

Resources Loaded

30 ms

Page Rendered

56 ms

labrys.io screenshot

About Website

Click here to check amazing Labrys content for Russia. Otherwise, check out these important facts you probably never knew about labrys.io

Labrys are global leaders in blockchain solution development. Engage Labrys to plan, design, develop and launch blockchain applications.

Visit labrys.io

Key Findings

We analyzed Labrys.io page load time and found that the first response time was 22 ms and then it took 86 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

labrys.io performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value3,550 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

labrys.io

22 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Labrys.io and no external sources were called. The less responsive or slowest element that took the longest time to load (22 ms) belongs to the original domain Labrys.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 39.9 kB (38%)

Content Size

104.4 kB

After Optimization

64.5 kB

In fact, the total size of Labrys.io main page is 104.4 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Javascripts take 77.3 kB which makes up the majority of the site volume.

HTML Optimization

-14%

Potential reduce by 16 B

  • Original 118 B
  • After minification 118 B
  • After compression 102 B

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 16 B or 14% of the original size.

JavaScript Optimization

-24%

Potential reduce by 18.5 kB

  • Original 77.3 kB
  • After minification 77.3 kB
  • After compression 58.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 18.5 kB or 24% of the original size.

CSS Optimization

-79%

Potential reduce by 21.4 kB

  • Original 26.9 kB
  • After minification 26.9 kB
  • After compression 5.6 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. Labrys.io needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

labrys.io accessibility score

84

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-hidden="true"] elements contain focusable descendents

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

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.

Best Practices

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

Page has valid source maps

SEO Factors

labrys.io SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Labrys.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Labrys.io main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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