Tools & Wizards About Us
zetaly.io screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

zetaly.io

ZETALY - Get the big picture at last with a one-stop solution

Page Load Speed

10.3 sec in total

First Response

2.2 sec

Resources Loaded

7.6 sec

Page Rendered

496 ms

zetaly.io screenshot

About Website

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

A one-stop mainframe solution to rule them all. ZETALY makes mainframe logs contents understandable, applicable, and actionable.

Visit zetaly.io

Key Findings

We analyzed Zetaly.io page load time and found that the first response time was 2.2 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

zetaly.io performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value4,020 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value13.3 s

11/100

10%

Network Requests Diagram

zetaly.io

2232 ms

jquery.min.js

103 ms

highcharts.js

152 ms

css

74 ms

lazysizes.min.js

353 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 75% of them (24 requests) were addressed to the original Zetaly.io, 3% (1 request) were made to Code.highcharts.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Zetaly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.8 kB (33%)

Content Size

1.0 MB

After Optimization

687.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 187.6 kB

  • Original 229.0 kB
  • After minification 229.0 kB
  • After compression 41.4 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 187.6 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 32.9 kB

  • Original 517.0 kB
  • After minification 484.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. ZETALY images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 113.2 kB

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

CSS Optimization

-0%

Potential reduce by 186 B

  • Original 64.3 kB
  • After minification 64.3 kB
  • After compression 64.2 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. Zetaly.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (50%)

Requests Now

22

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zetaly.io

zetaly.io

2232 ms

jquery.min.js

jquery.min.js

103 ms

highcharts.js

highcharts.js

152 ms

css

css

74 ms

lazysizes.min.js

lazysizes.min.js

353 ms

5231628.js

5231628.js

263 ms

autoptimize_3c2795ef78d8ae3804d1238859c7835e.js

autoptimize_3c2795ef78d8ae3804d1238859c7835e.js

768 ms

Pattern_ZETALY_left_bottom_corner_green.svg

Pattern_ZETALY_left_bottom_corner_green.svg

180 ms

tailored-fit-pricing.png

tailored-fit-pricing.png

327 ms

mainframe-production.jpg

mainframe-production.jpg

517 ms

Tailorfit-pricing.jpg

Tailorfit-pricing.jpg

597 ms

Pattern_ZETALY_leftright_green.svg

Pattern_ZETALY_leftright_green.svg

741 ms

Surt-RegularExtended.woff2

Surt-RegularExtended.woff2

383 ms

Surt-RegularExtended.woff2

Surt-RegularExtended.woff2

327 ms

Surt-BoldExtended.woff2

Surt-BoldExtended.woff2

410 ms

Surt-BoldExtended.woff2

Surt-BoldExtended.woff2

448 ms

modules.ttf

modules.ttf

502 ms

modules.ttf

modules.ttf

1734 ms

et-divi-dynamic-33-late.css

et-divi-dynamic-33-late.css

520 ms

5231628.js

5231628.js

196 ms

collectedforms.js

collectedforms.js

201 ms

5231628.js

5231628.js

263 ms

fb.js

fb.js

200 ms

logo_zetaly_OK-e1560709025634.png

logo_zetaly_OK-e1560709025634.png

196 ms

modernization.svg

modernization.svg

191 ms

Mockup_laptop_Service-Delivery-1024x599.png

Mockup_laptop_Service-Delivery-1024x599.png

264 ms

autoptimize_5172e717685d409a201ec4dc85b5ed17.css

autoptimize_5172e717685d409a201ec4dc85b5ed17.css

259 ms

modules.woff

modules.woff

1280 ms

modules.ttf

modules.ttf

100 ms

autoptimize_400da7a94d1ca504d25568404e3d2406.css

autoptimize_400da7a94d1ca504d25568404e3d2406.css

88 ms

modules.svg

modules.svg

1323 ms

__ptq.gif

__ptq.gif

50 ms

Accessibility Review

zetaly.io accessibility score

84

Accessibility Issues

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

High

Some elements have a [tabindex] value greater than 0

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

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

zetaly.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

zetaly.io SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

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

zetaly.io

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