Tools & Wizards About Us
tray.io screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

tray.io

Unified, AI-powered iPaaS for every team to automate at scale | Tray.io

Page Load Speed

2.8 sec in total

First Response

498 ms

Resources Loaded

2.1 sec

Page Rendered

234 ms

tray.io screenshot

About Website

Click here to check amazing Tray content for United States. Otherwise, check out these important facts you probably never knew about tray.io

Dramatically simplify API integrations with Tray connectors, the Connector Builder, and our Authentication and Projects features. Visit Tray.io to learn more.

Visit tray.io

Key Findings

We analyzed Tray.io page load time and found that the first response time was 498 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

tray.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value1,670 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.197

63/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

tray.io

498 ms

tray.io

679 ms

main.css

164 ms

ohx0hfv.js

208 ms

bugsnag-2.min.js

48 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 43% of them (17 requests) were addressed to the original Tray.io, 23% (9 requests) were made to Use.typekit.net and 5% (2 requests) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (679 ms) belongs to the original domain Tray.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.8 kB (15%)

Content Size

442.1 kB

After Optimization

377.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-70%

Potential reduce by 9.7 kB

  • Original 14.0 kB
  • After minification 12.9 kB
  • After compression 4.3 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 9.7 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 324.5 kB
  • After minification 324.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. Tray images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 55.1 kB

  • Original 103.7 kB
  • After minification 103.7 kB
  • After compression 48.5 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 55.1 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (33%)

Requests Now

30

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tray. 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 as a result speed up the page load time.

Network Requests Diagram

tray.io

tray.io

498 ms

tray.io

tray.io

679 ms

main.css

main.css

164 ms

ohx0hfv.js

ohx0hfv.js

208 ms

bugsnag-2.min.js

bugsnag-2.min.js

48 ms

135 ms

jquery.min.js

jquery.min.js

76 ms

init.min.js

init.min.js

244 ms

analytics.min.js

analytics.min.js

191 ms

tray.io

tray.io

48 ms

texture.png

texture.png

307 ms

logo@2x.png

logo@2x.png

106 ms

button-arrow.png

button-arrow.png

204 ms

browser-filled@2x.jpg

browser-filled@2x.jpg

511 ms

browser-filled-responsive@2x.jpg

browser-filled-responsive@2x.jpg

597 ms

illustration-1.png

illustration-1.png

279 ms

illustration-2.png

illustration-2.png

271 ms

illustration-3.png

illustration-3.png

334 ms

benefit-1.png

benefit-1.png

410 ms

benefit-2.png

benefit-2.png

409 ms

benefit-3.png

benefit-3.png

410 ms

press-logo.png

press-logo.png

425 ms

press-logo-light.png

press-logo-light.png

492 ms

channel.html

channel.html

51 ms

dLl26jSNwIrc_lFp6Es8Sh7J5_hNQQJoHBCKPAAkQgtffJLcMUMdeMJ6Mk6f5MI.woff

dLl26jSNwIrc_lFp6Es8Sh7J5_hNQQJoHBCKPAAkQgtffJLcMUMdeMJ6Mk6f5MI.woff

28 ms

gps6qmbrNCXD8fnecohs1iGyMqrBROzfrYpZFpECQPSffJWcMUMdeMJ6Mk6f5Mw.woff

gps6qmbrNCXD8fnecohs1iGyMqrBROzfrYpZFpECQPSffJWcMUMdeMJ6Mk6f5Mw.woff

54 ms

ZvIuXsLfIKAaLt5GpC_H1aU4nbPlaSOf3Gl0y_0_UK9ffJRcMUMdeMJ6Mk6f5M9.woff

ZvIuXsLfIKAaLt5GpC_H1aU4nbPlaSOf3Gl0y_0_UK9ffJRcMUMdeMJ6Mk6f5M9.woff

116 ms

zZU85xav7wnERnVcQnJCU_hthBO3CM8nFgWI5zNqoywffJdcMUMdeMJ6Mk6f5MS.woff

zZU85xav7wnERnVcQnJCU_hthBO3CM8nFgWI5zNqoywffJdcMUMdeMJ6Mk6f5MS.woff

128 ms

z2e5Kt26cgvYzGj7onpgGAGyprHbcyellIQINOs4e5jffJ1cMUMdeMJ6Mk6f5M6.woff

z2e5Kt26cgvYzGj7onpgGAGyprHbcyellIQINOs4e5jffJ1cMUMdeMJ6Mk6f5M6.woff

164 ms

KVSoBhzrCzhjzIizNeqz2Ck5az7a_Mahp7A59cHuNQtffHV3gsMdeMJ6Mk6f5Mb.woff

KVSoBhzrCzhjzIizNeqz2Ck5az7a_Mahp7A59cHuNQtffHV3gsMdeMJ6Mk6f5Mb.woff

163 ms

HtoYSVzeXRfn1VHNmwd0wQ_KH8H5OYRuB9zzbqrn0ejffH13gsMdeMJ6Mk6f5MS.woff

HtoYSVzeXRfn1VHNmwd0wQ_KH8H5OYRuB9zzbqrn0ejffH13gsMdeMJ6Mk6f5MS.woff

163 ms

q9wh2juz

q9wh2juz

77 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

64 ms

tracker.js

tracker.js

93 ms

44 ms

intercom.c5a1eeb5.js

intercom.c5a1eeb5.js

84 ms

p.gif

p.gif

182 ms

echo.515e8809.js

echo.515e8809.js

23 ms

ping

ping

94 ms

pv

pv

36 ms

Accessibility Review

tray.io accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tray.io SEO score

100

Search Engine Optimization Advices

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

tray.io

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