2.1 sec in total
106 ms
1.8 sec
196 ms
Welcome to rebuild1.com homepage info - get ready to check Rebuild 1 best content for United States right away, or after learning these important things about rebuild1.com
Our large salvage dealer inventory makes finding your rebuildable or ready to drive vehicle easy and affordable. Search by type or make now.
Visit rebuild1.comWe analyzed Rebuild1.com page load time and found that the first response time was 106 ms and then it took 2 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.
rebuild1.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value6.5 s
9/100
25%
Value9.2 s
13/100
10%
Value1,140 ms
22/100
30%
Value0.964
2/100
15%
Value15.7 s
6/100
10%
106 ms
79 ms
876 ms
73 ms
103 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 83% of them (70 requests) were addressed to the original Rebuild1.com, 6% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Rebuild1.com.
Page size can be reduced by 138.9 kB (17%)
834.0 kB
695.0 kB
In fact, the total size of Rebuild1.com main page is 834.0 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. 50% of websites need less resources to load. Images take 367.4 kB which makes up the majority of the site volume.
Potential reduce by 49.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. This page needs HTML code to be minified as it can gain 16.1 kB, which is 28% 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 49.1 kB or 87% of the original size.
Potential reduce by 3.1 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. Rebuild 1 images are well optimized though.
Potential reduce by 85.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 85.8 kB or 24% of the original size.
Potential reduce by 887 B
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. Rebuild1.com has all CSS files already compressed.
Number of requests can be reduced by 28 (38%)
74
46
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rebuild 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
rebuild1.com
106 ms
www.rebuild1.com
79 ms
www.rebuild1.com
876 ms
bootstrap.css
73 ms
bootstrap-theme.css
103 ms
style.css
140 ms
color1.css
101 ms
modernizr.js
104 ms
adsbygoogle.js
53 ms
js
50 ms
jquery-2.0.0.min.js
143 ms
prettyphoto.js
105 ms
ui-plugins.js
169 ms
helper-plugins.js
170 ms
owl.carousel.min.js
135 ms
password-checker.js
143 ms
bootstrap.js
170 ms
init.js
171 ms
jquery.flexslider.js
175 ms
signup-form-widget.min.js
37 ms
font-awesome.css
37 ms
line-icons.css
66 ms
animations.css
68 ms
css
28 ms
css
43 ms
css
46 ms
logo2.png
128 ms
search.jpg
126 ms
car.jpg
127 ms
truck.jpg
126 ms
cycle.jpg
128 ms
rv.jpg
128 ms
misc.jpg
129 ms
rebuild.jpg
131 ms
readytodrive.jpg
128 ms
clean.jpg
130 ms
11-chevy.jpg
130 ms
11-dodge.jpg
129 ms
11-ford.jpg
131 ms
11-gmc.jpg
132 ms
11-honda.jpg
133 ms
11-jeep.jpg
132 ms
11-nissan.jpg
131 ms
11-toyota.jpg
132 ms
11-allmakes.jpg
146 ms
301287-(1).jpg
147 ms
168942-0.jpg
148 ms
172602-0.jpg
148 ms
202060-(1).jpg
149 ms
201761-(1).jpg
148 ms
img_3633-(medium).jpg
172 ms
171311-0.jpg
171 ms
nophoto-600.jpg
173 ms
159597-0.jpg
172 ms
172294-0.jpg
171 ms
159699-0.jpg
172 ms
dscn6190_001.jpg
203 ms
make3.jpg
202 ms
rebuild2.jpg
202 ms
readytodrive2.jpg
202 ms
clean2.jpg
200 ms
slotcar_library.js
89 ms
search2.jpg
79 ms
car2.jpg
111 ms
truck2.jpg
112 ms
suv2.jpg
111 ms
cycle2.jpg
110 ms
misc2.jpg
111 ms
r1ad2.jpg
111 ms
icon-price.png
140 ms
icon-miles.png
140 ms
KFOmCnqEu92Fr1Mu4mxM.woff
30 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
31 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
35 ms
fontawesome-webfont.woff
253 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff
41 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff
45 ms
outlined-iconset.woff
136 ms
prettyPhoto.css
113 ms
owl.carousel.css
114 ms
owl.theme.css
141 ms
custom.css
140 ms
underscore-min.js
25 ms
api.js
31 ms
rebuild1.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rebuild1.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
Browser errors were logged to the console
Page has valid source maps
rebuild1.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rebuild1.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Rebuild1.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.
rebuild1.com
Open Graph description is not detected on the main page of Rebuild 1. 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: