5.2 sec in total
682 ms
2.8 sec
1.7 sec
Click here to check amazing Tillo content for United States. Otherwise, check out these important facts you probably never knew about tillo.io
Streamline your rewards, incentives and gift card management with Tillo’s user-friendly platform. Access 2000+ brands and discover new ways to grow.
Visit tillo.ioWe analyzed Tillo.io page load time and found that the first response time was 682 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tillo.io performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.6 s
35/100
25%
Value8.2 s
20/100
10%
Value3,390 ms
2/100
30%
Value0.018
100/100
15%
Value17.5 s
4/100
10%
682 ms
55 ms
73 ms
89 ms
78 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 72% of them (104 requests) were addressed to the original Tillo.io, 6% (8 requests) were made to Cdnjs.cloudflare.com and 3% (5 requests) were made to 6207949.fs1.hubspotusercontent-na1.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source 6207949.fs1.hubspotusercontent-na1.net.
Page size can be reduced by 418.1 kB (32%)
1.3 MB
895.8 kB
In fact, the total size of Tillo.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. 65% of websites need less resources to load. Images take 689.6 kB which makes up the majority of the site volume.
Potential reduce by 408.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 130.3 kB, which is 29% 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 408.2 kB or 90% of the original size.
Potential reduce by 470 B
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. Tillo images are well optimized though.
Potential reduce by 6.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.
Potential reduce by 3.0 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. Tillo.io needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 15% of the original size.
Number of requests can be reduced by 74 (53%)
139
65
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tillo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.tillo.io
682 ms
main.min.css
55 ms
theme-overrides.min.css
73 ms
module_134720085077_menu-new.min.css
89 ms
module_121307012197_button.min.css
78 ms
module_-35056501883_Video.min.css
108 ms
module_85504883732_brand-carousel-gradient.min.css
79 ms
owl.carousel.css
78 ms
owl.theme.default.min.css
83 ms
module_123617950244_footer-button.min.css
310 ms
module_123611935060_footer-menu.min.css
112 ms
module_-98251788440_Image_Grid.min.css
134 ms
basicLightbox.min.css
76 ms
module_121309289508_social-follow.min.css
109 ms
jquery-3.6.0.min.js
77 ms
gsap.min.js
84 ms
ScrollTrigger.min.js
87 ms
DrawSVGPlugin.min.js
107 ms
MotionPathPlugin.min.js
78 ms
core.min.js
78 ms
embed.js
84 ms
main.min.js
108 ms
umbrella.min.js
127 ms
typewriter.min.js
142 ms
blend-gradient.min.js
150 ms
project.js
152 ms
jquery.js
153 ms
ma5-menu.min.js
166 ms
desktop-menu-fixed-v4.js
164 ms
module_-35056501883_Video.min.js
146 ms
loader.js
99 ms
module_85504883732_brand-carousel-gradient.min.js
200 ms
owl.carousel.min.js
88 ms
v2.js
211 ms
module_-98251788440_Image_Grid.min.js
127 ms
fitty.min.js
84 ms
basicLightbox.min.js
73 ms
6207949.js
212 ms
index.js
184 ms
gtm.js
435 ms
fbevents.js
391 ms
hotjar-3709179.js
483 ms
gcav-service-provider-award-2023.png
473 ms
logo-main-actually-white@3x.svg
441 ms
buyer-hub.svg
357 ms
brand-hub.svg
357 ms
gift-card-api.svg
354 ms
digital-assets.svg
359 ms
consumer-experience.svg
357 ms
bulk-buy.svg
772 ms
features.svg
402 ms
use-cases.svg
400 ms
digital-gift-cards.svg
403 ms
consumer-card-%20programs.svg
402 ms
government-and-charity.svg
459 ms
storefront.svg
466 ms
choicelink.svg
469 ms
wrappr.svg
460 ms
buy-now-pay-later.svg
477 ms
cashback.svg
480 ms
crypto-and-blockchain.svg
484 ms
employee-rewards-and-recognition.svg
496 ms
loyalty-programmes.svg
493 ms
neobanks-and-challenger-banks.svg
504 ms
open-banking-and-embedded-finance.svg
502 ms
retailers.svg
509 ms
customer-stories.svg
520 ms
about-us.svg
523 ms
careers.svg
532 ms
engineering-hub.svg
569 ms
contact-us.svg
675 ms
api-ocumentation.svg
552 ms
blog.svg
560 ms
guides.svg
564 ms
webinars.svg
575 ms
wild-cards-podcast.svg
606 ms
events.svg
594 ms
cta-pointer.svg
598 ms
g2-easiest-to-use-fall-2023.png
1200 ms
g2-user-adoption-fall-2023.png
1377 ms
g2-high-performer-europe-fall-2023.png
552 ms
27001%20RGB%20White.png
604 ms
insight.min.js
346 ms
50cd6c345fcf00fa.min.js
628 ms
Revolut%20logo.svg
555 ms
collectedforms.js
311 ms
6207949.js
318 ms
web-interactives-embed.js
309 ms
fb.js
323 ms
6207949.js
427 ms
regular.woff
272 ms
300.woff
285 ms
700.woff
319 ms
900.woff
321 ms
regular.woff
288 ms
Banked%20logo.svg
354 ms
wagestream%20logo.svg
319 ms
fluz.svg
352 ms
coingate%20logo.svg
304 ms
honey.svg
298 ms
modules.a4fd7e5489291affcf56.js
23 ms
insight_tag_errors.gif
95 ms
reward%20gateway.svg
333 ms
Edenred.svg
339 ms
Bitrefill.svg
337 ms
paypal%20logo.svg
359 ms
sprive%20logo.svg
373 ms
Tillo%20shapes%20set%201.png
325 ms
shape%20set%202.svg
361 ms
Tillo%20API%20sample%20code%20V2.png
396 ms
reporting-3.png
1061 ms
2.svg
382 ms
Airbnb.svg
388 ms
4.svg
414 ms
5.svg
394 ms
6.svg
407 ms
7.svg
459 ms
8.svg
435 ms
9.svg
434 ms
10.svg
428 ms
11.svg
422 ms
12.svg
429 ms
13.svg
431 ms
14.svg
441 ms
15.svg
450 ms
16.svg
431 ms
17.svg
402 ms
18.svg
431 ms
19.svg
631 ms
21.svg
586 ms
22.svg
707 ms
live%20demo-1.png
409 ms
lapis-pointer.svg
461 ms
social-linkedin.svg
457 ms
sync
64 ms
x-twitter-icon.svg
585 ms
social-instagram.svg
444 ms
social-facebook.svg
472 ms
ip.json
102 ms
social-youtube.svg
492 ms
sync
45 ms
tap.php
44 ms
log
66 ms
js
56 ms
rum
34 ms
tillo.io accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
tillo.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tillo.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tillo.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 Tillo.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.
tillo.io
Open Graph data is detected on the main page of Tillo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: