1.6 sec in total
46 ms
996 ms
575 ms
Click here to check amazing Tendr content for United States. Otherwise, check out these important facts you probably never knew about tendr.com
Visit tendr.comWe analyzed Tendr.com page load time and found that the first response time was 46 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
tendr.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
46 ms
81 ms
52 ms
306 ms
100 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 82% of them (83 requests) were addressed to the original Tendr.com, 7% (7 requests) were made to Ajax.googleapis.com and 3% (3 requests) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Cloud.typography.com.
Page size can be reduced by 744.7 kB (17%)
4.3 MB
3.5 MB
In fact, the total size of Tendr.com main page is 4.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. 70% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 32.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 5.9 kB, which is 14% 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 32.2 kB or 79% of the original size.
Potential reduce by 50.4 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. Tendr images are well optimized though.
Potential reduce by 467.0 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 467.0 kB or 70% of the original size.
Potential reduce by 195.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. Tendr.com needs all CSS files to be minified and compressed as it can save up to 195.0 kB or 88% of the original size.
Number of requests can be reduced by 28 (29%)
98
70
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tendr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
tendr.com
46 ms
tendr.com
81 ms
tracker.js
52 ms
1508940005.js
306 ms
jquery.min.js
100 ms
angular.min.js
119 ms
angular-route.min.js
132 ms
angular-animate.js
140 ms
angular-resource.min.js
142 ms
angular-touch.min.js
141 ms
angular-cookies.min.js
141 ms
matchMedia.js
27 ms
TweenMax.min.js
78 ms
angular-dropdowns.min.js
35 ms
services.js
52 ms
controllers.js
75 ms
editCardController.js
75 ms
filters.js
52 ms
directives.js
73 ms
animation.js
53 ms
angular-post-message.js
52 ms
app.js
66 ms
88 ms
tokenization.v2.js
168 ms
jquery.ui.widget.js
73 ms
jquery.iframe-transport.js
71 ms
jquery.fileupload.js
91 ms
jquery.mCustomScrollbar.concat.min.js
81 ms
jquery.imgareaselect.min.js
79 ms
tendr.css
104 ms
jquery.mCustomScrollbar.css
86 ms
fonts.css
394 ms
logo-white.png
7 ms
221FAFF57E6817FC8.css
9 ms
small_arrow.png
9 ms
Facebook_Icon.png
64 ms
Twitter_Icon.png
64 ms
Tumblr_Icon.png
63 ms
Step1.png
64 ms
Step3.png
64 ms
arrow-up.png
63 ms
ga.js
201 ms
homepage_sbb.html
10 ms
bullet-check.png
184 ms
Step2.jpg
187 ms
channel.html
185 ms
93 ms
foot1.html
24 ms
tendr_fb.png
26 ms
tendr_twitter.png
27 ms
logo.png
28 ms
mobile_menu_icon.png
29 ms
tendr_heart.png
29 ms
Money_iPad.jpg
50 ms
Wedding_Landing.png
59 ms
Card_and_Env.jpg
57 ms
Yay_Card.jpg
55 ms
Rulers_Card.jpg
54 ms
ScreechOwl_Card.jpg
55 ms
Lovebirds_Card.jpg
82 ms
AccountPage.jpg
85 ms
100LC_Grey.png
83 ms
RS_Grey.png
83 ms
SMP_Grey.png
83 ms
Glamour_Grey.png
85 ms
USAToday_Grey.png
85 ms
Brides_Grey.png
86 ms
Baby_Landing.png
120 ms
Baby_Card_Env.jpg
112 ms
yay_for_love.png
120 ms
gift_for_you.png
119 ms
hooray.jpg
120 ms
multiple_birds.jpg
116 ms
Grad_Landing.png
130 ms
PartyTime_Card_and_Env.jpg
129 ms
Fancy_Congrats_Card.jpg
141 ms
Haleluyeah_Card.jpg
153 ms
Hooray_Card.jpg
153 ms
Red_Congrats_Card.jpg
139 ms
Mitzvah_Landing.png
182 ms
33 ms
Mitzvah_Card_and_Env.jpg
174 ms
Blue_Congrats_Card.jpg
169 ms
Mazel_Star_Card.jpg
164 ms
Challah_Card.jpg
166 ms
Yay_Card_normal.jpg
170 ms
close-button.png
175 ms
WeddingHero1.jpg
203 ms
__utm.gif
19 ms
GradHero1.jpg
186 ms
__utm.gif
16 ms
Baby_Hero2.jpg
180 ms
Mitzvah_Homepage.jpg
182 ms
wait_spinner.gif
167 ms
tip_arrow.png
178 ms
Plus_Button.png
178 ms
wepay-logo.png
177 ms
pricing-A.png
158 ms
pricing-B.png
159 ms
pricing-stripe-A.png
159 ms
pricing-stripe-B.png
160 ms
tendr.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
Document doesn't have a <title> element
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
tendr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
tendr.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tendr.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Tendr.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.
tendr.com
Open Graph description is not detected on the main page of Tendr. 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: