1.6 sec in total
17 ms
1.5 sec
137 ms
Visit rebuild.charitybuzz.com now to see the best up-to-date Rebuild Charitybuzz content for United States and also check out these interesting facts you probably never knew about rebuild.charitybuzz.com
Bid on unique and extraordinary experiences while supporting charity. Hang out with your favorite celebrity, or go on a dream vacation.
Visit rebuild.charitybuzz.comWe analyzed Rebuild.charitybuzz.com page load time and found that the first response time was 17 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 35% of websites can load faster.
rebuild.charitybuzz.com performance score
17 ms
153 ms
62 ms
59 ms
82 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Rebuild.charitybuzz.com, 26% (28 requests) were made to Cdnjs.cloudflare.com and 25% (27 requests) were made to Dh14kvn94lo27.cloudfront.net. The less responsive or slowest element that took the longest time to load (403 ms) relates to the external source Dh14kvn94lo27.cloudfront.net.
Page size can be reduced by 280.1 kB (24%)
1.2 MB
900.8 kB
In fact, the total size of Rebuild.charitybuzz.com main page is 1.2 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. Javascripts take 974.3 kB which makes up the majority of the site volume.
Potential reduce by 93.4 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 93.4 kB or 82% of the original size.
Potential reduce by 346 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. Obviously, Rebuild Charitybuzz needs image optimization as it can save up to 346 B or 55% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 177.8 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 177.8 kB or 18% of the original size.
Potential reduce by 8.6 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. Rebuild.charitybuzz.com has all CSS files already compressed.
Number of requests can be reduced by 69 (73%)
94
25
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rebuild Charitybuzz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
rebuild.charitybuzz.com
17 ms
rebuild.charitybuzz.com
153 ms
font-awesome.min.css
62 ms
introjs.min.css
59 ms
slick.min.css
82 ms
slick-theme.css
74 ms
application-9d48c5d8.css
118 ms
jquery.min.js
77 ms
jquery-ui.min.js
78 ms
jquery.ui.touch-punch.min.js
80 ms
jquery.easing.min.js
78 ms
jquery.validate.min.js
89 ms
jquery.hoverIntent.min.js
86 ms
jquery.cookie.min.js
91 ms
jquery.transit.min.js
89 ms
jquery.expander.min.js
152 ms
lazyload.min.js
91 ms
jquery.countdown.min.js
99 ms
jquery-deparam.js
100 ms
jquery.form.min.js
97 ms
6b8f3a06bf.js
76 ms
modernizr.min.js
106 ms
underscore-min.js
104 ms
moment.min.js
107 ms
moment-timezone.min.js
111 ms
intro.min.js
111 ms
noframework.waypoints.min.js
113 ms
url-search-params.js
149 ms
pusher.min.js
149 ms
clipboard.min.js
180 ms
URI.min.js
181 ms
amplify.min.js
181 ms
handlebars.min.js
184 ms
optimize.js
93 ms
758ed9b26b06412c8e54441ae0392a1e.js.ubembed.com
84 ms
59 ms
api.js
68 ms
application-e0a8a7c1e6fc358d2ada.js
343 ms
application-core-75df2ff82f1b67134f98e00968ef3158996567a973820ba3e0c671b13d07d1d0.js
256 ms
application-vendor-c43dd4da1c027a33ffaf34cfbdabe5ee249e1bdb824d236df4ffa9e28f63922c.js
403 ms
firebase-app.js
58 ms
firebase-analytics.js
62 ms
firebase-messaging.js
67 ms
firebase-database.js
76 ms
css
73 ms
application-9595f3b357d2c46ef155025cb90d21a6f1a36005806c68759384816476fca3c2.js
253 ms
index-f84c64635acd48474d3f07e53fffbc9e7da257a7d152f9bf1ff610056b8b9e85.js
253 ms
typeahead.bundle.min-99584d606a2fa7a34a9168007db8491e7c121211e4c5532fca6cd94fb08472a7.js
293 ms
autocomplete-4701fcd509dce846ca9f4f482c3a396bd4eb08f0cc68a434f6acf632a41ebe76.js
294 ms
index-90ce604f78d5cda7cd6e0707a49a87392c2ac417e74e5f37b5e0561f11d4274e.js
300 ms
validations-6251153cd3435c8576e389e3db1cd68a767ba2a6840a80e71ad4684a80262f1d.js
311 ms
password_fields-27e87dc54f331bbff605e88b75a3a1bfcdc38d550f3024346710dff685bcc496.js
378 ms
frd-3dfef553e95531d0725b267af39e60a0ad327219ab53ec567f47c663e051f027.js
379 ms
hide_or_show_facebook_login-6228f811b7dd5e02350417388dbea03015e6c763042b6aee81ff90b2b4da333f.js
379 ms
js
89 ms
css2
20 ms
gpi0jzf.js
95 ms
bundle.js
61 ms
recaptcha__en.js
15 ms
analytics.js
268 ms
fbevents.js
266 ms
A3669491-43a7-45cb-bae7-07675ceaecb21.js
271 ms
cb-main_no_tagline-1fcbf5551720a566c09789b7e793d07eb2931ddde28edf54fa09c0ab06313d63.svg
260 ms
blank-25cf0f0ce42f8acd9ea6facc223f54105c7fd0cce63fb7bb5d83e6600100acbd.jpg
261 ms
cb-main_no_tagline_WHITE-35eafaee2fb1b5649a9380f7c2cf26611eb1c01211fc94eb077b139af74303b4.svg
262 ms
app-store-badge-55341f94f00e4f1e19283ef410df363f378b0b8e202f11fdfe3785aefc5df19a.svg
260 ms
google-play-badge-a6ae1f2b13ad1628bcdb2d2b74b2d674ecba4f5996cb8a80e6d257671b9e3e43.svg
261 ms
facebook_footer-169f132ee51b42e56671a2efa1b9f696e459232b3298f64d80bc940f2b170635.svg
258 ms
twitter_footer-aeccbbf293f4e961a37cb1545bf3d9f684ed70fd28171c3ceb2a43b64b9b679f.svg
363 ms
instagram_footer-f9894cc142c0e5310b023186e5ed0426cd1a571e327cd9b54373ed8ce49afab3.svg
362 ms
cn-logo-3d349d75f7ef885d575a1a74fa42581a72144206e1cd7ba542b7ea46d780e291.svg
358 ms
PRIZEO_LOGO-85fd1e48f19e685ddc766b40aa1bf6d404b51a4a6589514d2dcb8b35e9f5b048.svg
361 ms
fontawesome-webfont.woff
151 ms
widgets.js
336 ms
rum.js
341 ms
gtm.js
316 ms
catalog_items
273 ms
channel.html
75 ms
d
76 ms
d
171 ms
d
196 ms
d
218 ms
get_carousel.json
191 ms
230 ms
js
174 ms
1927195054276461
82 ms
collect
70 ms
collect
101 ms
d
145 ms
p.gif
141 ms
index-vendor.css
68 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
47 ms
js
98 ms
settings
168 ms
index-vendor.css
130 ms
application-2508c51b4457db29b525ca01508d785a11a785fc639718f9f95d6e9b463fcb49.css
243 ms
collect
22 ms
80 ms
index-b4c43d79b6cddb55c2815541fb676ca072c61b4f4693e612312e0a906776ba0d.css
77 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
38 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
37 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aXw.woff
43 ms
index-b4c43d79b6cddb55c2815541fb676ca072c61b4f4693e612312e0a906776ba0d.css
46 ms
outer.html
44 ms
record-data
90 ms
inner.html
73 ms
rebuild.charitybuzz.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rebuild.charitybuzz.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 Rebuild.charitybuzz.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.
rebuild.charitybuzz.com
Open Graph description is not detected on the main page of Rebuild Charitybuzz. 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: