Access zilwatch.io. zilWatch Farewell Note. TL;DR: We regret that we have decided… | by zilWatch.io

Report Summary

About Website

Welcome to zilwatch.io homepage info - get ready to check ZilWatch best content right away, or after learning these important things about zilwatch.io

TL;DR: We regret that we have decided to shut down zilWatch for good on 20 Feb 2022. We will also shut down our Twitter and Telegram group shortly after that. First, we would like to express our…

Visit zilwatch.io

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value4,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

zilwatch.io

65 ms

zilwatch-farewell-note-5f8d209ddfc4

100 ms

unbound.css

39 ms

manifest.749d8bab.js

69 ms

3057.5e22bbb0.js

91 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zilwatch.io, 63% (33 requests) were made to Cdn-client.medium.com and 25% (13 requests) were made to Glyph.medium.com. The less responsive or slowest element that took the longest time to load (190 ms) relates to the external source Cdn-client.medium.com.

Content Size

736.8 kB

After Optimization

666.0 kB

In fact, the total size of Zilwatch.io main page is 736.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. 70% of websites need less resources to load. Javascripts take 629.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 67.3 kB

Original 91.5 kB
After minification 91.5 kB
After compression 24.2 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 67.3 kB or 74% of the original size.

Image Optimization

-19%

Potential reduce by 2.9 kB

Original 15.0 kB
After minification 12.1 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. Obviously, ZilWatch needs image optimization as it can save up to 2.9 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 500 B

Original 629.3 kB
After minification 629.3 kB
After compression 628.8 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

-5%

Potential reduce by 46 B

Original 994 B
After minification 994 B
After compression 948 B

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. Zilwatch.io has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

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

zilwatch.io

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

Report Summary

Performance

Accessibility

Best Practices

SEO

zilWatch Farewell Note. TL;DR: We regret that we have decided… | by zilWatch.io | Medium

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)