Access zowe.org. Zowe

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value4,310 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value21.7 s

1/100

10%

zowe.org

84 ms

zowe.org

16 ms

www.zowe.org

52 ms

osano.js

394 ms

js

92 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 58% of them (45 requests) were addressed to the original Zowe.org, 10% (8 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Zowe.org.

Content Size

543.5 kB

After Optimization

325.6 kB

In fact, the total size of Zowe.org main page is 543.5 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. 85% 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 219.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.6 kB

Original 60.0 kB
After minification 49.7 kB
After compression 11.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. This page needs HTML code to be minified as it can gain 10.2 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.6 kB or 81% of the original size.

Image Optimization

-64%

Potential reduce by 130.7 kB

Original 205.2 kB
After minification 74.5 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, Zowe needs image optimization as it can save up to 130.7 kB or 64% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 38.7 kB

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

CSS Optimization

-0%

Potential reduce by 0 B

Original 59.0 kB
After minification 59.0 kB
After compression 59.0 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. Zowe.org has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zowe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS 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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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 Zowe.org 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 Zowe.org 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

zowe.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Zowe

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)

Network Requests Diagram

zowe.org

zowe.org

www.zowe.org

osano.js

js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

zowe.org

zowe.org

www.zowe.org

osano.js

js

index.min.js

style.css

menu.css

css

bootstrap.min.css

jquery-3.5.1.slim.min.js

bootstrap.bundle.min.js

f449f80794.js

retainable.js

feedback.js

retainable.css

hotjar-3063896.js

bg2.webp

Zowe.vscode-extension-for-zowe.svg

DO_Logo_horizontal_white.svg

lf-projects.svg

transparent-Zowe-logo2.png

navbar-toggler.png

learn.png

use.png

create.png

contribute.png

zowe-desktop-image.webp

zowe-apiml-image.webp

zowe-cli.webp

zowe-explorer-image.webp

zss-project.webp

nodejs-sdk-project.webp

apiml-jobs.webp

apiml-data-sets.webp

intellij_squad.webp

kotlin-sdk-project.webp

chat-thumbnail-v2.webp

zebra-image.webp

python-sdk-project.webp

swift-sdk-project.webp

java-sdk-project.webp

apiml-metrics-service.webp