638 ms in total
25 ms
431 ms
182 ms
Visit inkind.com now to see the best up-to-date InKind content for United States and also check out these interesting facts you probably never knew about inkind.com
The app that gives you bonuses and exclusive perks at your favorite restaurants
Visit inkind.comWe analyzed Inkind.com page load time and found that the first response time was 25 ms and then it took 613 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
inkind.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value14.2 s
0/100
25%
Value14.6 s
1/100
10%
Value7,290 ms
0/100
30%
Value0.021
100/100
15%
Value39.7 s
0/100
10%
25 ms
28 ms
240 ms
11 ms
22 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Inkind.com, 8% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Neo.tildacdn.com. The less responsive or slowest element that took the longest time to load (244 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 623.4 kB (22%)
2.8 MB
2.2 MB
In fact, the total size of Inkind.com main page is 2.8 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 165.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. 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 165.1 kB or 86% of the original size.
Potential reduce by 113.3 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. InKind images are well optimized though.
Potential reduce by 265.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 265.5 kB or 68% of the original size.
Potential reduce by 79.4 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. Inkind.com needs all CSS files to be minified and compressed as it can save up to 79.4 kB or 85% of the original size.
Number of requests can be reduced by 23 (42%)
55
32
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of InKind. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
inkind.com
25 ms
inkind.com
28 ms
tilda-fallback-1.0.min.js
240 ms
tilda-grid-3.0.min.css
11 ms
tilda-blocks-page39437594.min.css
22 ms
highlight.min.css
20 ms
tilda-forms-1.0.min.css
20 ms
css2
41 ms
custom.css
20 ms
tilda-polyfill-1.0.min.js
23 ms
jquery-1.10.2.min.js
20 ms
tilda-scripts-3.0.min.js
22 ms
tilda-blocks-page39437594.min.js
28 ms
tilda-menu-1.0.min.js
28 ms
tilda-zero-1.1.min.js
28 ms
tilda-popup-1.0.min.js
28 ms
tilda-forms-1.0.min.js
28 ms
highlight.min.js
27 ms
tilda-zero-scale-1.0.min.js
30 ms
tilda-zero-video-1.0.min.js
30 ms
tilda-skiplink-1.0.min.js
29 ms
tilda-events-1.0.min.js
30 ms
privacy-modal.js
123 ms
snippet.js
116 ms
tilda-popup-1.1.min.css
3 ms
tild6330-3636-4730-b034-643264386235__inkind_logo.svg
165 ms
map
148 ms
tild3138-3533-4534-a662-613239616265__logo.svg
125 ms
tild6266-3163-4230-a165-383932653332__inkind_bg.png
129 ms
tild3963-3930-4363-a235-363134306161__zagat.png
126 ms
tild3134-3262-4336-a264-376562393930__wall_street_journal.png
126 ms
tild3230-3565-4263-b062-303432396135__washington_post.png
126 ms
tild6331-6336-4561-b563-383637363635__eater.png
128 ms
tild3863-3638-4034-b863-396666313530__forbes.png
128 ms
tild3532-3862-4065-b234-623231383432__robb_report.png
132 ms
tild3636-6262-4537-a130-376338373536__pay_with_phone.svg
131 ms
tild3230-3336-4563-b666-333231663130__earn_15_percent_back.svg
130 ms
tild6362-6635-4862-a130-393666366564__monthly_dining_bonus.svg
133 ms
tild3164-6462-4033-b366-313264333338__inkind_modal_header_.png
141 ms
tild6338-3663-4433-b936-313865633861__jose_andres_1.png
133 ms
tild6538-6437-4162-b332-613965646639__michael_mina.png
139 ms
tild3038-6165-4065-a636-616438313663__boqueria.png
135 ms
tild3336-3864-4163-b463-313534636231__hamptonsocial.png
139 ms
tild6335-3631-4632-a638-326236313961___images_toca-madera-.png
140 ms
tild3765-3265-4139-b365-343339336563__maman.png
141 ms
tild3235-6365-4165-b463-626330376264__inkind_review.png
146 ms
tild3237-3839-4238-b936-396330323332__inkind_review.png
147 ms
tild6339-3237-4166-b466-623732313261__inkind_app.png
182 ms
tild6435-3532-4931-b331-333839306564__logo.svg
144 ms
tild3032-3232-4639-b130-343334643063__apple.png
146 ms
tild3965-3835-4238-a333-656266373739__google.png
172 ms
tild6430-6362-4330-b935-326431316266__square-facebook.svg
179 ms
tild3738-6337-4564-a236-633366356539__instagram.svg
178 ms
tild3562-3338-4530-a532-623532383233__linkedin.svg
178 ms
tild3532-3431-4332-a462-346236363962__appinkind.svg
176 ms
tild6666-3462-4036-a266-616639383235__opt-out-svg.svg
177 ms
AMODz4SDuXOMCPfdoglY9JQuWHBGG0X45DmqkoZWCE3mma-bga0.woff
176 ms
AMODz4SDuXOMCPfdoglY9JQuWHBGG0X45DmqkuFWCE3mma-bga0.woff
201 ms
AMODz4SDuXOMCPfdoglY9JQuWHBGG0X45Dmqkr9WCE3mma-bga0.woff
209 ms
AMODz4SDuXOMCPfdoglY9JQuWHBGG0X45DmqklNRCE3mma-bga0.woff
240 ms
AMODz4SDuXOMCPfdoglY9JQuWHBGG0X45DmqkmFRCE3mma-bga0.woff
244 ms
fbevents.js
130 ms
tilda-forms-dict-1.0.min.js
73 ms
inkind.com accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
inkind.com 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
Missing source maps for large first-party JavaScript
inkind.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inkind.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 Inkind.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.
inkind.com
Open Graph data is detected on the main page of InKind. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: