3.8 sec in total
764 ms
2.7 sec
267 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 764 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
l2.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value6.5 s
9/100
25%
Value21.0 s
0/100
10%
Value56,830 ms
0/100
30%
Value0.045
99/100
15%
Value70.7 s
0/100
10%
764 ms
70 ms
87 ms
108 ms
57 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original L2.com, 9% (9 requests) were made to Google-analytics.com and 5% (5 requests) were made to Lithia.com. The less responsive or slowest element that took the longest time to load (764 ms) relates to the external source Lithia.com.
Page size can be reduced by 1.2 MB (51%)
2.4 MB
1.2 MB
In fact, the total size of L2.com main page is 2.4 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 849.9 kB which makes up the majority of the site volume.
Potential reduce by 90.9 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 90.9 kB or 79% of the original size.
Potential reduce by 14.5 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 529.7 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 529.7 kB or 69% of the original size.
Potential reduce by 575.3 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 575.3 kB or 87% of the original size.
Number of requests can be reduced by 58 (67%)
86
28
The browser has sent 86 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 39 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.lithia.com
764 ms
font-face-default.css
70 ms
blue_white.css
87 ms
blue_white-widgets.css
108 ms
widget.css
57 ms
widget.css
58 ms
srm.css
68 ms
custom.css
19 ms
newrelic.js
79 ms
modernizr-2.6.2.min.js
80 ms
pxa.min.js
28 ms
pixall.min.js
26 ms
conversion.js
22 ms
VisitorContext.aspx
19 ms
ddc.jquery.min.js
152 ms
ddc.min.js
95 ms
jquery.backstretch.min.js
96 ms
widget.min.js
106 ms
widget.min.js
106 ms
widget.min.js
108 ms
jsapi
28 ms
widget.min.js
118 ms
widget.min.js
126 ms
widget.min.js
119 ms
dropdown.min.js
125 ms
widget.min.js
136 ms
widget.min.js
144 ms
jquery.timeago.min.js
144 ms
widget.min.js
153 ms
tracker.min.js
148 ms
widget.min.js
176 ms
widget.min.js
168 ms
widget.min.js
168 ms
data-layer-helper.min.js
169 ms
variation.min.js
192 ms
PopIn.js
19 ms
PopInGenerator.aspx
27 ms
blue_white-blessed1.css
153 ms
iframe.php
118 ms
cookie-messaging.html
38 ms
ddc-logo-black.png
81 ms
webfont.ttf
97 ms
webfont.ttf
98 ms
webfont.ttf
95 ms
webfont.ttf
73 ms
pixel
181 ms
pixel
169 ms
analytics.js
77 ms
156 ms
gtm.js
74 ms
font.woff
74 ms
appnexus
118 ms
click_matrix.cfm
104 ms
475 ms
pixel
449 ms
pixel
447 ms
demdex.js
19 ms
298 ms
profiles
420 ms
mycars-icon-sprite-white.png
251 ms
collect
215 ms
ca4d7f211b06f6b9ad52484b063b70d3x.jpg
150 ms
clear.gif
355 ms
label.gif
138 ms
jquery.cao.js
158 ms
MTBAutoLargeIconLightGrayAnimation.js
128 ms
907278415478ae1f92564d76f1932309x.jpg
117 ms
f482cc3b7ef16f9a14750812586fd033x.jpg
115 ms
ee16507324eb2dd6011162c5f39abe42x.jpg
127 ms
9a55692e9c97788c6199b4aa79a656bbx.jpg
117 ms
collect
258 ms
collect
122 ms
collect
122 ms
2163e6b1-4499-4b2f-817a-43776fe81aa5.agent.790782.jpeg
122 ms
button3.jpg
121 ms
lithiagroupsite.png
332 ms
ui.min.js
105 ms
validator.min.js
100 ms
users
295 ms
pixel.php
271 ms
pixel.php
263 ms
generic
159 ms
fbdrop.php
387 ms
2163e6b1-4499-4b2f-817a-43776fe81aa5.agent.790782.jpeg
470 ms
MTBAuto_LargeIcon_MaxChatButtonText.png
326 ms
ui+en.css
166 ms
format+en,default+en,ui+en,corechart+en.I.js
209 ms
collect
48 ms
collect
44 ms
collect
42 ms
collect
42 ms
firstevent
126 ms
nr-632.min.js
74 ms
dest2.html
75 ms
default.aspx
38 ms
82e1cf9367
54 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.
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
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
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
Missing source maps for large first-party JavaScript
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
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: