Tools & Wizards About Us

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gwava.com

GWAVA History and Product Links | OpenText

Page Load Speed

1.9 sec in total

First Response

332 ms

Resources Loaded

1.4 sec

Page Rendered

185 ms

About Website

Click here to check amazing GWAVA content for United States. Otherwise, check out these important facts you probably never knew about gwava.com

GWAVA software is now a part of OpenText and all products and information previously on GWAVA.com are now on opentext.com

Visit gwava.com

Key Findings

We analyzed Gwava.com page load time and found that the first response time was 332 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

gwava.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value4,220 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.224

56/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

gwava.com

332 ms

overview

62 ms

microfocus

265 ms

bootstrap-grid.min.css

68 ms

opentext.min.css

39 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Gwava.com, 48% (12 requests) were made to Assets.ot.digital and 24% (6 requests) were made to Opentext.com. The less responsive or slowest element that took the longest time to load (364 ms) relates to the external source Secure.marketinghub.opentext.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.9 kB (68%)

Content Size

546.4 kB

After Optimization

177.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Gwava.com main page is 546.4 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. 60% of websites need less resources to load. CSS take 363.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 65.6 kB

  • Original 79.4 kB
  • After minification 62.5 kB
  • After compression 13.7 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 16.9 kB, which is 21% 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 65.6 kB or 83% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 104.0 kB
  • After minification 103.7 kB
  • After compression 102.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.

CSS Optimization

-83%

Potential reduce by 302.0 kB

  • Original 363.1 kB
  • After minification 362.9 kB
  • After compression 61.1 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. Gwava.com needs all CSS files to be minified and compressed as it can save up to 302.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (69%)

Requests Now

13

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gwava.com accessibility score

92

Accessibility Issues

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

gwava.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

gwava.com SEO score

92

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 Gwava.com 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 Gwava.com 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 GWAVA. 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: