Tools & Wizards About Us
typesense.org screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 81% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

typesense.org

Typesense | Open Source Alternative to Algolia + Pinecone

Page Load Speed

3 sec in total

First Response

34 ms

Resources Loaded

2.1 sec

Page Rendered

826 ms

typesense.org screenshot

About Website

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

Typesense is a fast, typo-tolerant search engine optimized for instant search-as-you-type experiences and ease of use.

Visit typesense.org

Key Findings

We analyzed Typesense.org page load time and found that the first response time was 34 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

typesense.org performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

typesense.org

34 ms

typesense.org

33 ms

helpscout.js

16 ms

js

904 ms

state.js

12 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 69% of them (68 requests) were addressed to the original Typesense.org, 22% (22 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (945 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.0 kB (26%)

Content Size

1.2 MB

After Optimization

876.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Typesense.org main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Javascripts take 427.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 301.4 kB

  • Original 357.2 kB
  • After minification 355.8 kB
  • After compression 55.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. 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 301.4 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 6.2 kB

  • Original 402.6 kB
  • After minification 396.5 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. Typesense images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 427.8 kB
  • After minification 427.7 kB
  • After compression 424.4 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.

Requests Breakdown

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

Requests Now

75

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

typesense.org

typesense.org

34 ms

typesense.org

typesense.org

33 ms

helpscout.js

helpscout.js

16 ms

js

js

904 ms

state.js

state.js

12 ms

d0bf3a1.js

d0bf3a1.js

50 ms

421abad.js

421abad.js

49 ms

fe3c470.js

fe3c470.js

50 ms

7dfbca9.js

7dfbca9.js

48 ms

61a9bf8.js

61a9bf8.js

58 ms

20910a9.js

20910a9.js

57 ms

27b3782.js

27b3782.js

95 ms

1101ea2.js

1101ea2.js

91 ms

gtm.js

gtm.js

915 ms

css2

css2

931 ms

css2

css2

945 ms

typesense_logo_white.cf85c7f.svg

typesense_logo_white.cf85c7f.svg

55 ms

github.8acd339.svg

github.8acd339.svg

56 ms

try_it_out.cdaf71e.svg

try_it_out.cdaf71e.svg

59 ms

codecademy-logo.5589a8c.svg

codecademy-logo.5589a8c.svg

862 ms

changelog.4285e86.svg

changelog.4285e86.svg

861 ms

oddle_eats.a0dbb42.svg

oddle_eats.a0dbb42.svg

863 ms

macro-factor.06699d9.svg

macro-factor.06699d9.svg

857 ms

poorvika-logo.0d5a37a.svg

poorvika-logo.0d5a37a.svg

858 ms

aerotrade.e7916f9.svg

aerotrade.e7916f9.svg

858 ms

soundsnap.a125b97.svg

soundsnap.a125b97.svg

885 ms

trading-strategy.34a4317.svg

trading-strategy.34a4317.svg

894 ms

instatus.1abeb8a.svg

instatus.1abeb8a.svg

891 ms

rerobe.15fdf44.svg

rerobe.15fdf44.svg

904 ms

Google-IO-Logo.37e120e.svg

Google-IO-Logo.37e120e.svg

889 ms

thoughtworks-logo.5c9e909.svg

thoughtworks-logo.5c9e909.svg

887 ms

NASDAQ_Logo.b02c1a2.svg

NASDAQ_Logo.b02c1a2.svg

913 ms

typesense-on-nasdaq.b642d1a.jpeg

typesense-on-nasdaq.b642d1a.jpeg

907 ms

typo_tolerance_icon.b53525c.svg

typo_tolerance_icon.b53525c.svg

891 ms

result_pinning_icon.e02c7ab.svg

result_pinning_icon.e02c7ab.svg

901 ms

synonyms_icon.5a8de04.svg

synonyms_icon.5a8de04.svg

908 ms

api_keys_icon.40b7ec1.svg

api_keys_icon.40b7ec1.svg

919 ms

grouping_icon.d2c9cef.svg

grouping_icon.d2c9cef.svg

905 ms

geo_search_icon.c8dd81a.svg

geo_search_icon.c8dd81a.svg

911 ms

federated_search_icon.293d288.svg

federated_search_icon.293d288.svg

937 ms

vector_search_icon.7253fd8.svg

vector_search_icon.7253fd8.svg

910 ms

high_availability_icon.66fe46b.svg

high_availability_icon.66fe46b.svg

917 ms

Go-Logo_Blue.3279db0.svg

Go-Logo_Blue.3279db0.svg

919 ms

php.9ac7527.svg

php.9ac7527.svg

913 ms

ruby.372ec8f.svg

ruby.372ec8f.svg

904 ms

python.67fee84.svg

python.67fee84.svg

909 ms

logo_dart_192px.b04b21b.svg

logo_dart_192px.b04b21b.svg

915 ms

clojure-logo.fbac412.svg

clojure-logo.fbac412.svg

916 ms

java-logo.82cee2c.svg

java-logo.82cee2c.svg

898 ms

swift_logo.f966418.svg

swift_logo.f966418.svg

891 ms

rust-logo.084b227.svg

rust-logo.084b227.svg

878 ms

laravel-logo.84af9d8.svg

laravel-logo.84af9d8.svg

883 ms

symfony-logo.740ad67.svg

symfony-logo.740ad67.svg

887 ms

gatsby-logo.d22b3c3.svg

gatsby-logo.d22b3c3.svg

881 ms

manifest.js

manifest.js

102 ms

instantsearch-logo.8140727.svg

instantsearch-logo.8140727.svg

153 ms

docsearch-logo.0dc7877.svg

docsearch-logo.0dc7877.svg

83 ms

docusaurus-logo.85a9827.svg

docusaurus-logo.85a9827.svg

152 ms

firebase-logo-standard.fe7e65c.svg

firebase-logo-standard.fe7e65c.svg

152 ms

wordpress-logo.c43e203.svg

wordpress-logo.c43e203.svg

145 ms

woocommerce-logo-color-white.8c8e8a3.svg

woocommerce-logo-color-white.8c8e8a3.svg

146 ms

magento-logo.35447f7.svg

magento-logo.35447f7.svg

129 ms

craft-cms-logo.e838f05.svg

craft-cms-logo.e838f05.svg

128 ms

plone-logo.afe45c8.svg

plone-logo.afe45c8.svg

129 ms

tooljet-logo.d2e2d46.svg

tooljet-logo.d2e2d46.svg

126 ms

langchain-logo.ac711a9.svg

langchain-logo.ac711a9.svg

121 ms

magic_wand.d6d09ba.svg

magic_wand.d6d09ba.svg

132 ms

email.d5a7130.svg

email.d5a7130.svg

128 ms

slack.f3ed395.svg

slack.f3ed395.svg

125 ms

np_help_3407902_FFFFFF.c1f65c6.svg

np_help_3407902_FFFFFF.c1f65c6.svg

126 ms

video_call.ef2d47e.svg

video_call.ef2d47e.svg

127 ms

js

js

119 ms

analytics.js

analytics.js

109 ms

payload.js

payload.js

7 ms

9XUilJ90n1fBFg7ceXwU2nloxA.ttf

9XUilJ90n1fBFg7ceXwU2nloxA.ttf

735 ms

9XUilJ90n1fBFg7ceXwUvnpoxA.ttf

9XUilJ90n1fBFg7ceXwUvnpoxA.ttf

737 ms

9XUhlJ90n1fBFg7ceXwUEltI.ttf

9XUhlJ90n1fBFg7ceXwUEltI.ttf

736 ms

9XUnlJ90n1fBFg7ceXwsdg.ttf

9XUnlJ90n1fBFg7ceXwsdg.ttf

560 ms

9XUilJ90n1fBFg7ceXwUgnhoxA.ttf

9XUilJ90n1fBFg7ceXwUgnhoxA.ttf

561 ms

9XUilJ90n1fBFg7ceXwUrn9oxA.ttf

9XUilJ90n1fBFg7ceXwUrn9oxA.ttf

553 ms

9XUilJ90n1fBFg7ceXwUyn5oxA.ttf

9XUilJ90n1fBFg7ceXwUyn5oxA.ttf

596 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPJ_a1ak.ttf

595 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPja1ak.ttf

595 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPNHa1ak.ttf

653 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPKba1ak.ttf

597 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPErd1ak.ttf

623 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjd1ak.ttf

623 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPCbd1ak.ttf

623 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPPjd1ak.ttf

623 ms

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc1ak.ttf

o-0bIpQoyXQa2RxT7-5B6Ryxs2E_6n1iPHjc1ak.ttf

624 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj248K0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj248K0Fg.ttf

625 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj20cK0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj20cK0Fg.ttf

901 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2PcW0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2PcW0Fg.ttf

626 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2BMW0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2BMW0Fg.ttf

627 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2Y8W0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2Y8W0Fg.ttf

710 ms

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2SsW0Fg.ttf

QGYwz_0dZAGKJJ4t3FFkc3Q8AkNP9Pj2SsW0Fg.ttf

702 ms

collect

collect

512 ms

collect

collect

77 ms

ga-audiences

ga-audiences

47 ms

Accessibility Review

typesense.org accessibility score

93

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

typesense.org best practices score

92

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

SEO Factors

typesense.org SEO score

91

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Typesense.org 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 Typesense.org 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

typesense.org

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