2.7 sec in total
41 ms
2.4 sec
215 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 41 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
rebuild.charitybuzz.com performance score
41 ms
207 ms
94 ms
96 ms
100 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 4% of them (4 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 (792 ms) relates to the external source P.typekit.net.
Page size can be reduced by 182.1 kB (17%)
1.1 MB
886.2 kB
In fact, the total size of Rebuild.charitybuzz.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 801.4 kB which makes up the majority of the site volume.
Potential reduce by 143.5 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 143.5 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 29.3 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 8.8 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 72 (76%)
95
23
The browser has sent 95 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 62 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
rebuild.charitybuzz.com
41 ms
rebuild.charitybuzz.com
207 ms
font-awesome.min.css
94 ms
introjs.min.css
96 ms
slick.min.css
100 ms
slick-theme.css
107 ms
application-9d48c5d8.css
234 ms
jquery.min.js
123 ms
jquery-ui.min.js
120 ms
jquery.ui.touch-punch.min.js
108 ms
jquery.easing.min.js
109 ms
jquery.validate.min.js
106 ms
jquery.hoverIntent.min.js
117 ms
jquery.cookie.min.js
119 ms
jquery.transit.min.js
119 ms
jquery.expander.min.js
121 ms
lazyload.min.js
124 ms
jquery.countdown.min.js
125 ms
jquery-deparam.js
129 ms
jquery.form.min.js
125 ms
6b8f3a06bf.js
128 ms
modernizr.min.js
134 ms
underscore-min.js
134 ms
moment.min.js
130 ms
moment-timezone.min.js
135 ms
intro.min.js
134 ms
noframework.waypoints.min.js
138 ms
url-search-params.js
140 ms
pusher.min.js
145 ms
clipboard.min.js
146 ms
URI.min.js
147 ms
amplify.min.js
143 ms
handlebars.min.js
147 ms
optimize.js
116 ms
758ed9b26b06412c8e54441ae0392a1e.js.ubembed.com
138 ms
84 ms
api.js
97 ms
application-edaab39a10ebefdedb13.js
539 ms
application-core-75df2ff82f1b67134f98e00968ef3158996567a973820ba3e0c671b13d07d1d0.js
458 ms
application-vendor-c43dd4da1c027a33ffaf34cfbdabe5ee249e1bdb824d236df4ffa9e28f63922c.js
615 ms
firebase-app.js
83 ms
firebase-analytics.js
87 ms
firebase-messaging.js
91 ms
firebase-database.js
96 ms
application-9595f3b357d2c46ef155025cb90d21a6f1a36005806c68759384816476fca3c2.js
503 ms
index-f84c64635acd48474d3f07e53fffbc9e7da257a7d152f9bf1ff610056b8b9e85.js
478 ms
typeahead.bundle.min-99584d606a2fa7a34a9168007db8491e7c121211e4c5532fca6cd94fb08472a7.js
474 ms
autocomplete-4701fcd509dce846ca9f4f482c3a396bd4eb08f0cc68a434f6acf632a41ebe76.js
652 ms
index-41f5188e319799e14af65c134e7f8a9405a9ddf8a11f33ae985282a32f5ad08f.js
652 ms
validations-6251153cd3435c8576e389e3db1cd68a767ba2a6840a80e71ad4684a80262f1d.js
651 ms
password_fields-27e87dc54f331bbff605e88b75a3a1bfcdc38d550f3024346710dff685bcc496.js
652 ms
frd-3dfef553e95531d0725b267af39e60a0ad327219ab53ec567f47c663e051f027.js
747 ms
hide_or_show_facebook_login-6228f811b7dd5e02350417388dbea03015e6c763042b6aee81ff90b2b4da333f.js
689 ms
js
109 ms
css
84 ms
css2
19 ms
gpi0jzf.js
193 ms
bundle.js
87 ms
recaptcha__en.js
24 ms
analytics.js
358 ms
fbevents.js
47 ms
A3669491-43a7-45cb-bae7-07675ceaecb21.js
421 ms
cb-main_no_tagline-1fcbf5551720a566c09789b7e793d07eb2931ddde28edf54fa09c0ab06313d63.svg
357 ms
blank-25cf0f0ce42f8acd9ea6facc223f54105c7fd0cce63fb7bb5d83e6600100acbd.jpg
357 ms
cb-main_no_tagline_WHITE-35eafaee2fb1b5649a9380f7c2cf26611eb1c01211fc94eb077b139af74303b4.svg
352 ms
app-store-badge-55341f94f00e4f1e19283ef410df363f378b0b8e202f11fdfe3785aefc5df19a.svg
357 ms
google-play-badge-a6ae1f2b13ad1628bcdb2d2b74b2d674ecba4f5996cb8a80e6d257671b9e3e43.svg
354 ms
facebook_footer-169f132ee51b42e56671a2efa1b9f696e459232b3298f64d80bc940f2b170635.svg
353 ms
twitter_footer-aeccbbf293f4e961a37cb1545bf3d9f684ed70fd28171c3ceb2a43b64b9b679f.svg
418 ms
instagram_footer-f9894cc142c0e5310b023186e5ed0426cd1a571e327cd9b54373ed8ce49afab3.svg
416 ms
cn-logo-3d349d75f7ef885d575a1a74fa42581a72144206e1cd7ba542b7ea46d780e291.svg
412 ms
PRIZEO_LOGO-85fd1e48f19e685ddc766b40aa1bf6d404b51a4a6589514d2dcb8b35e9f5b048.svg
414 ms
fontawesome-webfont.woff
86 ms
widgets.js
438 ms
1927195054276461
295 ms
rum.js
403 ms
js
305 ms
js
397 ms
gtm.js
396 ms
389 ms
channel.html
105 ms
d
105 ms
d
151 ms
d
370 ms
d
274 ms
get_carousel.json
330 ms
collect
73 ms
collect
341 ms
js
267 ms
p.gif
792 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
426 ms
collect
359 ms
js
295 ms
index-vendor.css
225 ms
application-0da183b5bd1c44a9111ed1de524dff444717c0604f8efbac14695289b03d17b9.css
401 ms
224 ms
settings
229 ms
index-b4c43d79b6cddb55c2815541fb676ca072c61b4f4693e612312e0a906776ba0d.css
158 ms
application-0da183b5bd1c44a9111ed1de524dff444717c0604f8efbac14695289b03d17b9.css
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
45 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
44 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf
45 ms
index-b4c43d79b6cddb55c2815541fb676ca072c61b4f4693e612312e0a906776ba0d.css
45 ms
outer.html
84 ms
record-data
134 ms
inner.html
57 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: