Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

go2.innotas.com

Planview PPM Pro (formerly Innotas) project portfolio management software

Page Load Speed

1.9 sec in total

First Response

314 ms

Resources Loaded

1.2 sec

Page Rendered

333 ms

About Website

Visit go2.innotas.com now to see the best up-to-date Go 2 Innotas content for United States and also check out these interesting facts you probably never knew about go2.innotas.com

Learn about the leading provider of cloud solutions for Project Portfolio Management software, IT Project Portfolio Management, and Resource Management.

Visit go2.innotas.com

Key Findings

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

Performance Metrics

go2.innotas.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value3,300 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.278

44/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

go2.innotas.com

314 ms

www.innotas.com

31 ms

www.innotas.com

70 ms

a23f81f6-b5a4-4e57-86a7-ea596fab4129.js

199 ms

09ff86dc-664a-4b55-b9ac-75e9cac7d8aa.css

156 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Go2.innotas.com, 45% (14 requests) were made to Innotas.com and 26% (8 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (314 ms) belongs to the original domain Go2.innotas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.0 kB (55%)

Content Size

631.2 kB

After Optimization

284.2 kB

In fact, the total size of Go2.innotas.com main page is 631.2 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. 50% of websites need less resources to load. Images take 234.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.8 kB

  • Original 26.0 kB
  • After minification 23.6 kB
  • After compression 6.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 19.8 kB or 76% of the original size.

Image Optimization

-32%

Potential reduce by 74.0 kB

  • Original 234.4 kB
  • After minification 160.4 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, Go 2 Innotas needs image optimization as it can save up to 74.0 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 90.9 kB

  • Original 172.8 kB
  • After minification 172.8 kB
  • After compression 81.9 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 90.9 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 162.4 kB

  • Original 198.0 kB
  • After minification 180.0 kB
  • After compression 35.6 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. Go2.innotas.com needs all CSS files to be minified and compressed as it can save up to 162.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

10

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go 2 Innotas. 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 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

go2.innotas.com accessibility score

94

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.

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

go2.innotas.com best practices score

67

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

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

SEO Factors

go2.innotas.com SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 Go2.innotas.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 Go2.innotas.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 data is detected on the main page of Go 2 Innotas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: