Tools & Wizards About Us
innso.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

innso.com

Foundever - Omnichannel contact center solutions for better CX

Page Load Speed

1.8 sec in total

First Response

62 ms

Resources Loaded

1.1 sec

Page Rendered

667 ms

innso.com screenshot

About Website

Welcome to innso.com homepage info - get ready to check Innso best content right away, or after learning these important things about innso.com

Foundever is one of the largest customer experience (CX) companies in the world. Foundever provides omnichannel contact center solutions.

Visit innso.com

Key Findings

We analyzed Innso.com page load time and found that the first response time was 62 ms and then it took 1.7 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

innso.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value2,810 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

innso.com

62 ms

foundever.com

153 ms

index.css

14 ms

style.min.css

31 ms

dashicons.min.css

39 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Innso.com, 85% (35 requests) were made to Foundever.com and 5% (2 requests) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (494 ms) relates to the external source Foundever.matomo.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.3 kB (23%)

Content Size

809.0 kB

After Optimization

620.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 152.8 kB

  • Original 184.9 kB
  • After minification 175.9 kB
  • After compression 32.1 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 152.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 369 B

  • Original 444.2 kB
  • After minification 443.8 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. Innso images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 977 B

  • Original 93.8 kB
  • After minification 93.8 kB
  • After compression 92.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. This website has mostly compressed JavaScripts.

CSS Optimization

-40%

Potential reduce by 34.2 kB

  • Original 86.1 kB
  • After minification 52.7 kB
  • After compression 51.9 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. Innso.com needs all CSS files to be minified and compressed as it can save up to 34.2 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (63%)

Requests Now

24

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

innso.com

innso.com

62 ms

foundever.com

foundever.com

153 ms

index.css

index.css

14 ms

style.min.css

style.min.css

31 ms

dashicons.min.css

dashicons.min.css

39 ms

style.css

style.css

34 ms

style.css

style.css

34 ms

search-forms.css

search-forms.css

26 ms

jquery.min.js

jquery.min.js

45 ms

jquery-migrate.min.js

jquery-migrate.min.js

44 ms

stub.js

stub.js

87 ms

iubenda_cs.js

iubenda_cs.js

98 ms

index.js

index.js

84 ms

separate-accordion.js

separate-accordion.js

76 ms

group-accordion.js

group-accordion.js

83 ms

script.min.js

script.min.js

85 ms

smush-lazy-load-native.min.js

smush-lazy-load-native.min.js

105 ms

gtm.js

gtm.js

201 ms

Insights-banner-midnight.svg

Insights-banner-midnight.svg

25 ms

career-CTA-footer.jpg

career-CTA-footer.jpg

99 ms

logo.svg

logo.svg

22 ms

IMG_COVER.png

IMG_COVER.png

25 ms

smush-placeholder.png

smush-placeholder.png

21 ms

subset-NotoSans-Regular.ce184da1.woff

subset-NotoSans-Regular.ce184da1.woff

124 ms

subset-NotoSans-Medium.1e1607c0.woff

subset-NotoSans-Medium.1e1607c0.woff

125 ms

subset-NotoSans-Light.acf9ddf9.woff

subset-NotoSans-Light.acf9ddf9.woff

126 ms

subset-NotoSans-ExtraLight.c152460d.woff

subset-NotoSans-ExtraLight.c152460d.woff

128 ms

subset-NotoSans-Thin.d313b3b3.woff

subset-NotoSans-Thin.d313b3b3.woff

126 ms

subset-NotoSans-SemiBold.067aaf35.woff

subset-NotoSans-SemiBold.067aaf35.woff

125 ms

subset-NotoSans-Bold.5d7835a8.woff

subset-NotoSans-Bold.5d7835a8.woff

183 ms

subset-NotoSans-ExtraBold.f8263bb2.woff

subset-NotoSans-ExtraBold.f8263bb2.woff

184 ms

subset-NotoSans-Black.91fe5c5f.woff

subset-NotoSans-Black.91fe5c5f.woff

184 ms

Foundever-Sans-Regular.d39c6afe.woff

Foundever-Sans-Regular.d39c6afe.woff

185 ms

Foundever-Sans-Light.3f99c03f.woff

Foundever-Sans-Light.3f99c03f.woff

210 ms

Foundever-Sans-Thin.6e1542b2.woff

Foundever-Sans-Thin.6e1542b2.woff

202 ms

Foundever-Sans-Medium.01ca1b5e.woff

Foundever-Sans-Medium.01ca1b5e.woff

264 ms

Foundever-Sans-Bold.dc886e91.woff

Foundever-Sans-Bold.dc886e91.woff

274 ms

Foundever-Sans-Black.7fcf36d7.woff

Foundever-Sans-Black.7fcf36d7.woff

284 ms

matomo.js

matomo.js

31 ms

matomo.php

matomo.php

494 ms

Push.png

Push.png

14 ms

Accessibility Review

innso.com accessibility score

100

Accessibility Issues

Best Practices

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

High

Page has valid source maps

SEO Factors

innso.com 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 Innso.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 Innso.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

innso.com

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