Tools & Wizards About Us
receptive.io screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

receptive.io

Pendo Feedback - In-App Feedback - Customer Feedback Tools

Page Load Speed

365 ms in total

First Response

23 ms

Resources Loaded

342 ms

Page Rendered

0 ms

receptive.io screenshot

About Website

Welcome to receptive.io homepage info - get ready to check Receptive best content for United States right away, or after learning these important things about receptive.io

Create impactful products and features by capturing and understanding qualitative feedback at scale, to help prioritize and inform what you develop next.

Visit receptive.io

Key Findings

We analyzed Receptive.io page load time and found that the first response time was 23 ms and then it took 342 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

receptive.io performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value12.8 s

3/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

receptive.io

23 ms

app

3 ms

4 ms

css.44e37e29acb581166614.css

4 ms

app.44e37e29acb581166614.js

79 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Receptive.io, 75% (6 requests) were made to Feedback.pendo.io and 13% (1 request) were made to Cdn.pendo.io. The less responsive or slowest element that took the longest time to load (167 ms) relates to the external source Cdn.pendo.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.9 kB (0%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • JavaScript

In fact, the total size of Receptive.io main page is 1.3 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. 15% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.8 kB

  • Original 5.9 kB
  • After minification 4.9 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 922 B, which is 16% 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 3.8 kB or 65% of the original size.

JavaScript Optimization

-0%

Potential reduce by 126 B

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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 3 (60%)

Requests Now

5

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

receptive.io

receptive.io

23 ms

app

app

3 ms

4 ms

css.44e37e29acb581166614.css

css.44e37e29acb581166614.css

4 ms

app.44e37e29acb581166614.js

app.44e37e29acb581166614.js

79 ms

css.44e37e29acb581166614.js

css.44e37e29acb581166614.js

48 ms

templates.js

templates.js

54 ms

pendo.js

pendo.js

167 ms

Accessibility Review

receptive.io accessibility score

98

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

receptive.io SEO score

85

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

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

receptive.io

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