Tools & Wizards About Us
esapi.intellexer.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

esapi.intellexer.com

Intellexer - Natural Language Processing and Text Mining API

Page Load Speed

2.2 sec in total

First Response

304 ms

Resources Loaded

1.6 sec

Page Rendered

262 ms

esapi.intellexer.com screenshot

About Website

Click here to check amazing Es API Intellexer content for Canada. Otherwise, check out these important facts you probably never knew about esapi.intellexer.com

The Intellexer API enables developers to embed text analysis solutions in consumer or enterprise applications, or web-services. You can use Intellexer API with any software component that issue an HTT...

Visit esapi.intellexer.com

Key Findings

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

Performance Metrics

esapi.intellexer.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

esapi.intellexer.com

304 ms

jquery-2.2.3.min.js

20 ms

angular.min.js

233 ms

gdpr-cookie-notice.js

251 ms

angular-animate.js

62 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 83% of them (35 requests) were addressed to the original Esapi.intellexer.com, 10% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (743 ms) belongs to the original domain Esapi.intellexer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.8 kB (51%)

Content Size

930.2 kB

After Optimization

451.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 35.9 kB

  • Original 44.5 kB
  • After minification 33.8 kB
  • After compression 8.6 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.6 kB, which is 24% 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 35.9 kB or 81% of the original size.

Image Optimization

-47%

Potential reduce by 277.2 kB

  • Original 593.0 kB
  • After minification 315.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. Obviously, Es API Intellexer needs image optimization as it can save up to 277.2 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 154.7 kB

  • Original 238.8 kB
  • After minification 143.7 kB
  • After compression 84.1 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 154.7 kB or 65% of the original size.

CSS Optimization

-20%

Potential reduce by 10.9 kB

  • Original 54.0 kB
  • After minification 51.3 kB
  • After compression 43.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. Esapi.intellexer.com needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

esapi.intellexer.com

esapi.intellexer.com

304 ms

jquery-2.2.3.min.js

jquery-2.2.3.min.js

20 ms

angular.min.js

angular.min.js

233 ms

gdpr-cookie-notice.js

gdpr-cookie-notice.js

251 ms

angular-animate.js

angular-animate.js

62 ms

angular-route.min.js

angular-route.min.js

256 ms

bootstrap.min.js

bootstrap.min.js

257 ms

bootstrap.min.css

bootstrap.min.css

374 ms

offcanvas.css

offcanvas.css

262 ms

gdpr-cookie-notice.css

gdpr-cookie-notice.css

359 ms

font-awesome.min.css

font-awesome.min.css

371 ms

Site.css

Site.css

372 ms

sweetalert.css

sweetalert.css

372 ms

sweetalert.min.js

sweetalert.min.js

382 ms

mainController.js

mainController.js

474 ms

mainController.js

mainController.js

528 ms

ng-directives.js

ng-directives.js

528 ms

css

css

34 ms

logo.png

logo.png

212 ms

head_bg.jpg

head_bg.jpg

213 ms

api_banner1.png

api_banner1.png

660 ms

API_banner2.png

API_banner2.png

382 ms

API_banner3.png

API_banner3.png

540 ms

sa-icon.svg

sa-icon.svg

212 ms

ner-icon.svg

ner-icon.svg

275 ms

summarizer-icon.svg

summarizer-icon.svg

291 ms

file-tree.svg

file-tree.svg

277 ms

comporator-icon.svg

comporator-icon.svg

397 ms

python.png

python.png

413 ms

php.png

php.png

431 ms

javalogo.png

javalogo.png

520 ms

windows-8-icon.png

windows-8-icon.png

534 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

86 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

87 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

159 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

160 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

743 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

640 ms

summarizer_box_clean.jpg

summarizer_box_clean.jpg

601 ms

ic_4.png

ic_4.png

538 ms

ic_2.png

ic_2.png

540 ms

social-sprite.png

social-sprite.png

654 ms

Accessibility Review

esapi.intellexer.com accessibility score

77

Accessibility Issues

ARIA

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.

Impact

Issue

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.

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.

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

Links do not have a discernible name

Best Practices

esapi.intellexer.com best practices score

75

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

Page has valid source maps

SEO Factors

esapi.intellexer.com SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Esapi.intellexer.com 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 Esapi.intellexer.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

esapi.intellexer.com

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