2.4 sec in total
238 ms
2 sec
128 ms
Visit rebuild.org now to see the best up-to-date Rebuild content and also check out these interesting facts you probably never knew about rebuild.org
Visit rebuild.orgWe analyzed Rebuild.org page load time and found that the first response time was 238 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
rebuild.org performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value2.1 s
96/100
25%
Value2.6 s
97/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.0 s
100/100
10%
238 ms
414 ms
154 ms
163 ms
248 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 56% of them (28 requests) were addressed to the original Rebuild.org, 8% (4 requests) were made to Pagead2.googlesyndication.com and 8% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Rebuild.org.
Page size can be reduced by 94.7 kB (22%)
424.5 kB
329.9 kB
In fact, the total size of Rebuild.org main page is 424.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 252.6 kB which makes up the majority of the site volume.
Potential reduce by 10.6 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 10.6 kB or 71% of the original size.
Potential reduce by 489 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. Rebuild images are well optimized though.
Potential reduce by 78.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 78.4 kB or 52% of the original size.
Potential reduce by 5.1 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.org needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 78% of the original size.
Number of requests can be reduced by 23 (49%)
47
24
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rebuild. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
rebuild.org
238 ms
www.rebuild.org
414 ms
common.css
154 ms
common.js
163 ms
jquery-1.3.2.min.js
248 ms
fl.js
8 ms
webtrends.min.js
265 ms
rate_box.htm
258 ms
ico_facebook.gif
259 ms
header.jpg
368 ms
corner-bt.gif
171 ms
menu-i-b.gif
257 ms
menu-mortgage.jpg
400 ms
menu-dconsolidation.jpg
491 ms
menu-personal.jpg
492 ms
menu-auto.jpg
504 ms
menu-payday.jpg
425 ms
square-orange.gif
497 ms
text_ifyouare.gif
646 ms
debt-box.jpg
741 ms
1px.gif
661 ms
personal-box.jpg
976 ms
mortgage-box.jpg
904 ms
auto-box.jpg
836 ms
payday-box.jpg
1083 ms
text-aboutreb.gif
838 ms
text-statescover.gif
902 ms
g.js
134 ms
i0.html
119 ms
ga.js
27 ms
__utm.gif
11 ms
rateTableFormStartHeader.gif
828 ms
rateTableFormStartButton.gif
826 ms
wtid.js
131 ms
p.gif
101 ms
show_ads.js
4 ms
zrt_lookup.html
20 ms
show_ads_impl.js
50 ms
ads
309 ms
osd.js
17 ms
dcs.gif
133 ms
dcs.gif
143 ms
m_js_controller.js
16 ms
abg.js
30 ms
favicon
49 ms
googlelogo_color_112x36dp.png
46 ms
nessie_icon_tiamat_white.png
27 ms
s
12 ms
x_button_blue2.png
3 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
2 ms
rebuild.org 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
<frame> or <iframe> elements do not have a title
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
rebuild.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
rebuild.org 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
N/A
UTF8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rebuild.org 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Rebuild.org main page’s claimed encoding is utf8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
rebuild.org
Open Graph description is not detected on the main page of Rebuild. 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: