1.7 sec in total
134 ms
1.5 sec
100 ms
Welcome to l2.com homepage info - get ready to check L 2 best content right away, or after learning these important things about l2.com
Search new cars and used cars for sale at prices you'll love. Experience the rewards offered by our automotive group's Powered by Lithia advantage.
Visit l2.comWe analyzed L2.com page load time and found that the first response time was 134 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
l2.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value4.3 s
42/100
25%
Value7.0 s
32/100
10%
Value7,590 ms
0/100
30%
Value0.081
94/100
15%
Value30.0 s
0/100
10%
134 ms
438 ms
203 ms
139 ms
176 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original L2.com, 66% (60 requests) were made to Lithia.com and 21% (19 requests) were made to Pictures.dealer.com. The less responsive or slowest element that took the longest time to load (678 ms) relates to the external source Lithia.com.
Page size can be reduced by 1.1 MB (54%)
2.1 MB
975.8 kB
In fact, the total size of L2.com main page is 2.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. 55% of websites need less resources to load. Javascripts take 783.7 kB which makes up the majority of the site volume.
Potential reduce by 228.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 228.0 kB or 74% of the original size.
Potential reduce by 5.6 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. L 2 images are well optimized though.
Potential reduce by 308.9 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 308.9 kB or 39% of the original size.
Potential reduce by 590.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. L2.com needs all CSS files to be minified and compressed as it can save up to 590.1 kB or 84% of the original size.
Number of requests can be reduced by 59 (68%)
87
28
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
l2.com
134 ms
www.lithia.com
438 ms
light-blue_white.css
203 ms
type.css
139 ms
light-blue_white-widgets.css
176 ms
custom.css
62 ms
ldclient.min.js
26 ms
pix-ddc-fp.min.js
332 ms
jquery.min.js
37 ms
track.js
334 ms
js
81 ms
phone-swapping.min.js
104 ms
ddc.jquery.async.each.min.js
151 ms
ddc.min.js
115 ms
ddc-core-js-polyfills.min.js
131 ms
react.production.min.js
142 ms
react-dom.production.min.js
145 ms
prop-types.min.js
160 ms
react-bootstrap.min.js
168 ms
redux.min.js
165 ms
react-redux.min.js
245 ms
redux-thunk.min.js
181 ms
html-react-parser.min.js
179 ms
umd.js
244 ms
hysterics.js
191 ms
loader.js
244 ms
animations.min.js
429 ms
widget.min.js
262 ms
data-layer-helper.min.js
244 ms
widget.min.js
329 ms
widget.min.js
257 ms
widget.min.js
256 ms
bundle.fc6b8bf491687e246451a00306ba51e2.js
281 ms
bundle.02953ca8f1e80ffc9fa5ebf0e175b3e8.js
280 ms
lib.js
324 ms
pubsub.min.js
328 ms
eo.min.js
324 ms
userProfileController.min.js
462 ms
bundle.9f0820ce4e832d108f8dfb1c71bd560d.js
435 ms
bundle.421e099d72c3ea25f5386bd7d2133b00.js
435 ms
snap-sHtYpphSLg4ANYoHH.js
41 ms
lad-push.js
326 ms
bundle.1f4ea265f949cf67d3f77a7ae2dfd4b7.js
435 ms
bundle.de647c6a44b1c3f4b7ddfe7f0aecb9ac.js
419 ms
snap-sHtYpphSLg4ANYoHH.js
214 ms
widget.min.js
398 ms
widget.js
530 ms
bundle.bd11dcfc23da4ebe66d3f3a4d9afcda0.js
547 ms
widget.min.js
350 ms
dropdown.min.js
320 ms
widget.min.js
337 ms
_bootstrap_2_3_1_carryover-typeahead.min.js
351 ms
search-typeahead.min.js
351 ms
widget.min.js
342 ms
widget.min.js
339 ms
variation.min.js
345 ms
web-vitals.attribution.min.js
346 ms
index.min.js
678 ms
ddc.jquery-ui.dialog.min.js
334 ms
component.min.js
340 ms
JFYY6-S63U5-AQ5LH-89V7M-PNV6G
103 ms
6f6e4c0f357c0fe67416990a5e64dcabx.jpg
200 ms
label-co2-website-white-en.png
303 ms
6a39b0beeaa92f7344400a53915c409bx.jpg
199 ms
23c5e9cab7e56aed165fdfcde4313f9ex.jpg
282 ms
d59755b4d4024e8a1eb1e3452e24c9f9x.jpg
210 ms
80b9b8d3299ca88b1a3c79ae7ef6eaa1x.jpg
208 ms
70b6b5c2057931c4941d17d5ce68beb4x.jpg
210 ms
98fa085e0faf3f5d3d22024e28b10ef3x.jpg
504 ms
24977843ad6806a93b8eb032a9ba01e1x.jpg
253 ms
bada4cd527f71635ddff0ba1d0ba36a1x.jpg
226 ms
1c09fc133e6434b3363a6b7d113bd81dx.jpg
239 ms
eb0c244be44adda3c72eddbaacfe281bx.jpg
290 ms
b5bc7a7705fe4d1eeebdfc376fc7ec61x.jpg
243 ms
6120849693e8058d42b8d206216f20d7x.jpg
254 ms
fbf80673ce45b884435004be476fdc3bx.jpg
258 ms
2b19279b0cef7398410d3653ee29eb69x.jpg
273 ms
f26e50fd64d8ce1a378fbe10291702c6x.jpg
270 ms
6d04142ebdf6bfaf7bd91982383b307cx.jpg
277 ms
blank.gif
353 ms
component.min.js
349 ms
0e9f7c85350991d48a4038316bb3b4a1x.jpg
250 ms
blank.gif
267 ms
font.8ba6dc5e9758b1099e483016605edfef.woff
351 ms
cc3727adce03371e8fd0c2ed54bd9b12x.jpg
566 ms
6058fc5522c1e
409 ms
ddc-white.png
508 ms
analytics.js
108 ms
config.json
131 ms
component.css
158 ms
data.htm
219 ms
l2.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
l2.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
l2.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 L2.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 L2.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.
l2.com
Open Graph description is not detected on the main page of L 2. 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: