2.9 sec in total
65 ms
2.7 sec
147 ms
Welcome to 101collisioncenter.com homepage info - get ready to check 101 Collision Center best content right away, or after learning these important things about 101collisioncenter.com
Serving the South Bay Area since 1994, 101 Collision Center is open to serve all of your collision repair needs! Being I-CAR Gold certified & Tesla Approved..
Visit 101collisioncenter.comWe analyzed 101collisioncenter.com page load time and found that the first response time was 65 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
101collisioncenter.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value16.4 s
0/100
25%
Value9.1 s
13/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value15.3 s
7/100
10%
65 ms
62 ms
8 ms
14 ms
88 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 101collisioncenter.com, 38% (30 requests) were made to Nebula.wsimg.com and 29% (23 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Nebula.wsimg.com.
Page size can be reduced by 657.1 kB (2%)
26.6 MB
26.0 MB
In fact, the total size of 101collisioncenter.com main page is 26.6 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. Images take 26.2 MB which makes up the majority of the site volume.
Potential reduce by 75.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 75.4 kB or 79% of the original size.
Potential reduce by 413.8 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. 101 Collision Center images are well optimized though.
Potential reduce by 73.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 73.4 kB or 41% of the original size.
Potential reduce by 94.5 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. 101collisioncenter.com needs all CSS files to be minified and compressed as it can save up to 94.5 kB or 84% of the original size.
Number of requests can be reduced by 23 (34%)
68
45
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 101 Collision Center. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
www.101collisioncenter.com
65 ms
site.css
62 ms
duel.js
8 ms
addthis_widget.js
14 ms
scc-c2.min.js
88 ms
jq.js
28 ms
form.js
39 ms
2d4ac585f9b2349e7696d08bfe5cee9f
342 ms
facebookSDKHelper.js
27 ms
mapbox.js
25 ms
media.gallery.js
25 ms
cookiemanager.js
127 ms
iebackground.js
22 ms
30a37252a90a750c22c39b27f9b41545
690 ms
e8914133d43fc7f90de8efbaba9c6a9d
314 ms
ea9270fd36c31bef07f3203e9179a8d6
8 ms
16297df1fd9ab7d8049aaacabd646bf1
373 ms
eb4586437553c0a6881ebb0a42aba9e4
402 ms
e4f1411802f34d18ca06def8d8ee3915
291 ms
66280f94b937db011631ad7b617504ef
864 ms
6c248ca96aeda0bcd1cb463cb1111c4e
324 ms
5da4f5b5cc33c76e54f0eeff4a836e43
581 ms
1bba5bd41033db2fdb92202221f622ff
500 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
20 ms
helper.js
21 ms
mapbox.js
7 ms
mapbox.css
7 ms
util.instances.js
14 ms
util.model.js
6 ms
documentHelper.js
75 ms
util.fbSDKLoader.js
12 ms
util.window.js
17 ms
regexhelper.js
17 ms
api.guid.js
25 ms
jquery.xDomainRequest.js
24 ms
mapbox.js
19 ms
mapbox.css
18 ms
growl.js
28 ms
browser.js
21 ms
icons.svg
26 ms
streets-v11
13 ms
marker-icon.png
35 ms
sf.core.pkg.js
28 ms
1588
122 ms
1589
156 ms
1588
141 ms
1588
217 ms
1589
275 ms
1589
147 ms
marker-shadow.png
34 ms
mapbox.mapbox-streets-v8,mapbox.mapbox-terrain-v2.json
160 ms
80f8f748de36696d44249e9bfe56b4e0
996 ms
5e8bdc757c6439df9ee9d431a9ea08a8
1097 ms
5d6d84294a83879fee696d6502c289b8
1003 ms
3bae93ae9732d883f38f648beffe1e5d
1201 ms
marker-icon.png
13 ms
app.css
12 ms
marker-shadow.png
8 ms
sdk.js
10 ms
sdk.js
5 ms
page.php
35 ms
66 ms
7027af6fbd4df7ef8f18f4e0d8942a63
473 ms
0dac37d0038b4d00a1e6e53a7e0473cc
234 ms
e9b6a421593f2aafb75ef1e9465a1b93
327 ms
51f1efd0f3d4521e2bee6b4c5be46c0f
688 ms
e223d4328e134ccb10ee4a73ed3b84fd
526 ms
126a48227484374e73e2d5676af31897
459 ms
3ff1b6269a57ee172dedd24725798efb
766 ms
f4c88b074a0a7a97c3a22840c616b3bd
668 ms
05111c5adde0449926824ffa6fd14794
835 ms
97857882c8f9140a9ee62f1f6e2a3cfd
704 ms
7861896ed8da1a7a4d53e999dd92449c
819 ms
5c843f30061490a8f183264e7b42e2cb
1004 ms
5cbad12b00501f98e5d26f0b4d4657ce
948 ms
4cebca492b9a2fc4fcc1cc6e8c05cff5
1151 ms
5cb8e32387b5a90db35d6b5ad1ea0443
1036 ms
101collisioncenter.com accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
101collisioncenter.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
101collisioncenter.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 101collisioncenter.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 101collisioncenter.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.
101collisioncenter.com
Open Graph data is detected on the main page of 101 Collision Center. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: