PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Apr 8, 2025, 7:09:10 AM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.1 s
Page LoadsGood (≤ 2.5 s)84%Needs Improvement (2.5 s - 4 s)12%Poor (> 4 s)3%75th Percentile - 2.1 sCore Web Vital
Interaction to Next Paint (INP)
246 ms
Page LoadsGood (≤ 200 ms)57%Needs Improvement (200 ms - 500 ms)38%Poor (> 500 ms)5%75th Percentile - 246 msCore Web Vital
Cumulative Layout Shift (CLS)
0
Page LoadsGood (≤ 0.1)88%Needs Improvement (0.1 - 0.25)8%Poor (> 0.25)4%75th Percentile - 0Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2 s
Page LoadsGood (≤ 1.8 s)70%Needs Improvement (1.8 s - 3 s)23%Poor (> 3 s)8%75th Percentile - 2 s 
Time to First Byte (TTFB)
1.5 s
Page LoadsGood (≤ 0.8 s)36%Needs Improvement (0.8 s - 1.8 s)48%Poor (> 1.8 s)16%75th Percentile - 1.5 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
1.9 s
Page LoadsGood (≤ 2.5 s)87%Needs Improvement (2.5 s - 4 s)10%Poor (> 4 s)3%75th Percentile - 1.9 sCore Web Vital
Interaction to Next Paint (INP)
228 ms
Page LoadsGood (≤ 200 ms)66%Needs Improvement (200 ms - 500 ms)30%Poor (> 500 ms)4%75th Percentile - 228 msCore Web Vital
Cumulative Layout Shift (CLS)
0.12
Page LoadsGood (≤ 0.1)74%Needs Improvement (0.1 - 0.25)9%Poor (> 0.25)17%75th Percentile - 0.12Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.4 s
Page LoadsGood (≤ 1.8 s)85%Needs Improvement (1.8 s - 3 s)12%Poor (> 3 s)3%75th Percentile - 1.4 s 
Time to First Byte (TTFB)
1 s
Page LoadsGood (≤ 0.8 s)64%Needs Improvement (0.8 s - 1.8 s)30%Poor (> 1.8 s)6%75th Percentile - 1 sExperimental
Latest 28-day collection period
Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
56 FCP+9LCP+11TBT+8CLS+25SI+4 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
4.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
1,020 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
6.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Apr 8, 2025, 7:09 AM UTC
  • Emulated Moto G Power with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 305 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 134.0.6998.165 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 5.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
2,840 ms
Other
742 ms
Style & Layout
603 ms
Garbage Collection
420 ms
Script Parsing & Compilation
207 ms
Rendering
175 ms
Parse HTML & CSS
143 ms
Reduce JavaScript execution time 2.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
plattevalleyauto.com
1st party
2,258 ms
993 ms
60 ms
1,499 ms
535 ms
36 ms
/pixall/pix-ddc-fp.min.js
(www.plattevalleyauto.com)
296 ms
163 ms
2 ms
201 ms
95 ms
4 ms
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
104 ms
75 ms
1 ms
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
101 ms
70 ms
15 ms
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
58 ms
54 ms
1 ms
Google Tag Manager
tag-manager
1,113 ms
910 ms
69 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
318 ms
218 ms
15 ms
/gtag/js?id=…
(www.googletagmanager.com)
200 ms
144 ms
14 ms
/gtag/js?id=…
(www.googletagmanager.com)
163 ms
154 ms
8 ms
/gtag/js?id=…
(www.googletagmanager.com)
123 ms
111 ms
10 ms
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
122 ms
114 ms
8 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
111 ms
101 ms
9 ms
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
76 ms
69 ms
6 ms
Unattributable
479 ms
52 ms
0 ms
Unattributable
479 ms
52 ms
0 ms
iviewanalytics.com
115 ms
113 ms
0 ms
115 ms
113 ms
0 ms
swipetospin.com
99 ms
89 ms
2 ms
99 ms
89 ms
2 ms
New Relic
utility
99 ms
91 ms
3 ms
/nr-spa-1.286.0.min.js
(js-agent.newrelic.com)
99 ms
91 ms
3 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 640 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
1,194 KiB
574 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
181 KiB
192 ms
/gtag/js?id=…
(www.googletagmanager.com)
147 KiB
147 ms
/gtag/js?id=…
(www.googletagmanager.com)
119 KiB
109 ms
/gtag/js?id=…
(www.googletagmanager.com)
122 KiB
67 ms
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
107 KiB
37 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
101 KiB
22 ms
/gtag/js?id=…
(www.googletagmanager.com)
111 KiB
0 ms
/gtag/js?id=AW-794…
(www.googletagmanager.com)
111 KiB
0 ms
/gtag/js?id=…
(www.googletagmanager.com)
107 KiB
0 ms
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
87 KiB
0 ms
…5430/sw_iframe.html?origin=…
(www.googletagmanager.com)
2 KiB
0 ms
iviewanalytics.com
2 KiB
63 ms
1 KiB
63 ms
/scripts/analytics.min.js
(cdn.iviewanalytics.com)
1 KiB
0 ms
swipetospin.com
26 KiB
2 ms
26 KiB
2 ms
mPulse
analytics
30 KiB
1 ms
29 KiB
1 ms
/api/config.json?key=…
(c.go-mpulse.net)
1 KiB
0 ms
0 KiB
0 ms
esm1.net
5 KiB
1 ms
1 KiB
1 ms
1 KiB
0 ms
/v2/iframe?u=…
(cs.esm1.net)
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/cookie
(pixall.esm1.net)
1 KiB
0 ms
0 KiB
0 ms
Dealer
hosting
49 KiB
0 ms
22 KiB
0 ms
17 KiB
0 ms
8 KiB
0 ms
/phones?platform=DDC_MOBILE
(phone-swap-service-v2-prod.us-east-1.web.dealer.com)
1 KiB
0 ms
…adchoices/logo.svg
(images.dealer.com)
1 KiB
0 ms
New Relic
utility
34 KiB
0 ms
/nr-spa-1.286.0.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/NRBR-a735…?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/NRBR-a735…?a=…
(bam.nr-data.net)
0 KiB
0 ms
Cloudflare CDN
cdn
27 KiB
0 ms
…2.2.4/jquery.min.js
(cdnjs.cloudflare.com)
27 KiB
0 ms
Google Analytics
analytics
25 KiB
0 ms
/analytics.js
(www.google-analytics.com)
21 KiB
0 ms
/j/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
impel.io
22 KiB
0 ms
12 KiB
0 ms
6 KiB
0 ms
2 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
BlueCava
ad
21 KiB
0 ms
/js/bc.js
(sync.graph.bluecava.com)
16 KiB
0 ms
/req.bci
(sync.graph.bluecava.com)
2 KiB
0 ms
/Scripts/BlueCava.Lib.js
(sync.graph.bluecava.com)
2 KiB
0 ms
1 KiB
0 ms
/init.bci
(sync.graph.bluecava.com)
1 KiB
0 ms
motominer.com
15 KiB
0 ms
15 KiB
0 ms
Google/Doubleclick Ads
ad
8 KiB
0 ms
…viewthrou…/794…?random=…
(googleads.g.doubleclick.net)
3 KiB
0 ms
…viewthrou…/109…?random=…
(googleads.g.doubleclick.net)
3 KiB
0 ms
…rul/794…?random=…
(td.doubleclick.net)
1 KiB
0 ms
…rul/109…?random=…
(td.doubleclick.net)
1 KiB
0 ms
1 KiB
0 ms
wehaacdn.com
8 KiB
0 ms
/web/vdpx.js
(autoevents.wehaacdn.com)
8 KiB
0 ms
Launch Darkly
utility
6 KiB
0 ms
…contexts/eyJraW5kI…
(app.launchdarkly.com)
3 KiB
0 ms
…goals/5a6a54d…
(app.launchdarkly.com)
2 KiB
0 ms
…diagnostic/5a6a54d…
(events.launchdarkly.com)
1 KiB
0 ms
…bulk/5a6a54d…
(events.launchdarkly.com)
1 KiB
0 ms
Pubmatic
ad
2 KiB
0 ms
/AdServer/Pug?vcode=…
(simage2.pubmatic.com)
1 KiB
0 ms
/AdServer/UCookieSetPug?oid=…
(image6.pubmatic.com)
1 KiB
0 ms
/AdServer/UCookieSetPug?oid=…
(image6.pubmatic.com)
1 KiB
0 ms
kbb.com
2 KiB
0 ms
/instant-cash-offer.js
(ddc.plugin.syndication.kbb.com)
2 KiB
0 ms
LiveRamp IdentityLink
analytics
2 KiB
0 ms
/1000.gif?memo=CNeUHBIkC…
(idsync.rlcdn.com)
1 KiB
0 ms
1 KiB
0 ms
Akamai
cdn
1 KiB
0 ms
/eum/getdns.txt?c=pwmr8iukt
(trial-eum-clientnsv4-s.akamaihd.net)
0 KiB
0 ms
/eum/results.txt
(74-125-215-96_s-104-93-21-49_ts-1744096159-clienttons-s.akamaihd.net)
0 KiB
0 ms
/eum/results.txt
(ijtanidilukrqz7uzopq-pwmr8i-80ff89ac2-clientnsv4-s.akamaihd.net)
0 KiB
0 ms
/eum/getdns.txt?c=pwmr8iukt
(trial-eum-clienttons-s.akamaihd.net)
0 KiB
0 ms
Other Google APIs/SDKs
utility
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/ccm/collect?en=…
(www.google.com)
0 KiB
0 ms
Facebook
social
1 KiB
0 ms
/tr/?id=…
(www.facebook.com)
0 KiB
0 ms
/tr/?id=…
(www.facebook.com)
0 KiB
0 ms
AppNexus
ad
1 KiB
0 ms
1 KiB
0 ms
Tremor Video
ad
0 KiB
0 ms
/sync?UIDC=M9wp1cFKV…
(partners.tremorhub.com)
0 KiB
0 ms
alcmpn.com
0 KiB
0 ms
0 KiB
0 ms
fluencyinc.co
0 KiB
0 ms
/ftm-ddc.js
(ftm.fluencyinc.co)
0 KiB
0 ms
Largest Contentful Paint element 4,280 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
Shop Any Location Any Type Any Year All Filters Search
<div data-width-multiplier="1" data-responsive-image-group="true" style="max-height: 450px; background-repeat: no-repeat; background-size: 135%;" class="page-section no-gutter-spacing js-hero-expand-container" data-name="index-landing-0011-hero-shop-container-1">
Phase
% of LCP
Timing
TTFB
14%
600 ms
Load Delay
31%
1,350 ms
Load Time
5%
230 ms
Render Delay
49%
2,100 ms
Reduce initial server response time Root document took 690 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
plattevalleyauto.com
1st party
690 ms
690 ms
Reduce unused CSS Potential savings of 77 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
plattevalleyauto.com
1st party
69.0 KiB
65.7 KiB
…css/blue_white-mobile.css?r=174…
(www.plattevalleyauto.com)
44.1 KiB
41.5 KiB
24.9 KiB
24.2 KiB
impel.io
11.4 KiB
11.4 KiB
11.4 KiB
11.4 KiB
Eliminate render-blocking resources Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
plattevalleyauto.com
1st party
70.4 KiB
450 ms
…css/blue_white-mobile.css?r=174…
(www.plattevalleyauto.com)
44.8 KiB
300 ms
25.6 KiB
150 ms
Avoid an excessive DOM size 1,674 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
1,674
Maximum DOM Depth
Any Location
<span>
20
Maximum Child Elements
body.screen-orientation-portrait
<body class="screen-orientation-portrait">
96
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
Blazer
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer/SUV/perspecti…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Blazer" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Blazer EV
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer EV/SUV/perspe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Blazer EV" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Equinox
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox/SUV/perspect…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Equinox" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Equinox EV
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox EV/SUV/persp…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Equinox EV" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Suburban
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Suburban/SUV/perspec…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Suburban" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Tahoe
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Tahoe/SUV/perspectiv…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Tahoe" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Trailblazer
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Trailblazer/SUV/pers…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Trailblazer" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Traverse
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Traverse/SUV/perspec…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Traverse" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Trax
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Trax/SUV/perspective…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Trax" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Durango
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Dodge/Durango/SUV/perspective/…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Durango" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Hornet
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Dodge/Hornet/SUV/perspective/f…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Hornet" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Bronco
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Bronco/SUV/perspective/fr…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Bronco" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Bronco Sport
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Bronco Sport/SUV/perspect…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Bronco Sport" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Escape
<img data-lazy="https://images.dealer.com/autodata/us/640/2025/USD50FOS131A0/USD30FOS131B0…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Escape" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Expedition
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Expedition/SUV/perspectiv…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Expedition" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Expedition Max
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Expedition Max/SUV/perspe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Expedition Max" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Explorer
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Explorer/SUV/perspective/…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Explorer" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Mustang Mach-E
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Ford/Mustang Mach-E/SUV/perspe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Mustang Mach-E" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Compass
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Compass/SUV/perspective/f…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Compass" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Grand Cherokee
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Grand Cherokee/SUV/perspe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Grand Cherokee" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Grand Cherokee 4xe
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Grand Cherokee 4xe/SUV/pe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Grand Cherokee 4xe" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Grand Cherokee L
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Grand Cherokee L/SUV/pers…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Grand Cherokee L" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Grand Wagoneer
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Grand Wagoneer/SUV/perspe…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Grand Wagoneer" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Grand Wagoneer L
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Grand Wagoneer L/SUV/pers…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Grand Wagoneer L" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Wagoneer
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Wagoneer/SUV/perspective/…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Wagoneer" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Wagoneer L
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Wagoneer L/SUV/perspectiv…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Wagoneer L" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Wagoneer S
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Wagoneer S/SUV/perspectiv…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Wagoneer S" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Wrangler
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Wrangler/SUV/perspective/…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Wrangler" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Wrangler 4xe
<img data-lazy="https://images.dealer.com/ddc/vehicles/2025/Jeep/Wrangler 4xe/SUV/perspect…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Wrangler 4xe" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Traverse Limited
<img data-lazy="https://images.dealer.com/ddc/vehicles/2024/Chevrolet/Traverse Limited/SUV…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Traverse Limited" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Edge
<img data-lazy="https://images.dealer.com/ddc/vehicles/2024/Ford/Edge/SUV/perspective/fron…" src="data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==" alt="Edge" fetchpriority="high" style=" height: auto; width: 100%; object-fit: contain ">
Enable text compression Potential savings of 15 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
motominer.com
14.8 KiB
10.2 KiB
14.8 KiB
10.2 KiB
wehaacdn.com
7.3 KiB
4.7 KiB
/web/vdpx.js
(autoevents.wehaacdn.com)
7.3 KiB
4.7 KiB
Serve static assets with an efficient cache policy 98 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
plattevalleyauto.com
1st party
1,112 KiB
13m 7s
7 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
13m 7s
3 KiB
/pixall/pix-ddc-fp.min.js
(www.plattevalleyauto.com)
15m
28 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
2h 23s
19 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
9h 27m 46s
19 KiB
…1.10.2/lib.js
(www.plattevalleyauto.com)
13h 26m 55s
20 KiB
…Didot/Didot_L06_100.ttf
(www.plattevalleyauto.com)
18h 46m 1s
53 KiB
21h 24m
402 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
1d 4h 56m 18s
17 KiB
…1.10.2/loader.js
(www.plattevalleyauto.com)
1d 5h 38m 18s
1 KiB
…v1/swipetospin.js
(www.plattevalleyauto.com)
1d 8h 30m 52s
1 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
1d 12h 39m 37s
17 KiB
…stylesheets/custom-fonts.css
(www.plattevalleyauto.com)
2d
1 KiB
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
14d
49 KiB
…css/blue_white-mobile.css?r=174…
(www.plattevalleyauto.com)
14d
45 KiB
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
14d
43 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
14d
35 KiB
…17.0.1/react-dom.production.min.js
(www.plattevalleyauto.com)
14d
34 KiB
14d
33 KiB
14d
26 KiB
…dist/ddc.mobile.min.js?r=174…
(www.plattevalleyauto.com)
14d
23 KiB
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
14d
17 KiB
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
14d
17 KiB
…tracking/bundle.553.2fc58e2….js
(www.plattevalleyauto.com)
14d
16 KiB
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
14d
14 KiB
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
14d
13 KiB
…slick/slick.min.js?r=174…
(www.plattevalleyauto.com)
14d
10 KiB
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
14d
9 KiB
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
14d
9 KiB
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
14d
9 KiB
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
14d
7 KiB
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
14d
7 KiB
…dist/phone-swapping.min.js?r=174…
(www.plattevalleyauto.com)
14d
6 KiB
…hours/bundle.808635c….js
(www.plattevalleyauto.com)
14d
5 KiB
…7.2.6/react-redux.min.js
(www.plattevalleyauto.com)
14d
5 KiB
…17.0.1/react.production.min.js
(www.plattevalleyauto.com)
14d
5 KiB
14d
4 KiB
…tagging/bundle.1689.138fdf6….js
(www.plattevalleyauto.com)
14d
4 KiB
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
14d
4 KiB
…ddc-logo/bundle.2c0d626….js
(www.plattevalleyauto.com)
14d
4 KiB
14d
4 KiB
…tagging/bundle.869.beac321….js
(www.plattevalleyauto.com)
14d
3 KiB
…tagging/bundle.1115.ebd8118….js
(www.plattevalleyauto.com)
14d
3 KiB
…1.0.8/ddc-core-js-polyfills.min.js
(www.plattevalleyauto.com)
14d
3 KiB
…tagging/bundle.2587.ea409ea….js
(www.plattevalleyauto.com)
14d
3 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…tagging/bundle.9132.330a7f7….js
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…4.1.1/redux.min.js
(www.plattevalleyauto.com)
14d
2 KiB
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…specials/bundle.430.239b279….css
(www.plattevalleyauto.com)
14d
2 KiB
…mobile/directions-icon.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…v1/component.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…v1/userProfi….min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…0.3.0/umd.js
(www.plattevalleyauto.com)
14d
1 KiB
…15.7.2/prop-types.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…new-relic/index.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v3.3.7/tab.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
14d
1 KiB
…v0.0.5/tocca.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v1/eo.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…dist/index.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v1.0/jquery.inview.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget-tracking.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…2.4.0/redux-thunk.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…specials/bundle.430.e8a6de5….js
(www.plattevalleyauto.com)
14d
1 KiB
mPulse
analytics
29 KiB
7d
29 KiB
swipetospin.com
26 KiB
10m
26 KiB
Google Analytics
analytics
21 KiB
/analytics.js
(www.google-analytics.com)
2h
21 KiB
impel.io
18 KiB
1m
1 KiB
7d
12 KiB
7d
6 KiB
Dealer
hosting
9 KiB
14d
8 KiB
…adchoices/logo.svg
(images.dealer.com)
14d
1 KiB
wehaacdn.com
8 KiB
/web/vdpx.js
(autoevents.wehaacdn.com)
None
8 KiB
kbb.com
2 KiB
/instant-cash-offer.js
(ddc.plugin.syndication.kbb.com)
None
2 KiB
BlueCava
ad
2 KiB
/Scripts/BlueCava.Lib.js
(sync.graph.bluecava.com)
30d
2 KiB
Facebook
social
1 KiB
/tr/?id=…
(www.facebook.com)
None
0 KiB
/tr/?id=…
(www.facebook.com)
None
0 KiB
iviewanalytics.com
1 KiB
/scripts/analytics.min.js
(cdn.iviewanalytics.com)
None
1 KiB
Tremor Video
ad
0 KiB
/sync?UIDC=M9wp1cFKV…
(partners.tremorhub.com)
None
0 KiB
alcmpn.com
0 KiB
None
0 KiB
esm1.net
0 KiB
None
0 KiB
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
URL
Potential Savings
plattevalleyauto.com
1st party
400 ms
270 ms
…Didot/Didot_L06_100.ttf
(www.plattevalleyauto.com)
130 ms
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Source
plattevalleyauto.com
1st party
Defer offscreen images Potential savings of 7 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
plattevalleyauto.com
1st party
7.1 KiB
7.1 KiB
Dealer.com
<img src="/static/assets/images/logos/dealer-dot-com/logo-one-color-white.svg" alt="Dealer.com" height="20" width="162">
7.1 KiB
7.1 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 2 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
Other
0 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
BlueCava
ad
9.8 KiB
/js/bc.js
(sync.graph.bluecava.com)
9.8 KiB
/js/bc.js:48:497
(sync.graph.bluecava.com)
Date.prototype.toJSON
/js/bc.js:54:42
(sync.graph.bluecava.com)
Date.now
plattevalleyauto.com
1st party
6.8 KiB
…dist/ddc.mobile.min.js?r=174…
(www.plattevalleyauto.com)
6.7 KiB
Number.isInteger
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
0.1 KiB
@babel/plugin-transform-classes
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
0.1 KiB
../src/pubsub.js:2:1
@babel/plugin-transform-classes
…dist/phone-swapping.min.js?r=174…
(www.plattevalleyauto.com)
0.0 KiB
@babel/plugin-transform-classes
Reduce unused JavaScript Potential savings of 602 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
1,181.5 KiB
546.4 KiB
/gtag/js?id=…
(www.googletagmanager.com)
109.7 KiB
83.0 KiB
/gtag/js?id=…
(www.googletagmanager.com)
105.9 KiB
82.5 KiB
/gtag/js?id=…
(www.googletagmanager.com)
145.9 KiB
59.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
121.0 KiB
51.3 KiB
/gtag/js?id=…
(www.googletagmanager.com)
117.6 KiB
48.2 KiB
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
105.9 KiB
48.0 KiB
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
85.7 KiB
46.5 KiB
/gtag/js?id=AW-794…
(www.googletagmanager.com)
109.6 KiB
44.3 KiB
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
180.0 KiB
43.5 KiB
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
100.4 KiB
40.1 KiB
plattevalleyauto.com
1st party
83.1 KiB
55.7 KiB
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
48.5 KiB
35.6 KiB
…./node_modules/wsm-specials-display/dist/es.js
23.3 KiB
16.9 KiB
…./node_modules/react-to-print/lib/index.js
3.5 KiB
3.0 KiB
…./node_modules/wsm-incentive-modal/dist/es.js
3.3 KiB
1.9 KiB
…./src/templates/commonFragments.jsx
1.0 KiB
1.0 KiB
…./src/utilities/printViewOnChromeIos.js
0.9 KiB
0.9 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
34.6 KiB
20.1 KiB
Avoid enormous network payloads Total size was 2,908 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google Tag Manager
tag-manager
1,105.5 KiB
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
181.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
146.9 KiB
/gtag/js?id=…
(www.googletagmanager.com)
122.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
118.7 KiB
/gtag/js?id=…
(www.googletagmanager.com)
110.8 KiB
/gtag/js?id=AW-794…
(www.googletagmanager.com)
110.7 KiB
/gtag/js?id=…
(www.googletagmanager.com)
106.9 KiB
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
106.9 KiB
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
101.5 KiB
plattevalleyauto.com
1st party
402.4 KiB
402.4 KiB
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
924 ms
/gtag/js?id=…
(www.googletagmanager.com)
12,378 ms
197 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
6,487 ms
163 ms
/gtag/js?id=…
(www.googletagmanager.com)
8,778 ms
159 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
5,028 ms
129 ms
/gtag/js?id=…
(www.googletagmanager.com)
13,728 ms
117 ms
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
18,546 ms
87 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
6,415 ms
72 ms
plattevalleyauto.com
1st party
606 ms
/pixall/pix-ddc-fp.min.js
(www.plattevalleyauto.com)
9,001 ms
120 ms
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
12,575 ms
94 ms
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
12,751 ms
88 ms
1,431 ms
74 ms
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
6,650 ms
64 ms
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
20,834 ms
58 ms
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
11,401 ms
57 ms
13,939 ms
51 ms
mPulse
analytics
254 ms
2,838 ms
254 ms
iviewanalytics.com
113 ms
15,397 ms
113 ms
Unattributable
52 ms
Unattributable
1,677 ms
52 ms
swipetospin.com
52 ms
24,604 ms
52 ms
esm1.net
51 ms
9,912 ms
51 ms
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
<div class="navbar bg-none border-0 position-relative shadow-none">
0.001
Ford
<li style="position: absolute; top: 0px; left: 0px; display: block; z-index: 6;">
0.000
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
Web font loaded
<li style="position: absolute; top: 0px; left: 0px; display: none; z-index: 6;">
0.000
Dodge
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/d/dodge/white/117x80.png?r=1…" alt="Dodge" loading="eager">
Media element lacking an explicit size
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Name
Type
Start Time
Duration
ldSDK
Measure
1,842.61 ms
700.30 ms
ldSDKInit
Measure
2,545.25 ms
163.01 ms
ldSDKStart
Mark
1,842.61 ms
ldSDKEnd
Mark
2,542.91 ms
ldSDKInitStart
Mark
2,545.25 ms
ldSDKInitEnd
Mark
2,708.26 ms
basePageCacheStatus-REVALIDATE
Mark
3,636.40 ms
basePageCacheable-true
Mark
3,636.43 ms
Avoid non-composited animations 8 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-2">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-8">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-3">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-7">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-1">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-6">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-4">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-5">
Unsupported CSS Property: background-color
loader
Avoid chaining critical requests 42 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 3,682.197 ms
Initial Navigation
- 529.189 ms, 32.87 KiB
…dist/ddc.mobile.min.js?r=174…
(www.plattevalleyauto.com)
- 319.181 ms, 23.27 KiB
…1.0.8/ddc-core-js-polyfills.min.js
(www.plattevalleyauto.com)
- 277.001 ms, 2.70 KiB
…17.0.1/react.production.min.js
(www.plattevalleyauto.com)
- 71.03 ms, 4.52 KiB
…17.0.1/react-dom.production.min.js
(www.plattevalleyauto.com)
- 243.928 ms, 34.32 KiB
…15.7.2/prop-types.min.js
(www.plattevalleyauto.com)
- 105.908 ms, 1.28 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
- 109.604 ms, 35.28 KiB
…4.1.1/redux.min.js
(www.plattevalleyauto.com)
- 200.06 ms, 2.02 KiB
…7.2.6/react-redux.min.js
(www.plattevalleyauto.com)
- 90.524 ms, 5.38 KiB
…2.4.0/redux-thunk.min.js
(www.plattevalleyauto.com)
- 72.084 ms, 0.78 KiB
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
- 173.67 ms, 12.96 KiB
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
- 194.356 ms, 8.94 KiB
…0.3.0/umd.js
(www.plattevalleyauto.com)
- 229.971 ms, 1.37 KiB
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
- 239.351 ms, 3.81 KiB
…1.10.2/loader.js
(www.plattevalleyauto.com)
- 90.856 ms, 0.87 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 209.057 ms, 1.75 KiB
- 183.334 ms, 4.09 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 236.295 ms, 1.39 KiB
…css/blue_white-mobile.css?r=174…
(www.plattevalleyauto.com)
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
- 95.37 ms, 42.90 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 231.215 ms, 1.92 KiB
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
- 112.836 ms, 1.38 KiB
…v1/userProfi….min.js?r=174…
(www.plattevalleyauto.com)
- 117.538 ms, 1.42 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 225.551 ms, 1.12 KiB
…v1.0/jquery.inview.min.js?r=174…
(www.plattevalleyauto.com)
- 126.953 ms, 0.92 KiB
…v3.3.7/tab.min.js?r=174…
(www.plattevalleyauto.com)
- 266.644 ms, 1.27 KiB
- 350.458 ms, 25.56 KiB
…slick/slick.min.js?r=174…
(www.plattevalleyauto.com)
- 136.451 ms, 10.12 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 208.25 ms, 2.30 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 283.85 ms, 0.97 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 342.704 ms, 1.87 KiB
- 237.207 ms, 1.97 KiB
- 119.91 ms, 1.25 KiB
…stylesheets/custom-fonts.css
(www.plattevalleyauto.com)
- 274.307 ms, 402.44 KiB
…Didot/Didot_L06_100.ttf
(www.plattevalleyauto.com)
- 126.081 ms, 53.40 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 150.918 ms, 2.14 KiB
…v0.0.5/tocca.min.js?r=174…
(www.plattevalleyauto.com)
- 216.143 ms, 1.14 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 143.945 ms, 1.54 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
- 436.273 ms, 3.16 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 68.65 ms, 18.59 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 131.982 ms, 19.32 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 86.849 ms, 16.57 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 289.445 ms, 17.06 KiB
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (13)
Show Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
Preconnect to required origins
Warnings: More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
Shop Any Location Any Type Any Year All Filters Search
<div data-width-multiplier="1" data-responsive-image-group="true" style="max-height: 450px; background-repeat: no-repeat; background-size: 135%;" class="page-section no-gutter-spacing js-hero-expand-container" data-name="index-landing-0011-hero-shop-container-1">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Failing Elements
SUV Convertible Coupe Sedan Truck Van Wagon
<select class="form-control model-selector-responsive-tabs d-inline-block m-auto w-50 fon…" role="tablist">
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.
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Failing Elements
Shop
<h3 class="ddc-heading display-1 spacing-reset widget-heading">
These are opportunities to improve keyboard navigation in your application.
ARIA
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Failing Elements
SUV Convertible Coupe Sedan Truck Van Wagon
<select class="form-control model-selector-responsive-tabs d-inline-block m-auto w-50 fon…" role="tablist">
SUV
<option selected="" value="SUV-responsive-tab-model-selector1" role="tab">
Convertible
<option value="Convertible-responsive-tab-model-selector1" role="tab">
Coupe
<option value="Coupe-responsive-tab-model-selector1" role="tab">
Sedan
<option value="Sedan-responsive-tab-model-selector1" role="tab">
Truck
<option value="Truck-responsive-tab-model-selector1" role="tab">
Van
<option value="Van-responsive-tab-model-selector1" role="tab">
Wagon
<option value="Wagon-responsive-tab-model-selector1" role="tab">
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.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (28)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (26)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
plattevalleyauto.com
1st party
Unload event listeners are deprecated and will be removed.
Uses third-party cookies 1 cookie found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Name
URL
BlueCava
ad
ssx
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
impel.io
Failed to load resource: the server responded with a status of 403 (Forbidden)
plattevalleyauto.com
1st party
…images/blurbIcon_globe.png:1:0
(www.plattevalleyauto.com)
Failed to load resource: the server responded with a status of 404 (Not Found)
…images/blurbIcon_gears.png:1:0
(www.plattevalleyauto.com)
Failed to load resource: the server responded with a status of 404 (Not Found)
…images/blurbIcon_camera.png:1:0
(www.plattevalleyauto.com)
Failed to load resource: the server responded with a status of 404 (Not Found)
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
Cookie
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Bootstrap
3.3.7
jQuery
1.7.2
jQuery UI
1.8.6
React
17.0.1
Underscore
1.4.4
jQuery Tools
1.2.4
boomerang.js
1.737.20
core-js
core-js-pure@2.5.7
Trust and Safety
Requests the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Source
plattevalleyauto.com
1st party
webpack://ws-facet-browse/./src/components/buttons/SearchButton.jsx:40:27
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
No `includeSubDomains` directive found
includeSubDomains
Medium
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
URL
Aspect Ratio (Displayed)
Aspect Ratio (Actual)
plattevalleyauto.com
1st party
Dodge
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/d/dodge/white/117x80.png?r=1…" alt="Dodge" loading="eager">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Jeep
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/j/jeep/white/117x80.png?r=17…" alt="Jeep">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Ford
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/f/ford/white/117x80.png?r=17…" alt="Ford">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Chrysler
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/c/chrysler/white/117x80.png?…" alt="Chrysler">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Ram
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/r/ram/white/117x80.png?r=174…" alt="Ram">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Passed audits (9)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
plattevalleyauto.com
1st party
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
…1.9.7/redux-toolkit.umd.min.js.map
(www.plattevalleyauto.com)
SyntaxError: Unexpected token 'N', "Not found
" is not valid JSON
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
…tracking/bundle.aa5eefd….js.map
(www.plattevalleyauto.com)
…tracking/bundle.553.2fc58e2….js
(www.plattevalleyauto.com)
…tagging/bundle.9132.330a7f7….js
(www.plattevalleyauto.com)
…tagging/bundle.869.beac321….js
(www.plattevalleyauto.com)
…tagging/bundle.869.beac321….js.map
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js.map
(www.plattevalleyauto.com)
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
…tagging/bundle.2587.ea409ea….js
(www.plattevalleyauto.com)
…tagging/bundle.1689.138fdf6….js
(www.plattevalleyauto.com)
…tagging/bundle.1115.ebd8118….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js.map
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js.map
(www.plattevalleyauto.com)
…hours/bundle.808635c….js
(www.plattevalleyauto.com)
…hours/bundle.808635c….js.map
(www.plattevalleyauto.com)
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
…ddc-logo/bundle.2c0d626….js
(www.plattevalleyauto.com)
…ddc-logo/bundle.2c0d626….js.map
(www.plattevalleyauto.com)
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
…content-cta/bundle.4ce609b….js.map
(www.plattevalleyauto.com)
…0.3.0/umd.js
(www.plattevalleyauto.com)
…0.3.0/umd.js.map
(www.plattevalleyauto.com)
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
…1.1.0/pubsub.min.js.map
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js.map
(www.plattevalleyauto.com)
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
…3.0.4/hysterics.js.map
(www.plattevalleyauto.com)
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
…1.4.0/html-react-parser.min.js.map
(www.plattevalleyauto.com)
…1.0.0/es.js
(www.plattevalleyauto.com)
…1.0.0/es.js.map
(www.plattevalleyauto.com)
…1.10.2/loader.js
(www.plattevalleyauto.com)
…1.10.2/loader.js.map
(www.plattevalleyauto.com)
…1.10.2/lib.js
(www.plattevalleyauto.com)
…1.10.2/lib.js.map
(www.plattevalleyauto.com)
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
3.1 s
Page LoadsGood (≤ 2.5 s)67%Needs Improvement (2.5 s - 4 s)19%Poor (> 4 s)14%75th Percentile - 3.1 sCore Web Vital
Interaction to Next Paint (INP)
196 ms
Page LoadsGood (≤ 200 ms)77%Needs Improvement (200 ms - 500 ms)17%Poor (> 500 ms)6%75th Percentile - 196 msCore Web Vital
Cumulative Layout Shift (CLS)
0.16
Page LoadsGood (≤ 0.1)3%Needs Improvement (0.1 - 0.25)87%Poor (> 0.25)10%75th Percentile - 0.16Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2.8 s
Page LoadsGood (≤ 1.8 s)57%Needs Improvement (1.8 s - 3 s)21%Poor (> 3 s)23%75th Percentile - 2.8 s 
Time to First Byte (TTFB)
1.7 s
Page LoadsGood (≤ 0.8 s)41%Needs Improvement (0.8 s - 1.8 s)35%Poor (> 1.8 s)24%75th Percentile - 1.7 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.2 s
Page LoadsGood (≤ 2.5 s)81%Needs Improvement (2.5 s - 4 s)13%Poor (> 4 s)7%75th Percentile - 2.2 sCore Web Vital
Interaction to Next Paint (INP)
158 ms
Page LoadsGood (≤ 200 ms)83%Needs Improvement (200 ms - 500 ms)13%Poor (> 500 ms)4%75th Percentile - 158 msCore Web Vital
Cumulative Layout Shift (CLS)
0.21
Page LoadsGood (≤ 0.1)4%Needs Improvement (0.1 - 0.25)77%Poor (> 0.25)19%75th Percentile - 0.21Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.4 s
Page LoadsGood (≤ 1.8 s)83%Needs Improvement (1.8 s - 3 s)10%Poor (> 3 s)7%75th Percentile - 1.4 s 
Time to First Byte (TTFB)
0.9 s
Page LoadsGood (≤ 0.8 s)73%Needs Improvement (0.8 s - 1.8 s)22%Poor (> 1.8 s)5%75th Percentile - 0.9 sExperimental
Latest 28-day collection period
Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
60 FCP+10LCP+24TBT+3CLS+18SI+6 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
840 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.165
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Apr 8, 2025, 7:09 AM UTC
  • Emulated Desktop with Lighthouse 12.4.0
    Unthrottled CPU/Memory Power: 385 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.2
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: North America
  • Using HeadlessChromium 134.0.6998.165 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 5.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
3,059 ms
Other
815 ms
Style & Layout
792 ms
Garbage Collection
239 ms
Script Parsing & Compilation
181 ms
Parse HTML & CSS
168 ms
Rendering
81 ms
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
plattevalleyauto.com
1st party
2,875 ms
1,354 ms
44 ms
2,151 ms
1,017 ms
30 ms
389 ms
59 ms
3 ms
/pixall/pix-ddc-fp.min.js
(www.plattevalleyauto.com)
85 ms
80 ms
2 ms
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
81 ms
68 ms
1 ms
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
62 ms
38 ms
1 ms
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
54 ms
42 ms
6 ms
…tracking/bundle.553.2fc58e2….js
(www.plattevalleyauto.com)
53 ms
51 ms
1 ms
Google Tag Manager
tag-manager
1,166 ms
923 ms
67 ms
/gtag/js?id=…
(www.googletagmanager.com)
335 ms
174 ms
10 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
226 ms
193 ms
15 ms
/gtag/js?id=…
(www.googletagmanager.com)
169 ms
156 ms
11 ms
/gtag/js?id=…
(www.googletagmanager.com)
140 ms
131 ms
8 ms
/gtag/js?id=…
(www.googletagmanager.com)
113 ms
104 ms
9 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
98 ms
88 ms
9 ms
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
85 ms
79 ms
6 ms
Unattributable
359 ms
45 ms
0 ms
Unattributable
359 ms
45 ms
0 ms
New Relic
utility
95 ms
86 ms
3 ms
/nr-spa-1.286.0.min.js
(js-agent.newrelic.com)
95 ms
86 ms
3 ms
swipetospin.com
91 ms
83 ms
2 ms
91 ms
83 ms
2 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 580 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
tag-manager
1,195 KiB
582 ms
/gtag/js?id=…
(www.googletagmanager.com)
119 KiB
231 ms
/gtag/js?id=…
(www.googletagmanager.com)
147 KiB
113 ms
/gtag/js?id=…
(www.googletagmanager.com)
107 KiB
88 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
181 KiB
82 ms
/gtag/js?id=…
(www.googletagmanager.com)
122 KiB
60 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
102 KiB
7 ms
/gtag/js?id=AW-794…
(www.googletagmanager.com)
111 KiB
1 ms
/gtag/js?id=…
(www.googletagmanager.com)
111 KiB
0 ms
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
107 KiB
0 ms
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
87 KiB
0 ms
…5430/sw_iframe.html?origin=…
(www.googletagmanager.com)
2 KiB
0 ms
/td?id=…
(www.googletagmanager.com)
1 KiB
0 ms
mPulse
analytics
30 KiB
0 ms
29 KiB
0 ms
/api/config.json?key=…
(c.go-mpulse.net)
1 KiB
0 ms
0 KiB
0 ms
swipetospin.com
26 KiB
0 ms
26 KiB
0 ms
Dealer
hosting
473 KiB
0 ms
96 KiB
0 ms
82 KiB
0 ms
…1111/e315efe…x.jpg
(pictures.dealer.com)
63 KiB
0 ms
50 KiB
0 ms
49 KiB
0 ms
45 KiB
0 ms
39 KiB
0 ms
38 KiB
0 ms
8 KiB
0 ms
/phones?platform=DDC_PRIMARY_WEBSITE
(phone-swap-service-v2-prod.us-west-2.web.dealer.com)
2 KiB
0 ms
…adchoices/logo.svg
(images.dealer.com)
1 KiB
0 ms
New Relic
utility
34 KiB
0 ms
/nr-spa-1.286.0.min.js
(js-agent.newrelic.com)
33 KiB
0 ms
/1/NRBR-a735…?a=…
(bam.nr-data.net)
1 KiB
0 ms
…1/NRBR-a735…?a=…
(bam.nr-data.net)
0 KiB
0 ms
Cloudflare CDN
cdn
27 KiB
0 ms
…2.2.4/jquery.min.js
(cdnjs.cloudflare.com)
27 KiB
0 ms
Google Analytics
analytics
25 KiB
0 ms
/analytics.js
(www.google-analytics.com)
21 KiB
0 ms
/j/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
/g/collect?v=…
(www.google-analytics.com)
1 KiB
0 ms
impel.io
22 KiB
0 ms
12 KiB
0 ms
6 KiB
0 ms
2 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
BlueCava
ad
21 KiB
0 ms
/js/bc.js
(sync.graph.bluecava.com)
16 KiB
0 ms
/req.bci
(sync.graph.bluecava.com)
2 KiB
0 ms
/Scripts/BlueCava.Lib.js
(sync.graph.bluecava.com)
2 KiB
0 ms
1 KiB
0 ms
/init.bci
(sync.graph.bluecava.com)
1 KiB
0 ms
motominer.com
15 KiB
0 ms
15 KiB
0 ms
Google/Doubleclick Ads
ad
8 KiB
0 ms
…viewthrou…/794…?random=…
(googleads.g.doubleclick.net)
3 KiB
0 ms
…viewthrou…/109…?random=…
(googleads.g.doubleclick.net)
3 KiB
0 ms
…rul/794…?random=…
(td.doubleclick.net)
1 KiB
0 ms
…rul/109…?random=…
(td.doubleclick.net)
1 KiB
0 ms
1 KiB
0 ms
wehaacdn.com
8 KiB
0 ms
/web/vdpx.js
(autoevents.wehaacdn.com)
8 KiB
0 ms
Launch Darkly
utility
6 KiB
0 ms
…contexts/eyJraW5kI…
(app.launchdarkly.com)
3 KiB
0 ms
…goals/5a6a54d…
(app.launchdarkly.com)
2 KiB
0 ms
…diagnostic/5a6a54d…
(events.launchdarkly.com)
1 KiB
0 ms
…bulk/5a6a54d…
(events.launchdarkly.com)
1 KiB
0 ms
esm1.net
5 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/v2/iframe?u=…
(cs.esm1.net)
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/cookie
(pixall.esm1.net)
1 KiB
0 ms
0 KiB
0 ms
iviewanalytics.com
2 KiB
0 ms
1 KiB
0 ms
/scripts/analytics.min.js
(cdn.iviewanalytics.com)
1 KiB
0 ms
Pubmatic
ad
2 KiB
0 ms
/AdServer/Pug?vcode=…
(simage2.pubmatic.com)
1 KiB
0 ms
/AdServer/UCookieSetPug?oid=…
(image6.pubmatic.com)
1 KiB
0 ms
/AdServer/UCookieSetPug?oid=…
(image6.pubmatic.com)
1 KiB
0 ms
kbb.com
2 KiB
0 ms
/instant-cash-offer.js
(ddc.plugin.syndication.kbb.com)
2 KiB
0 ms
LiveRamp IdentityLink
analytics
1 KiB
0 ms
/1000.gif?memo=CNeUHBIkC…
(idsync.rlcdn.com)
1 KiB
0 ms
1 KiB
0 ms
Other Google APIs/SDKs
utility
1 KiB
0 ms
1 KiB
0 ms
1 KiB
0 ms
/ccm/collect?en=…
(www.google.com)
0 KiB
0 ms
Akamai
cdn
1 KiB
0 ms
/eum/results.txt
(66-249-84-228_s-23-32-75-29_ts-1744096160-clienttons-s.akamaihd.net)
0 KiB
0 ms
/eum/results.txt
(il4vjqixfecnaz7uzoqa-ps36dh-005c9fd10-clientnsv4-s.akamaihd.net)
0 KiB
0 ms
/eum/getdns.txt?c=ps36dhujm
(trial-eum-clienttons-s.akamaihd.net)
0 KiB
0 ms
/eum/getdns.txt?c=ps36dhujm
(trial-eum-clientnsv4-s.akamaihd.net)
0 KiB
0 ms
Facebook
social
1 KiB
0 ms
/tr/?id=…
(www.facebook.com)
0 KiB
0 ms
/tr/?id=…
(www.facebook.com)
0 KiB
0 ms
AppNexus
ad
1 KiB
0 ms
1 KiB
0 ms
Tremor Video
ad
0 KiB
0 ms
/sync?UIDC=KJopcZzRf…
(partners.tremorhub.com)
0 KiB
0 ms
alcmpn.com
0 KiB
0 ms
0 KiB
0 ms
fluencyinc.co
0 KiB
0 ms
/ftm-ddc.js
(ftm.fluencyinc.co)
0 KiB
0 ms
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLSCLS
Element
Layout shift score
Shop Any Location Any Type All Filters Search Shop Service Browse new models SU…
<div class="ddc-wrapper" style="padding-top: 221px;">
0.165
Home New Vehicle Search Pre-Owned Vehicles Search Sell Us Your Car Finance Tool…
<div class="header-nav-container ml-auto">
0.046
Dodge
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/d/dodge/white/117x80.png?r=1…" alt="Dodge" loading="eager">
Media element lacking an explicit size
Home New Vehicle Search Pre-Owned Vehicles Search Sell Us Your Car Finance Tool…
<div class="header-nav-container ml-auto">
0.005
Dodge
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/d/dodge/white/117x80.png?r=1…" alt="Dodge" loading="eager">
Media element lacking an explicit size
…v1/webfont.woff2
(www.plattevalleyauto.com)
Web font loaded
…v1/webfont.woff2
(www.plattevalleyauto.com)
Web font loaded
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
Web font loaded
…v1/webfont.woff2
(www.plattevalleyauto.com)
Web font loaded
Avoid an excessive DOM size 1,436 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
1,436
Maximum DOM Depth
Any Location
<span>
19
Maximum Child Elements
body
<body>
101
Reduce unused CSS Potential savings of 78 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Potential Savings
plattevalleyauto.com
1st party
69.6 KiB
66.1 KiB
…css/blue_white.css?r=174…
(www.plattevalleyauto.com)
69.6 KiB
66.1 KiB
impel.io
11.4 KiB
11.4 KiB
11.4 KiB
11.4 KiB
Eliminate render-blocking resources Potential savings of 80 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.LCPFCP
URL
Transfer Size
Potential Savings
plattevalleyauto.com
1st party
70.3 KiB
80 ms
…css/blue_white.css?r=174…
(www.plattevalleyauto.com)
70.3 KiB
80 ms
Does not have a <meta name="viewport"> tag with width or initial-scale
No `<meta name="viewport">` tag found
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
URL
Dealer
hosting
div.d-flex > div.cst_HEADER_SELF > a.btn > img
<img src="https://pictures.dealer.com/p/plattevalleyautone/1111/e315efe246a3ad0ce571…" alt="">
…1111/e315efe…x.jpg
(pictures.dealer.com)
Equinox
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox/SUV/perspect…" alt="Equinox" fetchpriority="high" style=" width: auto " aria-hidden="false">
Blazer EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer EV/SUV/perspe…" alt="Blazer EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
Blazer
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer/SUV/perspecti…" alt="Blazer" fetchpriority="high" style=" width: auto " aria-hidden="false">
Equinox EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox EV/SUV/persp…" alt="Equinox EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
Suburban
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Suburban/SUV/perspec…" alt="Suburban" fetchpriority="high" style=" width: auto " aria-hidden="false">
Serve images in next-gen formats Potential savings of 215 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.LCPFCP
URL
Resource Size
Potential Savings
Dealer
hosting
280.9 KiB
215.3 KiB
Equinox
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox/SUV/perspect…" alt="Equinox" fetchpriority="high" style=" width: auto " aria-hidden="false">
49.5 KiB
43.2 KiB
Equinox EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox EV/SUV/persp…" alt="Equinox EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
48.8 KiB
40.7 KiB
Blazer EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer EV/SUV/perspe…" alt="Blazer EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
44.2 KiB
37.7 KiB
Suburban
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Suburban/SUV/perspec…" alt="Suburban" fetchpriority="high" style=" width: auto " aria-hidden="false">
38.7 KiB
33.1 KiB
Blazer
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer/SUV/perspecti…" alt="Blazer" fetchpriority="high" style=" width: auto " aria-hidden="false">
37.4 KiB
31.5 KiB
div.d-flex > div.cst_HEADER_SELF > a.btn > img
<img src="https://pictures.dealer.com/p/plattevalleyautone/1111/e315efe246a3ad0ce571…" alt="">
…1111/e315efe…x.jpg
(pictures.dealer.com)
62.3 KiB
29.1 KiB
Enable text compression Potential savings of 15 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.LCPFCP
URL
Transfer Size
Potential Savings
motominer.com
14.8 KiB
10.2 KiB
14.8 KiB
10.2 KiB
wehaacdn.com
7.3 KiB
4.7 KiB
/web/vdpx.js
(autoevents.wehaacdn.com)
7.3 KiB
4.7 KiB
Serve static assets with an efficient cache policy 101 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
URL
Cache TTL
Transfer Size
plattevalleyauto.com
1st party
685 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
13m 7s
3 KiB
13m 8s
7 KiB
/pixall/pix-ddc-fp.min.js
(www.plattevalleyauto.com)
15m
28 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
4h 40m 31s
19 KiB
…1.10.2/lib.js
(www.plattevalleyauto.com)
13h 26m 56s
20 KiB
…1.10.2/loader.js
(www.plattevalleyauto.com)
13h 26m 56s
1 KiB
…v1/swipetospin.js
(www.plattevalleyauto.com)
13h 27m 22s
1 KiB
…dist/split-hero.min.js
(www.plattevalleyauto.com)
13h 53m 24s
3 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
1d 4h 56m 18s
17 KiB
…stylesheets/custom-fonts.css
(www.plattevalleyauto.com)
1d 11h 26m
1 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
1d 12h 39m 37s
17 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
1d 19h 35m 8s
19 KiB
…css/blue_white.css?r=174…
(www.plattevalleyauto.com)
14d
70 KiB
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
14d
49 KiB
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
14d
43 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
14d
35 KiB
…17.0.1/react-dom.production.min.js
(www.plattevalleyauto.com)
14d
34 KiB
14d
33 KiB
…dist/ddc.min.js?r=174…
(www.plattevalleyauto.com)
14d
18 KiB
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
14d
17 KiB
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
14d
17 KiB
…tracking/bundle.553.2fc58e2….js
(www.plattevalleyauto.com)
14d
16 KiB
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
14d
14 KiB
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
14d
13 KiB
…slick/slick.min.js?r=174…
(www.plattevalleyauto.com)
14d
10 KiB
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
14d
9 KiB
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
14d
9 KiB
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
14d
9 KiB
…css/blue_white-widgets.css?r=174…
(www.plattevalleyauto.com)
14d
8 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
8 KiB
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
14d
7 KiB
…navigation/bundle.e6da238….js
(www.plattevalleyauto.com)
14d
7 KiB
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
14d
7 KiB
…dist/phone-swapping.min.js?r=174…
(www.plattevalleyauto.com)
14d
6 KiB
…hours/bundle.808635c….js
(www.plattevalleyauto.com)
14d
5 KiB
…7.2.6/react-redux.min.js
(www.plattevalleyauto.com)
14d
5 KiB
14d
5 KiB
…17.0.1/react.production.min.js
(www.plattevalleyauto.com)
14d
5 KiB
14d
4 KiB
14d
4 KiB
…tagging/bundle.1689.138fdf6….js
(www.plattevalleyauto.com)
14d
4 KiB
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
14d
4 KiB
…ddc-logo/bundle.2c0d626….js
(www.plattevalleyauto.com)
14d
4 KiB
14d
4 KiB
…js/variation.min.js?r=174…
(www.plattevalleyauto.com)
14d
4 KiB
…tagging/bundle.869.beac321….js
(www.plattevalleyauto.com)
14d
3 KiB
…slick/ajax-loader.gif
(www.plattevalleyauto.com)
14d
3 KiB
…tagging/bundle.1115.ebd8118….js
(www.plattevalleyauto.com)
14d
3 KiB
…1.0.8/ddc-core-js-polyfills.min.js
(www.plattevalleyauto.com)
14d
3 KiB
…tagging/bundle.2587.ea409ea….js
(www.plattevalleyauto.com)
14d
3 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…overrides/type.css?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…tagging/bundle.9132.330a7f7….js
(www.plattevalleyauto.com)
14d
2 KiB
…4.1.1/redux.min.js
(www.plattevalleyauto.com)
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…v1/component.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
2 KiB
…v3.3.7/dropdown.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v1/userProfi….min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…0.3.0/umd.js
(www.plattevalleyauto.com)
14d
1 KiB
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…15.7.2/prop-types.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…new-relic/index.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v3.3.7/tab.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…specials/bundle.172.1b874c2….css
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v1/eo.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…dist/index.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…v1.0/jquery.inview.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget-tracking.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
14d
1 KiB
14d
1 KiB
…2.4.0/redux-thunk.min.js
(www.plattevalleyauto.com)
14d
1 KiB
…specials/bundle.172.23aff98….js
(www.plattevalleyauto.com)
14d
1 KiB
Dealer
hosting
72 KiB
…1111/e315efe…x.jpg
(pictures.dealer.com)
14d
63 KiB
14d
8 KiB
…adchoices/logo.svg
(images.dealer.com)
14d
1 KiB
mPulse
analytics
29 KiB
7d
29 KiB
swipetospin.com
26 KiB
10m
26 KiB
Google Analytics
analytics
21 KiB
/analytics.js
(www.google-analytics.com)
2h
21 KiB
impel.io
18 KiB
1m
1 KiB
7d
12 KiB
7d
6 KiB
wehaacdn.com
8 KiB
/web/vdpx.js
(autoevents.wehaacdn.com)
None
8 KiB
kbb.com
2 KiB
/instant-cash-offer.js
(ddc.plugin.syndication.kbb.com)
None
2 KiB
BlueCava
ad
2 KiB
/Scripts/BlueCava.Lib.js
(sync.graph.bluecava.com)
30d
2 KiB
Facebook
social
1 KiB
/tr/?id=…
(www.facebook.com)
None
0 KiB
/tr/?id=…
(www.facebook.com)
None
0 KiB
iviewanalytics.com
1 KiB
/scripts/analytics.min.js
(cdn.iviewanalytics.com)
None
1 KiB
Tremor Video
ad
0 KiB
/sync?UIDC=KJopcZzRf…
(partners.tremorhub.com)
None
0 KiB
alcmpn.com
0 KiB
None
0 KiB
esm1.net
0 KiB
None
0 KiB
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Source
plattevalleyauto.com
1st party
Properly size images Potential savings of 218 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.LCPFCP
URL
Resource Size
Potential Savings
Dealer
hosting
288.9 KiB
212.0 KiB
div.d-flex > div.cst_HEADER_SELF > a.btn > img
<img src="https://pictures.dealer.com/p/plattevalleyautone/1111/e315efe246a3ad0ce571…" alt="">
…1111/e315efe…x.jpg
(pictures.dealer.com)
62.3 KiB
61.5 KiB
Equinox
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox/SUV/perspect…" alt="Equinox" fetchpriority="high" style=" width: auto " aria-hidden="false">
49.5 KiB
32.7 KiB
Equinox EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Equinox EV/SUV/persp…" alt="Equinox EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
48.8 KiB
32.2 KiB
Blazer EV
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer EV/SUV/perspe…" alt="Blazer EV" fetchpriority="high" style=" width: auto " aria-hidden="false">
44.2 KiB
29.2 KiB
Suburban
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Suburban/SUV/perspec…" alt="Suburban" fetchpriority="high" style=" width: auto " aria-hidden="false">
38.7 KiB
25.7 KiB
Blazer
<img src="https://images.dealer.com/ddc/vehicles/2025/Chevrolet/Blazer/SUV/perspecti…" alt="Blazer" fetchpriority="high" style=" width: auto " aria-hidden="false">
37.4 KiB
24.7 KiB
Platte Valley Auto
<img width="32" height="45" src="https://pictures.dealer.com/p/plattevalleyautone/1646/5853a3ebe9d117252924…" alt="Platte Valley Auto" class="dealer-path-override-img" style="max-height:45px;width:auto;" loading="eager">
8.0 KiB
6.1 KiB
plattevalleyauto.com
1st party
7.2 KiB
6.4 KiB
Ford
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/f/ford/white/117x80.png?r=17…" alt="Ford">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
7.2 KiB
6.4 KiB
Defer offscreen images Potential savings of 14 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
URL
Resource Size
Potential Savings
plattevalleyauto.com
1st party
14.3 KiB
14.3 KiB
Ford
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/f/ford/white/117x80.png?r=17…" alt="Ford">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
7.2 KiB
7.2 KiB
Dealer.com
<img src="/static/assets/images/logos/dealer-dot-com/logo-one-color-white.svg" alt="Dealer.com" height="20" width="162">
7.1 KiB
7.1 KiB
Remove duplicate modules in JavaScript bundles Potential savings of 2 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. LCPFCP
Source
Transfer Size
Potential Savings
Other
0 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
…navigation/bundle.e6da238….js
(www.plattevalleyauto.com)
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
Avoid serving legacy JavaScript to modern browsers Potential savings of 17 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScriptLCPFCP
URL
Potential Savings
BlueCava
ad
9.8 KiB
/js/bc.js
(sync.graph.bluecava.com)
9.8 KiB
/js/bc.js:48:497
(sync.graph.bluecava.com)
Date.prototype.toJSON
/js/bc.js:54:42
(sync.graph.bluecava.com)
Date.now
plattevalleyauto.com
1st party
7.3 KiB
…dist/ddc.min.js?r=174…
(www.plattevalleyauto.com)
7.1 KiB
…dist/ddc.min.js?r=174…:1:14750
(www.plattevalleyauto.com)
Number.isInteger
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
0.1 KiB
@babel/plugin-transform-classes
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
0.1 KiB
../src/pubsub.js:2:1
@babel/plugin-transform-classes
…dist/phone-swapping.min.js?r=174…
(www.plattevalleyauto.com)
0.0 KiB
@babel/plugin-transform-classes
…dist/split-hero.min.js
(www.plattevalleyauto.com)
0.0 KiB
…dist/split-hero.min.js:1:83
(www.plattevalleyauto.com)
@babel/plugin-transform-classes
Reduce unused JavaScript Potential savings of 601 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
Google Tag Manager
tag-manager
1,181.1 KiB
545.7 KiB
/gtag/js?id=…
(www.googletagmanager.com)
109.5 KiB
82.9 KiB
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
105.8 KiB
82.5 KiB
/gtag/js?id=…
(www.googletagmanager.com)
145.7 KiB
58.6 KiB
/gtag/js?id=…
(www.googletagmanager.com)
120.9 KiB
52.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
117.5 KiB
48.2 KiB
/gtag/js?id=…
(www.googletagmanager.com)
105.9 KiB
48.0 KiB
/gtm.js?id=GTM-TSFC9FZ
(www.googletagmanager.com)
85.7 KiB
45.5 KiB
/gtag/js?id=AW-794…
(www.googletagmanager.com)
109.6 KiB
44.0 KiB
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
180.0 KiB
42.7 KiB
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
100.4 KiB
41.2 KiB
plattevalleyauto.com
1st party
83.1 KiB
55.7 KiB
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
48.5 KiB
35.6 KiB
…./node_modules/wsm-specials-display/dist/es.js
23.3 KiB
16.9 KiB
…./node_modules/react-to-print/lib/index.js
3.5 KiB
3.0 KiB
…./node_modules/wsm-incentive-modal/dist/es.js
3.3 KiB
1.9 KiB
…./src/templates/commonFragments.jsx
1.0 KiB
1.0 KiB
…./src/utilities/printViewOnChromeIos.js
0.9 KiB
0.9 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
34.6 KiB
20.1 KiB
Avoid enormous network payloads Total size was 2,897 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
Google Tag Manager
tag-manager
1,105.0 KiB
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
181.1 KiB
/gtag/js?id=…
(www.googletagmanager.com)
146.7 KiB
/gtag/js?id=…
(www.googletagmanager.com)
122.0 KiB
/gtag/js?id=…
(www.googletagmanager.com)
118.6 KiB
/gtag/js?id=AW-794…
(www.googletagmanager.com)
110.7 KiB
/gtag/js?id=…
(www.googletagmanager.com)
110.6 KiB
/gtag/js?id=…
(www.googletagmanager.com)
106.9 KiB
/gtag/js?id=G-GMCX6CHKK8
(www.googletagmanager.com)
106.9 KiB
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
101.5 KiB
plattevalleyauto.com
1st party
99.3 KiB
…inv-listing/bundle.c7d452d….js
(www.plattevalleyauto.com)
99.3 KiB
Avoid long main-thread tasks 17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Google Tag Manager
tag-manager
1,121 ms
/gtag/js?id=…
(www.googletagmanager.com)
3,396 ms
178 ms
/gtag/js?id=…
(www.googletagmanager.com)
2,610 ms
163 ms
/gtag/js?id=…
(www.googletagmanager.com)
3,624 ms
153 ms
/gtag/js?id=AW-794…
(www.googletagmanager.com)
3,950 ms
140 ms
/gtag/js?id=…
(www.googletagmanager.com)
4,598 ms
138 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
1,425 ms
131 ms
/gtag/js?id=…
(www.googletagmanager.com)
3,092 ms
110 ms
/gtm.js?id=GTM-4H673&l=dataLayer
(www.googletagmanager.com)
1,847 ms
57 ms
/gtm.js?id=GTM-NFTX3XB&l=dataLayer
(www.googletagmanager.com)
1,374 ms
51 ms
plattevalleyauto.com
1st party
750 ms
4,130 ms
285 ms
3,272 ms
124 ms
417 ms
93 ms
581 ms
73 ms
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
2,961 ms
63 ms
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
3,202 ms
59 ms
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
4,818 ms
53 ms
swipetospin.com
50 ms
4,506 ms
50 ms
User Timing marks and measures 8 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Name
Type
Start Time
Duration
ldSDK
Measure
985.55 ms
154.93 ms
ldSDKInit
Measure
1,140.57 ms
259.81 ms
ldSDKStart
Mark
985.55 ms
ldSDKEnd
Mark
1,140.48 ms
ldSDKInitStart
Mark
1,140.57 ms
ldSDKInitEnd
Mark
1,400.38 ms
basePageCacheStatus-HIT
Mark
3,532.40 ms
basePageCacheable-true
Mark
3,532.44 ms
Avoid non-composited animations 8 animated elements found
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Element
Name
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-1">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-4">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-6">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-3">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-8">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-5">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-2">
Unsupported CSS Property: background-color
loader
div.facet-browse-container > div.loading-container > div.data-loading > div.bar
<div class="bar bar-7">
Unsupported CSS Property: background-color
loader
Avoid chaining critical requests 42 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.
Maximum critical path latency: 3,097.67 ms
Initial Navigation
- 46.539 ms, 32.87 KiB
…dist/ddc.min.js?r=174…
(www.plattevalleyauto.com)
- 146.602 ms, 18.48 KiB
…1.0.8/ddc-core-js-polyfills.min.js
(www.plattevalleyauto.com)
- 39.344 ms, 2.70 KiB
…17.0.1/react.production.min.js
(www.plattevalleyauto.com)
- 117.578 ms, 4.52 KiB
…17.0.1/react-dom.production.min.js
(www.plattevalleyauto.com)
- 31.706 ms, 34.31 KiB
…15.7.2/prop-types.min.js
(www.plattevalleyauto.com)
- 41.716 ms, 1.28 KiB
…0.33.1/react-bootstrap.min.js
(www.plattevalleyauto.com)
- 35.545 ms, 35.28 KiB
…4.1.1/redux.min.js
(www.plattevalleyauto.com)
- 22.352 ms, 2.02 KiB
…7.2.6/react-redux.min.js
(www.plattevalleyauto.com)
- 30.218 ms, 5.38 KiB
…css/blue_white.css?r=174…
(www.plattevalleyauto.com)
…merged/font.ebfac27….woff2
(www.plattevalleyauto.com)
- 107.415 ms, 42.90 KiB
…2.4.0/redux-thunk.min.js
(www.plattevalleyauto.com)
- 117.336 ms, 0.78 KiB
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
- 22.846 ms, 12.96 KiB
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
- 30.679 ms, 8.94 KiB
…0.3.0/umd.js
(www.plattevalleyauto.com)
- 39.405 ms, 1.38 KiB
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
- 102.494 ms, 3.81 KiB
…1.10.2/loader.js
(www.plattevalleyauto.com)
- 26.465 ms, 0.87 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 23.432 ms, 1.75 KiB
- 32.225 ms, 4.09 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 38.879 ms, 1.39 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 27.772 ms, 1.91 KiB
…overrides/type.css?r=174…
(www.plattevalleyauto.com)
- 75.271 ms, 2.29 KiB
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
- 24.645 ms, 1.38 KiB
…v1/userProfi….min.js?r=174…
(www.plattevalleyauto.com)
- 34.371 ms, 1.42 KiB
…dist/split-hero.min.js
(www.plattevalleyauto.com)
- 24.418 ms, 3.05 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 95.335 ms, 1.12 KiB
…v1.0/jquery.inview.min.js?r=174…
(www.plattevalleyauto.com)
- 48.379 ms, 0.92 KiB
…css/blue_white-widgets.css?r=174…
(www.plattevalleyauto.com)
- 44.783 ms, 8.14 KiB
…v3.3.7/tab.min.js?r=174…
(www.plattevalleyauto.com)
- 38.326 ms, 1.27 KiB
…slick/slick.min.js?r=174…
(www.plattevalleyauto.com)
- 42.069 ms, 10.12 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 39.328 ms, 2.30 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 130.553 ms, 0.87 KiB
…stylesheets/custom-fonts.css
(www.plattevalleyauto.com)
- 101.608 ms, 0.89 KiB
…dist/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 51.697 ms, 2.14 KiB
…js/widget.min.js?r=174…
(www.plattevalleyauto.com)
- 46.71 ms, 1.53 KiB
…v3.3.7/dropdown.min.js?r=174…
(www.plattevalleyauto.com)
- 47.342 ms, 1.42 KiB
…js/variation.min.js?r=174…
(www.plattevalleyauto.com)
- 87.166 ms, 3.64 KiB
- 221.588 ms, 0.79 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 26.218 ms, 18.59 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 30.198 ms, 19.29 KiB
…1.0.0/es.js
(www.plattevalleyauto.com)
- 141.813 ms, 3.16 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 41.835 ms, 16.57 KiB
…v1/webfont.woff2
(www.plattevalleyauto.com)
- 37.966 ms, 17.06 KiB
Largest Contentful Paint element 1,040 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
div.bg-black > div.col-xs-12 > div.page-section > div.page-section
<div data-width-multiplier="1" data-responsive-image-group="true" style="background-repeat: no-repeat; background-size: cover; background-image: url(&quot;…&quot;);" class="page-section no-gutter-spacing js-hero-expand-background transition-proper…" data-name="index-landing-0011-hero-shop-background-1">
Phase
% of LCP
Timing
TTFB
15%
160 ms
Load Delay
11%
110 ms
Load Time
2%
20 ms
Render Delay
72%
750 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (12)
Show Hide
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.LCPFCP
Preconnect to required origins
Warnings: More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the most important origins.
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.LCPFCP
Initial server response time was short Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.LCPFCP
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
plattevalleyauto.com
1st party
40 ms
40 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.LCPFCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCPFCP
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Element
div.bg-black > div.col-xs-12 > div.page-section > div.page-section
<div data-width-multiplier="1" data-responsive-image-group="true" style="background-repeat: no-repeat; background-size: cover; background-image: url(&quot;…&quot;);" class="page-section no-gutter-spacing js-hero-expand-background transition-proper…" data-name="index-landing-0011-hero-shop-background-1">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
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.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Home
<a href="/" class="homeLink h-auto py-3 px-0 mx-3 ddc-font-size-small currentPage" target="_self" data-navigation-id="default">
div.no-gutter-spacing > div.d-flex > div.cst_HEADER_SELF > a.btn
<a class="btn btn-primary cstBtn ui-button btn-no-decoration" href="https://www.heartlandchevybuick.com/" target="_self" style="z-index: 950; background: none;">
New Vehicle Search
<a data-inactive="true" data-toggle="dropdown" aria-expanded="false" href="#" class="nav-with-children h-auto py-3 px-0 mx-3 ddc-font-size-small" data-navigation-id="default">
div.no-gutter-spacing > div.d-flex > div.cst_HEADER_SELF > a.btn
<a class="btn btn-primary cstBtn ui-button btn-no-decoration" href="https://www.heartlandchevybuick.com/" target="_self" style="z-index: 950; background: none;">
These items highlight common accessibility best practices.
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Failing Elements
Shop
<h3 class="display-1 spacing-reset widget-heading opacity-0" tabindex="-1">
These are opportunities to improve keyboard navigation in your application.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (25)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (29)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
plattevalleyauto.com
1st party
Unload event listeners are deprecated and will be removed.
Uses third-party cookies 1 cookie found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
Name
URL
BlueCava
ad
ssx
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
impel.io
Failed to load resource: the server responded with a status of 403 (Forbidden)
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
Cookie
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
Bootstrap
3.3.7
jQuery
1.7.2
jQuery UI
1.8.6
React
17.0.1
Underscore
1.4.4
boomerang.js
1.737.20
core-js
core-js-pure@2.5.7
Trust and Safety
Requests the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Source
plattevalleyauto.com
1st party
webpack://ws-facet-browse/./src/components/buttons/SearchButton.jsx:40:27
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
`script-src` directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing `object-src` allows the injection of plugins that execute unsafe scripts. Consider setting `object-src` to `'none'` if you can.
object-src
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
`max-age` is too low
max-age
High
No `includeSubDomains` directive found
includeSubDomains
Medium
No `preload` directive found
preload
Medium
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
URL
Aspect Ratio (Displayed)
Aspect Ratio (Actual)
plattevalleyauto.com
1st party
Dodge
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/d/dodge/white/117x80.png?r=1…" alt="Dodge" loading="eager">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Jeep
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/j/jeep/white/117x80.png?r=17…" alt="Jeep">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Ford
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/f/ford/white/117x80.png?r=17…" alt="Ford">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Chrysler
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/c/chrysler/white/117x80.png?…" alt="Chrysler">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Ram
<img width="32" height="32" style="width: auto;height: auto;" src="/static/v8/global/images/franchise-logos/auto/r/ram/white/117x80.png?r=174…" alt="Ram">
…white/117x80.png?r=174…
(www.plattevalleyauto.com)
32 x 32 (1.00)
117 x 80 (1.46)
Does not have a <meta name="viewport"> tag with width or initial-scale
No `<meta name="viewport">` tag found
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Passed audits (7)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
plattevalleyauto.com
1st party
…1.9.7/redux-toolkit.umd.min.js
(www.plattevalleyauto.com)
…1.9.7/redux-toolkit.umd.min.js.map
(www.plattevalleyauto.com)
SyntaxError: Unexpected token 'N', "Not found
" is not valid JSON
…tracking/bundle.aa5eefd….js
(www.plattevalleyauto.com)
…tracking/bundle.aa5eefd….js.map
(www.plattevalleyauto.com)
…tracking/bundle.553.2fc58e2….js
(www.plattevalleyauto.com)
…tagging/bundle.9132.330a7f7….js
(www.plattevalleyauto.com)
…tagging/bundle.869.beac321….js
(www.plattevalleyauto.com)
…tagging/bundle.869.beac321….js.map
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js
(www.plattevalleyauto.com)
…tagging/bundle.4aa4280….js.map
(www.plattevalleyauto.com)
…tagging/bundle.4674.efc9941….js
(www.plattevalleyauto.com)
…tagging/bundle.2587.ea409ea….js
(www.plattevalleyauto.com)
…tagging/bundle.1689.138fdf6….js
(www.plattevalleyauto.com)
…tagging/bundle.1115.ebd8118….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js
(www.plattevalleyauto.com)
…specials/bundle.ae5e8ce….js.map
(www.plattevalleyauto.com)
…navigation/bundle.e6da238….js
(www.plattevalleyauto.com)
…navigation/bundle.e6da238….js.map
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js
(www.plattevalleyauto.com)
…mycars-nav/bundle.6b005f9….js.map
(www.plattevalleyauto.com)
…hours/bundle.808635c….js
(www.plattevalleyauto.com)
…hours/bundle.808635c….js.map
(www.plattevalleyauto.com)
…facet-browse/bundle.421e099….js
(www.plattevalleyauto.com)
…ddc-logo/bundle.2c0d626….js
(www.plattevalleyauto.com)
…ddc-logo/bundle.2c0d626….js.map
(www.plattevalleyauto.com)
…content-cta/bundle.4ce609b….js
(www.plattevalleyauto.com)
…content-cta/bundle.4ce609b….js.map
(www.plattevalleyauto.com)
…0.3.0/umd.js
(www.plattevalleyauto.com)
…0.3.0/umd.js.map
(www.plattevalleyauto.com)
…1.1.0/pubsub.min.js
(www.plattevalleyauto.com)
…1.1.0/pubsub.min.js.map
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js
(www.plattevalleyauto.com)
…3.1.4/ldclient.min.js.map
(www.plattevalleyauto.com)
…3.0.4/hysterics.js
(www.plattevalleyauto.com)
…3.0.4/hysterics.js.map
(www.plattevalleyauto.com)
…1.4.0/html-react-parser.min.js
(www.plattevalleyauto.com)
…1.4.0/html-react-parser.min.js.map
(www.plattevalleyauto.com)
…1.0.0/es.js
(www.plattevalleyauto.com)
…1.0.0/es.js.map
(www.plattevalleyauto.com)
…1.10.2/loader.js
(www.plattevalleyauto.com)
…1.10.2/loader.js.map
(www.plattevalleyauto.com)
…1.10.2/lib.js
(www.plattevalleyauto.com)
…1.10.2/lib.js.map
(www.plattevalleyauto.com)
Not applicable (3)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (10)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.