The tools a typical dealer page carries
| Tool | Who asked for it | What it adds to the page |
|---|---|---|
| Chat and texting | Sales | A widget that starts on every page |
| Trade-in and payment tools | Used cars, finance | Forms and calculators, often with their own code |
| Reviews | Marketing | A widget that fetches and shows ratings |
| Analytics | Marketing, agencies | Code that records visits and events |
| Ad pixels | Each ad platform and agency | One piece of code per platform |
| Manufacturer programs | The brand | Required tracking or content |
How they slow a page down
A phone runs a page's code one piece at a time. While a chat widget or a tag starts up, the phone can't draw the vehicle photo or answer a tap. Each tool also means another download, often from another company's server.
No single vendor sees the problem. Each tests its own tool on its own and finds it light. The shopper's phone gets all of them at once.
Does Google Tag Manager slow down a site?
The tag manager itself is small. What it loads is the cost: every tag inside it runs on the page. A container that has collected tags from several agencies over the years can be the heaviest thing on a dealer site. Google's own guidance is to remove tags nobody uses and to load the rest when they are needed.
How to find which scripts cost the most
- 1
Run a vehicle page through PageSpeed Insights
Use the mobile result. Open the Diagnostics section.
- 2
Find the third-party list
The report lists each outside company's code with how long it kept the page busy.
- 3
Match each one to a tool
Note who asked for it and whether it's still in use. Old pixels from past agencies are common.
Keep the tools, change the order
Removing tools is rarely the answer; sales still needs chat and marketing still needs tracking. What helps is when they load. With Site Speed Engine, every script stays on the site and loads after the vehicle and price, so chat and tracking keep working and shoppers see the car sooner. More on why dealer websites are slow.