Tools & Wizards About Us
komprehend.io screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

komprehend.io

Komprehend | World Class NLP APIs for Text Analysis

Page Load Speed

2.6 sec in total

First Response

248 ms

Resources Loaded

2.1 sec

Page Rendered

227 ms

komprehend.io screenshot

About Website

Visit komprehend.io now to see the best up-to-date Komprehend content for India and also check out these interesting facts you probably never knew about komprehend.io

Use our Text Analysis APIs to derive high-end information from your data and solve problems like building chatbots, social media analytics, process automation.

Visit komprehend.io

Key Findings

We analyzed Komprehend.io page load time and found that the first response time was 248 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

komprehend.io performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

komprehend.io

248 ms

pd_templates.min.css

187 ms

js

67 ms

pd.min.js

206 ms

templates.js

206 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 79% of them (48 requests) were addressed to the original Komprehend.io, 5% (3 requests) were made to Gstatic.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Komprehend.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.4 kB (25%)

Content Size

994.4 kB

After Optimization

742.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 59.1 kB

  • Original 70.3 kB
  • After minification 45.0 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 25.4 kB, which is 36% 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 59.1 kB or 84% of the original size.

Image Optimization

-31%

Potential reduce by 191.7 kB

  • Original 619.0 kB
  • After minification 427.3 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, Komprehend needs image optimization as it can save up to 191.7 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.6 kB

  • Original 303.8 kB
  • After minification 303.4 kB
  • After compression 302.2 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

-1%

Potential reduce by 15 B

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

Requests Breakdown

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

Requests Now

56

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Komprehend. 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

komprehend.io

komprehend.io

248 ms

pd_templates.min.css

pd_templates.min.css

187 ms

js

js

67 ms

pd.min.js

pd.min.js

206 ms

templates.js

templates.js

206 ms

api.js

api.js

37 ms

css

css

32 ms

j.php

j.php

144 ms

new_logo.png

new_logo.png

228 ms

21.png

21.png

307 ms

22.png

22.png

339 ms

23.png

23.png

336 ms

25.png

25.png

334 ms

26.png

26.png

405 ms

custom-classifier-icon.png

custom-classifier-icon.png

364 ms

27.png

27.png

594 ms

28.png

28.png

575 ms

29.png

29.png

614 ms

31.png

31.png

555 ms

32.png

32.png

577 ms

top_ai_badge.png

top_ai_badge.png

647 ms

api1.png

api1.png

766 ms

positive.png

positive.png

746 ms

neutral.png

neutral.png

752 ms

negative.png

negative.png

644 ms

happy.png

happy.png

786 ms

angry.png

angry.png

839 ms

excited.png

excited.png

841 ms

sad.png

sad.png

938 ms

fear.jpg

fear.jpg

924 ms

bored.png

bored.png

980 ms

news.png

news.png

981 ms

feedback.png

feedback.png

1012 ms

query.png

query.png

1035 ms

marketing.png

marketing.png

1100 ms

spam.png

spam.png

1108 ms

abusive.png

abusive.png

1156 ms

non-abusive.png

non-abusive.png

1175 ms

accurate_api.png

accurate_api.png

1184 ms

diverse_data_api.png

diverse_data_api.png

1235 ms

flexible_api.png

flexible_api.png

1273 ms

privacy_api.png

privacy_api.png

1300 ms

forbes.png

forbes.png

1206 ms

recaptcha__en.js

recaptcha__en.js

122 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

89 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

89 ms

main.js

main.js

1062 ms

v.gif

v.gif

18 ms

fallback

fallback

26 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1173 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

13 ms

logo_48.png

logo_48.png

4 ms

adweek-header-wt.png

adweek-header-wt.png

1057 ms

pw.png

pw.png

1051 ms

i42.png

i42.png

1076 ms

aim.png

aim.png

1114 ms

l-logo.png

l-logo.png

1137 ms

f-logo.png

f-logo.png

1131 ms

t-logo.png

t-logo.png

1007 ms

Accessibility Review

komprehend.io accessibility score

61

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

komprehend.io 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

komprehend.io SEO score

69

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Komprehend.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Komprehend.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

komprehend.io

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