Tools & Wizards About Us

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

plezi.io

WebSockets for Ruby made easy

Page Load Speed

369 ms in total

First Response

62 ms

Resources Loaded

186 ms

Page Rendered

121 ms

About Website

Click here to check amazing Plezi content. Otherwise, check out these important facts you probably never knew about plezi.io

WebSockets for Ruby made easy

Visit plezi.io

Key Findings

We analyzed Plezi.io page load time and found that the first response time was 62 ms and then it took 307 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

plezi.io performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

plezi.io

62 ms

css

31 ms

jquery.min.js

20 ms

main.css

26 ms

logo_thick_dark.png

21 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 44% of them (4 requests) were addressed to the original Plezi.io, 33% (3 requests) were made to Fonts.gstatic.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (62 ms) belongs to the original domain Plezi.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.3 kB (10%)

Content Size

317.1 kB

After Optimization

284.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Plezi.io main page is 317.1 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. 15% of websites need less resources to load. Images take 276.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 7.5 kB

  • Original 10.6 kB
  • After minification 10.6 kB
  • After compression 3.1 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 7.5 kB or 71% of the original size.

Image Optimization

-9%

Potential reduce by 24.8 kB

  • Original 276.8 kB
  • After minification 252.0 kB

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

JavaScript Optimization

-0%

Potential reduce by 18 B

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

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plezi. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

plezi.io accessibility score

71

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

plezi.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plezi.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 Plezi.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

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