3.7 sec in total
820 ms
2.1 sec
807 ms
Welcome to sanleandrohonda.com homepage info - get ready to check San Leandro Honda best content for United States right away, or after learning these important things about sanleandrohonda.com
Shop for new Hondas or pre-owned cars in San Leandro Honda. We also offer certified Honda parts and car repair and service. Near Hayward Oakland Castro Valley Alameda Fremont San Francisco California.
Visit sanleandrohonda.comWe analyzed Sanleandrohonda.com page load time and found that the first response time was 820 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
sanleandrohonda.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value11.3 s
0/100
25%
Value6.8 s
34/100
10%
Value1,940 ms
8/100
30%
Value0.002
100/100
15%
Value16.1 s
6/100
10%
820 ms
19 ms
21 ms
26 ms
22 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Sanleandrohonda.com, 59% (74 requests) were made to Static.dealer.com and 14% (17 requests) were made to Pictures.dealer.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Sanleandrohonda.com.
Page size can be reduced by 894.1 kB (23%)
4.0 MB
3.1 MB
In fact, the total size of Sanleandrohonda.com main page is 4.0 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. 75% 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 121.0 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 121.0 kB or 84% of the original size.
Potential reduce by 38.9 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. San Leandro Honda images are well optimized though.
Potential reduce by 587.2 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 587.2 kB or 67% of the original size.
Potential reduce by 146.9 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. Sanleandrohonda.com needs all CSS files to be minified and compressed as it can save up to 146.9 kB or 84% of the original size.
Number of requests can be reduced by 45 (37%)
122
77
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of San Leandro Honda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.sanleandrohonda.com
820 ms
combo.css
19 ms
widget.css
21 ms
variation.css
26 ms
blue_white.css
22 ms
custom.css
140 ms
newrelic.js
21 ms
modernizr-2.6.2.min.js
19 ms
jquery-ui.css
10 ms
default.css
12 ms
print.css
10 ms
pxa.min.js
7 ms
pixall.min.js
7 ms
site-bg.png
61 ms
iframe.php
156 ms
74ccd743391a325767476ffd8e95855ex.jpg
125 ms
buttonblock.jpg
269 ms
main-top-bg.jpg
50 ms
search-bg-right.png
39 ms
search-bg.png
29 ms
freeform-bg.png
43 ms
btn-xsmall.png
41 ms
btn-xsmall-right.png
41 ms
nav-bg-left.png
43 ms
nav-bg.png
46 ms
nav-divider.png
44 ms
dropdown-bottom.png
43 ms
dropdown-top.png
45 ms
dropdown-repeat.png
47 ms
page-top.png
47 ms
main-bottom-bg.png
48 ms
page-center.png
49 ms
prev-btn.png
109 ms
next-btn.png
267 ms
facetsearch-bg.png
50 ms
facetsearch-border.png
49 ms
facetsearch-arrow.png
50 ms
controls-bg.png
88 ms
faux-buttonblock.png
117 ms
2016_31.png
41 ms
2014_31.png
97 ms
2016_36.png
242 ms
2016_45.png
94 ms
2016_31.png
197 ms
2016_46.png
89 ms
2015_36.png
99 ms
blank.gif
173 ms
header-strikethrough.png
90 ms
models-selector-tabs-right.png
154 ms
models-selector-tabs.png
153 ms
model-selector-divider.png
171 ms
type-3-tl.png
92 ms
type-3-tr.png
92 ms
type-3-l.png
92 ms
type-3-r.png
93 ms
link-arrow.png
104 ms
type-3-bl.png
105 ms
type-3-br.png
106 ms
embed
145 ms
f0444873086e023330d1ad8223f6fea9x.jpg
346 ms
page-bottom.png
85 ms
footer-bg-repeat.png
86 ms
footer-bg.png
89 ms
generic-map-5to2.png
88 ms
conversion.js
73 ms
ddc.jquery.min.js
128 ms
ddc.min.js
90 ms
jquery.cycle2.min.js
76 ms
jquery.cycle2.swipe.min.js
70 ms
widget.min.js
76 ms
widget.min.js
92 ms
widget.min.js
91 ms
widget.min.js
92 ms
widget.min.js
162 ms
xregexp-all.min.js
180 ms
widget.min.js
162 ms
tracker.min.js
161 ms
widget.min.js
124 ms
widget.min.js
194 ms
widget.min.js
176 ms
generaltag.js
67 ms
btn.png
259 ms
btn-right.png
176 ms
footer-nav-divider.png
175 ms
ddclogo.png
275 ms
analytics.js
34 ms
js
253 ms
init_embed.js
248 ms
225 ms
pixel
69 ms
pixel.php
210 ms
pixel.php
239 ms
activity;xsp=332306;ord=OV038318AD6DF0831175H45
172 ms
collect
47 ms
clear.gif
244 ms
collect
80 ms
collect
40 ms
66 ms
ui.min.js
29 ms
validator.min.js
26 ms
jquery.unveil.min.js
21 ms
hours.min.js
20 ms
dialog.min.js
25 ms
fbdrop.php
65 ms
apn.php
91 ms
934aedbe87d53a3741e89caf45606c4ex.jpg
354 ms
USB60HOV011C0.jpg
131 ms
ui-bg_flat_75_ffffff_40x100.png
21 ms
de1b23861cc4be6a8de2f4bdc8aff1b8x.jpg
39 ms
cef05cff7d3ac940eda8710d9fd774cax.jpg
44 ms
9159b17c2ec9462cb01ad62213c6a2c6x.jpg
37 ms
36214e7403535750ed6048da423146dcx.jpg
44 ms
5e8fd6683a1139466ecd1c6ec38ff621x.jpg
37 ms
e42cc5896cc4a30226cf2e3dcdd8e54cx.jpg
374 ms
e6610e958524abfd4200b85bcae5725ex.jpg
327 ms
53b31fb56a9383d52fc37cc37064c405x.jpg
69 ms
f239dae0aec1f98b4b3145aeeb74d1ddx.jpg
84 ms
cca84be434c1cfaa817eb76ff72094c0x.jpg
83 ms
41b3d51810b61201f2cb301c7354f388x.jpg
278 ms
102a7666c2c16c2c5ffdef1f51aa68a3x.jpg
346 ms
390930cadfa2b53b582d7666837b2882x.jpg
539 ms
4d55a02706116cb1f82d6d97a4d7426fx.jpg
573 ms
ui-icons_222222_256x240.png
11 ms
nr-632.min.js
33 ms
slideshow-paging.png
19 ms
sanleandrohonda.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
sanleandrohonda.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
Missing source maps for large first-party JavaScript
sanleandrohonda.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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanleandrohonda.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 Sanleandrohonda.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.
sanleandrohonda.com
Open Graph description is not detected on the main page of San Leandro Honda. 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: